1.Description
Progressive dialing report page. Designed to view information on the progressive dialing of subscribers (Fig. 1).
Consists of:
- Drop-down list with multiple choice "Queues"
- "Operators" table
- "Active calls" table
- Queue calls
- Block "Hangup cause"
- "Information" table
Displaying information in progressive dialing
1.1. Drop-down list with multiple choice "Queues"
Designed to select queues for which information needs to be viewed
1.2 "Operators" table
Displays general information on calls for each operator. When you click on the operator's name, it redirects to the "Operator" dashboard, where extensive information on a particular operator is displayed.
Consists of columns:
- Operator - operator's name;
- Status - the operator's status at the moment. There are such statuses: online (1, colored green) - active; offline (2, colored red) - inactive; break (3, colored yellow) - during a break; break out (4, colored black) - forced transfer to offline mode;
- In the queue - how much is left to call the subscribers assigned to this operator;
- Completed (Successful) - the number of subscribers with whom the operator was connected;
- Completed (Unsuccessful) - the number of subscribers who could not get through for several dialing attempts. The number of dialing attempts is indicated on the details page "Dialing subscribers settings" of this queue;
- Subscriber did not answer - the number of dialing attempts that were not answered by subscribers;
- Subscriber answered - the number of dialing attempts that were accepted by the subscriber;
- Connected to operator - the number of dialing attempts that were accepted by the subscriber and connected to the operator;
- Missed - the number of calls when they got through to the subscriber, but did not connect with the operator;
- ANT - the average hour of call processing by the operator. Talk time + post-processing is taken into account;
- ASA of the operator - the average time of connection with the operator;
- ASA of the subscriber - the average call time to the subscriber;
- Load - the percentage of the number of subscribers for a given operator to the total number of all subscribers for calling. It is calculated by the formula: (the number of subscribers "in the queue" of the given operator / the number of all subscribers "in the queue") * 100%.
1.3. "Active calls" table
Displays information about calls that are currently being processed.
Consists of columns:
Time - the time the dialer started the call;
Number - subscriber's number;
Status - Displays the status of a specific active call. There are three states: waiting - waiting for a connection with a subscriber, offering - connected with a subscriber, connecting with an operator, bridged - a call connected with an operator:
Answered - time of connection with the subscriber;
Operator - the name of the operator with whom you connected;
Operator in conversation - the time from the connection with the operator to the present moment;
Duration - the time from the start of the dialing attempt to this moment;
Resource is the gateway that is being used.
1.4. Queue calls
Displays the number of calls by queue in a certain period of time. Constant updates in real time.
1.5. Block "Hangup cause"
Consists of:
- Pie chart;
- List of reasons.
The pie chart displays the percentage of completed calls for the selected reasons.
When you hover the cursor over a sector of the pie chart, it displays the reason and the number of completed calls for this reason.
The list of reasons displays only those reasons that took place during the period under consideration. For a list of possible causes, see Table 1.
The list of reasons includes:
- the color in which the given reason is displayed on the diagram;
- the name of the reason;
- SIP response.
When you move the cursor over the name of a reason in the list, only the sector that displays information for this reason is highlighted in the pie chart. When you click on the name of the reason in the list, it becomes inactive (gray). Information for inactive reasons is not displayed on the chart.
| SIP response | Cause | Description |
|---|---|---|
| UNSPECIFIED | Issued by the router when none of the other codes match. This cause usually occurs in situations of the same type as Cause 1, Cause 88, and Cause 100 | |
| 404 | UNALLOCATED_NUMBER | This cause indicates that the called party could not be reached because although the called party's number is in a valid format, it is not currently assigned (assigned). |
| 404 | NO_ROUTE_TRANSIT_NET | This cause indicates that the equipment sending this cause has received a request to route the call through a specific transit network that it does not recognize. The equipment sending this cause does not recognize the transit network, either because the transit network does not exist or because this particular transit network, although it exists, does not service the equipment that sends this cause. |
| 404 | NO_ROUTE_DESTINATION | This cause indicates that the called party could not be reached because the network through which the call was routed does not serve the desired destination. This reason is supported depending on the network. |
| CHANNEL_UNACCEPTABLE | This cause indicates that the last channel identified is not acceptable for the sending entity to use in this call. | |
| CALL_AWARDED_DELIVERED | The user was presented with an incoming call, and that the incoming call connects to a channel already set up for that user for similar calls (for example, burst mode x.25 virtual calls). | |
| NORMAL_CLEARING | Normal call termination | |
| 486 | USER_BUSY | The called party cannot accept another call because the user is busy. This reason value can be generated by the called user or the network. In the case where the user is determined to be busy, it is noted that the user equipment is compatible with the call. |
| 408 | NO_USER_RESPONSE | The called party does not respond to the call setup message with either a warning or a connection indication for the prescribed allotted time period. |
| 480 | NO_ANSWER | This cause is used when the called party has been alerted but does not respond with a call indication within the prescribed time period. Note. This cause is not necessarily generated by Q.931 procedures, but may be generated by internal network timers. |
| 480 | SUBSCRIBER_ABSENT | This reason value is used when the mobile station is logged out, radio communication with the mobile station is not established, or if the personal telecommunication user temporarily does not have an address in any user network interface. |
| 603 | CALL_REJECTED | This cause indicates that the equipment sending this cause does not want to receive the call, although it could have received the call because the equipment sending this cause is not busy or is incompatible. The network can also generate this cause, indicating that the call was dropped due to a supplementary service restriction. The diagnostic field can contain additional information about the additional service and the reason for the refusal. |
| 410 | NUMBER_CHANGED | This reason is returned to the calling party when the called party number specified by the calling party is no longer assigned. The new called party number can optionally be included in the diagnostic field. If the network does not support this reason, reason #: 1, an unassigned (unassigned) number must be used. |
| 410 | REDIRECTION_TO_NEW_DESTINATION | This reason is used by the general ISUP mechanism, which can be triggered by a switch deciding that a call should be placed on a different called number. Such an exchange can trigger a redirection mechanism using this reason value to request a previous exchange involved in the call to route the call to a new number. |
| 483 | EXCHANGE_ROUTING_ERROR | This cause indicates that the user-specified destination could not be reached because the intermediate switch disconnected the call due to a hop count limit being reached. This cause is generated by the intermediate node, which returns 0 when the hop count is decreased. |
| 502 | DESTINATION_OUT_OF_ORDER | This cause indicates that the user-specified destination could not be reached because the destination interface is not working properly. The term "not working correctly" indicates that the signaling message could not be delivered to the remote side; for example, a failure of the physical layer or the data link layer on the remote side or disconnected user equipment. |
| 484 | INVALID_NUMBER_FORMAT | This cause indicates that the called party could not be reached because the called party's number is invalid or incomplete. |
| 501 | FACILITY_REJECTED | This reason is returned when the additional service requested by the user cannot be provided by the network. |
| RESPONSE_TO_STATUS_ENQUIRY | This cause is included in the STATUS message when the STATUS message was generated because the STATUS INQUIRY was previously received. | |
| 480 | NORMAL_UNSPECIFIED | This reason is used to report a normal event only when no other reason in the normal class applies. |
| 503 | NORMAL_CIRCUIT_CONGESTION | This cause indicates that there is currently no suitable circuit / channel to handle the call. |
| 503 | NETWORK_OUT_OF_ORDER | This cause indicates that the network is not working as expected and that the condition is likely to last for a relatively long period of time, for example, an immediate call retry is unlikely to be successful. |
| 503 | NORMAL_TEMPORARY_FAILURE | This reason indicates that the network is not working properly and that this condition is unlikely to last for a long period of time; for example, the user might want to try another call attempt almost immediately. |
| 503 | SWITCH_CONGESTION | This cause indicates that the switching equipment generating this cause is experiencing a period of high traffic. |
| ACCESS_INFO_DISCARDED | This cause indicates that the network was unable to deliver to the remote user the access information as requested, that is, user-to-user information, low-level compatibility, high-level compatibility, or sub-address as indicated in the diagnostics. | |
| 503 | REQUESTED_CHAN_UNAVAIL | This reason is returned when the other side of the interface cannot provide the schema or channel specified by the requesting entity. |
| FACILITY_NOT_SUBSCRIBED | This reason indicates that the user has requested an additional service that is available, but the user is not authorized to use it. | |
| 403 | OUTGOING_CALL_BARRED | This cause indicates that although the calling party is an outgoing CUG subscriber, outgoing calls are not allowed for that CUG subscriber. |
| 403 | INCOMING_CALL_BARRED | This cause indicates that although the called party is a CUG subscriber for an incoming CUG call, incoming calls are not allowed for that CUG subscriber. |
| 403 | BEARERCAPABILITY_NOTAUTH | This cause indicates that the user has requested a portability that is being implemented by the hardware that generated the cause, but the user is not authorized to use it. |
| 503 | BEARERCAPABILITY_NOTAVAIL | This cause indicates that the user has requested a portability that is being implemented by the hardware that generated the cause, but is not currently available. |
| SERVICE_UNAVAILABLE | This cause is used to report a service or parameter unavailable event only when no other reason in the service class or parameter unavailable applies. | |
| 488 | BEARERCAPABILITY_NOTIMPL | This cause indicates that the equipment sending this cause does not support the requested portability. |
| CHAN_NOT_IMPLEMENTED | This cause indicates that the equipment sending this cause does not support the requested channel type. | |
| 501 | FACILITY_NOT_IMPLEMENTED | This cause indicates that the equipment sending this cause does not support the requested additional services. |
| 501 | SERVICE_NOT_IMPLEMENTED | This cause is used to report an unimplemented service or parameter event only when no other reason in the unimplemented service or parameter class applies. |
| INVALID_CALL_REFERENCE | This cause indicates that the equipment sending this cause received a message with a call reference that is not currently being used in the user-network interface. | |
| 488 | INCOMPATIBLE_DESTINATION | This cause indicates that the equipment sending this cause has received a call setup request that has low level compatibility, high level compatibility, or other compatibility attributes (eg, data rate) that cannot be met. |
| INVALID_MSG_UNSPECIFIED | This reason is used to report an invalid message event only if no other reason in the invalid message class applies. | |
| MANDATORY_IE_MISSING | This cause indicates that the equipment sending this cause received a message that is missing an information element that must be present in the message before the message can be processed. | |
| MESSAGE_TYPE_NONEXIST | This cause indicates that the equipment sending this cause received a message with a message type that it does not recognize because the message is undefined or is defined but not implemented by the equipment sending this cause. | |
| WRONG_MESSAGE | This cause indicates that the equipment sending this cause received a message such that the procedures do not indicate that it is a valid message to receive in a call state, or that a STATUS message was received indicating an inconsistent call state. | |
| IE_NONEXIST | This cause indicates that the equipment sending this cause received a message that includes unrecognized information element (s) / parameter (s) because the information element (s) / parameter name (s) are undefined or defined, but the hardware sending the reason is not implemented. This cause indicates that the information element (s) / parameter (s) have been discarded. However, the information element does not need to be present in the message for the equipment sending the cause to be able to process the message. | |
| INVALID_IE_CONTENTS | This cause indicates that the equipment sending this cause received an information item that it implemented; however, one or more fields in I.E. are coded in a way that was not implemented by the hardware sending this cause. | |
| WRONG_CALL_STATE | This cause indicates that a message was received that is incompatible with the call state. | |
| 504 | RECOVERY_ON_TIMER_EXPIRE | This cause indicates that the procedure was initiated by the expiration of a timer associated with error procedures. This is often associated with NAT issues. Make sure "NAT Mapping Enable" is enabled in your ATA. If it is not NAT related, sometimes it can be ISP related, make sure another outgoing ISP is not fixing the problem. |
| MANDATORY_IE_LENGTH_ERROR | This cause indicates that the equipment sending this cause received a message that includes parameters that are not recognized because the parameters are not defined or are not implemented by the equipment sending this cause. The reason indicates that the parameters were ignored. In addition, if the equipment sending this cause is an intermediate point, then this cause indicates that the parameter (s) were sent unchanged. | |
| PROTOCOL_ERROR | This cause is used to report a protocol error event only when no other reason in the protocol error class applies. | |
| INTERWORKING | This cause indicates that the interworking call (usually a SW56 service call) has ended. | |
| MANAGER_REQUEST | This reason is used when you send the api command to make it complete the call. | |
| PICKED_OFF | This reason means that the call was picked up from a different extension. | |
| USER_NOT_REGISTERED | This means that you tried to call a SIP user who was not registered. | |
| GATEWAY_DOWN | Gateway not working (not responding to OPTIONS or SUBSCRIBE) | |
| ABANDONED | This means that the call was canceled by the dialer. | |
| ORIGINATOR_CANCEL | The one who started the call (operator or customer) stopped it before the answer was received (Answer) |
List of possible reasons for the end of the call
1.6. "Information" table
This table displays information about the number of subscribers in queues and the progress of their calls.
Consists of:
- Queue - the name of the call queue
- In work - the number of subscribers in work
- Pending - the number of subscribers that is pending
- Total - the total number of subscribers added to the call queue for the entire time
- Progress is a scale that displays the percentage of processed subscribers to the total number of subscribers in this queue. From 0% to 60% colors in red, from 60% to 80% in orange, from 80% to 100% in green.
Add Comment