User guide

C-67
Cisco Media Gateway Manager 5.0 User Guide
OL-5461-02
Appendix C Troubleshooting
Connection Management Problems
This section includes the following information:
• C.9.1.1 Connections Tab—Double Click on a Tree View Does not Launch Connection's Internal
Frame
• C.9.1.2 Connections Tab—Drag and Drop Does Not Launch Connection's Internal Frame
• C.9.1.3 Connection List Tab—Cannot Launch Internal Frame To Modify An Existing Connection
(Using the Modify Button)
• C.9.1.4 Advanced Mode Tab—Cannot Launch Connection Details Dialog (Using the 'Detail'
Button)
• C.9.1.5 Advanced Mode Tab—Cannot Launch Template Details Dialog (Using the 'Template
Details' Button)
• C.9.1.6 Cross Application—Cannot Launch Other Application from Connection List
• C.9.1.7 Cross Application—Connection List as Drag Source
• C.9.1.8 Cross Application—Connection Tab's Content Pane as Drop Target
• C.9.1.9 Configuration Center's Connection Tab Does Not Respond (GUI Is Grayed-Out)
C.9.1.1 Connections Tab—Double Click on a Tree View Does not Launch Connection's Internal
Frame
The double click operation on a network element in the Tree View on Connection tab (a) fails to open
an internal frame, (b) fails to recycle the contents of an existing internal frame to display the double
clicked connections attributes or (c) results in the 'Operation Not Supported' message dialog box.
Step 1 Determine that the double click operation is supported for the selected object
The 'Connection tab' supports connection management for the Node, Card, Line and Port objects. The
for connect 'Folder', IMA and IMA link objects are not supported.
Defect Information—Collect the following information for further analysis:
• Collect CMSCclient.log file under the D:\Documents and Settings\username\log directory.
• Collect Java Console information (In particular any java raised exceptions).
• Collect screen snapshots. In particular, error/information message dialog boxes.
• Collect cmsvr.log file under the /opt/svplus/log directory.
• Collect configserver.log file under the /opt/svplus/log directory.
Possible alternative workaround—None