Page History

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.

...

• 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

  Spacevars
  0 product2

  , 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 

  Spacevars
  0 product2

  .
• 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

  Spacevars
  0 product2

  , 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

  Spacevars
  0 product2

  .
• 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

  Spacevars
  0 product2

  , 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

  Spacevars
  0 product2

  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

  Spacevars
  0 product2

  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. Include Page_channel_detail_info_pages_pt1_channel_detail_info_pages_pt1