SIP Monitor and Trace operations allow the Oracle® Enterprise Session Border Controller (E-SBC) 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 E-SBC to capture SIP Monitor and Trace data for display in the Web GUI.

The E-SBC 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 E-SBC sends the message on egress, the E-SBC applies the SPL, applies the HMR, and sends out the captured SIP message.

The SIP Notable Events Summary contains all logged sessions that have a notable event on the Oracle® Enterprise Session Border Controller (E-SBC) 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.

The SIP Registrations Summary displays a summary of all logged SIP registrations sessions on the Oracle® Enterprise Session Border Controller (E-SBC). 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 Sessions Summary is a SIP session summary of all logged call sessions on the Oracle® Enterprise Session Border Controller (E-SBC). 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 Subscriptions Report displays a summary of all logged SIP subscription sessions on the Oracle® Enterprise Session Border Controller (E-SBC). 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 Subscriptions Report page.

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 (E-SBC), which can help you with troubleshooting efforts. The Web GUI can display a ladder diagram for each of the summary reports available through Monitor and Trace.

To display a ladder diagram for a specific record in a Summary Report, select a record in the summary table and right-click. Click Ladder diagram on the pop-up menu. Each ladder diagram contains the following sections.

• Session Summary—Displays session data. Use the [+] and [-] controls to toggle between show and hide.
• Ladder Diagram—Displays SIP message and call flow information. Hover over a line in the ladder diagram to see more information for the highlighted flow.
• QoS Statistics—Displays Quality of Service (QoS) information. Use the [+] and [-] controls to toggle between show and hide.

The following illustration shows an example of an E-SBC ladder diagram, and how you can make it display more information.

The following table describes the additional controls on a Ladder Diagram page.

	Refreshes the data on the page.
	Exports all of the information in the Ladder Diagram (Session Summary, SIP Message Details, and QoS Statistics) to a file in text format on the local machine.
	Exports detailed information about the SIP messages and media events associated with the session in focus to a file in text format on the local machine.
	Closes the Ladder Diagram page.

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.

The Search button at the top of the report page allows you to find a specific record within a Monitor and Trace report. It also allows you to specify criteria on which to perform 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 are 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 E-SBC in the FROM header. Valid values are 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 E-SBC in the REQUEST header. Valid values are alpha-numeric characters. For example, sip:service@172.16.34.226:5060.
   To URI—Search on the To-URI header.	Enter URI formatted string of the call destination information you are searching. Valid values are 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 are 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 value are 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 are 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 value are 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 are 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 are 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 are 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 include: 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 for which you want to search. Valid values include: any event—search displays any notable event that was stored in memory. hort session—search displays only records that indicate a short-session duration has occurred. local rejection— search displays only records that indicate a local-rejection has occurred.
   In Realm—Search the realm from which the initial request was received.	Enter the name of the realm for which the incoming call belongs. Valid values are 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 for which the outgoing call belongs. Valid values are 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 are 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 are 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. IP Address must be entered 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. IP Address must be entered 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 Net-Net ECB to your network. IP Address must be entered 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 your Net-Net ECB to the outside network. IP Address must be entered in dotted decimal format (0.0.0.0). For example, 192.45.6.8.

2. Click Search.

Monitor and Trace allows you to export information to a text file from the Sessions, Registrations, Subscriptions and Notable Events Reports, as well as from a specific ladder diagram, or from a page containing the results of a search. The system exports data to a file that you can open and view as required.

You can export any of the following:

• All information from each report
• Information from a specific record only
• Information from a search result
• Information from a Ladder Diagram

The following list identifies the buttons to use to export specific information from Monitor and Trace. All the export buttons in the GUI export to text files.

	Exports the SIP messages and media events associated with the selected session, to a file in text format on the local machine.
	Exports all logged session summary records to a file in text format on the local machine. Note: This button exports ALL call session summary records or the records that matched a search criteria to the file.
	Exports all of the information in the Ladder Diagram (Session Summary, SIP Message Details, and QoS statistics), to an HTML file format on the local machine.
	Exports detailed information about the SIP messages and media events in the Ladder Diagram associated with the selected session, to a file in text format on the local machine.

The License widget on the Web GUI provides a workspace where you can view, add, and delete Oracle® Enterprise Session Border Controller (E-SBC) licenses.

From the Widgets tab on the Web GUI, the system displays the Licenses page when you click Widgets, System, Licences.

If you want to see the details of a particular license, click the show-hide toggle by the license name to expand the view to show all of the details. The following illustration shows an example of license details.

The Licenses widget provides the controls to Add and Delete licenses.

When you click Add, the system displays the Set license dialog.

When you select a license from the Licenses list and click Delete, the system displays the delete Confirmation dialog.

The License widget includes the Refresh, Download, Add to Dashboard, Pin to Favorites, and Help icons, familiar from other widgets, in the top, right-hand corner. Note that the License widget does not include the Settings icon and the Auto-refresh function because these operations do not apply to licenses.

The Set License wizard is linked to the License widget, so that you can view your licences from the wizard. After launching the Set License wizard, use the "View current license information" link in the Set License dialog to see a view-only list of your E-SBC licenses.

The only operations allowed in view mode are Refresh and Download.