Avaya MCC1 Maintenance Procedures page 193

Figure 49: A500:show signaling stats A1.2 q93b
A500:show signaling stats a1.2 q93b
-------------------------Q.93B Statistics------------------------
Port A1.2:
----------
Connect Messages:
Setup Messages:
Release Messages:
Rel Cmplt Messages:
Add Party Messages:
Add Party Acks:
Add Party Rejects:
Drop Party Messages:
Drop Party Acks:
Last Cause Code:
Last Diag Code:
Total Connections:
Current Connections:
NOTE:
If there is no connection between the TN230X and the A500 at the Q93B protocol layer,
then no report displays.
2 Ensure that the fields have the following indicated values.
3 If connections are being rejected, the Last Cause Code may suggest why. The cause code (in
following
port even though the PN port is the one misbehaving, and vice versa.
Enter show signaling cause causecode on the A500 console.
cause 31,
Maintenance Procedures
December 2003
Tx
--------
15
18
17
13
0
0
0
0
0
31
0. 0. 0
33
3
If this field is not configured for UNI signaling,
Port
A1.2 then the port was administered for no UNI signaling (admin
(or the port link command). Use the show signaling summary command
of interest) to verify that Signaling is UNI3.1.
These counters should be non-zero if the A500 is handling
Connect
Q.93B protocol layer messages sent by the PPN and PN. They
Messages
may not increase during troubleshooting unless calls are being
Setup
made, since the PPN initially sets up control connections to the
Messages
PPN and then sets up talk path connections as needed.
Release
Messages
Table 62, Observed cause codes,
on page 194 shows the screen output for this command.
Rx
--------
18
15
13
17
0
0
0
0
0
31
71. 0.29
on page 195) indicating the error may be on the PPN
Figure 50, A500:show signaling
Troubleshooting
Troubleshooting ATM
193