Skip to end of metadata
Go to start of metadata

The SIP SG Counters reflect the SIP messages sent/received at the Signalling group level. They are modeled based on the SIP RFC 3261. The request messages and its responses are incremented on send/receive directions. These counters are used mainly to troubleshoot issues and isolate failures.


SIP Counters

Request Message Counters

SIP requests or methods are considered "verbs" in the protocol, since they request a specific action to be taken by another user agent or server. The INVITE, REGISTER, BYE, ACK, CANCEL, and OPTIONS methods are the original six methods in SIP. The REFER, SUBSCRIBE, NOTIFY, MESSAGE, UPDATE, INFO, and PRACK methods are described in separate RFCs. The call-flow counters in general give a broader view of the system to help identify high-level trends or see a systematic problem.

Response Message Counters

There are six classes of SIP responses. The first five classes were borrowed from HTTP, the sixth was created for SIP.

  • 1xx: Informational, Indicates status of call prior to completion. If first informational or provisional response.
  • 2xx: Success, Request has succeeded. If for an INVITE, ACK should be sent; otherwise, stop retransmissions of request.
  • 3xx: Redirection, Server has returned possible locations. The client should retry request at another server.
  • 4xx: Client error, The request has failed due to an error by the client. The client may retry the request if reformulated according to response.
  • 5xx: Server failure, The request has failed due to an error by the server. The request may be retried at another server.
  • 6xx: Global failure, The request has failed. The request should not be tried again at this or other servers.

For more information see RFC 3261.

A SIP response is a message generated by a UAS or a SIP server to reply to a request generated by a UAC. A response may contain additional header fields containing information needed by the UAC. Or, it may be a simple acknowledgment to prevent retransmissions of the request by the UAC. Many responses direct the UAC to take specific additional steps.

Responses counters can be helpful as a tool for developers and service engineers to identify high-level service affecting trends. It gives a broader view of the system in terms of call-flow specifics.

Transaction Counters

SIP transactions occur between a UAC and a UAS. A SIP transaction comprises all messages from the first request sent from the UAC to the UAS up to a final response (non-1xx) sent from the UAS to the UAC.

Transaction counters can be helpful as a tool for developers and service engineers to identify high-level service affecting trends. It gives a broader view of the system in terms of call-flow specifics.

Call Counters

  • Current Calls: Number of con-concurrent calls, both Inbound and Outbound, incremented on the start of Client/Server CallSession transactions.
  • Total Calls: Total Number of completed and attempted calls. Incremented on the start of Client/Server CallSession transaction.;
  • Connected Calls: Number of Accepted calls, usually incremented by receiving 200OK Response message.
  • Refused Calls: Number of calls that were not accepted by the SBC, incremented on receiving Response codes greater than 400 and CCNak.
  • Errored Calls: Number of calls that resulted in an error, incremented on unexpected conditions that result in the call state to change to CallStateTerminated.
  • Blocked Calls: This has not been defined yet.
  • Egress Call Attempts: Number of outbound call attempts, incremented on start of Client transaction by UAC on the SBC.
  • Egress Calls Accepted: Number of outbound calls accepted, incremented on 200OK from UAS.
  • Egress Calls Completed: Number of outbound calls completed, incremented on transaction state change to completed.
  • Egress Calls Rejected: Number of outbound calls that were not accepted by the SBC, incremented on receiving Response codes greater than 400 and CCNak.
  • Ingress Call Attempts: Number of inbound calls accepted, incremented on start of Server transaction by UAS on the SBC.
  • Ingress Calls Accepted: Number of inbound calls accepted, incremented on 200OK from UAC.
  • Ingress Calls Completed: Number of inbound calls completed, incremented on transaction state change to completed.
  • IngressCalls Rejected: Number of inbound calls that were not accepted by the SBC, incremented on receiving Response codes greater than 400 and CCNak.

QOE Counters

  • Successful QoE Reports Sent: Total number of QoE Reports sent that were successfully received by the QoE Monitoring Agent.
  • Failed QoE Reports Sent: Total Number of QoE Reports sent that failed to be received by the QoE Monitoring Agent.

Busy Hour Call Counters

  • Busy Hour Call Attempted. Number of busy hour calls attempted by the SBC at the 60-minute period during which occurs the maximum total traffic load in a given 24-hour period.
  • Busy Hour Calls Completed. Number of busy hour calls completed by the SBC at the 60-minute period during which occurs the maximum total traffic load in a given 24-hour period.

Channel Detail Information Pages

The SBC provides a fine level of granularity of port/channel information, with nested dialogs.

Click Channels, and then click through the Channel Table, Detailed Call information, and Outbound Channel Details pages.

Detailed Call Information

This page provides you with a detailed list of information about a call which is currently up on the channel selected in the Channel Table.
To view the details of an active call in the Channel Table:

  • Click the Call Details text in the row corresponding to the channel in the Channel Table panel.

Outbound Channel Details

This page provides you with the finest granularity of detail, with information about the current call on the outbound channel.
To view information about a call on an outbound channel

  • Click the Channel Details text in the Outbound Channel Properties pane of the Detailed Call Information panel: