Table Of Contents
Simple Gateway Control Protocol Support on the Cisco MC3810 and Cisco 3600 Series Routers
Supported Standards, MIBs and RFCs
Configuring SGCP Tuning Values
Blocking New Calls and Gracefully Terminating Existing Calls
Verifying the SGCP Configuration
sgcp quarantine-buffer disable
Simple Gateway Control Protocol Support on the Cisco MC3810 and Cisco 3600 Series Routers
This document describes the Simple Gateway Control Protocol feature on the Cisco MC3810 and Cisco 3600 series routers and includes the following sections:
•
Supported Standards, MIBs and RFCs
Feature Overview
Simple Gateway Control Protocol (SGCP) enables intelligent external call agents to control gateways in Voice over IP (VoIP) environments.Gateways include trunking and residential gateways. Call agents include Telecordia SM 1.5 and third-party products. This release supports SGCP Version 1.1+.
SGCP is intended for use in large IP networks typical of competitive local exchange carriers (CLECs) and Internet exchange carriers (IXCs).
Note
Benefits
Provides Alternative Dial Tone for Voice over IP Environments
Deregulation in the telecommunications industry gives CLECs opportunities to provide toll bypass from the Incumbent Local Exchange Carriers (ILECs). One way of providing toll bypass is through Voice over IP (VoIP). SGCP is a call agent protocol that enables a VoIP system to control call setup and teardown as well as CLASS features for less sophisticated gateways.
Removes Configuration Requirement for Static Voice over IP Network Dial Peers
When using SGCP as the call agent in a VoIP environment, configuring static VoIP network dial peers is not required, which simplifies the configuration. The SGCP call agent provides similar functions to VoIP network dial peers.
Note
Restrictions
SGCP CAS PBX trunk gateway is supported only on digital interfaces. Analog interfaces are not supported. On the Cisco 3640 and Cisco 3660 routers, a digital T1 packet voice trunk network module is required.
In addition, the following features are not supported:
•
•
•
•
•
•
•
CautionSGCP 1.1+ does not support SVCs. Voice over ATM SVCs were first supported on the Cisco MC3810 in Cisco IOS Release 12.0(5)XK and 12.0(7)T. If you are upgrading a Cisco MC3810 from IOS release 12.0(5)XK or 12.0(7)T to this release to obtain Voice over IP and SGCP support, you will lose support for your Voice over ATM SVCs.
Related Documents
•
•
•
•
•
Supported Platforms
•
•
•
This feature is not supported on the Cisco 3620.
Supported Standards, MIBs and RFCs
Standards
The following standards are supported:
•
•
MIBs
•
•
For descriptions of supported MIBs and how to use them, see Cisco's MIB web site on Cisco Connection Online CCO at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
RFCs
No RFCs are supported by this feature
Prerequisites
You must complete the following tasks before configuring SGCP on the Cisco MC3810 and Cisco 3600 series routers:
•
•
•
•
Configuration Tasks
This section is divided into the following configuration and verification tasks:
•
•
•
Configuring Support for SGCP
To configure support for SGCP on the router so that the call agent is notified, use the following commands beginning in global configuration mode:
1
Enable the SGCP daemon.
Note
2
ipaddress[:udp port]Configure the call agent's IP address or hostname. You can optionally enter the 16-bit UDP port number. The default UDP port number is 2427.
3
{ca | cisco | nse}(Optional) Enable SGCP modem or fax passthrough. This command is disabled by default.
If you specify the nse value to enable the Named Service Elements (NSE) upspeed option, then you must configure the sgcp tse payload command in the next step. If you do not specify the nse value, skip the next step.
4
type(Optional) Enable Inband Telephony Signaling Events (TSE) for fax/modem operation. The default for the type value is 0 (meaning the command is disabled), and the valid values are between 96 and 119.
5
number potsEnter dial peer configuration mode for the POTS dial peer.
6
SGCPAPPEnable the SGCP application to control the dial peer.
7
Enter controller configuration mode.
Note
8
channel-number timeslots range
type (e&m-immediate | e&m-wink |
fxs-ground-start}Configure the DS0 group for CAS PBX operation.
When configuring SGCP 1.1+ as a Voice over IP call agent, only the e&m-immediate, e&m-wink, and fxs-ground-start options are supported.
Configuring SGCP Tuning Values
To configure settings to tune your SGCP configuration, use the following commands beginning in global configuration mode:
Blocking New Calls and Gracefully Terminating Existing Calls
You can block all new SGCP calls to the router and gracefully terminate all existing active calls. When active calls are gracefully terminated, they are not terminated until a caller hangs up. To block all new calls, use the following commands beginning in global configuration mode:
Disabling SGCP Support
To disable the SGCP daemon and terminate any active calls, use the following commands beginning in global configuration mode:
1
Disable the SGCP daemon and terminate all active calls.
2
Save the configuration file before rebooting the router.
Note
Verifying the SGCP Configuration
To verify your SGCP configuration and obtain SGCP statistics, use the following commands beginning in global configuration mode:
Configuration Example
The following configuration example shows a configuration in which a Cisco MC3810 is sending Voice over IP traffic over ATM with SGCP being used as the call agent. In this configuration, there are three ATM PVCs:
•
•
•
hostname r3810-5!!network-clock base-rate 56kip subnet-zeroip wccp version 2!sgcpsgcp call-agent 1.4.43.1cns event-service servercodec-complexity medium!xgcp snmp sgcp!controller T1 1mode casframing esfclock source internallinecode b8zsds0-group 1 timeslots 1 type e&m-wink-startds0-group 2 timeslots 2 type e&m-wink-start!controller T1 0framing esflinecode b8zsmode atm!!interface Loopback1ip address 1.7.43.4 255.255.0.0no ip directed-broadcast!interface Ethernet0ip address 1.5.43.4 255.255.0.0no ip directed-broadcastno ip mroute-cache!interface Serial0bandwidth 1300no ip addressno ip directed-broadcastno ip mroute-cacheshutdownno fair-queuehold-queue 4096 out!interface Serial1no ip addressno ip directed-broadcastno ip route-cacheno ip mroute-cacheshutdown!interface ATM0no ip addressno ip directed-broadcast!interface ATM0.701 point-to-pointdescription data channelip address 173.1.101.2 255.255.255.0no ip directed-broadcastpvc data 1/101encapsulation aal5snap!!interface ATM0.801 point-to-pointdescription SGCP signaling channelip address 173.1.102.2 255.255.255.0no ip directed-broadcastpvc signal 1/102ubr-nrt 64 64encapsulation aal5snap!!interface ATM0.901 point-to-pointdescription bearer channelip address 173.1.103.2 255.255.255.0no ip directed-broadcastpvc bearer 1/103vbr-rt 900 900encapsulation aal5snap!!interface Switch0no ip addressno ip directed-broadcastencapsulation frame-relayno fair-queueshutdown!interface FR-ATM20no ip addressno ip directed-broadcastshutdown!ip classlessip route 1.4.0.0 255.255.0.0 173.1.102.2ip route 1.6.0.0 255.255.0.0 173.1.101.2ip route 1.8.0.0 255.255.0.0 173.1.103.2no ip http server!!!line con 0transport input noneline aux 0line 2 3line vty 0 4login!voice-port 1:1!voice-port 1:2!!dial-peer voice 20 potsapplication SGCPAPPport 1:1!dial-peer voice 21 potsapplication SGCPAPPport 1:2Command Reference
This section documents new or modified commands. The following new and modified commands are described in this section. Modified commands are marked by an asterisk. All other commands used with this feature are documented in the Cisco IOS Release 12.0 command references. For new and modified debug commands, see "Debug Commands" on page 48.
application*
clear sgcp statistics*
dial-type*
ds0-group*
sgcp*
sgcp*
sgcp call-agent*
sgcp graceful-shutdown*
sgcp max-waiting-delay*
sgcp modem passthru
sgcp quarantine-buffer disable
sgcp request retries*
sgcp request timeout*
sgcp restart
sgcp retransmit timer*
sgcp timer*
sgcp tse payload
show sgcp connection*
show sgcp endpoint*
show sgcp statistics*
voice-group*In Cisco IOS Release 12.0(1)T or later, you can search and filter the output for show and more commands. This functionality is useful when you need to sort through large amounts of output, or if you want to exclude output that you do not need to see.
To use this functionality, enter a show or more command followed by the "pipe" character (|), one of the keywords begin, include, or exclude, and an expression on which you wish to search or filter:
command | {begin | include | exclude} regular-expression
Following is an example of the show atm vc command in which you want the command output to begin with the first line in which the expression "PeakRate" appears:
show atm vc | begin PeakRate
For more information on the search and filter functionality, refer to the Cisco IOS Release 12.0(1)T feature module titled CLI String Search.
application
To enable a specific application on a dial-peer, use the application dial-peer configuration command. To remove the application from the dial-peer, use the no form of this command.
application name
no application nameSyntax Description
Default
No default behavior or values.
Command Mode
Dial-peer configuration
Command History
Usage Guidelines
Enter the SGCPAPP application in upper-case characters. This application can only be applied to POTS dial peers. Note that SGCP dial peers do not use dial-peer hunting.
Note
Example
The following example shows how to apply the SGCP application to a dial peer:
Router(config)# dial-peer voice 1 potsRouter(config-dial-peer)# application SGCPAPPRelated Commands
Starts and allocates resources for the SCGP daemon.
Defines the IP address of the default SGCP call agent.
clear sgcp statistics
To clear all SGCP statistics, use the clear sgcp statistics EXEC command.
clear sgcp statistics
Syntax Description
This command has no arguments or keywords.
Default
No default behavior or values.
Command Mode
EXEC
Command History
Example
The following example clears all SGCP statistics:
MC3810#clear sgcp statisticsMC3810#Related Commands
dial-type
To specify the type of out-dialing for voice port interfaces, use the dial-type voice-port configuration command. Use the no form of this command to disable the selected type of dialing.
dial-type {dtmf | pulse | mf}
no dial-typeSyntax Description
Default
dtmf
Command Mode
Voice-port configuration
Command History
11.3(1)T
This command was introduced.
11.3(1) MA3
The pulse-dialer option was added.
12.0(7)XK
The mf option was added.
Usage Guidelines
Use the dial-type command to specify an out-dialing type for an FXO or E&M voice port interface; this command is not applicable to all voice ports because the ports do not generate out-dialing. Voice ports can always detect dtmf and pulse signals. This command does not affect voice port dialing detection.
The dial-type command affects out-dialing as configured for the dial peer.
The dial-type command is not supported on FXO voice port interfaces on the Cisco MC3810. If you are using the dial-type command with E&M wink-start, use the mf option.
SGCP 1.1+ does not support pulse dialing.
Examples
The following example configures a voice port on the Cisco MC3810 to support a rotary (pulse tone) dialer:
Router(config)# voice-port 1/1Router(config-voice-port)# dial-type pulseThe following example configures a voice port on the Cisco MC3810 to support a DTMF (touch-tone) dialer:
Router(config)# voice-port 1/1Router(config-voice-port)# dial-type dtmfThe following example configures a voice port on the Cisco MC3810 to support a Multifrequency Tone dialer:
Router(config)# voice-port 1/1Router(config-voice-port)# dial-type mfRelated Commands
ds0-group
To specify the DS0 timeslots that make up a logical voice port on a T1 or E1 controller, and to specify the signaling type, use the ds0-group controller configuration command. Use the no form of the command to remove the DS0 group and signaling setting.
ds0-group ds0-group-no timeslots timeslot-list type signal-type
no ds0-group ds0-group-no
Syntax Description
Default
No DS0 group is defined.
Command Mode
Controller configuration
Command History
Usage Guidelines
The ds0-group command automatically creates a logical voice port that is numbered as follows:
Cisco 2600 and 3600 series:
slot/port:ds0-group-no.
Cisco MC3810:
slot:ds0-group-no
On the Cisco MC3810, the slot number is the controller number. Although only one voice port is created for each group, applicable calls are routed to any channel in the group.
Examples
The following example configures ranges of T1 controller timeslots for FXS ground-start and FXO loop-start signaling on a Cisco 2600 or 3600 Series router:
Router(config)# controller T1 1/0Router(config-controller)# framing esfRouter(config-controller)# linecode b8zsRouter(config-controller)# ds0-group 1 timeslot 1-10 type fxs-ground-startRouter(config-controller)# ds0-group 2 timeslot 11-24 type fxo-loop-startThe following example configures DS0 groups 1 and 2 on controller T1 1 on the Cisco MC3810 to support Transparent CCS:
Router(config)# controller T1 1Router(config-controller)# mode ccs cross-connectRouter(config-controller)# ds0-group 1 timeslot 1-10 type ext-sigRouter(config-controller)# ds0-group 2 timeslot 11-24 type ext-sigRelated Commands
sgcp
To start and allocate resources for the SGCP daemon, use the sgcp global configuration command. Use the no form of this command to terminate all calls, release all allocated resources, and kill the SGCP daemon.
sgcp
no sgcpSyntax Description
This command has no arguments or keywords.
Default
The SGCP daemon is not enabled.
Command Mode
Global configuration
Command History
Usage Guidelines
When the SGCP daemon is not active, all SGCP messages are ignored.
When you enter the no sgcp command, the SGCP process is removed.
Note
Examples
The following example enables the SGCP daemon:
Router(config)# sgcpThe following example disables the SGCP daemon:
Router(config)# no sgcpRelated Commands
sgcp call-agent
To define the IP address of the default SGCP call agent in the router configuration file, use the sgcp call-agent global configuration command. Use the no form of this command to remove the IP address of the default SGCP call agent from the router configuration.
sgcp call-agent ipaddress[:udp port]
no sgcp call-agent ipaddressSyntax Description
ipaddress
Specifies the IP address or hostname of the call-agent.
:udp port
(Optional) Specifies the UDP port of the call-agent.
Default
No IP address is configured.
Command Mode
Global configuration
Command History
Usage Guidelines
Setting this command defines the IP address of the default SGCP call agent that the router sends an initial RSIP (Restart-In-Progress) packet to when the router boots up. This is used for initial bootup only before the SGCP call agent contacts the router acting as the gateway.
When you enter the no sgcp call-agent command, only the IP address of the default SGCP call agent is removed.
Example
The following example enables SGCP and specifies the IP address of the call-agent:
Router(config)# sgcpRouter(config)# sgcp call-agent 209.165.200.225Related Commands
sgcp graceful-shutdown
To block all new calls and gracefully terminate all existing calls (waits for the caller to end the call), use the sgcp graceful-shutdown configuration command. To unblock all calls and allow new calls to go through, use the no form of this command.
sgcp graceful-shutdown
no sgcp graceful-shutdownSyntax Description
This command has no arguments or keywords.
Default
No default behavior or values.
Command Mode
Global configuration
Command History
Usage Guidelines
Once you issue this command, all requests for new connections (CreateConnection requests) are denied. All existing calls are maintained until users terminate them, or until you enter the no sgcp command. When the last active call is terminated, the SGCP daemon is terminated and all resources allocated to it are released.
Example
The following example blocks all new calls and terminates existing calls:
Router(config)# sgcp graceful-shutdownRouter(config)#Related Commands
sgcp max-waiting-delay
To set the SGCP maximum waiting delay to prevent restart avalanches, use the sgcp max-waiting-delay configuration command. Use the no form of this command to restore the default value.
sgcp max-waiting-delay delay
no sgcp max-waiting-delay delaySyntax Description
delay
Sets the maximum waiting delay (MWD) value in milliseconds. The valid range is 0 to 600,000. The default is 3,000.
Default
3,000
Command Mode
Global configuration
Command History
Example
The following example sets the maximum wait delay value to 40 milliseconds:
Router(config)# sgcp max-waiting-delay 40Router(config)#Related Commands
sgcp modem passthru
To enable SGCP modem or fax passthrough, use the sgcp modem passthru global configuration command. To disable SGCP modem or fax passthrough, use the no form of this command.
sgcp modem passthru {ca | cisco | nse}
no sgcp modem passthru {ca | cisco | nse}Syntax Description
ca
Uses the Call Agent controlled modem upspeed method violation message.
cisco
Uses Cisco's proprietary upspeed method based on the protocol.
nse
Uses the NSE-based modem upspeed method.
Default
SGCP modem/fax passthrough is disabled by default.
Command Mode
Global configuration mode.
Command History
12.0(7)XK
This command was introduced on the Cisco MC3810 and Cisco 3600 series routers (except the Cisco 3620) in a private release that was not generally available.
Usage Guidelines
You can use this command for FAX passthrough since the answer tone can come from either modem or FAX transmissions. The upspeed method is the method used to dynamically change the codec type and speed to meet network conditions.
If you use the nse option, you must also configure the sgcp tse payload command.
Examples
The following example configures SGCP modem passthrough using the Call Agent upspeed method:
Router(config)# sgcp modem passthru caThe following example configures SGCP modem passthrough using the proprietary Cisco upspeed method:
Router(config)# sgcp modem passthru ciscoThe following example configures SGCP modem passthrough using the NSE-based modem upspeed
Router(config)# sgcp modem passthru nseRouter(config)# sgcp tse payload 110Related Commands
sgcp quarantine-buffer disable
To disable the SGCP quarantine buffer, use the sgcp quarantine-buffer disable configuration command. To reenable the SGCP quarantine buffer, use the no form of this command.
sgcp quarantine-buffer disable
no sgcp quarantine-buffer disableSyntax Description
This command has no arguments or keywords.
Default
The SGCP quarantine buffer is enabled.
Command Mode
Global configuration
Command History
12.0(7)XK
This command was introduced on the Cisco MC3810 and the Cisco 3600 series routers (except for the Cisco 3620) in a private release that was not generally available.
Usage Guidelines
The SGCP quarantine buffer is the mechanism for buffering the SGCP events between two RQNT messages.
Example
The following example disables the SGCP quarantine buffer:
Router(config)# sgcp quarantine-buffer disableRouter(config)#Related Commands
sgcp request retries
To specify the number of times to retry sending Notify and Delete messages to the SGCP call agent, use the sgcp request retries configuration command. The no form of this command restores the default value.
sgcp request retries count
no sgcp request retriesSyntax Description
count
Specifies the number of times a Notify and Delete message is retransmitted to the SGCP call agent before it is dropped. The valid range is 1 to 100. The default is 3.
Default
3.
Command Mode
Global configuration
Command History
Usage Guidelines
The actual retry count may be different from the value you enter for this command. The retry count is also limited by the call agent. If there is no response from the call agent after 30 seconds, the gateway will not retry anymore, even though the number set using the sgcp request retries command has not been reached.
The router will stop sending retries after 30 seconds, regardless of the setting for this command.
Example
The following example specifies that the system will try to send the sgcp command 10 times before dropping the request:
Router(config)# sgcp request retries 10Router(config)#Related Commands
sgcp request timeout
To specify how long the system should wait for a response to a request, use the sgcp request timeout configuration command. Use the no form of this command to restore the default value.
sgcp request timeout timeout
no sgcp request timeoutSyntax Description
timeout
Specifies the number of milliseconds to wait for a response to a request. Valid range is 1 to 10,000.
Default
500.
Command Mode
Global configuration
Command History
Usage Guidelines
This command is used for Notify and Delete messages, which are sent to the SGCP call agent.
Example
The following example specifies that the system waits 40 milliseconds for a reply to a request:
Router(config)# sgcp request timeout 40Router(config)#Related Commands
sgcp restart
To trigger the router to send an RSIP message to the SGCP call agent indicating that the T1 controller is up or down, so that the call agent can synchronize with the T1 controller, use the sgcp restart configuration command. Use the no form of this command to restore the default value.
sgcp restart {delay delay | notify}
no sgcp restart {delay delay | notify}Syntax Description
Default
0
Command Mode
Global configuration
Command History
12.0(7)XK
This command was introduced on the Cisco MC3810 and Cisco 3600 series routers (except the Cisco 3620) in a private release that was not generally available.
Usage Guidelines
This command is used to send RSIP (Re-start In Progress) messages from the router to the SGCP call agent. The RSIP messages are used to synchronize the router and the call agent. RSIP messages are also sent when the sgcp command is entered, enabling the SGCP daemon.
You must enter the notify option to enable RSIP messages to be sent.
Examples
The following example specifies that the system waits 40 milliseconds before restarting SGCP:
Router(config)# sgcp restart delay 40Router(config)#The following example specifies that the system sends an RSIP notification to the SGCP call agent when the T1 controller state changes:
Router(config)# sgcp restart notifyRouter(config)#Related Commands
sgcp retransmit timer
To configure the SGCP retransmission timer to use a random algorithm method, use the sgcp retransmit timer configuration command. Use the no form of this command to restore the default value.
sgcp retransmit timer {random}
no sgcp retransmit timer {random}Syntax Description
random
Enables the SGCP retransmission timer to use a random algorithm method. This is the only keyword supported in this release.
Default
The SGCP retransmission timer does not use the random algorithm.
Command Mode
Global configuration
Command History
12.0(7)XK
This command was introduced on the Cisco 3600 and Cisco MC3810 in a private release that was not generally available. Only the random keyword was supported.
Usage Guidelines
Use this command to enable the random algorithm component of the retransmission timer. For example, if the retransmission timer is set to 200 milliseconds, the first retransmission timer is 200 milliseconds, but the second retransmission timer picks up a timer value randomly between either 200 or 400. The third retransmission timer picks up a timer value randomly of 200, 400, or 800 as shown below:
First retransmission timer: 200
Second retransmission timer: 200 or 400
Third retransmission timer: 200, 400, or 800
Fourth retransmission timer: 200, 400, 800, or 1600
Fifth retransmission timer: 200, 400, 800, 1600, or 3200
and so on.
After 30 seconds, the retransmission timer no longer retries.
Example
The following example sets the retransmission timer to use the random algorithm:
Router(config)# sgcp retransmit timer randomRelated Commands
sgcp timer
To configure how the gateway detects the RTP stream host, use the sgcp timer configuration command. Use the no form of this command to restore the default value.
sgcp timer {receive-rtcp timer | rtp-nse timer}
no sgcp timer {receive-rtcp timer | rtp-nse timer}Syntax Description
Default
receive-rtcp timer default is 5.
rtp-nse timer default is 200.
Command Mode
Global configuration
Command History
Usage Guidelines
The RTP NSE timer is used for proxy ringing (ringback tone is provided at the originating gateway).
Examples
The following example sets the receive-rtcp timer to 100:
Router(config)# sgcp timer receive-rtcp 100Router(config)#The following example sets the rtp-nse timer to 1000:
Router(config)# sgcp timer rtp-nse 1000Router(config)#Related Commands
sgcp tse payload
To enable Inband Telephony Signaling Events (TSE) for fax/modem operation, use the sgcp tse payload configuration command. Use the no form of this command to restore the default value.
sgcp tse payload type
no sgcp tse payload typeSyntax Description
type
Sets the TSE payload type. The valid range is 96 to 119. The default is 0, meaning the command is disabled.
Default
0.
Command Mode
Global configuration
Command History
12.0(7)XK
This command was introduced on the Cisco MC3810 and Cisco 3600 series routers (except the Cisco 3620) in a private release that was not generally available.
Usage Guidelines
Because this command is disabled by default, you must specify a TSE payload type.
If you configure the sgcp modem passthru command to the nse value, then you must configure this command.
Example
The following example SGCP modem passthrough using the NSE-based modem upspeed and sets the Inband Telephony Signaling Events payload value to 110:
Router(config)# sgcp modem passthru nseRouter(config)# sgcp tse payload 110Router(config)#Related Commands
show sgcp connection
To display all the active SGCP connections on this router, use the show sgcp connection EXEC command.
show sgcp connection [interface number]
Syntax Description
interface
(Optional) Specifies a DS1 interface.
number
(Optional) Specifies the T1 interface (controller) number. Valid values on the Cisco MC3810 are from 0 to 1.
Default
No default behavior or values.
Command Mode
EXEC
Command History
Usage Guidelines
If you do not specify an interface, this command shows all the active SGCP connections on this host. If you specify an interface, this command shows only those active connections on the specified interface.
Examples
The following example shows the active connections on this router:
MC3810-5# show sgcp connectionEndpoint Call_ID(C) Conn_ID(I) (P)ort (M)ode (S)tate (E)vent[SIFL] (R)esult[EA]1. ds1-0/1@r3810-5 C=1,1,2 I=0x1 P=16492,16476 M=3 S=4 E=3,0,0,3 R=0, 0The following example displays the state of SGCP on the router:
MC3810# show sgcp connectionSGCP Admin State DOWN, Oper State DOWNSGCP call-agent: 209.165.200.225 , SGCP graceful-shutdown enabled? FALSESGCP request timeout 40, SGCP request retries 10Table 1
show sgcp connection Field Descriptions
Related Commands
Displays SGCP endpoint information.
Displays global statistics for the SGCP packet count, success and failure counts.
show sgcp endpoint
To display SGCP endpoints eligible for SGCP management, use the show sgcp endpoint EXEC command.
show sgcp endpoint [interface ds1 [ds0]]
Syntax Description
Default
No default behavior or values.
Command Mode
EXEC
Command History
Usage Guidelines
You can use this command to display SGCP endpoint information for the whole router, or you can display SGCP endpoint information for a specific DS1 interface and, optionally, a specific DS0. If you enter a nonexistent combination of a DS1 and DS0, the following error message appears: "No matching connection found" appears.
Example
The following command displays SGCP endpoint information for a matching connection between DS1 interface 1 and DS0 interface 10.
MC3810# show sgcp endpoint interface 1 10Related Commands
Display all the active connections on the host router.
Displays global statistics for the SGCP packet count, success and failure counts, and the like.
show sgcp statistics
To display global statistics for the SGCP packet count, success and failure counts, and other information, use the show sgcp statistics EXEC command.
show sgcp statistics
Syntax Description
This command has no arguments or keywords.
Default
No default behavior or values.
Command Mode
EXEC
Command History
Example
The following example displays SGCP packet statistics:
MC3810-5# show sgcp statisticsUDP pkts rx 5, tx 13Unrecognized rx pkts 0, SGCP message parsing errors 0Duplicate SGCP ack tx 0Failed to send SGCP messages 0CreateConn rx 1, successful 1, failed 0DeleteConn rx 0, successful 0, failed 0ModifyConn rx 0, successful 0, failed 0DeleteConn tx 0, successful 0, failed 0NotifyRequest rx 3, successful 3, failed 0Notify tx 3, successful 3, failed 0ACK tx 4, NACK tx 0ACK rx 1, NACK rx 0IP address based Call Agents statistics:IP address 1.4.63.100, Total msg rx 5,successful 5, failed 2The following examples show how you can filter the command return for specific information:
MC3810# show sgcp statist | begin FailedFailed to send SGCP messages 0CreateConn rx 0, successful 0, failed 0DeleteConn rx 0, successful 0, failed 0ModifyConn rx 0, successful 0, failed 0DeleteConn tx 0, successful 0, failed 0NotifyRequest rx 0, successful 0, failed 0Notify tx 0, successful 0, failed 0ACK tx 0, NACK tx 0ACK rx 0, NACK rx 0MC3810# show sgcp statist | exclude ACKUDP pkts rx 0, tx 0Unrecognized rx pkts 0, SGCP message parsing errors 0Duplicate SGCP ack tx 0Failed to send SGCP messages 0CreateConn rx 0, successful 0, failed 0DeleteConn rx 0, successful 0, failed 0ModifyConn rx 0, successful 0, failed 0DeleteConn tx 0, successful 0, failed 0NotifyRequest rx 0, successful 0, failed 0Notify tx 0, successful 0, failed 0MC3810# show sgcp statist | include ACKACK tx 0, NACK tx 0ACK rx 0, NACK rx 0Related Commands
Display all the active connections on the host AS5300.
Displays SGCP endpoint information.
voice-group
This command was added in Cisco IOS Release 11.3(1)MA on the Cisco MC3810. Beginning with Cisco IOS Release 12.0(7)XK, this command is no longer supported.
Debug Commands
This section documents new debug commands. All other commands used with this feature are documented in the Cisco IOS Release 12.0 command references.
debug rtpspi all
debug rtpspi errors
debug rtpspi inout
debug rtpspi send-nse
debug sgcp errors
debug sgcp events
debug sgcp packet
debug vtsp send-nsedebug rtpspi all
To debug all RTP SPI errors, sessions, and in/out functions, use the debug rtpspi all EXEC command. Use the no debug rtpspi all command to turn off debugging.
debug rtpspi all
no debug rtpspi allSyntax Description
This command has no arguments or keywords.
Default
No default behavior or values.
Command Mode
EXEC
Usage Guidelines
CautionBe careful when you use this command. Use of this command can result in console flooding and reduced voice quality.
Command History
12.0(7)XK
This command was introduced on the Cisco MC3810 and Cisco 3600 series routers (except the Cisco 3620) in a private release that was not generally available.
Example
The following example shows a debug trace for RTP SPI errors, sessions and in/out functions on a gateway:
router# debug rtpspi allRTP SPI Error, Session and function in/out tracings are enabled.*Mar 1 00:38:59.381:rtpspi_allocate_rtp_port:Entered.*Mar 1 00:38:59.381:rtpspi_allocate_rtp_port:allocated RTP port 16544*Mar 1 00:38:59.381:rtpspi_allocate_rtp_port:Success. port = 16544. Leaving.*Mar 1 00:38:59.381:rtpspi_call_setup_request:entered.Call Id = 5, dest = 0.0.0.0; callInfo:final dest flag = 0,rtp_session_mode = 0x2,local_ip_addrs = 0x5000001,remote_ip_addrs = 0x0,local rtp port = 16544, remote rtp port = 0*Mar 1 00:38:59.381:rtpspi_call_setup_request:spi_info copied for rtpspi_app_data_t.*Mar 1 00:38:59.385:rtpspi_call_setup_request:leaving*Mar 1 00:38:59.385:rtpspi_call_setup() entered*Mar 1 00:38:59.385:rtpspi_initialize_ccb:Entered*Mar 1 00:38:59.385:rtpspi_initialize_ccb:leaving*Mar 1 00:38:59.385:rtpspi_call_setup:rtp_session_mode = 0x2*Mar 1 00:38:59.385:rtpspi_call_setup:mode = CC_CALL_NORMAL.destianation number = 0.0.0.0*Mar 1 00:38:59.385:rtpspi_call_setup:Passed local_ip_addrs=0x5000001*Mar 1 00:38:59.385:rtpspi_call_setup:Passed local_rtp_port = 16544*Mar 1 00:38:59.385:rtpspi_call_setup:Saved RTCP Session = 0x1AF57E0*Mar 1 00:38:59.385:rtpspi_call_setup:Passed remote rtp port = 0.*Mar 1 00:38:59.389:rtpspi_start_rtcp_session:entered. rtp session mode=0x2, rem rtp=0, rem ip=0x0*Mar 1 00:38:59.389:rtpspi_get_rtcp_mode:entered. rtp_mode = 0x2*Mar 1 00:38:59.389:rtpspi_start_rtcp_session:Starting RTCP session.Local IP addr = 0x5000001, Remote IP addr = 0x0,Local RTP port = 16544, Remote RTP port = 0, mode = 0x2*Mar 1 00:38:59.389:rtpspi_start_rtcp_session:RTP Session creation Success.*Mar 1 00:38:59.389:rtpspi_call_setup:RTP Session creation Success.*Mar 1 00:38:59.389:rtpspi_call_setup:calling cc_api_call_connected()*Mar 1 00:38:59.389:rtpspi_call_setup:Leaving.*Mar 1 00:38:59.393:rtpspi_bridge:entered. conf id = 1, src i/f = 0x1859E88,dest i/f = 0x1964EEC, src call id = 5, dest call id = 4call info = 0x1919140, xmit fn = 0xDA7494, tag = 0*Mar 1 00:38:59.393:rtpspi_get_rtcp_mode:entered. rtp_mode = 0x2*Mar 1 00:38:59.393:rtpspi_modify_rtcp_session_parameters():xmit fn=0xDA7494,dstIF=0x1964EEC, dstCallID=4, voip_mode=0x2, rtp_mode=0x2, ssrc_status=0*Mar 1 00:38:59.393:rtpspi_bridge:Calling cc_api_bridge_done() for 5(0x1AF5400) and 4(0x0).*Mar 1 00:38:59.393:rtpspi_bridge:leaving.*Mar 1 00:38:59.397:rtpspi_caps_ind:Entered. vdb = 0x1859E88 call id = 5, srcCallId = 4*Mar 1 00:38:59.397:rtpspi_caps_ind:caps from VTSP:codec=0x83FB, codec_bytes=0x50,fax rate=0x7F, vad=0x3 modem=0x0*Mar 1 00:38:59.397:rtpspi_get_rtcp_session_parameters():CURRENT VALUES:dstIF=0x1964EEC, dstCallID=4, current_seq_num=0x0*Mar 1 00:38:59.397:rtpspi_get_rtcp_session_parameters():NEW VALUES:dstIF=0x1964EEC, dstCallID=4, current_seq_num=0x261C*Mar 1 00:38:59.397:rtpspi_caps_ind:Caps Used:codec=0x1, codec bytes=80,fax rate=0x1, vad=0x1, modem=0x1, dtmf_relay=0x1, seq_num_start=0x261D*Mar 1 00:38:59.397:rtpspi_caps_ind:calling cc_api_caps_ind().*Mar 1 00:38:59.397:rtpspi_caps_ind:Returning success*Mar 1 00:38:59.397:rtpspi_caps_ack:Entered. call id = 5, srcCallId = 4*Mar 1 00:38:59.397:rtpspi_caps_ack:leaving.*Mar 1 00:38:59.618:rtpspi_call_modify:entered. call-id=5, nominator=0x7, params=0x18DD440*Mar 1 00:38:59.618:rtpspi_call_modify:leaving*Mar 1 00:38:59.618:rtpspi_do_call_modify:Entered. call-id = 5*Mar 1 00:38:59.622:rtpspi_do_call_modify:Remote RTP port changed. New port=16432*Mar 1 00:38:59.622:rtpspi_do_call_modify:Remote IP addrs changed. New IP addrs=0x6000001*Mar 1 00:38:59.622:rtpspi_do_call_modify:new mode 2 is the same as the current mode*Mar 1 00:38:59.622:rtpspi_do_call_modify:Starting new RTCP session.*Mar 1 00:38:59.622:rtpspi_start_rtcp_session:entered. rtp session mode=0x2, rem rtp=16432, rem ip=0x6000001*Mar 1 00:38:59.622:rtpspi_get_rtcp_mode:entered. rtp_mode = 0x2*Mar 1 00:38:59.622:rtpspi_start_rtcp_session:Removing old RTCP session.*Mar 1 00:38:59.622:rtpspi_start_rtcp_session:Starting RTCP session.Local IP addr = 0x5000001, Remote IP addr = 0x6000001,Local RTP port = 16544, Remote RTP port = 16432, mode = 0x2*Mar 1 00:38:59.622:rtpspi_start_rtcp_session:RTCP Timer creation Success. (5)*(5000)*Mar 1 00:38:59.622:rtpspi_start_rtcp_session:RTP Session creation Success.*Mar 1 00:38:59.622:rtpspi_do_call_modify:RTP Session creation Success.*Mar 1 00:38:59.622:rtpspi_do_call_modify:Calling cc_api_call_modify(), result=0x0*Mar 1 00:38:59.626:rtpspi_do_call_modify:success. leaving*Mar 1 00:39:05.019:rtpspi_call_modify:entered. call-id=5, nominator=0x7, params=0x18DD440*Mar 1 00:39:05.019:rtpspi_call_modify:leaving*Mar 1 00:39:05.019:rtpspi_do_call_modify:Entered. call-id = 5*Mar 1 00:39:05.019:rtpspi_do_call_modify:New remote RTP port = old rtp port = 16432*Mar 1 00:39:05.019:rtpspi_do_call_modify:New remote IP addrs = old IP addrs = 0x6000001*Mar 1 00:39:05.019:rtpspi_do_call_modify:Mode changed. new = 3, old = 2*Mar 1 00:39:05.019:rtpspi_get_rtcp_mode:entered. rtp_mode = 0x3*Mar 1 00:39:05.023:rtpspi_modify_rtcp_session_parameters():xmit fn=0xDA7494,dstIF=0x1964EEC, dstCallID=4, voip_mode=0x3, rtp_mode=0x3, ssrc_status=2*Mar 1 00:39:05.023:rtpspi_do_call_modify:RTCP Timer start.*Mar 1 00:39:05.023:rtpspi_do_call_modify:Calling cc_api_call_modify(), result=0x0*Mar 1 00:39:05.023:rtpspi_do_call_modify:success. leaving*Mar 1 00:40:13.786:rtpspi_bridge_drop:entered. src call-id=5, dest call-id=4, tag=0*Mar 1 00:40:13.786:rtpspi_get_rtcp_mode:entered. rtp_mode = 0x3*Mar 1 00:40:13.786:rtpspi_modify_rtcp_session_parameters():xmit fn=0x0,dstIF=0x0, dstCallID=0, voip_mode=0x3, rtp_mode=0x3, ssrc_status=2*Mar 1 00:40:13.786:rtpspi_bridge_drop:leaving*Mar 1 00:40:13.790:rtpspi_call_disconnect:entered. call-id=5, cause=16, tag=0*Mar 1 00:40:13.790:rtpspi_call_disconnect:leaving.*Mar 1 00:40:13.790:rtpspi_do_call_disconnect:Entered. call-id = 5*Mar 1 00:40:13.790:rtpspi_do_call_disconnect:calling rtpspi_call_cleanup(). call-id=5*Mar 1 00:40:13.794:rtpspi_call_cleanup:entered. ccb = 0x1AF5400, call-id=5, rtp port = 16544*Mar 1 00:40:13.794:rtpspi_call_cleanup:releasing ccb cache. RTP port=16544*Mar 1 00:40:13.794:rtpspi_store_call_history_entry():Entered.*Mar 1 00:40:13.794:rtpspi_store_call_history_entry():Leaving.*Mar 1 00:40:13.794:rtpspi_call_cleanup:RTCP Timer Stop.*Mar 1 00:40:13.794:rtpspi_call_cleanup:deallocating RTP port 16544.*Mar 1 00:40:13.794:rtpspi_free_rtcp_session:Entered.*Mar 1 00:40:13.794:rtpspi_free_rtcp_session:Success. Leaving*Mar 1 00:40:13.794::rtpspi_call_cleanup freeing ccb (0x1AF5400)*Mar 1 00:40:13.794:rtpspi_call_cleanup:leaving*Mar 1 00:40:13.794:rtpspi_do_call_disconnect:leavingRelated Commands
debug rtpspi errors
To debug RTP SPI errors, use the debug rtpspi errors EXEC command. Use the no debug rtpspi errors command to turn off debugging.
debug rtpspi errors
no debug rtpspi errorsSyntax Description
This command has no arguments or keywords.
Default
No default behavior or values.
Command Mode
EXEC
Command History
12.0(7)XK
This command was introduced on the Cisco MC3810 and Cisco 3600 series routers (except the Cisco 3620) in a private release that was not generally available.
Usage Guidelines
CautionBe careful when you use this command. Use of this command can result in console flooding and reduced voice quality.
Examples
This example performs a debug trace for RTP SPI errors on two gateways. The following example is the debug trace on the first gateway:
router# debug rtpspi errors00:54:13.272:rtpspi_do_call_modify:new mode 2 is the same as the current mode00:54:18.738:rtpspi_do_call_modify:New remote RTP port = old rtp port = 1645200:54:18.738:rtpspi_do_call_modify:New remote IP addrs = old IP addrs = 0x6000001The following example is the debug trace on the second gateway:
router# debug rtpspi errors00:54:08:rtpspi_process_timers:00:54:08:rtpspi_process_timers:Timer 0x1A5AF9C expired.00:54:08:rtpspi_process_timers:Timer expired for callID 0x300:54:08:rtpspi_process_timers:00:54:08:rtpspi_process_timers:Timer 0x1A5AF9C expired.00:54:08:rtpspi_process_timers:Timer expired for callID 0x300:54:08:rtpspi_process_timers:00:54:08:rtpspi_process_timers:Timer 0x1A5AF9C expired.00:54:08:rtpspi_process_timers:Timer expired for callID 0x300:54:09:rtpspi_process_timers:00:54:09:rtpspi_process_timers:Timer 0x1A5AFBC expired.00:54:09:rtpspi_process_timers:Timer expired for callID 0x300:54:09:rtpspi_process_timers:00:54:09:rtpspi_process_timers:Timer 0x1A5B364 expired.00:54:09:rtpspi_process_timers:Timer expired for callID 0x3Related Commands
debug rtpspi inout
To debug RTP SPI in/out functions, use the debug rtpspi inout EXEC command. Use the no debug rtpspi inout command to turn off debugging.
debug rtpspi inout
no debug rtpspi inoutSyntax Description
This command has no arguments or keywords.
Default
No default behavior or values.
Command Mode
EXEC
Command History
12.0(7)XK
This command was introduced on the Cisco MC3810 and Cisco 3600 series routers (except the Cisco 3620) in a private release that was not generally available.
Usage Guidelines
CautionBe careful when you use this command. Use of this command can result in console flooding and reduced voice quality.
Example
The following example shows a debug trace for RTP SPI in/out functions on a gateway:
router# debug rtpspi inout*Mar 1 00:57:24.565:rtpspi_allocate_rtp_port:Entered.*Mar 1 00:57:24.565:rtpspi_allocate_rtp_port:Success. port = 16520. Leaving.*Mar 1 00:57:24.565:rtpspi_call_setup_request:entered.Call Id = 9, dest = 0.0.0.0; callInfo:final dest flag = 0,rtp_session_mode = 0x2,local_ip_addrs = 0x5000001,remote_ip_addrs = 0x0,local rtp port = 16520, remote rtp port = 0*Mar 1 00:57:24.565:rtpspi_call_setup_request:spi_info copied for rtpspi_app_data_t.*Mar 1 00:57:24.565:rtpspi_call_setup_request:leaving*Mar 1 00:57:24.569:rtpspi_call_setup() entered*Mar 1 00:57:24.569:rtpspi_initialize_ccb:Entered*Mar 1 00:57:24.569:rtpspi_initialize_ccb:leaving*Mar 1 00:57:24.569:rtpspi_start_rtcp_session:entered. rtp session mode=0x2, rem rtp=0, rem ip=0x0*Mar 1 00:57:24.569:rtpspi_get_rtcp_mode:entered. rtp_mode = 0x2*Mar 1 00:57:24.569:rtpspi_call_setup:Leaving.*Mar 1 00:57:24.573:rtpspi_bridge:entered. conf id = 3, src i/f = 0x1859E88,dest i/f = 0x1964EEC, src call id = 9, dest call id = 8call info = 0x1919140, xmit fn = 0xDA7494, tag = 0*Mar 1 00:57:24.573:rtpspi_get_rtcp_mode:entered. rtp_mode = 0x2*Mar 1 00:57:24.573:rtpspi_bridge:leaving.*Mar 1 00:57:24.573:rtpspi_caps_ind:Entered. vdb = 0x1859E88 call id = 9, srcCallId = 8*Mar 1 00:57:24.577:rtpspi_caps_ind:Returning success*Mar 1 00:57:24.577:rtpspi_caps_ack:Entered. call id = 9, srcCallId = 8*Mar 1 00:57:24.577:rtpspi_caps_ack:leaving.*Mar 1 00:57:24.818:rtpspi_call_modify:entered. call-id=9, nominator=0x7, params=0x18DD440*Mar 1 00:57:24.818:rtpspi_call_modify:leaving*Mar 1 00:57:24.818:rtpspi_do_call_modify:Entered. call-id = 9*Mar 1 00:57:24.818:rtpspi_start_rtcp_session:entered. rtp session mode=0x2, rem rtp=16396, rem ip=0x6000001*Mar 1 00:57:24.822:rtpspi_get_rtcp_mode:entered. rtp_mode = 0x2*Mar 1 00:57:24.822:rtpspi_do_call_modify:success. leaving*Mar 1 00:57:30.296:rtpspi_call_modify:entered. call-id=9, nominator=0x7, params=0x18DD440*Mar 1 00:57:30.296:rtpspi_call_modify:leaving*Mar 1 00:57:30.300:rtpspi_do_call_modify:Entered. call-id = 9*Mar 1 00:57:30.300:rtpspi_get_rtcp_mode:entered. rtp_mode = 0x3*Mar 1 00:57:30.300:rtpspi_do_call_modify:success. leaving*Mar 1 00:58:39.055:rtpspi_bridge_drop:entered. src call-id=9, dest call-id=8, tag=0*Mar 1 00:58:39.055:rtpspi_get_rtcp_mode:entered. rtp_mode = 0x3*Mar 1 00:58:39.055:rtpspi_bridge_drop:leaving*Mar 1 00:58:39.059:rtpspi_call_disconnect:entered. call-id=9, cause=16, tag=0*Mar 1 00:58:39.059:rtpspi_call_disconnect:leaving.*Mar 1 00:58:39.059:rtpspi_do_call_disconnect:Entered. call-id = 9*Mar 1 00:58:39.059:rtpspi_call_cleanup:entered. ccb = 0x1AF5400, call-id=9, rtp port = 16520*Mar 1 00:58:39.059:rtpspi_store_call_history_entry():Entered.*Mar 1 00:58:39.059:rtpspi_store_call_history_entry():Leaving.*Mar 1 00:58:39.059:rtpspi_free_rtcp_session:Entered.*Mar 1 00:58:39.059:rtpspi_free_rtcp_session:Success. Leaving*Mar 1 00:58:39.063:rtpspi_call_cleanup:leaving*Mar 1 00:58:39.063:rtpspi_do_call_disconnect:leavingRelated Commands
debug rtpspi send-nse
To trigger the RTP SPI software module to send a triple redundant NSE, use the debug rtpspi send-nse EXEC command. Use the no debug rtpspi send-nse to disable this action.
debug rtpspi send-nse callID NSE-eventID
no debug rtpspi send-nse callID NSE-eventIDSyntax Description
callID
Specifies the call ID of the active call. The valid range is from 0-65535.
NSE-eventID
Specifies the NSE Event ID. The valid range is from 0-255.
Default
No default behavior or values.
Command Mode
EXEC
Command History
12.0(7)XK
This command was introduced on the Cisco MC3810 and Cisco 3600 series routers (except the Cisco 3620) in a private release that was not generally available.
Example
The following example triggers the RTP SPI software module to send an NSE:
router# debug rtpspi send-nseRelated Commands
debug rtpspi session
To debug all RTP SPI sessions, use the debug rtpspi session EXEC command. Use the no debug rtpspi session command to turn off debugging.
debug rtpspi session
no debug rtpspi sessionSyntax Description
This command has no arguments or keywords.
Default
No default behavior or values.
Command Mode
EXEC
Command History
12.0(7)XK
This command was introduced on the Cisco MC3810 and Cisco 3600 series routers (except the Cisco 3620) in a private release that was not generally available.
Example
The following example shows a debug trace for RTP SPI sessions on a gateway:
router# debug rtpspi session*Mar 1 01:01:51.593:rtpspi_allocate_rtp_port:allocated RTP port 16406*Mar 1 01:01:51.593:rtpspi_call_setup:rtp_session_mode = 0x2*Mar 1 01:01:51.593:rtpspi_call_setup:mode = CC_CALL_NORMAL.destianation number = 0.0.0.0*Mar 1 01:01:51.593:rtpspi_call_setup:Passed local_ip_addrs=0x5000001*Mar 1 01:01:51.593:rtpspi_call_setup:Passed local_rtp_port = 16406*Mar 1 01:01:51.593:rtpspi_call_setup:Saved RTCP Session = 0x1AFDFBC*Mar 1 01:01:51.593:rtpspi_call_setup:Passed remote rtp port = 0.*Mar 1 01:01:51.598:rtpspi_start_rtcp_session:Starting RTCP session.Local IP addr = 0x5000001, Remote IP addr = 0x0,Local RTP port = 16406, Remote RTP port = 0, mode = 0x2*Mar 1 01:01:51.598:rtpspi_start_rtcp_session:RTP Session creation Success.*Mar 1 01:01:51.598:rtpspi_call_setup:RTP Session creation Success.*Mar 1 01:01:51.598:rtpspi_call_setup:calling cc_api_call_connected()*Mar 1 01:01:51.598:rtpspi_modify_rtcp_session_parameters():xmit fn=0xDA7494,dstIF=0x1964EEC, dstCallID=10, voip_mode=0x2, rtp_mode=0x2, ssrc_status=0*Mar 1 01:01:51.598:rtpspi_bridge:Calling cc_api_bridge_done() for 11(0x1AF5400) and 10(0x0).*Mar 1 01:01:51.602:rtpspi_caps_ind:caps from VTSP:codec=0x83FB, codec_bytes=0x50,fax rate=0x7F, vad=0x3 modem=0x0*Mar 1 01:01:51.602:rtpspi_get_rtcp_session_parameters():CURRENT VALUES:dstIF=0x1964EEC, dstCallID=10, current_seq_num=0x0*Mar 1 01:01:51.602:rtpspi_get_rtcp_session_parameters():NEW VALUES:dstIF=0x1964EEC, dstCallID=10, current_seq_num=0xF1E*Mar 1 01:01:51.602:rtpspi_caps_ind:Caps Used:codec=0x1, codec bytes=80,fax rate=0x1, vad=0x1, modem=0x1, dtmf_relay=0x1, seq_num_start=0xF1F*Mar 1 01:01:51.602:rtpspi_caps_ind:calling cc_api_caps_ind().*Mar 1 01:01:51.822:rtpspi_do_call_modify:Remote RTP port changed. New port=16498*Mar 1 01:01:51.822:rtpspi_do_call_modify:Remote IP addrs changed. New IP addrs=0x6000001*Mar 1 01:01:51.822:rtpspi_do_call_modify:Starting new RTCP session.*Mar 1 01:01:51.822:rtpspi_start_rtcp_session:Removing old RTCP session.*Mar 1 01:01:51.822:rtpspi_start_rtcp_session:Starting RTCP session.Local IP addr = 0x5000001, Remote IP addr = 0x6000001,Local RTP port = 16406, Remote RTP port = 16498, mode = 0x2*Mar 1 01:01:51.822:rtpspi_start_rtcp_session:RTCP Timer creation Success. (5)*(5000)*Mar 1 01:01:51.826:rtpspi_start_rtcp_session:RTP Session creation Success.*Mar 1 01:01:51.826:rtpspi_do_call_modify:RTP Session creation Success.*Mar 1 01:01:51.826:rtpspi_do_call_modify:Calling cc_api_call_modify(), result=0x0*Mar 1 01:01:57.296:rtpspi_do_call_modify:Mode changed. new = 3, old = 2*Mar 1 01:01:57.296:rtpspi_modify_rtcp_session_parameters():xmit fn=0xDA7494,dstIF=0x1964EEC, dstCallID=10, voip_mode=0x3, rtp_mode=0x3, ssrc_status=2*Mar 1 01:01:57.296:rtpspi_do_call_modify:RTCP Timer start.*Mar 1 01:01:57.296:rtpspi_do_call_modify:Calling cc_api_call_modify(), result=0x0*Mar 1 01:03:06.108:rtpspi_modify_rtcp_session_parameters():xmit fn=0x0,dstIF=0x0, dstCallID=0, voip_mode=0x3, rtp_mode=0x3, ssrc_status=2*Mar 1 01:03:06.112:rtpspi_do_call_disconnect:calling rtpspi_call_cleanup(). call-id=11*Mar 1 01:03:06.112:rtpspi_call_cleanup:releasing ccb cache. RTP port=16406*Mar 1 01:03:06.112:rtpspi_call_cleanup:RTCP Timer Stop.*Mar 1 01:03:06.112:rtpspi_call_cleanup:deallocating RTP port 16406.*Mar 1 01:03:06.112::rtpspi_call_cleanup freeing ccb (0x1AF5400)Related Commands
debug sgcp errors
To debug Simple Gateway Control Protocol errors, use the debug sgcp errors EXEC command. Use the no form of this command to turn off debugging.
debug sgcp errors [endpoint string]
no debug sgcp errorsSyntax Description
Default
No default behavior or values.
Command Mode
EXEC
Command History
Examples
The following example enables the debugging of SGCP errors:
router# debug sgcp errorsSimple Gateway Control Protocol errors debugging is onno errors since call went through successfully.The following example shows a debug trace for SGCP errors on a specific endpoint:
router# debug sgcp errors endpoint DS1-0/1End point name for error debug:DS1-0/1 (1)00:08:41:DS1 = 0, DS0 = 100:08:41:Call record found00:08:41:Enable error end point debug for (DS1-0/1)Related Commands
debug sgcp events
To debug Simple Gateway Control Protocol events, use the debug sgcp events EXEC command. Use the no debug sgcp events to turn off debugging.
debug sgcp events [endpoint string]
no debug sgcp eventsSyntax Description
Default
No default behavior or values.
Command Mode
EXEC
Command History
Examples
The following example shows a debug trace for SGCP events on a specific endpoint:
router# debug sgcp events endpoint DS1-0/1End point name for event debug:DS1-0/1 (1)00:08:54:DS1 = 0, DS0 = 100:08:54:Call record found00:08:54:Enable event end point debug for (DS1-0/1)The following example shows a debug trace for all SGCP events on a gateway:
router# debug sgcp events*Mar 1 01:13:31.035:callp :19196BC, state :0, call ID :-1, event :23*Mar 1 01:13:31.035:voice_if->call_agent_ipaddr used as Notify entityNotify entity available for Tx SGCP msgNTFY send to ipaddr=1092E01 port=2427*Mar 1 01:13:31.039:Push msg into SGCP wait ack queue* (1)[25]*Mar 1 01:13:31.039:Timed Out interval [1]:(2000)*Mar 1 01:13:31.039:Timed Out interval [1]:(2000)(0):E[25]*Mar 1 01:13:31.075:Removing msg :NTFY 25 ds1-1/13@mc1 SGCP 1.1X:358258758O:hd*Mar 1 01:13:31.075:Unqueue msg from SGCP wait ack q** (0)[25]DS1 = 1, DS0 = 13*Mar 1 01:13:31.091:callp :19196BC, vdbptr :1964EEC, state :1*Mar 1 01:13:31.091:Checking ack (trans ID 237740140) :*Mar 1 01:13:31.091:is_capability_ok:caps.codec=5, caps.pkt=10, caps.nt=8*Mar 1 01:13:31.091:is_capability_ok:supported signal=0x426C079C, signal2=0x80003,event=0x6003421F, event2=0x3FDrequested signal=0x0, signal2=0x0,event=0x20000004, event2=0xC*Mar 1 01:13:31.091:Same digit map is download (ds1-1/13@mc1)*Mar 1 01:13:31.091:R:requested trans_id (237740140)*Mar 1 01:13:31.091:process_signal_ev:seizure possible=1, signal mask=0x4, mask2=0x0*Mar 1 01:13:32.405:SGCP Session Appl:ignore CCAPI event 10*Mar 1 01:13:32.489:callp :19196BC, state :1, call ID :16, event :9*Mar 1 01:13:32.610:SGCP Session Appl:ignore CCAPI event 10*Mar 1 01:13:32.670:callp :19196BC, state :1, call ID :16, event :9*Mar 1 01:13:32.766:SGCP Session Appl:ignore CCAPI event 10*Mar 1 01:13:32.810:callp :19196BC, state :1, call ID :16, event :9*Mar 1 01:13:32.931:SGCP Session Appl:ignore CCAPI event 10*Mar 1 01:13:32.967:callp :19196BC, state :1, call ID :16, event :9*Mar 1 01:13:33.087:SGCP Session Appl:ignore CCAPI event 10*Mar 1 01:13:33.132:callp :19196BC, state :1, call ID :16, event :9*Mar 1 01:13:33.240:SGCP Session Appl:ignore CCAPI event 10*Mar 1 01:13:33.280:callp :19196BC, state :1, call ID :16, event :9*Mar 1 01:13:33.389:SGCP Session Appl:ignore CCAPI event 10*Mar 1 01:13:33.433:callp :19196BC, state :1, call ID :16, event :9*Mar 1 01:13:33.537:SGCP Session Appl:ignore CCAPI event 10*Mar 1 01:13:33.581:callp :19196BC, state :1, call ID :16, event :9*Mar 1 01:13:33.702:SGCP Session Appl:ignore CCAPI event 10*Mar 1 01:13:33.742:callp :19196BC, state :1, call ID :16, event :9*Mar 1 01:13:33.742:voice_if->call_agent_ipaddr used as Notify entityNotify entity available for Tx SGCP msgNTFY send to ipaddr=1092E01 port=2427*Mar 1 01:13:33.742:Push msg into SGCP wait ack queue* (1)[26]*Mar 1 01:13:33.742:Timed Out interval [1]:(2000)*Mar 1 01:13:33.742:Timed Out interval [1]:(2000)(0):E[26]*Mar 1 01:13:33.786:Removing msg :NTFY 26 ds1-1/13@mc1 SGCP 1.1X:440842371O:k0, 4081037, s0*Mar 1 01:13:33.786:Unqueue msg from SGCP wait ack q** (0)[26]DS1 = 1, DS0 = 13*Mar 1 01:13:33.802:callp :19196BC, vdbptr :1964EEC, state :1*Mar 1 01:13:33.802:Checking ack (trans ID 698549528) :*Mar 1 01:13:33.802:is_capability_ok:caps.codec=5, caps.pkt=10, caps.nt=8*Mar 1 01:13:33.802:is_capability_ok:supported signal=0x426C079C, signal2=0x80003,event=0x6003421F, event2=0x3FDrequested signal=0x0, signal2=0x0,event=0x4, event2=0x0*Mar 1 01:13:33.802:R:requested trans_id (698549528)*Mar 1 01:13:33.802:set_up_voip_call_leg:peer_addr=0, peer_port=0.*Mar 1 01:13:33.806:call_setting_crcx:Enter CallProceeding state rc = 0, call_id=16*Mar 1 01:13:33.806:callp :19196BC, state :4, call ID :16, event :31*Mar 1 01:13:33.810:callp :1AF5798, state :2, call ID :17, event :8call_pre_bridge!*Mar 1 01:13:33.810:send_oc_create_ack:seizure_possiblle=1, ack-lready-sent=0, ack_send=0*Mar 1 01:13:33.814:callp :1AF5798, state :4, call ID :17, event :28*Mar 1 01:13:33.814:Call Connect:Raw Msg ptr=0x1995360, no-offhook=0; call-id=17*Mar 1 01:13:33.814:SGCP Session Appl:ignore CCAPI event 37*Mar 1 01:13:33.947:callp :19196BC, state :5, call ID :16, event :32process_nse_on_origDS1 = 1, DS0 = 13*Mar 1 01:13:34.007:callp :19196BC, vdbptr :1964EEC, state :5*Mar 1 01:13:34.007:Checking ack (trans ID 123764791) :*Mar 1 01:13:34.007:is_capability_ok:caps.codec=5, caps.pkt=10, caps.nt=8*Mar 1 01:13:34.007:is_capability_ok:supported signal=0x426C079C, signal2=0x80003,event=0x6003421F, event2=0x3FDrequested signal=0x0, signal2=0x0,event=0x4, event2=0x0*Mar 1 01:13:34.007:R:requested trans_id (123764791)*Mar 1 01:13:34.007:process_signal_ev:seizure possible=1, signal mask=0x0, mask2=0x0*Mar 1 01:13:34.007:modify_connection:echo_cancel=1.*Mar 1 01:13:34.007:modify_connection:vad=0.*Mar 1 01:13:34.007:modify_connection:peer_addr=6000001, peer_port=0->16500.*Mar 1 01:13:34.007:modify_connection:conn_mode=2.*Mar 1 01:13:34.011:callp :19196BC, state :5, call ID :16, event :31*Mar 1 01:13:34.011:callp :1AF5798, state :5, call ID :17, event :31process_nse_event*Mar 1 01:13:34.051:callp :19196BC, state :5, call ID :16, event :39*Mar 1 01:13:34.051:call_id=16, ignore_ccapi_ev:ignore 19 for state 5DS1 = 1, DS0 = 13*Mar 1 01:13:39.497:callp :19196BC, vdbptr :1964EEC, state :5*Mar 1 01:13:39.497:Checking ack (trans ID 553892443) :*Mar 1 01:13:39.497:is_capability_ok:caps.codec=5, caps.pkt=10, caps.nt=8*Mar 1 01:13:39.497:is_capability_ok:supported signal=0x426C079C, signal2=0x80003,event=0x6003421F, event2=0x3FDrequested signal=0x8, signal2=0x0,event=0x4, event2=0x0*Mar 1 01:13:39.497:R:requested trans_id (553892443)*Mar 1 01:13:39.497:process_signal_ev:seizure possible=1, signal mask=0x0, mask2=0x0*Mar 1 01:13:39.497:modify_connection:echo_cancel=1.*Mar 1 01:13:39.497:modify_connection:vad=0.*Mar 1 01:13:39.497:modify_connection:peer_addr=6000001, peer_port=16500->16500.*Mar 1 01:13:39.497:modify_connection:conn_mode=3.*Mar 1 01:13:39.497:callp :19196BC, state :5, call ID :16, event :31*Mar 1 01:13:39.501:callp :1AF5798, state :5, call ID :17, event :31*Mar 1 01:14:01.168:Removing ack (trans ID 237740140) :200 237740140 OK*Mar 1 01:14:03.883:Removing ack (trans ID 698549528) :200 698549528 OKI:7v=0c=IN IP4 5.0.0.1m=audio 16400 RTP/AVP 0*Mar 1 01:14:04.087:Removing ack (trans ID 123764791) :200 123764791 OKI:7v=0c=IN IP4 5.0.0.1m=audio 16400 RTP/AVP 0*Mar 1 01:14:09.573:Removing ack (trans ID 553892443) :200 553892443 OKI:7v=0c=IN IP4 5.0.0.1m=audio 16400 RTP/AVP 0*Mar 1 01:14:48.091:callp :19196BC, state :5, call ID :16, event :12*Mar 1 01:14:48.091:voice_if->call_agent_ipaddr used as Notify entityNotify entity available for Tx SGCP msgNTFY send to ipaddr=1092E01 port=2427*Mar 1 01:14:48.091:Push msg into SGCP wait ack queue* (1)[27]*Mar 1 01:14:48.091:Timed Out interval [1]:(2000)*Mar 1 01:14:48.091:Timed Out interval [1]:(2000)(0):E[27]*Mar 1 01:14:48.128:Removing msg :NTFY 27 ds1-1/13@mc1 SGCP 1.1X:97849341O:hu*Mar 1 01:14:48.128:Unqueue msg from SGCP wait ack q** (0)[27]DS1 = 1, DS0 = 13*Mar 1 01:14:48.212:callp :19196BC, vdbptr :1964EEC, state :5*Mar 1 01:14:48.212:Checking ack (trans ID 79307869) :*Mar 1 01:14:48.212:is_capability_ok:caps.codec=5, caps.pkt=10, caps.nt=8*Mar 1 01:14:48.212:is_capability_ok:supported signal=0x426C079C, signal2=0x80003,event=0x6003421F, event2=0x3FDrequested signal=0x4, signal2=0x0,event=0x0, event2=0x0*Mar 1 01:14:48.212:delete_call:callp:19196BC, call ID:16*Mar 1 01:14:48.212:sgcp delete_call:Setting disconnect_by_dlcx to 1*Mar 1 01:14:48.216:callp :1AF5798, state :6, call ID :17, event :29*Mar 1 01:14:48.216:Call disconnect:Raw Msg ptr = 0x0, call-id=17*Mar 1 01:14:48.216:disconnect_call_leg O.K. call_id=17*Mar 1 01:14:48.216:SGCP:Call disconnect:No need to send onhook*Mar 1 01:14:48.216:Call disconnect:Raw Msg ptr = 0x19953B0, call-id=16*Mar 1 01:14:48.216:disconnect_call_leg O.K. call_id=16*Mar 1 01:14:48.220:callp :1AF5798, state :7, call ID :17, event :13*Mar 1 01:14:48.220:Processing DLCX signal request :4, 0, 0*Mar 1 01:14:48.220:call_disconnected:call_id=17, peer 16 is not idle yet.DS1 = 1, DS0 = 13*Mar 1 01:14:48.272:callp :19196BC, vdbptr :1964EEC, state :7*Mar 1 01:14:48.272:Checking ack (trans ID 75540355) :*Mar 1 01:14:48.272:is_capability_ok:caps.codec=5, caps.pkt=10, caps.nt=8*Mar 1 01:14:48.272:is_capability_ok:supported signal=0x426C079C, signal2=0x80003,event=0x6003421F, event2=0x3FDrequested signal=0x0, signal2=0x0,event=0x8, event2=0x0*Mar 1 01:14:48.272:R:requested trans_id (75540355)*Mar 1 01:14:48.272:process_signal_ev:seizure possible=1, signal mask=0x4, mask2=0x0*Mar 1 01:14:49.043:callp :19196BC, state :7, call ID :16, event :27*Mar 1 01:14:49.043:process_call_feature:Onhook event*Mar 1 01:14:49.043:callp :19196BC, state :7, call ID :16, event :13*Mar 1 01:15:18.288:Removing ack (trans ID 79307869) :250 79307869 OK*Mar 1 01:15:18.344:Removing ack (trans ID 75540355) :200 75540355 OKRelated Commands
debug sgcp packet
To debug Simple Gateway Control Protocol, use the debug sgcp packet EXEC command. Use the no debug sgcp packet to turn off debugging.
debug sgcp packet [endpoint string]
no debug sgcp packetSyntax Description
Default
No default behavior or values.
Command Mode
EXEC
Command History
Examples
The following example shows a debug trace for SGCP packets on a specific endpoint:
router# debug sgcp packet endpoint DS1-0/1End point name for packet debug:DS1-0/1 (1)00:08:14:DS1 = 0, DS0 = 100:08:14:Enable packet end point debug for (DS1-0/1)The following example shows a debug trace for all SGCP packets on a gateway:
router# debug sgcp packet*Mar 1 01:07:45.204:SUCCESS:Request ID string building is OK*Mar 1 01:07:45.204:SUCCESS:Building SGCP Parameter lines is OK*Mar 1 01:07:45.204:SUCCESS:SGCP message building OK*Mar 1 01:07:45.204:SUCCESS:END of building*Mar 1 01:07:45.204:SGCP Packet sent --->NTFY 22 ds1-1/13@mc1 SGCP 1.1X:550092018O:hd<---*Mar 1 01:07:45.204:NTFY Packet sent successfully.*Mar 1 01:07:45.240:Packet received -200 22*Mar 1 01:07:45.244:SUCCESS:SGCP Header parsing was OK*Mar 1 01:07:45.244:SUCCESS:END of Parsing*Mar 1 01:07:45.256:Packet received -RQNT 180932866 ds1-1/13@mc1 SGCP 1.1X:362716780R:hu,k0(A),s0(N),[0-9T](A) (D)D:(9xx|xxxxxxx)*Mar 1 01:07:45.256:SUCCESS:SGCP Header parsing was OK*Mar 1 01:07:45.256:SUCCESS:Request ID string(362716780) parsing is OK*Mar 1 01:07:45.260:SUCCESS:Requested Event parsing is OK*Mar 1 01:07:45.260:SUCCESS:Digit Map parsing is OK*Mar 1 01:07:45.260:SUCCESS:END of Parsing*Mar 1 01:07:45.260:SUCCESS:SGCP message building OK*Mar 1 01:07:45.260:SUCCESS:END of building*Mar 1 01:07:45.260:SGCP Packet sent --->200 180932866 OK<---*Mar 1 01:07:47.915:SUCCESS:Request ID string building is OK*Mar 1 01:07:47.915:SUCCESS:Building SGCP Parameter lines is OK*Mar 1 01:07:47.919:SUCCESS:SGCP message building OK*Mar 1 01:07:47.919:SUCCESS:END of building*Mar 1 01:07:47.919:SGCP Packet sent --->NTFY 23 ds1-1/13@mc1 SGCP 1.1X:362716780O:k0, 4081037, s0<---*Mar 1 01:07:47.919:NTFY Packet sent successfully.*Mar 1 01:07:47.955:Packet received -200 23*Mar 1 01:07:47.955:SUCCESS:SGCP Header parsing was OK*Mar 1 01:07:47.955:SUCCESS:END of Parsing*Mar 1 01:07:47.971:Packet received -CRCX 938694984 ds1-1/13@mc1 SGCP 1.1M:recvonlyL:p:10,e:on,s:off, a:G.711uR:huC:6*Mar 1 01:07:47.971:SUCCESS:SGCP Header parsing was OK*Mar 1 01:07:47.971:SUCCESS:Connection Mode parsing is OK*Mar 1 01:07:47.971:SUCCESS:Packet period parsing is OK*Mar 1 01:07:47.971:SUCCESS:Echo Cancellation parsing is OK*Mar 1 01:07:47.971:SUCCESS:Silence Supression parsing is OK*Mar 1 01:07:47.971:SUCCESS:CODEC strings parsing is OK*Mar 1 01:07:47.971:SUCCESS:Local Connection option parsing is OK*Mar 1 01:07:47.971:SUCCESS:Requested Event parsing is OK*Mar 1 01:07:47.975:SUCCESS:Call ID string(6) parsing is OK*Mar 1 01:07:47.975:SUCCESS:END of Parsing*Mar 1 01:07:47.979:SUCCESS:Conn ID string building is OK*Mar 1 01:07:47.979:SUCCESS:Building SGCP Parameter lines is OK*Mar 1 01:07:47.979:SUCCESS:SGCP message building OK*Mar 1 01:07:47.979:SUCCESS:END of building*Mar 1 01:07:47.979:SGCP Packet sent --->200 938694984 OKI:6v=0c=IN IP4 5.0.0.1m=audio 16538 RTP/AVP 0<---*Mar 1 01:07:48.188:Packet received -MDCX 779665338 ds1-1/13@mc1 SGCP 1.1I:6M:recvonlyL:p:10,e:on,s:off,a:G.711uR:huC:6v=0c=IN IP4 6.0.0.1m=audio 16392 RTP/AVP 0*Mar 1 01:07:48.188:SUCCESS:SGCP Header parsing was OK*Mar 1 01:07:48.188:SUCCESS:Conn ID string(6) parsing is OK*Mar 1 01:07:48.192:SUCCESS:Connection Mode parsing is OK*Mar 1 01:07:48.192:SUCCESS:Packet period parsing is OK*Mar 1 01:07:48.192:SUCCESS:Echo Cancellation parsing is OK*Mar 1 01:07:48.192:SUCCESS:Silence Supression parsing is OK*Mar 1 01:07:48.192:SUCCESS:CODEC strings parsing is OK*Mar 1 01:07:48.192:SUCCESS:Local Connection option parsing is OK*Mar 1 01:07:48.192:SUCCESS:Requested Event parsing is OK*Mar 1 01:07:48.192:SUCCESS:Call ID string(6) parsing is OK*Mar 1 01:07:48.192:SUCCESS:SDP Protocol version parsing OK*Mar 1 01:07:48.192:SUCCESS:SDP Conn Data OK*Mar 1 01:07:48.192:SUCCESS:END of Parsing*Mar 1 01:07:48.200:SUCCESS:Conn ID string building is OK*Mar 1 01:07:48.200:SUCCESS:Building SGCP Parameter lines is OK*Mar 1 01:07:48.200:SUCCESS:SGCP message building OK*Mar 1 01:07:48.200:SUCCESS:END of building*Mar 1 01:07:48.200:SGCP Packet sent --->200 779665338 OKI:6v=0c=IN IP4 5.0.0.1m=audio 16538 RTP/AVP 0<---*Mar 1 01:07:53.674:Packet received -MDCX 177780432 ds1-1/13@mc1 SGCP 1.1I:6M:sendrecvX:519556004L:p:10,e:on, s:off,a:G.711uC:6R:huS:hdv=0c=IN IP4 6.0.0.1m=audio 16392 RTP/AVP 0*Mar 1 01:07:53.674:SUCCESS:SGCP Header parsing was OK*Mar 1 01:07:53.674:SUCCESS:Conn ID string(6) parsing is OK*Mar 1 01:07:53.674:SUCCESS:Connection Mode parsing is OK*Mar 1 01:07:53.674:SUCCESS:Request ID string(519556004) parsing is OK*Mar 1 01:07:53.678:SUCCESS:Packet period parsing is OK*Mar 1 01:07:53.678:SUCCESS:Echo Cancellation parsing is OK*Mar 1 01:07:53.678:SUCCESS:Silence Supression parsing is OK*Mar 1 01:07:53.678:SUCCESS:CODEC strings parsing is OK*Mar 1 01:07:53.678:SUCCESS:Local Connection option parsing is OK*Mar 1 01:07:53.678:SUCCESS:Call ID string(6) parsing is OK*Mar 1 01:07:53.678:SUCCESS:Requested Event parsing is OK*Mar 1 01:07:53.678:SUCCESS:Signal Requests parsing is OK*Mar 1 01:07:53.678:SUCCESS:SDP Protocol version parsing OK*Mar 1 01:07:53.678:SUCCESS:SDP Conn Data OK*Mar 1 01:07:53.678:SUCCESS:END of Parsing*Mar 1 01:07:53.682:SUCCESS:Conn ID string building is OK*Mar 1 01:07:53.682:SUCCESS:Building SGCP Parameter lines is OK*Mar 1 01:07:53.682:SUCCESS:SGCP message building OK*Mar 1 01:07:53.682:SUCCESS:END of building*Mar 1 01:07:53.682:SGCP Packet sent --->200 177780432 OKI:6v=0c=IN IP4 5.0.0.1m=audio 16538 RTP/AVP 0<---*Mar 1 01:09:02.401:SUCCESS:Request ID string building is OK*Mar 1 01:09:02.401:SUCCESS:Building SGCP Parameter lines is OK*Mar 1 01:09:02.401:SUCCESS:SGCP message building OK*Mar 1 01:09:02.401:SUCCESS:END of building*Mar 1 01:09:02.401:SGCP Packet sent --->NTFY 24 ds1-1/13@mc1 SGCP 1.1X:519556004O:hu<---*Mar 1 01:09:02.401:NTFY Packet sent successfully.*Mar 1 01:09:02.437:Packet received -200 24*Mar 1 01:09:02.441:SUCCESS:SGCP Header parsing was OK*Mar 1 01:09:02.441:SUCCESS:END of Parsing*Mar 1 01:09:02.541:Packet received -DLCX 865375036 ds1-1/13@mc1 SGCP 1.1C:6S:hu*Mar 1 01:09:02.541:SUCCESS:SGCP Header parsing was OK*Mar 1 01:09:02.541:SUCCESS:Call ID string(6) parsing is OK*Mar 1 01:09:02.541:SUCCESS:Signal Requests parsing is OK*Mar 1 01:09:02.541:SUCCESS:END of Parsing*Mar 1 01:09:02.545:SUCCESS:SGCP message building OK*Mar 1 01:09:02.545:SUCCESS:END of building*Mar 1 01:09:02.545:SGCP Packet sent --->250 865375036 OK<---*Mar 1 01:09:02.577:Packet received -RQNT 254959796 ds1-1/13@mc1 SGCP 1.1X:358258758R:hd*Mar 1 01:09:02.577:SUCCESS:SGCP Header parsing was OK*Mar 1 01:09:02.577:SUCCESS:Request ID string(358258758) parsing is OK*Mar 1 01:09:02.577:SUCCESS:Requested Event parsing is OK*Mar 1 01:09:02.581:SUCCESS:END of Parsing*Mar 1 01:09:02.581:SUCCESS:SGCP message building OK*Mar 1 01:09:02.581:SUCCESS:END of building*Mar 1 01:09:02.581:SGCP Packet sent --->200 254959796 OKRelated Commands
debug vtsp send-nse
To trigger the VTSP software module to send a triple redundant NSE, use the debug vtsp send-nse EXEC command. Use the no debug vtsp send-nse to disable this action.
debug vtsp send-nse
no debug vtsp send-nseSyntax Description
This command has nor arguments or keywords.
Default
No default behavior or values.
Command Mode
EXEC
Command History
12.0(7)XK
This command was introduced on the Cisco MC3810 and the Cisco 3600 series routers (except the Cisco 3620) in a private release that was not generally available.
Example
The following example triggers the VTSP software module to send a triple redundant NSE:
router# debug vtsp send-nseRelated Commands
Glossary
NSE—Named Service Events.
RTP—Real-Time Protocol.
SGCP—Simple Gateway Control Protocol.
Simple Gateway Control Protocol—Simple Gateway Control Protocol (SGCP) enables intelligent, external call agents to control gateways in a Voice over IP (VoIP) environment. Gateways include trunking gateways and residential gateways. Call agents include TransPath and third-party products. SGCP is intended for use in large IP networks typical of competitive local exchange carriers (CLECs) and Internet exchange carriers (IXCs).
SPI—Service Provider Interface.
TSE—Telephony Signaling Events.
VTSP—Voice Telephony Service Provider.
