SIP Monitor and Trace operations allow the Oracle® Enterprise Session Border Controller (ESBC) to monitor SIP sessions in your network. The system processes SIP Monitor and Trace data on incoming messages first, and then sends the data out on outgoing messages. This process allows the ESBC to capture SIP Monitor and Trace data for display in the Web GUI.

The ESBC captures a SIP message in ingress, applies the Header Manipulation Rules (HMR) that you configured, and applies the Session Plug-in Language (SPL). When the ESBC sends the message on egress, the ESBC applies the SPL, applies the HMR, and sends out the captured SIP message.

The SIP Sessions Summary is a SIP session summary of all logged call sessions on the Oracle® Enterprise Session Border Controller (ESBC). When you enable Lightweight Directory Access Protocol (LDAP) on the Active Directory, LDAP session messages may also display. The columns that display on the Sessions Summary page depend on the columns that you specified in the "Customizing the Page Display" procedure.

The following table describes the columns on the SIP Session Summary page.

The SIP Registrations Summary displays a summary of all logged SIP registrations sessions on the Oracle® Enterprise Session Border Controller (ESBC). The columns that display on the Registrations Summary page depend on the columns you selected in the "Customizing the Page Display" procedure.

The following table describes the columns available on the Registrations Summary page.

The SIP Subscriptions Report displays a summary of all logged SIP subscription sessions on the Oracle® Enterprise Session Border Controller (ESBC). The columns that display on the Subscription Report page depend on the columns you selected in the "Customizing the Page Display" procedure.

The following table describes the columns on the Subscriptions Report page.

The SIP Notable Events Summary contains all logged sessions that have a notable event on the Oracle® Enterprise Session Border Controller (ESBC) associated with the session. The columns that display on the Notable Events Summary page depend on the columns that you selected in the "Customizing the Page Display" procedure.

The following table describes the columns that Notable Events Summary page can display.

A ladder diagram is a graphical representation of the flow of call and media packets on ingress and egress routes through the Oracle® Enterprise Session Border Controller (ESBC). Viewing ladder diagrams can help you with troubleshooting and system monitoring. The Web GUI can display ladder diagrams for each of the summary reports available through Monitor and Trace.

The ESBC can store up to 4,000 calls on a system with more than 4GB of memory and up to 2,000 calls on a system with less than 4GB of memory. A ladder diagram can display up to 999 rows, but the relationship to stored calls is inverse. The more calls you want to store, the fewer rows the ladder diagram can display. The more rows you want to see per call, the fewer the number of calls the ESBC can store. You can control the number of rows to display by setting the Ladder Diagram Rows parameter in the SIP Monitoring configuration under Session Router.

The following illustration shows a sample ladder diagram with notations about the controls for viewing and exporting.

Ladder diagrams contain the following sections.

Session Summary—Displays session data. Use the [+] and [-] controls to toggle between show and hide. The default is hide.

Ladder Diagram—Displays SIP message and call flow information. Hover over a line in the ladder diagram to see more information about the highlighted flow.

QoS Stats—Displays Quality of Service (QoS) information. Use the [+] and [-] controls to toggle between show and hide. The default is hide. You must enable Quality of Service (QoS) on your system to see the QoS Statistics information.

The following screen capture shows an example of a ladder diagram as initially displayed with the Session Summary and QoS Stats sections hidden.

The following screen capture shows an example of an ESBC ladder diagram with the Session Summary and QoS sections expanded. This screen capture also shows an example of the pop-up that displays detailed SIP Message Details when you hover over a row in the diagram.

You must enable SIP Monitoring and configure the options for displaying session data and notable event data on the Monitor and Trace page.

1. Access SIP Monitoring: Configuration, Session Router, SIP Monitoring.
2. On the SIP Monitoring page, do the following.

   Match Any Filter	Select to monitor all SIP traffic. Default: Disabled.
   State	Select to enable SIP monitoring.
   Short Session Duration	Enter a value, in seconds, for the maximum session duration of a short session. Default: 0. Range 0-999999999.
   Monitoring Filters	Create a global list of monitoring filters.
   Interesting Events	Create a global list of interesting events to monitor. Click Add, and do the following: Type—Select an event type from the drop-down list. Default: None. Valid values: Short Session, Local Rejection. Trigger Threshold—Set the number of events required to occur in within the trigger window before the system starts monitoring. Default: 0. Range: 0-999999999. Trigger Timeout—Set the amount of time, in seconds, that the monitoring persists. Default: 0. Range: 0-999999999, Click OK. The system displays the SIP monitoring page.

3. Click OK.
4. Save the configuration.

Use the Search button at the top of the report page to help you find a specific record in an Oracle® Enterprise Session Border Controller (ESBC) Monitor and Trace report. Search allows you to specify criteria for the search.

