Currently, the Operations Monitor 5.0 Release supports only English language.

When you click an element in the navigation pane, a panel appears in the center of the browser window. This panel is a user interface element that displays data.

Many panels can be added to your dashboard for at-a-glance viewing. For more information, see the Dashboard section.

To collapse panels and display titles only, you can click the angle-bracket in the upper-right hand corner.

Figure 3-2 Panels

Another common user interface element is the tab panel.

Figure 3-3 Tabs Panel

In the title bar of each panel is a ?-symbol. This is the information box. When you hover over the information box, a tooltip provides a brief description of the panel. When you click the ?-symbol, the corresponding section of the user manual appears in a new browser window or tab describing the panel and its functions.

Other user interface elements support tooltips. Hovering over an element with the mouse pointer often brings up a small box explaining the element underneath.

You may encounter modal windows overlaid on the user interface, similar to the windows of your desktop environment. These windows can be dragged by their title bar, and closed by clicking on the x -symbol or pressing the ESC key. These windows also contain Help and Close buttons at the bottom. The Help button opens the online Help in a new window, describing the current page and its functionality.

Some areas of the interface contain a Refresh button that controls the update interval for the content of the page, panel, or section. It is identified by a circle of dots (flashing during refresh). Click the button once to refresh the corresponding content. It also contains a drop-down list to set the interval for the Auto Refresh.

Figure 3-4 Refresh Panel Data

Some tables such as Calls, Registrations support the Filters feature. If a table column can be filtered, the Filter button is visible on the table menu bar.

Figure 3-5 Filters

You can choose to hide certain columns in each table. Click the Set Columns button to see a list of all available columns for this table. Select or deselect the check box to the left of each entry to show or hide the corresponding column.

Note the paging toolbar at the bottom of tables. The presence of this toolbar means that the table offers page-wise access to its data:

Figure 3-6 Paging Toolbar

• Click Now to show current data.
• Click Auto Refresh to toggle auto refresh to On or Off. The Auto Refresh button displays animation to indicate that the data is being refreshed.
• Click the Calendar control to show data for a specific date.
• Click the Next or Previous button to go to the next or previous page.
• Click Stop to stop the loading data into the table.

Tables such as Recent calls, Registrations, and the user table in User Devices have context menu entries to quickly trace or track a user. You can right-click on a table row to track or trace the user (in the Recent calls table, you can quickly inspect both the caller and the callee). For more information, see the Recent Calls, Registrations, and User Devices sections.

Figure 3-7 Context Menu for Calls

To pan the chart: click Right scroll or Left scroll buttons and drag. When you click Right scroll, the visible area is shifted further left (further in the past) on the time line. When you drag it to the left, the visible area is shifted further right (nearer to the present) on the time line.

Click Show Interval in Grid to filter the table to the time interval of the chart

Figure 3-9 Charts

1. In a web browser, log in to Operations Monitor.
   The Operations Monitor window appears.
2. In the navigation pane under Operations , do one of the following:
   • To display a message flow for a call event:
   1. Click Calls.
      The Calls page opens in the main display.
   2. In the Recent calls table, right-click the row for which to display the call event's message flow and select Message flow.

      The Message Flow for Call: caller and callee window appears.

      where caller is the number that initiated the call and callee is the call number that received the call.

      Note:

      Message flows for a call event can also be displayed by right-clicking on the call row and selecting Message flow in the Calls going through this device tab on the Devices page.

      Figure 3-10 Message Flow

      
   • To display a message flow for a registration event:
   1. Click Registrations.
      The Registrations page opens in the main display.
   2. In the Registrations table, select a registration event for which to display a registration message flow.
   3. From the Registrations table tool bar, click the Message flow button.

      The Registration registration_number window appears.

      where registration_number is the number of the registration event.

3. Press the ESC key, which closes the message flow window.

1. Verify that the message flow is displayed.
2. In the message flow window's toolbar, select the View menu.
3. From the View menu, select or de-select one or more of the following check boxes:
4. Enter the text of the second step here.
   • Pin Devices

     When enabled, the devices are always visible at the top of the scrolling area.

   • Unwind messaging

     By default, each network device appears only once and a transaction arrow is drawn for each message that passes between the hosts. When several messages are exchanged between two particular network devices, it becomes difficult to distinguish the call legs. When enabled, each call leg is drawn separately, which results in a wider diagram. Hosts that appear multiple times contain a number suffix, which is the number of times the host appears.

   • Resolve IP addresses

     When enabled, Operations Monitor creates a reverse DNS lookup on the IP addresses of the network devices.

   • Duplicates

     For retransmissions, only one SIP message appears. Enable this option to display all duplicate messages.

   • Transport protocol

     When enabled, the message flow displays the transport protocol (TCP or UDP).

   • IP addresses

     When enabled, the message flow displays the IP addresses for the source and destination of the message.

   • MAC addresses

     When enabled, this option displays the MAC addresses for the source and destination of the message. In a scenario where one server is realized by several machines, this can be used to determine which machine was used to process the request.

   • OPC/DPC

     When enabled, this option displays the originating point code (OPC) and the destination point code (DPC) for the source and destination of the message.

   • Codecs

     When enabled, the message flow displays the media codecs of the caller and the callee. If the codecs are the same for the both the caller and the callee after the INVITE transaction is completed, the codecs are grouped.

   • Absolute Time

     By default, the information below a transaction arrow displays the time that has passed after the first message was seen. When enabled, the date and time are displayed for each transaction arrow.

   • Media

     When enabled, protocol messages for media transport, such as RTP, are displayed in addition to the signal.

     Note:

     For some protocols, the raw message is not available.
   • DTMF Events

     When enabled, protocol messages for RTP events of the type DTMF are visible. The DTMF event will show the name and code of the tone. For tones 0-9 the name and the code are the same.

     DTMF Event '2' (2)
     DTMF Event '#' (11)

     Requires the View DTMF tones permission to be visible. See User Permissions.

   • SIP URIs

     When enabled, the transaction arrows display the recipient's URI.

   • Hide SIP Methods

     This submenu allows you to hide certain types of SIP messages based on their method. For example, enabling OPTIONS will remove all SIP messages from the diagram that have the method OPTIONS.

   • MEGACO

     This submenu allows you to hide selected MEGACO message properties.

