Troubleshooting guide

B-16
Cisco PGW 2200 Softswitch Release 9.8 Operations, Maintenance, and Troubleshooting Guide
OL-0800-14
Appendix B Troubleshooting Cisco ITP-L Signaling
Troubleshooting Cisco ITP-L to Cisco PGW 2200 Softswitch Communications
Identifying IP Communication Problems
ITP-L traffic is routed, rerouted, and (if necessary) retransmitted to the Cisco PGW 2200 Softswitches
through the LAN switches. Monitor the following Internet Control Message Protocol (ICMP)
error-reporting datagrams to help identify IP communication problems:
• Destination Not Reachable/No Echo Reply
• Source Quench/Receiving Buffer Congestion
• Redirection Required
• Time to Live Exceeded
• Parameter Problems
• Timestamp Request/Reply
• Echo Request/Reply
If IP communication is good, the RUDP application layer software could be the cause of the problem.
You should be able to use echo and timestamp request messages and monitoring response messages to
identify RUDP, IP, or Ethernet communication problems within the system.
Identifying RUDP Communications Problems
You can use the following command to discover a reason for RUDP communication problems:
debug ss7 sm session
ses_num
Where ses_num is the number of the affected session.
The system returns a response like the following:
SM: Failed to open session[0], return code = ‘ x ’
Where x is the RUDP return code. The valid value is an integer from 1 through 14. These return codes
are defined as follows:
• 1—RUDP_OPTION_NOT_SUPPORTED
• 2—RUDP_NOT_READY
• 3—RUDP_CONNREC_RESOURCE_UNAV
• 4—RUDP_BUFFER_RESOURCE_UNAVAIL
• 5—RUDP_EVENT_RESOURCE_UNAVAIL
• 6—RUDP_EVENT_ENQUEUE_FAILED
• 7—RUDP_INVALID_CONN_HANDLE
• 8—RUDP_BUFFER_TOO_LARGE
• 9—RUDP_EMPTY_SEND_BUFFER
• 10—RUDP_CONNECTION_NOT_OPEN
• 11—RUDP_SEND_WINDOW_FULL
• 12—RUDP_REMOTE_PORT_REQUIRED
• 13—RUDP_REMOTE_ADDRESS_REQUIRED
• 14—RUDP_LOCAL_PORT_IN_USE