1. On any reports page, click Search and do the following in the Search Filter dialog.

   Global Search—Search all parameters in all records.	Enter the URI formatted string of the call source information you are searching. Valid values: alpha-numeric characters. For example, sipp<sip:sipp@172.16.34.10:5060;tag=24.
   From URI—Search on the From-URI header.	Enter the URI formatted string that contains a protocol, name, location, or any other applicable characteristic, that is sent by the ESBC in the FROM header. Valid values: alpha-numeric characters. For example, sip:service@172.16.34.226:5060.
   Request URI—Search on the Request-URI header.	Enter the URI formatted string that contains a protocol, name, location, or any other applicable characteristic, that is sent by the ESBC in the REQUEST header. Valid values: alpha-numeric characters. For example, sip:service@172.16.34.226:5060.
   To URI—Search on the To-URI header.	Enter the URI formatted string of the call destination information you want to find. Valid values: alpha-numeric characters. For example, sut<sip:service@172.16.34.226:5060;tag=99.
   Start Date— Search from messages that start at the specified date and time.	Enter a starting date to search on in the first text box in the format YYYY-MM-DD (where Y =year, M=month, and D=day). For example, 2012-04-15 would search for all records ending on April 15, 2012. Valid values: numeric characters only. Enter a start time to search on in the last three text boxes in the format HH mm ss (where H=hour, m=minutes, and s=seconds). For example, 01 30 45 would search for all records starting at 1:30 and 45 seconds. Valid values: numeric characters only.
   End Date—Search from messages that end at the specified date and time.	Enter an end date to search on in the first text box in the format YYYY-MM-DD (where Y =year, M=month, and D=day). For example, 2012-04-15 would search for all records starting on April 15, 2012. Valid values: numeric characters only. Enter an end time to search on in the last three text boxes in the format HH mm ss (where H=hour, m=minutes, and s=seconds). For example, 01 30 45 would search for all records ending at 1:30 and 45 seconds. Valid values: numeric characters only.
   Session ID—Search on the monitored SIP session ID, as shown in the Summary table.	Enter the ID of the call session you want to search. Valid values: alpha-numeric characters. For example, 22-3412@172.16.34.1.
   In Call ID—Search on the SIP call ID of the initial received request.	Enter the ID of the incoming call (phone number and source IP address). Valid values: alpha-numeric characters. For example, 25-3412@172.16.34.10.
   Out Call ID—Search on the SIP call ID of the first routed request.	Enter the ID of the outgoing call (phone number and IP address). Valid values: alpha-numeric characters. For example, 14-3412@172.14.54.6.
   State (with result code)—Search on the state of the call, as shown in the Summary table.	Enter the status of the call session with the result code for which you want to search. Result codes can range from 1xx to 5xx. For example, terminated-200, or failed-400. Case-sensitive. Valid values: INITIAL—<result code> EARLY—<result code> ESTABLISHED—<result code> TERMINATED—<result code> FAILED—<result code>
   Notable Event—Search on a notable event type that you select from the drop-down list.	Select the notable event that you want to find. Valid values: any event—Search displays any notable event that was stored in memory. short session—Search displays only records that indicate a short-session duration occurred. local rejection— Search displays only records that indicate a local-rejection occurred.
   In Realm—Search the realm from which the initial request was received.	Enter the name of the realm to which the incoming call belongs. Valid values: alpha-numeric characters. For example, access.
   Out realm—Search the realm to which the first routed request was sent.	Enter the name of the realm to which the outgoing call belongs. Valid values: alpha-numeric characters. For example, backbone.
   Destination Agent—Search on the name of the session agent from which the initial request was received.	Enter the name of the session agent (SA) on the incoming call session. Valid values: alpha-numeric characters. For example, SA1.
   Destination Session Agent—Search on the realm to which the first routed request was sent.	Enter the name of the session agent (SA) on the outgoing call session. Valid values: alpha-numeric characters. For example, SA2.
   Ingress Destination Address—Search on the IP address from which the initial request was received.	Enter the source IP address of the SA that accepted the incoming call session. You must enter the IP Address in dotted decimal format (0.0.0.0). For example, 172.45.6.7.
   Egress Destination Address—Search on the IP address to which the initial request was sent.	Enter the destination IP address of the SA that accepted the outgoing call session. You must enter the IP Address in dotted decimal format (0.0.0.0). For example, 172.64.56.7.
   In Network Interface—Search on the IP address on which the initialƒ request was received.	Enter the incoming core network interface that connects the ESBC to your network. You must enter the IP Address in dotted decimal format (0.0.0.0). For example, 192.45.6.7.
   Out Network Interface—Search on the IP address that was the source for the routed request.	Enter the outgoing network interface that connects theESBC to the outside network. You must enter the IP Address in dotted decimal format (0.0.0.0). For example, 192.45.6.8.

2. Click Search.

Monitor and Trace allows you to export Monitor and Trace information to a text file from the Sessions, Registrations, Subscriptions, and Notable Events Reports.

The following list describes the export commands.