Components of IraVoice web monitor



Web-monitor :


  1. Campaigns/logical gateways: It allows to club multiple SIP trunks together into logical entities and use that for sending calls out. It is used to send calls with trunk redundancy and also allows to limit the usage of trunks.

  2. Queue: This column has the number of contacts yet to be dialled or in the waiting for the trunks to be freed.
     

  3. Limit : Limit on the dashboard is the max concurrent calls that campaign can have ,provided there are enough telephony trunks available.When you have multiple campaigns running, the sum of all the limits of active campaigns should not exceed the total channels available for the trunks in each campaign.This might use all the available channels and not leave much for other campaigns.

  4. Scheduled (SCHD): The router will schedule the calls from the queue when there is an availability of trunks .This column will show the count of scheduled calls.

  5. Used (USED) : This column shows the count of the calls being dialled/ringing, or answered; it will show the count of both .

  6. Answered(ANSD) stream (STRM) : these columns have the count of ongoing answered calls and the audio streams (web socket streams with bot). Count of answered calls  & streams should not be a large difference between these counts. If the difference is more, check the botstream log from botstream server for any errors.

  7. TRNST is the average transit time. That is, the time it takes for the data to be moved from websocket server to botstream, this will help us to detect if there is any congestion or problems while sending data.

  8. WRT is the average write time, that is, the amount of time it takes for data to be written completely into the socket on the websocket server.

  9. BDL: The BDL (average bot delay) is the average time taken by the bot to respond. Customers who use VAD will see the average time taken by all the bot responses throughout the call within 30 seconds, and if it's non-VAD, then it is the average time taken for the first audio response. These values are in milliseconds.


  10. Web errors(WERR)  :When there is an error from the web socket server, this column will show the call count that has had web errors for the last 30 seconds.
    Types of web-errors:
    Hover over the web error column to see the types:
    a. Resolve errors : Number of calls with a delay in resolving the DNS of WebSocket server .
    b. Connect errors: Number of calls which are unable to establish a connection to a  web socket server .
    c. SSL errors: Number of calls with a delay in SSL handshake .
    d. WSS errors: Number of calls with a delay in Web Socket handshake .
    Note :

  1.  Resolve errors can  be solved by adding the web socket DNS with its corresponding ip-address into the server host file .

  2. For Connect errors, check from botstream whether the web socket DNS or server is accessible.If required,make firewall changes on the websocket host as well as on botstream servers.

  3. And the SSL and WSS errors need to be taken care of by the client.

11. Bot errors (BERR): For VAD mode bot errors, they are marked for all the bot audio that was received beyond the threshold for the last 30 seconds. For non-VAD bot errors, they are marked only if the first audio is beyond threshold for the last 30 seconds.