Monitoring Panes:
EMS Configuration
Click on Dialogic IMG EMS in the Configuration Tree to see the EMS Configuration pane.
IMG Configuration
Click on an IMG entry in the Configuration Tree to see the IMG Configuration pane which includes the following information pertaining to the IMG, including Serial Number, Software Version, VoIP Module Status, and Connection State.
CIC Status
Click on Circuit Group entry in an SS7 Channel Group to see the Status pane for the CIC, which includes the following
SS7 Link Info
IP Bearer Profile Info
Click on an IP Bearer Profile in the Configuration Tree to see the Info Pane showing information for all of the entries in the profile.
Route Table Info
Click on a Route Table entry in the Configuration Tree to see the Status Pane for the table, showing all of the entries in the table with their configuration settings.
Route List Info
Click on a Route List in the Configuration Tree to see the Info pane, which shows all of the Channel Groups included in the route list.
To view the Status pane for the Route List, click the Status pane.
Translation Table Info
Click on a Translation Table entry in the Configuration Tree to see the Info Pane for the table, which shows the configuration information for all of the entries in the table.
Vocabulary Index File Info
Click on a Vocabulary Index File entry in the Configuration Tree to see the Info Pane which shows all of the voice files included in the VIF with their configuration settings.
RCOMM Object Table
The object table was added for software 10.5.0 but the Events below are in both 10.3.3 and 10.5.0
On the right side of ClientView at the bottom is the Object Table Tab. When selected it displays IP address and RCOMM information. Below is screen capture of what the table looks like.
This Table shows the Node ID, what the IP Address of that node is and its RCOMM Connection State information. RCOMM is signaling that occurs between each of the IMG nodes within a Logical Node Group. An example of RCOMM signaling is when there is a master SS7 node that controls CIC's on other remote nodes. The RCOMM signaling is what accomplishes this.
Within the table above the RCOMM Connection fields have different events. In the example above it shows RCOMM with an event of 0x02. This is a normal state. Below is a table of the different events and what they mean.
Event 0x00 | Link Deactivated |
Event 0x01 | Establishing_Link |
Event 0x02 | LINK_UP |
Event 0x03 | LINK_DOWN |
Event 0x04 | REMOTE_NODE_REMOVED |
Event 0x05 | REMOTE_NODE_ADDED |
Event 0x06 | REMOTE_SYS_BUSY =6 |
Event 0x07 | REMOTE_SYS_NOT_BUSY |
Event 0x08 | RCOMM_INITIALIZED |
Event 0x09 | LINK_UNRESPONSIVE |
Notes:
REMOTE_SYS_BUSY/NOT_BUSY is generated when there is congestion on one of the remote links.
LINK_DOWN is generated when there is no system software on IMG
LINK_UNRESPONSIVE is generated when the Master node stops hearing from any other node for at least 300 ms.
LINK_UNRESPONSIVE is generated between the LINK_DOWN and the LINK ESTABLISHING states.