5. Press the ESC key, which closes the message flow window.

1. Verify that the message flow is displayed.
2. In the message flow window's toolbar, select the Devices menu.
3. Do one or both of the following:
   • To hide a network device, deselect the check box of the network device you want to hide. Alternatively, select the check box of the network device you want to display.
   • To reposition a device in the sequence diagram, select the check box row of the network device you want repositioned and drag the check box row to the position you require. See the following figure.
4. Press the ESC key, which closes the message flow window.

Figure 3-11 Devices in the Device Map

1. Verify that the message flow is displayed.
2. In the message flow, click the message type you wish to view, which appears above the message transaction arrow.
   The Message transaction_number window appears.

   where transaction_number is the number associated with the order of the transaction between the network devices.

3. (Optional) Resize, or move the protocol message by dragging the title bar of the protocol message's window to the required position within the message flow.
4. When you have finished viewing the protocol message, click the Close icon in the protocol message window's title bar.
5. Press the ESC key, which closes the message flow window.

Figure 3-12 Individual Protocol Message Window

Note:

The maximum number of messages for a flow is limited. You can change the limit value in System Settings. For more information, see "System Settings".

1. Verify that the message flow is displayed.
2. In the message flow, click the message type identified by [1], which appears above the message transaction arrow.
   The Message transaction_number window appears.
3. Scroll down the protocol message until you see the Content-Type header. Do one of the following:
   • If the Content-Type header's value contains either, multipart/mixed and one of the multiple parts is application/ISUP, or application/ISUP, go to step 4.

     For example:

     Content-Type:application/ISUP;boundary=A6B35A2329D0F2312C9F4692

   • If the Content-Type header's value does not contain either, multipart/mixed and one of the multiple parts is application/ISUP, or application/ISUP, close the protocol message and click the next message.
4. Scroll down the protocol message until you see the decode ISUP body link.
5. Click the decode ISUP body link.
   The ISUP binary content is decoded into human readable text and an ISUP message contained in Message transaction_number window appears.
6. When you have finished viewing the ISUP message, click the Close icon in the ISUP protocol message window's title bar.
7. When you have finished viewing the protocol messages, click the Close icon in the protocol message window's title bar.
8. Press the ESC key, which closes the message flow window.

1. Verify that the message flow is displayed.
2. In the message flow window's toolbar, click the Download button.
   The Save As dialog box appears.
3. Browse to the directory in which you want to save the HTML file.
4. (Optional) In the File name text box, enter a file name for the HTML file.
   By default, HTML files are named message-flow.html.
5. Click Save.
6. Press the ESC key, which closes the message flow window.

1. In the navigation pane under Operations, click Calls.
   The Calls page opens in the main display.
2. In the Recent calls table, right-click the row for which to create a call event PDF report file and select PDF report. The Create Report window appears.

   Figure 3-13 Create Report

   
   
   

   By default, few of the Report Content options are enabled as shown in the screenshot options are selected.

3. In the Report Content section, deselect the options you do not require in your report. Do not deselect the Messages option.
4. (Optional) In the Additional Info section's Report Comment (optional) text box, enter information about the report.
5. (Optional) In the Additional Info section's, Filename (optional) text box, enter a file name for the report.

   By default, PDF files are named CallReport- YMDHMS-callid .pdf

   where

   • YMDHMS is the syntax for year, month, day, hour, minutes, and seconds that the file was generated.
   • callid is the call event's identifier.
6. Click the Create button.
   The Save As dialog box appears.
7. Browse to the directory in which you want to save the call event PDF file and click Save.
8. Click the Cancel button, which closes the Create Report window.

You can distinguish between ISUP and BICC messages by the protocol name looking at the Ladder Diagram section.

OCOM supports correlation among BICC, SIP, and ISUP messages. Apps such as Call count, Calls containing keywords, response code search apply to BICC calls in the same way as they apply to ISUP calls. Export of BICC calls is supported.

Limitations: ISUP and BICC protocols have very similar set of messages and hence, in the GUI, there is no way to differentiate ISUP and BICC signaling messages in a correlated call. A distinction between BICC and ISUP calls can be made by looking at the Message Flow information. Here messages are marked as 'ISDN User Part' and 'Bearer Independent Call Control'. There is also a difference in the size of the CIC for a BICC and ISUP message.