Viewing SIP Protocol Performance Statistics
This section contains the commands you use to access SIP protocol statistics. These statistics provide information about the SIP protocol performance.
Accessing SIP Statistics
You can access SIP statistics for both client and server SIP transactions by using the show sipd command. You can then use additional subcommands to display more specific information, including specific types of SIP messages.
Example
The following example show s the output of the show sipd command.
ORACLE# show sipd
14:10:32-178
SIP Status -- Period -- -------- Lifetime --------
Active High Total Total PerMax High
Sessions 0 0 0 0 0 0
Subscriptions 0 0 0 0 0 0
Dialogs 0 0 0 0 0 0
CallID Map 0 0 0 0 0 0
Rejections - - 0 0 0
ReINVITEs - - 0 0 0
Media Sessions 0 0 0 0 0 0
Media Pending 0 0 0 0 0 0
Client Trans 0 0 0 0 0 0
Server Trans 0 0 0 0 0 0
Resp Contexts 0 0 0 0 0 0
Saved Contexts 0 0 0 0 0 0
Sockets 0 0 0 0 0 0
Req Dropped - - 0 0 0
DNS Trans 0 0 0 0 0 0
DNS Sockets 0 0 0 0 0 0
DNS Results 0 0 0 0 0 0
Session Rate = 0.0
Load Rate = 0.0The display organizes the SIP transaction statistics for the system into two categories: Client Trans(actions) and Server Trans(actions). The remainder of the display provides information regarding dialogs, sessions, sockets, and DNS transactions.
Viewing SIP Status Information
The following example shows the output of the show sipd status command.
ORACLE# show sipd status
14:11:15-121
SIP Status -- Period -- -------- Lifetime --------
Active High Total Total PerMax High
Sessions 0 0 0 0 0 0
Subscriptions 0 0 0 0 0 0
Dialogs 0 0 0 0 0 0
CallID Map 0 0 0 0 0 0
Rejections - - 0 0 0
ReINVITEs - - 0 0 0
Media Sessions 0 0 0 0 0 0
Media Pending 0 0 0 0 0 0
Client Trans 0 0 0 0 0 0
Server Trans 0 0 0 0 0 0
Resp Contexts 0 0 0 0 0 0
Saved Contexts 0 0 0 0 0 0
Sockets 0 0 0 0 0 0
Req Dropped - - 0 0 0
DNS Trans 0 0 0 0 0 0
DNS Sockets 0 0 0 0 0 0
DNS Results 0 0 0 0 0 0
Replaced Dialogs - - 1 1 1
Session Rate = 0.0
Load Rate = 0.0The following table lists the SIP status statistics.
| Statistic | Description |
|---|---|
| Dialogs | Number of SIP signaling connections between the Oracle Communications Session Border Controller and a SIP UA (for example, a call leg) |
| Sessions | Number of sessions established by an INVITE request. A session consists of all dialogs created by one INVITE transaction. |
| Sockets | Number of active SIP communication ports (the number of open UDP and TCP sockets) |
| DNS Transactions | Number of outstanding DNS requests |
SIP Monitoring by Transaction Type
You can view statistics about SIP monitoring by transaction type.
SIP Server Transactions
Display statistics SIP server transactions by using the show sipd server command.
ORACLE# show sipd server
15:40:05-65
SIP Server Trans -- Period -- -------- Lifetime --------
Active High Total Total PerMax High
All States 0 346 2213 67975 3729 365
<Initial> 0 1 2213 67975 3729 1
<Trying> 0 48 1504 44773 2431 63
<Proceeding> 0 9 709 23202 1310 9
<Cancelled> 0 2 75 1370 182 4
<Established> 0 2 545 20201 971 3
<Completed> 0 148 959 24572 1489 149
<Confirmed> 0 157 716 23202 1309 161
<Terminated> 0 1 545 20201 972 1
ORACLE#The following table lists the specifics along with a brief description.
| Statistic | Description |
|---|---|
| All States | Total number of all server transactions. |
| Initial | State when the server transaction is created after a request is received. |
| Trying | Number of times the 100 Trying message has been sent, meaning that a request has been received and action is being taken. |
| Proceeding | Number of times a server transaction has been constructed for a request. |
| Cancelled | Number of INVITE transactions for which the system receives a CANCEL. |
| Established | Situation in which the server sends a 2xx response to an INVITE. |
| Completed | Number of times that the server has received a 300 to 699 status code and therefore entered the completed state. |
| Confirmed | Number of times that an ACK was received while the server was in the completed state and therefore transitioned to the confirmed state. |
| Terminated | Number of times that the server has received a 2xx response or has never received an ACK while in the completed state, and has therefore transitioned to the terminated state. |
SIP Client Transactions
Display statistics for SIP client transactions by using the show sipd client command.
ORACLE# show sipd client
15:40:09-69
SIP Client Trans -- Period -- -------- Lifetime --------
Active High Total Total PerMax High
All States 0 382 2042 64973 3371 387
<Initial> 0 1 2042 64973 3371 2
<Trying> 0 128 1333 41771 2073 128
<Calling> 0 2 709 23202 1310 2
<Proceeding> 0 8 613 21570 1130 9
<Cancelled> 0 2 75 1370 182 4
<EarlyMedia> 0 0 0 0 0 0
<Completed> 0 146 959 24571 1489 167
<SetMedia> 0 2 545 20201 972 2
<Established> 0 127 545 20201 971 127
<Terminated> 0 0 0 0 0 0
ORACLE#The following table lists the statistics along with a brief description.
| Statistic | Description |
|---|---|
| All States | Total number of all client transactions. |
| Initial | State before a request is sent out. |
| Trying | Number of times the trying state was entered due to the receipt of a request. |
| Calling | Number of times that the calling state was entered due to the receipt of an INVITE request. |
| Proceeding | Number of times that the proceeding state was entered due to the receipt of a provisional response while in the calling state. |
| Early Media | Number of times that the proceeding state was entered due to the receipt of a provisional response that contained SDP while in the calling state. |
| Completed | Number of times that the completed state was entered due to the receipt of a 300 to 699 status code when either in the calling or proceeding state. |
| SetMedia | Number of transactions in which the system is setting up NAT and steering ports (setting up the steering of the RTP flow). |
| Established | Number of situations in which the client receives a 2xx response to an INVITE, but can not forward it on because it requires NAT and steering port information. |
| Terminated | Number of times that the terminated state was entered due to the receipt of a 2xx message. |
Viewing SIP Media Event Errors
Display statistics for SIP media event errors by using the show sipd errors command.
ORACLE# show sipd errors
13:06:59-159
SIP Errors/Events ---- Lifetime ----
Recent Total PerMax
SDP Offer Errors 0 0 0
SDP Answer Errors 0 0 0
Drop Media Errors 0 0 0
Transaction Errors 0 0 0
Application Errors 0 0 0
Media Exp Events 0 0 0
Early Media Exps 0 0 0
Exp Media Drops 0 0 0
Expired Sessions 0 0 0
Multiple OK Drops 0 0 0
Multiple OK Terms 0 0 0
Media Failure Drops 0 0 0
Non-ACK 2xx Drops 0 0 0
Invalid Requests 0 0 0
Invalid Responses 0 0 0
Invalid Messages 0 0 0
CAC Session Drop 0 0 0
CAC BW Drop 0 0 0
Replace Dialog Fails 0 0 0The information displayed is divided into the following categories:
- Recent: number of errors that occurred within the number of seconds defined by the figure that appears directly after the time. In the example above, the Recent period of time is 60 seconds.
- Total: number of errors that occurred since the system was last rebooted.
- PerMax: period maximum number of errors that occurred since the system was last rebooted. This value identifies the highest individual Period Total value calculated over the lifetime of the monitoring.
These statistics record exceptional events encountered by the SIP application in processing SIP media sessions, dialogs, and sessions descriptions (SDP). Serious errors will be accompanied by a log message in log.sipd and acmelog (depending of the current log level setting) of the appropriate severity which will indicate the nature of the error.
| Statistic | Description |
|---|---|
| SDP Offer Errors | Number of errors encountered in setting up the media session for a session description in a SIP request or response which is an SDP Offer in the Offer/Answer model defined in RFC 3264. This may be a failure to send the transaction to MBCD or an error response from MBCD. These errors may also be counted in one of the show mbcd errors. |
| SDP Answer Errors | Number of errors encountered in setting up the media session for a session description in a SIP request or response which is an SDP Answer in the Offer/Answer model (RFC 3264). This may be a failure to send the transaction to MBCD or an error response from MBCD. These errors may also be counted in the show mbcd errors. |
| Drop Media Errors | Number of errors encountered in tearing down the media for a dialog or session that is being terminated due to: a) non-successful response to an INVITE transaction; or b) a BYE transaction received from one of the participants in a dialog/session; or c) a BYE initiated by the Oracle Communications Session Border Controller due to a timeout notification from MBCD. This may be a failure to send the transaction to MBCD or an error response from MBCD. These errors may also be counted in the show mbcd errors. |
| Transaction Errors | Number of errors in continuing the processing of the SIP client transaction associated with setting up or tearing down of the media session. |
| Missing Dialog | Number of requests received by the SIP application for which a matching dialog count not be found. Usually, this event will also be counted as a 481 (Does Not Exist) server response for the method of the SIP request. This event will occur quite often particularly when both endpoints send a BYE request at approximately the same time. |
| Application Errors | Number of miscellaneous errors that occur in the SIP application that are otherwise uncategorized. |
| Media Exp Events | Number of flow timer expiration notifications received from MBCD. These may be fairly common particularly if endpoints stop sending media (or do not start sending media) without sending the appropriate signaling message (BYE) to terminate the dialog/session. These events may also be counted in the show mbcd errors. |
| Early Media Exps | Number of flow timer expiration notifications received for media sessions that have not been completely set up due to an incomplete or still pending INVITE transaction (e.g., 200 OK response to the INVITE has not been received yet). This can occur if an INVITE transaction takes longer than the initial-guard-timer or subsq-guard-timer fields defined in the media-manager-config element. This event does not result in the dialog/session being terminated if the INVITE is still pending. Note that this statistic is a subset of the Media Exp Events above. |
| Exp Media Drops | Number of flow timer expiration notifications from MBCD which resulted in the SIP application terminating the dialog/session. |
| Multiple OK Drops | Number of dialogs that were terminated upon reception of a 200 OK response from multiple UASs for a given INVITE transaction which was forked by a downstream proxy. When multiple UASs accept an INVITE with a 200 OK responses, only the first one is passed on by the Oracle Communications Session Border Controller. If the subsequent 200 OK were processed and passed on the media session established by the first 200 OK would be disrupted. The Oracle Communications Session Border Controller will ACK the 200 OK response and then send a BYE request to terminate the dialog for the subsequent 200 OK response. The proscribed behavior for the proxy is to cancel outstanding branches of the fork when a 200 OK is received. However, there is a race condition where a subsequent 200 OK is generated by a UAS before the CANCEL reaches the UAS. |
| Multiple OK Terms | Number of dialogs that were terminated upon reception of a 200 OK response which conflicts with an existing established dialog on the Oracle Communications Session Border Controller. This is similar to the Multiple OK Drops statistic. The difference is that an upstream proxy forked the INVITE resulting in multiple INVITE transactions which have the same Call-ID and session description (SDP). The Oracle Communications Session Border Controller will accept only the first 200 OK received. If the subsequent 200 OK were processed, the media session established by the initial 200 OK would be disrupted. The Oracle Communications Session Border Controller will ACK the 200 OK response and then send a BYE request to terminate the dialog for the subsequent 200 OK response. The Oracle Communications Session Border Controller will send a 487 (Terminated) response upstream in order to complete the client transaction which conflicted with an established dialog. The prescribed behavior for the proxy is to cancel outstanding branches of the fork when a 200 OK is received. However, there is a race condition where a subsequent 200 OK is generated by a UAS before the CANCEL reaches the UAS. |
| Media Failure Drops | Number of dialogs that had to be terminated due to a failure in setting up the media session. This situation occurs when an SDP offer is sent downstream in a request, but the SDP answer in a response to that request encounters a failure. Rather than passing the successful response upstream to the User Agent Client (UAC), the Oracle Communications Session Border Controller terminates the session. For an INVITE transaction, the Oracle Communications Session Border Controller sends an ACK for the 200 OK response and then sends a BYE request. The Oracle Communications Session Border Controller then sends an error response to the UAC. |
| Expired Sessions | Number of sessions that were terminated due to the session timer expiring. When the media for a dialog/session does not traverse the Oracle Communications Session Border Controller, the SIP application sets a session timer (equal to the flow-time-limit defined in the media-manager-config). This to ensure that the session is properly cleaned up in the event that the endpoints do not send the appropriate signaling to terminate the session (e.g., BYE). Note that when the media session does traverse the Oracle Communications Session Border Controller, the flow timers are used by MBCD and the SIP application does not set a session timer. |
Viewing SIP Session Agent Statistics
Display SIP session agent information by using the show sipd agents command. With this command, the Oracle Communications Session Border Controller ascertains whether a session agent is in service. When the session agent stops responding to SIP requests, it transitions to the out-of-service state. You can configure the Oracle Communications Session Border Controller to periodically ping the session agent if it has gone out-of-service, or if no requests have been sent to it.
The show sipd agents command shows information about the number of active sessions, the average rate of session invitations, and the number of times that the constraints established in the session-agent element have been exceeded for sessions inbound to and outbound from each session agent, as well as the average and maximum latency and the maximum burst rate related to each session agent.
For example:
ORACLE# show sipd agents
19:39:34-95
---- Inbound ---- --- Outbound ---- -Latency- --- Max ---
Session Agent Active Rate ConEx Active Rate ConEx Avg Max Burst In Out
192.168.200.131 0 0.0 0 0 0.0 0 0.0 0.0 0 0 0Inbound statistics:
- Active: number of active sessions sent to each session agent listed
- Rate: average rate of session invitations (per second) sent to each session agent listed
- ConEx: number of times the constraints have been exceeded
Outbound statistics:
- Active: number of active sessions sent from each session agent
- Rate: average rate of session invitations (per second) sent from each session agent listed
- ConEx: number of times the constraints have been exceeded
Latency statistics:
- Avg: average latency for packets traveling to and from each session agent listed
- Max: maximum latency for packets traveling to and from each session agent listed
- Max Burst: total number of session invitations sent to or received from the session agent within the amount of time configured for the burst rate window of the session agent
The second column, which is not labeled, of the show sipd agents output shows the service state of each session agent identified in the first column. In the service state column, an I indicates that the particular session agent is in service and an O indicates that the particular session agent is out of service. An S indicates that the session agent is in transition from the out-of-service state to the in-service state; it remains in this transitional state for a period of time that is equal to its configured in-service period, or 100 milliseconds (whichever is greater). A D indicates that the session agent is disabled.
Viewing SIP Session Agent Group Statistics
Display session information for the session agent groups on the system by using the show sipd groups command. This information is compiled by totaling the session agent statistics for all of the session agents that make up a particular session agent group. While the show sipd groups command accesses the subcommands that are described in this section, the main show sipd groups command (when executed with no arguments) displays a list of all session agent groups for the system.
If you carry out this command, but you do not specify the name of an existing session agent group, the system informs you that the group statistics are not available.
Viewing Session and Dialog States
Display session and dialog states by using the show sipd sessions command. For example:
SIP Session Status -- Period -- -------- Lifetime --------
Active High Total Total PerMax High
Sessions 0 0 0 0 0 0
Initial 0 0 0 0 0 0
Early 0 0 0 0 0 0
Established 0 0 0 0 0 0
Terminated 0 0 0 0 0 0
Dialogs 0 0 0 0 0 0
Early 0 0 0 0 0 0
Confirmed 0 0 0 0 0 0
Terminated 0 0 0 0 0 0Sessions
- Initial—state of a new session for which an INVITE or SUBSCRIBE is being forwarded.
- Early—state the session enters when it receives the first provisional response (1xx other than 100).
- Established—state the session enters when it receives a success (2xx) response.
- Terminated—state the session enters when the session is ended by receiving or sending a BYE for an Established session or forwarding an error response for an Initial or Early session. The session remains in the Terminated state until all the resources for the session are freed.
Dialogs
A dialog is created when a dialog establishing method (INVITE or SUBSCRIBE) receives a provisional (1xx other than 100) or success (2xx) response.
- Early—dialog is created by a provisional response.
- Confirmed—dialog is created by a success response; an Early dialog transitions to Confirmed when it receives a success response.
- Terminated—dialog enters this state when the session is ended by receiving/sending a BYE for an Established session, or by receiving/sending error response Early dialog. The dialog remains in the Terminated state until all the resources for the session are freed.
Viewing SIP Endpoint
The show sipd sip-endpoint-ip command supports the look-up and display of registration information for a designated endpoint. This command uses the following syntax: show sipd endpoint-ip <phone number>. For the phone number value, you can enter as many components of the particular phone number about which you would like information—including information about adaptive HNT.
This command must be entered with the numerical value representing the endpoint to look up. The ACLI help menu prompts you for this information.
ORACLE# show sipd endpoint-ip ?
---------- ACLI v1.0 -----------
<phone number> enter phone number to look up endpointThere is no support for wildcard matches or lists of users. The first entry that matches the phone number given as an argument will be returned. The following examples show a range of matching values.
ORACLE# show sipd endpoint-ip 1781
Reg[sip:17815551111@69.69.69.10]
RegEntry[sip:17815551111@69.69.69.10] ID=4 exp=28
UA-contact='sip:17815551111@69.69.69.69:5062;acme_nat=192.168.201.50:5060'
SD-contact='sip:17815551111-1ke1g79h75pu8@69.69.69.10'
hnt-test-status='IN-PROGRESS'
successful-test-time='40 secs'
ORACLE# show sipd endpoint-ip 17815551111
Reg[sip:17815551111@69.69.69.10]
RegEntry[sip:17815551111@69.69.69.10] ID=4 exp=20
UA-contact='sip:17815551111@69.69.69.69:5062;acme_nat=192.168.201.50:5060'
SD-contact='sip:17815551111-1ke1g79h75pu8@69.69.69.10'
hnt-test-status='COMPLETED'
successful-test-time='40 secs'
ORACLE# show sipd endpoint-ip 17815559999
Reg[sip:17815559999@69.69.69.80]
RegEntry[sip:17815559999@69.69.69.80] ID=5 exp=29
UA-contact='sip:17815559999@69.69.69.69:5063;acme_nat=192.168.201.155:5060'
SD-contact='sip:17815559999-2se308dh8lp29@69.69.69.10'
hnt-test-status='IN-PROGRESS'
successful-test-time='40 secs'
ORACLE# show sipd endpoint-ip 1781555
Reg[sip:17815551111@69.69.69.10]
RegEntry[sip:17815551111@69.69.69.10] ID=4 exp=17
UA-contact='sip:17815551111@69.69.69.69:5062;acme_nat=192.168.201.50:5060'
SD-contact='sip:17815551111-1ke1g79h75pu8@69.69.69.10'
hnt-test-status='IN-PROGRESS'
successful-test-time='40 secs'
hnt-test-status='IN-PROGRESS'
successful-test-time='40 secs'
ORACLE# show sipd endpoint-ip 1781555555
Reg[sip:17815555555@69.69.69.80]
RegEntry[sip:17815555555@69.69.69.80] ID=3 exp=19
UA-contact='sip:17815555555@69.69.69.69:5060;user=phone'
SD-contact='sip:17815555555-v3etv61h55om8@69.69.69.10'
hnt-test-status='COMPLETED'
successful-test-time='40 secs'Viewing SIP Per User CAC Statistics
The commands in this section allow you to view information about SIP per user CAC.
IP-Based CAC Information
If you want to see information about the operation of SIP per user CAC for the IP address mode, you can use the new ACLI show sipd ip-cac command. You enter this command with the IP address for which you want to view data.
The Oracle Communications Session Border Controller will display the number of configured sessions allowed, number of active sessions, amount of configured bandwidth allowed, and the amount of bandwidth used.
To view information about SIP per user CAC using the IP address mode:
Viewing Statistics for SIP Per User Subscribe Dialog Limit
You can display the number of subscription dialogs per SUBSCRIBE event type using the ACLI show registration sipd subscriptions-by-user command. You can display this information per event type, or you can show data for all event types by wildcarding the event type argument.
The following example shows you how to use this command with a wildcard.
ORACLE# show registration sipd subscriptions-by-user *
Registration Cache FRI NOV 21 2008 13:40:14
User: sip:7815550001@192.168.1.206
AOC: <sip:7815550001@192.168.1.206:5060;transport=udp>
Event-Type: dialog --> Subscriptions: 2
----------------- -------------------------------- ------------------Message Rate Statistics
The Oracle Communications Session Border Controller provides message rate statistics for SIP traffic. You must first enable extra method statistics generation in the sip config.
To enable full SIP message rate statistics:
show sipd rate
The show sipd rate command displays request and response rates for messages (per method) on a system-wide basis. The rates are calculated based on the time in the current monitoring window (100+current period elapsed). The Message Received and the Messages sent columns are the sum of the corresponding Requests or responses. For example:
ORACLE# show sipd rate
17:24:28-103
Method Name Msg Recv Msg Sent Req Recv Req Sent Resp Recv Resp Sent
Rate Rate Rate Rate Rate Rate
INVITE 0.0 0.0 0.0 0.0 0.0 0.0
ACK 0.0 0.0 0.0 0.0 0.0 0.0
BYE 0.0 0.0 0.0 0.0 0.0 0.0
REGISTER 0.0 0.0 0.0 0.0 0.0 0.0
CANCEL 0.0 0.0 0.0 0.0 0.0 0.0
PRACK 0.0 0.0 0.0 0.0 0.0 0.0
OPTIONS 0.0 0.0 0.0 0.0 0.0 0.0
INFO 0.0 0.0 0.0 0.0 0.0 0.0
SUBSCRIBE 0.0 0.0 0.0 0.0 0.0 0.0
NOTIFY 0.0 0.0 0.0 0.0 0.0 0.0
REFER 0.0 0.0 0.0 0.0 0.0 0.0
UPDATE 0.0 0.0 0.0 0.0 0.0 0.0
MESSAGE 0.0 0.0 0.0 0.0 0.0 0.0
PUBLISH 0.0 0.0 0.0 0.0 0.0 0.0
OTHER 0.0 0.0 0.0 0.0 0.0 0.0
ALL 0.0 0.0 0.0 0.0 0.0 0.0
clank#show sipd rate interface
The show sipd rate interface command displays request and response rates for messages (per method) for all configured sip-interfaces. The rates are calculated based on the time in the current monitoring window (30+current period elapsed). The Message Received and the Messages sent columns are the sum of the corresponding Requests or responses. For example:
ORACLE# show sipd rate interface
17:24:33-58
Sip Interface core
Method Name Msg Recv Msg Sent Req Recv Req Sent Resp Recv Resp Sent
Rate Rate Rate Rate Rate Rate
INVITE 0.0 0.0 0.0 0.0 0.0 0.0
ACK 0.0 0.0 0.0 0.0 0.0 0.0
BYE 0.0 0.0 0.0 0.0 0.0 0.0
REGISTER 0.0 0.0 0.0 0.0 0.0 0.0
CANCEL 0.0 0.0 0.0 0.0 0.0 0.0
PRACK 0.0 0.0 0.0 0.0 0.0 0.0
OPTIONS 0.0 0.0 0.0 0.0 0.0 0.0
INFO 0.0 0.0 0.0 0.0 0.0 0.0
SUBSCRIBE 0.0 0.0 0.0 0.0 0.0 0.0
NOTIFY 0.0 0.0 0.0 0.0 0.0 0.0
REFER 0.0 0.0 0.0 0.0 0.0 0.0
UPDATE 0.0 0.0 0.0 0.0 0.0 0.0
MESSAGE 0.0 0.0 0.0 0.0 0.0 0.0
PUBLISH 0.0 0.0 0.0 0.0 0.0 0.0
OTHER 0.0 0.0 0.0 0.0 0.0 0.0
17:24:33-58
Sip Interface peer
Method Name Msg Recv Msg Sent Req Recv Req Sent Resp Recv Resp Sent
Rate Rate Rate Rate Rate Rate
INVITE 0.0 0.0 0.0 0.0 0.0 0.0
ACK 0.0 0.0 0.0 0.0 0.0 0.0
BYE 0.0 0.0 0.0 0.0 0.0 0.0
REGISTER 0.0 0.0 0.0 0.0 0.0 0.0
CANCEL 0.0 0.0 0.0 0.0 0.0 0.0
PRACK 0.0 0.0 0.0 0.0 0.0 0.0
OPTIONS 0.0 0.0 0.0 0.0 0.0 0.0
INFO 0.0 0.0 0.0 0.0 0.0 0.0
SUBSCRIBE 0.0 0.0 0.0 0.0 0.0 0.0
NOTIFY 0.0 0.0 0.0 0.0 0.0 0.0
REFER 0.0 0.0 0.0 0.0 0.0 0.0
UPDATE 0.0 0.0 0.0 0.0 0.0 0.0
MESSAGE 0.0 0.0 0.0 0.0 0.0 0.0
PUBLISH 0.0 0.0 0.0 0.0 0.0 0.0
OTHER 0.0 0.0 0.0 0.0 0.0 0.0By entering a configured interface, the ACLI displays aggregate statistics for that interface and then displays all Session Agents’ counts configured on that SIP interface. Displays have been truncated below. For example:
ORACLE# show sipd rate interface peer
17:24:40-34
Sip Interface peer
Method Name Msg Recv Msg Sent Req Recv Req Sent Resp Recv Resp Sent
Rate Rate Rate Rate Rate Rate
INVITE 0.0 0.0 0.0 0.0 0.0 0.0
[...]
OTHER 0.0 0.0 0.0 0.0 0.0 0.0
clank#
__________________________________________________________________________________
Session Agent 172.16.202.102
Method Name Msg Recv Msg Sent Req Recv Req Sent Resp Recv Resp Sent
Rate Rate Rate Rate Rate Rate
INVITE 0.0 0.0 0.0 0.0 0.0 0.0
ACK 0.0 0.0 0.0 0.0 0.0 0.0
BYE 0.0 0.0 0.0 0.0 0.0 0.0
REGISTER 0.0 0.0 0.0 0.0 0.0 0.0
CANCEL 0.0 0.0 0.0 0.0 0.0 0.0
PRACK 0.0 0.0 0.0 0.0 0.0 0.0
OPTIONS 0.0 0.0 0.0 0.0 0.0 0.0
INFO 0.0 0.0 0.0 0.0 0.0 0.0
SUBSCRIBE 0.0 0.0 0.0 0.0 0.0 0.0
NOTIFY 0.0 0.0 0.0 0.0 0.0 0.0
REFER 0.0 0.0 0.0 0.0 0.0 0.0
UPDATE 0.0 0.0 0.0 0.0 0.0 0.0
MESSAGE 0.0 0.0 0.0 0.0 0.0 0.0
PUBLISH 0.0 0.0 0.0 0.0 0.0 0.0
OTHER 0.0 0.0 0.0 0.0 0.0 0.0
17:26:21-46
Session Agent 192.168.202.100
Method Name Msg Recv Msg Sent Req Recv Req Sent Resp Recv Resp Sent
Rate Rate Rate Rate Rate Rate
INVITE 0.0 0.0 0.0 0.0 0.0 0.0
[...]
OTHER 0.0 0.0 0.0 0.0 0.0 0.0
ORACLE#show sipd rate agent
The show sipd rate agent command displays request and response rates for messages (per method) for all session agents. By adding a session agent name in the form show sipd rate agent <session-agent-name>, you can view statistics for the identified agent only. The rates are calculated based on the time in the current monitoring window (30+current period elapsed). The Message Received and the Messages sent columns are the sum of the corresponding Requests or responses. For example:
ORACLE# show sipd rate agent 192.168.202.100
17:26:47-42
Session Agent 192.168.202.100
Method Name Msg Recv Msg Sent Req Recv Req Sent Resp Recv Resp Sent
Rate Rate Rate Rate Rate Rate
INVITE 0.0 0.0 0.0 0.0 0.0 0.0
ACK 0.0 0.0 0.0 0.0 0.0 0.0
BYE 0.0 0.0 0.0 0.0 0.0 0.0
REGISTER 0.0 0.0 0.0 0.0 0.0 0.0
CANCEL 0.0 0.0 0.0 0.0 0.0 0.0
PRACK 0.0 0.0 0.0 0.0 0.0 0.0
OPTIONS 0.0 0.0 0.0 0.0 0.0 0.0
INFO 0.0 0.0 0.0 0.0 0.0 0.0
SUBSCRIBE 0.0 0.0 0.0 0.0 0.0 0.0
NOTIFY 0.0 0.0 0.0 0.0 0.0 0.0
REFER 0.0 0.0 0.0 0.0 0.0 0.0
UPDATE 0.0 0.0 0.0 0.0 0.0 0.0
MESSAGE 0.0 0.0 0.0 0.0 0.0 0.0
PUBLISH 0.0 0.0 0.0 0.0 0.0 0.0
OTHER 0.0 0.0 0.0 0.0 0.0 0.0Viewing IMS-AKA Statistics
The ACLI show sipd endpoint-ip command is updated to show the IMS-AKA parameters corresponding to each endpoint. The display shows the algorithms used, the ports used, and the security parameter indexes (SPIs) used.
In addition, the show sa stats command now shows the security associations information for IMS-AKA.
ORACLE# show sa stats
05:28:32-107
SA Statistics ---- Lifetime ----
Recent Total PerMax
IKE Statistics
ADD-SA Req Rcvd 0 0 0
ADD-SA Success Resp Sent 0 0 0
ADD-SA Fail Resp Sent 0 0 0
DEL-SA Req Rcvd 0 0 0
DEL-SA Success Resp Sent 0 0 0
DEL-SA Fail Resp Sent 0 0 0
ACQUIRE-SA Req Sent 0 0 0
ACQUIRE-SA Success Resp 0 0 0
ACQUIRE-SA Fail Resp Rcv 0 0 0
ACQUIRE-SA Trans Timeout 0 0 0
SA Added 0 0 0
SA Add Failed 0 0 0
SA Deleted 0 0 0
SA Delete Failed 0 0 0
IMS-AKA Statistics
ADD-SA Req Rcvd 0 0 0
ADD-SA Success Resp Sent 0 0 0
ADD-SA Fail Resp Sent 0 0 0
DEL-SA Req Rcvd 0 0 0
DEL-SA Success Resp Sent 0 0 0
DEL-SA Fail Resp Sent 0 0 0
SA Added 0 0 0
SA Add Failed 0 0 0
SA Deleted 0 0 0
SA Delete Failed 0 0 0STUN Server Statistics and Protocol Tracing
This section describes how you can monitor STUN server statistics and perform STUN protocol tracing.
STUN Server Statistics
You can display statistics for the STUN server using the ACLI show mbcd stun command when the STUN server has been enabled. However, if the STUN server has not been enabled since the last system reboot, the command does not appear and no statistics will be displayed.
ORACLE# show mbcd stun
09:05:21-193
STUN Statistics -- Period -- -------- Lifetime --------
Active High Total Total PerMax High
Servers 1 1 0 2 1 1
Server Ports 4 4 0 8 4 4
Binding Requests - - 4 861 4
Binding Responses - - 4 861 4
Binding Errors - - 0 0 0
Messages Dropped - - 0 0 0The table below lists and describes the STUN server statistics.
| STUN Server Display Category | Description |
|---|---|
| Servers | The number of STUN servers (the same as the number of realms configured with a STUN server). |
| Server Ports | Number of ports per STUN server; there will be four ports per STUN server. |
| Binding Requests | Number of STUN Binding Request messages received by all STUN servers. |
| Binding Responses | Number of STUN Binding Response messages sent by all STUN servers. |
| Binding Errors | Number of STUN Binding Error messages sent by all STUN servers. |
| Messages Dropped | Number of messages dropped by all STUN servers. |
STUN Protocol Tracing
You can enable STUN protocol tracing two ways: by configuration or on demand.
- By configuration—The Oracle Communications Session Border Controller’s STUN protocol trace file is called stun.log, which is classified as a call trace. This means that when the system configuration’s call-trace parameter is set to enabled, you will obtain STUN protocol information for the system. As with other call protocol traces, tracing data is controlled by the log-filter in the system configuration.
On demand—Using the ACLI notify mbcd log or notify mbcd debug commands, you enable protocol tracing for STUN. Using notify mbcd debug sets the STUN log level to TRACE. You can turn off tracing using the notify mbcd nolog or notify mbcd nodebug commands. Using notify mbcd nodebug returns the STUN log level back to its configured setting.
Local and Remote Call Termination Counters
The OCSBC maintains counters of gracefully terminated calls for cases where the BYE is generated both locally within the system and call is terminated externally, as expected. Each case is maintained in a unique counter. These counters are maintained for each session agent, realm, SIP Interface, and globally.
- show sipd agents
- show sipd realms
- show sipd interface
- show sipd status
# show sipd agents EP2
06:22:24-40
Session Agent EP2(Realm192) [In Service]
-- Period -- -------- Lifetime --------
Active High Total Total PerMax High
Inbound Sessions 0 0 0 0 0 0
[...]
Local Call Drops - - 1 1 0 -
Normal Call Drops - - 0 0 0 -Local call drops include scenarios wherein the OCSBC generates BYE messages because of internal triggers such as a media guard timer expiring, a negative Rx response after call establishment, or internal processing errors (SIP application exception or other MBCD drops). The OCSBC displays this counter in applicable show commands as Local Call Drops.
Remote call release scenarios include flows that terminate gracefully, such as the OCSBC receiving a BYE . The OCSBC increments the counter on the ingress and the egress sides, and displays this counter in applicable show commands as Normal Call Drops.
SIP Method Counters
The Oracle Communications Session Border Controller (OCSBC) displays detailed counts of SIP messages (methods) via the show sipd command. You append this command with the applicable message name to view information about individual SIP messages types, including: INVITEs, REGISTERs, OPTIONS, CANCELs, BYEs, ACKs, INFOs, PRACKs (provisional ACKs), SUBSCRIBEs, NOTIFYs, REFERs, and UPDATEs.
Counts for messages are grouped by the SIP response code that was sent or received for each method. If the OCSBC has not recorded a for the method, it is omitted from the output.
ORACLE# show sipd invite
INVITE (19:38:49-110)
--------- Server -------- --------- Client --------
Message/Event Recent Total PerMax Recent Total PerMax
------ --------- ------ ------ --------- ------
INVITE Requests 146 146 107 146 146 107
Retransmissions 0 0 0 0 0 0
100 Trying 146 146 107 0 0 0
180 Ringing 146 146 107 146 146 107
200 OK 146 146 107 146 146 107
Response Retrans 0 0 0 0 0 0
Transaction Timeouts - - - 0 0 0
Locally Throttled - - - 0 0 0
Avg Latency=0.000 for 146
Max Latency=0.001
The information is divided in two sections: Server and Client and includes information for recent, total, and period maximum messages or events.
- Recent: number of specific SIP messages and/or events that occurred within the current time period—in one-second increments, and always is between 100 and 199 and never below 100, constituting a 100-200 second recent period. This is done in order to keep the statistics from zeroing out between transition periods
- Total: current number of SIP messages and/or events that occurred since the system was last rebooted.
- PerMax: maximum number of SIP messages and/or events that occurred during a single time period since the system was last rebooted.
This display also shows information regarding the average and maximum latency. For each type of SIP message, only those transactions for which there are statistics will be shown.
HDR Output for SIP Method Counters
- sip-method
- sip-realm-method
- sip-interface-method
- sip-agent-method
These groups can be configured within the collect-group configuration element or from the request collection ACLI command.
Example 3-1 SNMP Output for SIP Method Counters
System level method statistics are output with the apSipMethodStatsTable, available in ap-sip.mib.
SIP Message Counters
SIP Message counters come in two forms, event-based and session-based. The Oracle Communications Session Border Controller maintains and presents both message counts on the ACLI through show commands.
Event-based messaging refers to short messages transported as SIP MESSAGEs. These statistics are retrieved by typing the show sipd status command, and viewing the row identified as "Standalone Messages".
Session-based messaging refers to short messages transported SIP INVITE messages. These statistics are retrieved by typing the show sessions command and viewing the row identified as "Messaging Sessions".
All Messaging Sessions counter rows are provided for the current Period (total and high), System lifetime (total, period maximum, and lifetime high), and finally the current active number. Message counters only show successful messages.
In order to label a SIP INVITE and/or SIP MESSAGE to be treated as a message for incrementing this message counters, you configure two parameters. If no values are configured, the OCSBC parses for a default IMS Communication Service Identifier (ICSI).
| Message Type | containing configuration elements | parameter | default |
|---|---|---|---|
| Session-based |
session-agent realm-config sip-interface |
sm-icsi-match-for-invite |
urn:rrn-7:3gpp-service.ims.icsi.oma.cpm.msg
|
| Event-based |
session-agent realm-config sip-interface |
sm-icsi-match-for-message |
urn:urn-7:3gpp-service.ims.icsi.oma.cpm.largemsg
|
When the ICSI value is embedded within a tag, the
OCSBC escapes the tag
value for comparison against the configured value. For example, If the
Accept-Contact: header contains the tag:
urn%3Aurn-7%3A3gpp-service.ims.icsi.oma.cpm.largemsg
it will be normalized to
urn:urn-7:3gpp-service.ims.icsi.oma.cpm.largemsg.
Session-based Message Counter Logic
- P-Asserted-Service
- P-Preferred-Service
- Feature-Caps
- Accept-Contact
- Contact
After a match is made, when the OCSBC receives the 200OK response for the forwarded INVITE, the counter is incremented.
Event-based (Standalone) Message Counter Logic
- P-Asserted-Service
- P-Preferred-Service
- Feature-Caps
- Accept-Contact
- Contact
After a match is made, when the OCSBC receives the 203 Accepted response for the forwarded MESSAGE and it does not contain an In-Reply-To header, the counter is incremented.
Alternatively, if a SIP MESSAGE's content-type matches:
application/vnd.3gpp.sms
the message counter is incremented when the
OCSBC receives the 203
Accepted response for the forwarded MESSAGE and that response does not contain
an In-Reply-To header.