001033: *Apr 27 14:29:25.

867: %IPPHONE-6-REG_ALARM: NAME=SEP000A10000075 Load=

P00308000500 Parms=Status/IPaddr Last=CM-closed-TCP
Note that sequence numbers are written after
rate-limiting, so they won't be useful to identify if IOS is dropping debugs bef
ore writing them to the buffer log.
voice iec syslog- This command prints out extra information in scenarios where t
he router is the origin of a disconnect. This is specific to voice, and is usef
ul to TAC engineers.
%VOICE_IEC-3-GW: C SCRIPTS: Internal Error (Incompatible protocols): IEC=1.1.47.
11.23.0 on callID 31102
The ouput can be decoded with:
Router# show voice iec description 1.1.47.11.23.0
IEC Version: 1
Entity: 1 (Gateway)
Category: 47 (no resource (47))
Subsystem: 11 (C SCRIPTS)
Error: 23 (Incompatible protocols)
Diagnostic Code: 0
How do I run these debugs?
Once you have the debugs setup, enable the relevant debugs which have been reque
sted to you by the TAC engineer, CSC member, or via the Multiservice Voice Debug
Lookup tool.
What debugs should I be running?
While we are talking about how to collect debugs, you may wonder what debugs you
should collect to troubleshoot your call issues. We have a very useful tool to
assist you with this, called the Multiservice Voice Debug Lookup.
Personally, here is what I like to collect as a starting point for the common ca
ll failures across IOS gateways:
H.323
debug voip ccapi inout
debug h225 asn1
debug h245 asn1
debug cch323 all
debug ip tcp transaction
SIP
debug voip ccapi inout
debug ccsip messages
debug voip rtp session named-event

MGCP
debug voip ccapi inout
debug mgcp packet
debug ip tcp transaction
<Be sure to enable appropriate POTS debugs, too.>
ISDN
debug voip ccapi inout
debug isdn q931
Analog or Non-ISDN POTS
debug voip ccapi inout
debug vpm signal