1. Access Notable Events: Monitoring, Monitor and Trace, Notable Events.
2. Use the controls on the page to view information about the records in this report.

1. Access Registrations: Monitoring, Monitor and Trace, Registrations.
2. Use the controls on the page to view information about the records in this report.

1. Access SIP Session Summary: Monitoring, Monitor and Trace, Sessions.
   The system displays the SIP Sessions Summary page.
2. Use the controls on the page to manage the records in the report.

1. Access Subscriptions: Monitoring, Monitor and Trace, Subscriptions.
2. Use the controls on the page to view information about the records in this report.

You can display a ladder diagram of call and media flow from any of the Monitor and Trace summary pages in the Web GUI. Each summary page displays a table, where each row represents one session. You can view a ladder diagram for each session with the following procedure.

1. Access a Summary: Monitoring, Monitor and Trace.
2. Under Monitor and Trace, select one of the following summaries:
   • Notable Events
   • Registrations
   • Sessions
   • Subscriptions
3. On the Summary page, select a row in the table and right-click.
4. On the pop-up menu, click Ladder Diagram.
5. (Optional)—On the ladder diagram, click the [+] to expand the Session Summary and QoS Stats sections.

To see a Session Summary, open a ladder diagram from a record in a Summary report and click the [+] control that precedes "Session Summary" at the top of the page. Monitor and Trace displays the session data and statistics.

The following screen capture shows a sample Session Summary page generated from a selected item on a ladder diagram.

The Quality of Service (QoS) Stats section of the Session Summary displays information about the quality of the service for a selected call session or media event. To see the QoS statistics, open a ladder diagram from a record in a Summary report and click the [+] control that precedes "QoS Statistics" at the bottom of the page.

Expand QoS Stats section with the [+} control.

The following table describes each column in the QoS Stats report.

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

1. In the Session Id field, 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.
2. In the In Call ID field, 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.
3. In the Out Call ID field, 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.
4. In the State (with result code) field, enter the status of the call session with the result code for which you want to search. Valid values are (case-sensitive):

   • INITIAL-<result code>

   • EARLY-<result code>

   • ESTABLISHED-<result code>

   • TERMINATED-<result code>

   • FAILED-<result code>

     Result codes can range from 1xx to 5xx. For example, terminated-200, or failed-400.

5. In the Notable Event field, select the notable event for which you want to search. Valid values are:

   • any-event - search displays any notable event that was stored in memory.

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

6. To search on additional parameters, click on the Additional Search Options down arrow to expand the dialog box.

1. In the “In Realm” field, enter the name of the realm for which the incoming call belongs. Valid values are alpha-numeric characters. For example, access.
2. In the “Out Realm” field, enter the name of the realm for which the outgoing call belongs. Valid values are alpha-numeric characters. For example, backbone.
3. In the “In SA” field, enter the name of the session agent (SA) on the incoming call session. Valid values are alpha-numeric characters. For example, SA1.
4. In the “Out SA” field, enter the name of the session agent (SA) on the outgoing call session. Valid values are alpha-numeric characters. For example, SA2.
5. In the “In Source Addr” field, 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.
6. In the “Out Dest Addr” field, 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.
7. In the In Network Interface field, 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.
8. In the Out Network Interface field, 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.
9. Click <Search> to perform the search with the values you specified. A list of the records that the search process filtered, display in the window. The GUI saves the search specifications until you click <Reset> in the search dialog box, OR until you log out of the GUI.

1. Access Monitor and Trace: Monitoring, Monitor and Trace.
2. On the Monitor and Trace page, select a report type. For example, Subscriptions.
3. On the report Summary page, select a report from the list, right-click, and do one of the following:
   • Click Export session details.
   • Click Export summary.
4. In the SessionDetails.txt or SummaryExport.txt dialog, do one of the following:
   • Click Open with, and select the application with which to open the resulting text file.
   • Click Save file to save the text file to your local PC.
5. Click OK to export the report information.