Troubleshooting guide

B-8
Cisco PGW 2200 Softswitch Release 9.8 Operations, Maintenance, and Troubleshooting Guide
OL-0800-14
Appendix B Troubleshooting Cisco ITP-L Signaling
Troubleshooting SS7 Link Problems
Table B-2 Debug Outputs, Probable Causes, and Recovery Actions (ANSI SS7)
Debug Output Probable Cause Recovery Action
No output MTP2 is not started. 1. Check that term monitor is
on.
2. Reload the Cisco ITP-L.
3. Cross check configuration
files.
15:08:31: MTP2 incoming trace enabled on channel 0.
15:08:31: MTP2 outgoing trace enabled on channel 0.
15:08:34: ---- Outgoing Rudp msg (41 bytes) ----
SM_msg_type 0x00008000
protocol_type 0x0001
msg_ID 0x0000
msg_type 0x0011
channel_ID 0x0000
bearer_ID 0x0000
length 0x0019
data 0xB2236ED6 0x006FD600 0x11F01122 0x33445566
0x778899AA 0xBBCCDDEE
15:08:34: ---- Incoming Rudp msg (41 bytes) ----
SM_msg_type 0x00008000
protocol_type 0x0001
msg_ID 0x0000
msg_type 0x0010
channel_ID 0x0000
bearer_ID 0x0000
length 0x0019
data 0xB2006FD6 0x236ED600 0x21F01122 0x33445566
0x778899AA 0xBBCCDDEE
Cisco PGW 2200 Softswitch
is exchanging messages with
remote STP.
Exchanged point codes must
match before
communication can be
established successfully.
Checkpoint codes: in data
0xB2236ED6 0x006FD6:
1. 236ED6 should be read
D6-6E-23 and converted in
decimal: 214-110-035, which
is the point code of the Cisco
PGW 2200 Softswitch.
2. 006FD6 should be read
D6-6F-00 and converted in
decimal: 214-111-000, which
is the point code of the STP
in this example.
The values in the incoming
and outgoing messages must
match.