Step 1
|
show
sccp
Before the start of a call, use the show sccp command to verify that the MTP or transcoder device is successfully registered with Cisco Unified Communications Manager:
Example:
Router# show sccp
SCCP Admin State: UP
Gateway IP Address: 192.168.20.1, Port Number: 0
IP Precedence: 5
User Masked Codec list: None
Call Manager: 192.168.20.11, Port Number: 2000
Priority: N/A, Version: 5.0.1, Identifier: 3
Call Manager: 192.168.20.12, Port Number: 2000
Priority: N/A, Version: 5.0.1, Identifier: 1
Call Manager: 192.168.20.13, Port Number: 2000
Priority: N/A, Version: 5.0.1, Identifier: 2
.....
Software MTP Oper State: ACTIVE - Cause Code: NONE
Active Call Manager: 192.168.20.12, Port Number: 2000
TCP Link Status: CONNECTED, Profile Identifier: 10
Reported Max Streams: 1004, Reported Max OOS Streams: 0
Supported Codec: pass-thru, Maximum Packetization Period: N/A
Supported Codec: g711ulaw, Maximum Packetization Period: 30
Supported Codec: rfc2833 dtmf, Maximum Packetization Period: 30
RSVP : ENABLED
|
Step 2
|
show
sccp
connections
During the call, use the show sccp connectionscommand to display information about the active SCCP connections established for the call, the DSP farm service type (MTP or transcoding), codec (for example, pass-through or g711ulaw), and remote end information:
Example:
Router# show sccp connections
sess_id conn_id stype mode codec ripaddr rport sport
17537646 19438263 mtp sendrecv pass_th 192.168.20.5 35548 16576
17537646 19438260 mtp sendrecv pass_th 192.168.22.1 16832 19164
Total number of active session(s) 1, and connection(s) 2
|
Step 3
|
show
sccp
connections
details
Use the show sccp connections details command to display details about active SCCP connections, including the internal call leg ID:
Example:
Router# show sccp connections details
bridge-info(bid, cid) - Normal bridge information(Bridge id, Calleg id)
mmbridge-info(bid, cid) - Mixed mode bridge information(Bridge id, Calleg id)
sess_id conn_id call-id codec pkt-period type bridge-info(bid, cid) mmbridge-info(bid, cid)
17537646 - 326 N/A N/A swmtpmsp All RTPSPI Callegs N/A
17537646 19438263 324 pass_th 20 rtpspi (221,326) N/A
17537646 - 326 N/A N/A swmtpmsp All RTPSPI Callegs N/A
17537646 19438260 325 pass_th 20 rtpspi (222,326) N/A
Total number of active session(s) 1, connection(s) 2, and callegs 4
|
Step 4
|
show
sccp
connections
rsvp
Use the show sccp connections rsvp command to display information about the active RSVP reservations for the call:
Example:
Router# show sccp connections rsvp
sess_id conn_id rsvp_id dir local ip :port remote ip :port
17537646 19438260 -244 SEND 192.168.20.1 :19164 192.168.22.1 :16832
17537646 19438260 -245 RECV 192.168.20.1 :19164 192.168.22.1 :16832
Total active sessions 1, connections 2, rsvp sessions 2
|
Step 5
|
show
ip
rsvp
installed
Use the show ip rsvp installed command to see that the RSVP reservation is successfully made and to display the reserved bandwidth for the call:
Example:
Router# show ip rsvp installed
RSVP: Loopback0 has no installed reservations
RSVP: FastEthernet0/0 has no installed reservations
RSVP: Serial0/0
BPS To From Protoc DPort Sport Weight Conversation
80K 192.168.22.1 192.168.20.1 UDP 16832 19164 25 265
RSVP: FastEthernet0/1 has no installed reservations
RSVP: Serial0/1 has no installed reservations
|
Step 6
|
show
sccp
statistics
Use the show sccp statisticscommand to display the SCCP messages exchanged between the RSVP agent and Cisco Unified Communications Manager:
Example:
Router# show sccp statistics
SCCP Application Service(s) Statistics:
Profile Identifier: 10, Service Type: Software MTP
TCP packets rx 9, tx 6
Unsupported pkts rx 0, Unrecognized pkts rx 0
Register tx 0, successful 0, rejected 0, failed 0
KeepAlive tx 1, successful 1, failed 0
OpenReceiveChannel rx 2, successful 2, failed 0
CloseReceiveChannel rx 0, successful 0, failed 0
StartMediaTransmission rx 2, successful 2, failed 0
StopMediaTransmission rx 0, successful 0, failed 0
PortReq rx 1
PortRes tx 1, successful 1, failed 0
PortClose rx 0
QosListen rx 1
QosPath rx 1
QosTeardown rx 0, send 0, recv 0, sendrecv 0
QosResvNotify tx 2, send 2, recv 0, sendrecv 0
QosErrorNotify tx 0, send 0, recv 0, sendrecv 0
err0 0, err1 0, err2 0, err3 0, err4 0, err5 0,
err6 0, err7 0, err8 0, err9 0, err10 0, err11 0,
QosModify rx 1, send 0, recv 1, sendrecv 0
UpdateDscp rx 0
Reset rx 0, successful 0, failed 0
MediaStreamingFailure rx 0
Switchover 0, Switchback 0
|
Step 7
|
debug
sccp
all
Use the debug sccp all command to display the sequence of the SCCP messages. The message sequence may be different if the RSVP policy defined in Cisco Unified Communications Manager is not set to mandatory.
Example:
Router# show sccp statistics
Router# show log | incl (rcvd | txed)
Feb 4 20:28:41.791: sccp_parse_control_msg: rcvd KeepAliveAckMessage msg
Feb 4 20:28:41.803: sccp_parse_control_msg: rcvd KeepAliveAckMessage msg
Feb 4 20:28:41.815: sccp_parse_control_msg: rcvd KeepAliveAckMessage msg
Feb 4 20:28:55.647: sccp_parse_control_msg: rcvd PortReq msg
:
Feb 4 20:28:55.647: sccp_send_port_res: PortRes
msg txed in hex(including header) - len 36
Feb 4 20:28:55.651: sccp_parse_control_msg: rcvd QosPath
msg:
Feb 4 20:28:55.651: sccp_parse_control_msg: rcvd QosListen
msg:
Feb 4 20:28:55.675: sccp_send_qos_resv_notify: QosResvNotify
txed in hex(including header) - len 36
Feb 4 20:28:57.706: OpenReceviceChannel
msg rcvd in hex -
Feb 4 20:28:57.710: sccp_open_receive_chnl_ack: OpenRecvChnlAck
msg txed in hex(including header) - len 32
Feb 4 20:28:57.714: OpenReceviceChannel
msg rcvd in hex -
Feb 4 20:28:57.718: StartMediaTrans
msg rcvd in hex -
Feb 4 20:28:57.726: sccp_open_receive_chnl_ack: OpenRecvChnlAck
msg txed in hex(including header) - len 32
Feb 4 20:28:57.866: StartMediaTrans
msg rcvd in hex -
Feb 4 20:28:57.870: sccp_parse_control_msg: rcvd QosModify
msg:
Feb 4 20:28:57.878: sccp_send_qos_resv_notify: QosResvNotify
txed in hex(including header) - len 36
|
Step 8
|
debug
call
rsvp-sync
{events | func-trace}
Use the debug call rsvp-sync event and debug call rsvp-sync func-trace with the debug sccp all command to show how SCCP messages and RSVP events trigger each other.
|
Step 9
|
debug
voip
ccapi
inout
Use the debug voip ccapi inoutcommand to trace the execution path through the call control application programming interface (API).
|