Table Of Contents
Simple Gateway Control Protocol for the Cisco AS5300 Voice/Gateway
Verifying the SGCP Configuration
Simple Gateway Control Protocol for the Cisco AS5300 Voice/Gateway
Feature Overview
The Simple Gateway Control Protocol (SGCP) version 1.1 enables intelligent, external call agents to control gateways in a Voice over IP (VoIP) environment. Gateways include trunking gateways and residential gateways. This release of SGCP also supports T1/CAS FGD-OS trunks.
Call agents include TransPath and third-party products. This feature is intended for use in large IP networks typical of competitive local exchange carriers (CLECs) and Internet exchange carriers (IXCs).
Benefits
Deregulation in the telecommunications industry gives CLECs opportunities to provide alternative dial tone from the Incumbent Local Exchange Carriers (ILECs). One way of providing alternative dial tone is through Voice over IP (VoIP). SGCP is a protocol that enables an VoIP system to control call setup and teardown as well as CLASS features for less sophisticated gateways.
Note
When you use SGCP in a Voice over IP (VoIP) environment, you do not need to configure VoIP dial peers. The SGCP call agent provides similar functions to VoIP dial peers.
Restrictions
This version of SGCP supports only one T1 controller per Cisco AS5300.
Supported Platform
•
Cisco Access Server 5300
•
uBR924 cable modem
Supported MIBs and RFCs
Standards
No new or modified standards are supported by this feature.
MIBs
•
CISCO-XGCP-MIB
For descriptions of supported MIBs and how to use MIBs, 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 new or modified RFCs are supported by this feature.
Configuration Tasks
This section is divided into the following configuration and verification tasks:
•
Verifying the SGCP Configuration
Configuring Support for SGCP
To configure SGCP on your AS5300, perform the following tasks:
Step 1
Configure IP addresses.
Step 2
Turn on the SGCP application.
Step 3
Enter configuration commands, one per line. End with CNTL/Z.
Step 4
Configure the t1 controller for being controlled by using SGCP.
Step 5
Enter configuration commands, one per line. End with CNTL/Z.
Verifying the SGCP Configuration
To verify your SGCP configuration and obtain SGCP statistics, enter the following commands beginning in the global configuration mode:
Configuration Examples
AS5300-TGW> enableAS5300-TGW# conf tAS5300-TGW(config)# sgcpAS5300-TGW(config)# controller t1 0AS5300-TGW(config-controll)# framing esfAS5300-TGW(config-controll)# clock source line primaryAS5300-TGW(config-controll)# linecode b8zsAS5300-TGW(config-controll)# ds0-group 0 timeslots 1-24 type none service sgcpAS5300-TGW(config-controll)# ^zAS5300-TGW#Command Reference
This section documents new or modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.0 command references.
•
sgcp
clear sgcp statistics
To clear all SGCP statistics, enter 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
Release Modification12.0(5)T
This command was introduced.
12.0(7)T
Support for this command was extend to the uBR924 cable modem.
Example
AS5300-TGW# clear sgcp statisticsAS5300-TGW#Related Commands
ds0-group
To configure channelized T1 timeslots with channel associated signaling, which enables an AS5300 modem to answer and send an analog call, enter the ds0-group controller configuration command. To disable channel associated signaling for one or more timeslots, enter the no form of this command.
ds0-group group-number timeslots range type type service type
no ds0-group group-number timeslots range type type service typeSyntax Description
Default
No default behavior or values.
Command Mode
CONFIG
Command History
Usage Guidelines
Channel associated signaling is also known as robbed bit signaling.
Examples
This example shows how to configure channels 1 through 24 of the T1 controller as CAS group 0 using fgd-eana for SGCP calls. The tone type is defaulted to MF.
router(config)# configure controller t1 1router(config-controller)# ds0-group 0 timeslots 1-24 type fgd-eana service sgcpThis example shows how to configure channels 1 through 24 of the T1 controller as CAS group 1 using fgd-os for SGCP outgoing calls (the default).
router(config)# configure controller t1 1router(config-controller)# ds0-group 1 timeslots 1-24 type fgd-os service sgcpThis example shows how to configure channels 1 through 24 of the T1 controller as CAS group 2 using fgd-tp for incoming voice calls.
router(config)# configure controller t1 1router(config-controller)# ds0-group 2 timeslots 1-24 type fgd-tp service voiceRelated Commands
sgcp
To start and allocate resources for the SCGP daemon, enter the sgcp configuration command. To terminate all calls, release all allocated resources, and kill the SGCP daemon, enter the no form of this command.
sgcp
no sgcpSyntax Description
This command has no arguments or keywords.
Default
No default behavior or values.
Command Mode
CONFIG
Command History
Release Modification12.0(5)T
This command was introduced.
12.0(7)T
Support for this command was extended to the Cisco uBR924 cable modem.
Usage Guidelines
Once you start the SGCP daemon with the sgcp command, you can suspend it (for example, for maintenance) using the sgcp graceful-shutdown command. When you are ready to resume normal SGCP operations, enter the no sgcp graceful-shutdown command. Only enter the no sgcp command if you intend to kill all SGCP applications and protocols.
When the SGCP daemon is not active, all SGCP messages are ignored.
Example
AS5300-TGW(config)# sgcpRelated Commands
Command DescriptionGracefully terminates all SGCP activity.
Specifies the number of times to retry sending the sgcp command.
Enable debugging on SGCP.
sgcp call-agent
To configure the call agent's (media gateway controller) address, enter the sgcp call-agent configuration command. To unconfigure the call agent's address, enter the no form of this command.
sgcp call-agent [ipaddr | hostname] [port]
no sgcp call-agentSyntax Description
ipaddr | hostname
(Optional) Specifies the IP address or name of the call-agent host.
port
(Optional) Specifies the UDP port for the call-agent to use. The default UDP port is 2427.
Default
UDP port 2427
Command Mode
CONFIG
Command History
Release Modification12.0(5)T
This command was introduced.
12.0(7)T
Support for this command was extended to the Cisco uBR924 cable modem.
Usage Guidelines
This command enables the router to find the Call Agent on the IP network. Entering the no sgcp call-agent command simply removes the IP address for the Call Agent.
Example
AS5300-TGW(config)# sgcp call-agent 172.22.92.17Related Commands
Command DescriptionGracefully terminates all SGCP activity.
Specifies the number of times to retry sending the sgcp command.
Enable debugging on SGCP.
sgcp graceful-shutdown
To block new calls while maintaining existing calls, enter the sgcp graceful-shutdown configuration command. To resume SGCP operation, enter 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
CONFIG
Command History
Release Modification12.0(5)T
This command was introduced.
12.0(7)T
Support for this command was extended to the Cisco uBR924 cable modem.
Usage Guidelines
Once you issue this command, all requests for new connections (CreateConnection requests) are denied. All existing calls will be maintained until users end them, or you enter the no sgcp command. When the last active call ends, the SGCP daemon terminates and releases all resources allocated to it. The no sgcp graceful-shutdown command returns the router to normal SGCP operations.
Example
AS5300-TGW(config)# sgcp graceful-shutdownAS5300-TGW(config)#Related Commands
sgcp request retries
To specify the number of times to retry sending the sgcp command, enter the sgcp request retries configuration command. Enter the no form of this command to restore the default value.
sgcp request retries count
no sgcp request retriesSyntax Description
count
Specifies the number of times a notify message is retransmitted to the call agent before it is dropped. The valid range is 1 to 1000.
Default
3.
Command Mode
CONFIG
Command History
Release Modification12.0(5)T
This command was introduced.
12.0(7)T
Support for this command was extended to the Cisco uBR924 cable modem.
Usage Guidelines
This command applies to a trunking gateway.
Example
The following example shows that the system will try to send the sgcp command 10 times before dropping the request:
AS5300-TGW(config)# sgcp request retries 10AS5300-TGW(config)#Related Commands
sgcp request timeout
To specify how long the system waits for a response to a request, enter the sgcp request timeout configuration command. Enter 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 100,000.
Default
500
Command Mode
CONFIG
Command History
Release Modification12.0(5)T
This command was introduced.
12.0(7)T
Support for this command was extended to the Cisco uBR924 cable modem.
Example
The following example shows that the system waits 40 milliseconds for a reply to a request:
AS5300-TGW(config)# sgcp request timeout 40AS5300-TGW(config)#Related Commands
show sgcp
To display SGCP statistics on this router, enter the show sgcp EXEC command.
show sgcp
Syntax Description
This command has no arguments or keywords.
Default
No default behavior or values.
Command Mode
EXEC
Command History
Usage Guidelines
Refer to LS1010 documentation for more information on this command.
Examples
AS5300-TGW# show sgcpSGCP Admin State DOWN, Oper State DOWNSGCP call-agent: 172.22.92.17 , SGCP graceful-shutdown enabled? FALSESGCP request timeout 40, SGCP request retries 10Table 1
show sgcp Field Descriptions
Related Commands
show sgcp connection
To display all the active SGCP connections on this router, enter the show sgcp connection EXEC command.
show sgcp connection [interface number]
Syntax Description
interface
(Optional) Specifies an interface.
number
(Optional) Specifies the T1 interface (controller) number. Valid values are from 0 to 1000.
Default
No default behavior or values.
Command Mode
EXEC
Command History
Release Modification12.0(5)T
This command was introduced.
12.0(7)T
Support for this command was extended to the Cisco uBR924 cable modem.
Usage Guidelines
If you do not specify an interface, this command shows all the active SGCP connections on this host. If you do specify an interface, this command shows only those active connections on the specified interface.
Examples
See the following example for a list of the active connections on this router:
AS5300-TGW# show sgcp connectionEndpoint Call_ID(C) Con_ID(I) (P)ort (M)ode(S)tate (E)vent[SIFL] (R)esult[EA]1. DS1-3/1 C=12320,1,2 I=0x1,1 P=16454,23420 M=3 S=4 E=0,0,0,0 R=0,02. ds1-3/24 C=12324,3,4 I=0x2,2 P=16390,23424 M=4 S=4 E=0,0,0,0 R=0,0See the following example for information on the active connections on interface 1:
AS5300-TGW# show sgcp connection interface 1 ds1-1/3 1234 3 ds1-1/7 1235 4Table 2
show sgcp connection Field Descriptions
Related Commands
show sgcp endpoint
To see which timeslots have been configured as end points for SGCP, enter the show sgcp endpoint EXEC command.
show sgcp endpoint [interface ds1 [ds0]]
Syntax Description
interface
Specifies the interface.
ds1
Specifies the DS1 timeslot. Valid range is from 0 to 1000.
ds0
(Optional) Specifies the DS0 timeslot. Valid range is from 1 to 24.
Default
No default behavior or values.
Command Mode
EXEC
Command History
Release Modification12.0(5)T
This command was introduced.
12.0(7)T
Support for this command was extended to the Cisco uBR924 cable modem.
Examples
See the following example for information on the timeslots (1-24) of group 1 configured for SGCP for port 0:
AS5300-TGW# show sgcp endpoint interface 0T1/0 ds0-group 1 timeslots 1-24See the following example for information on the timeslots (1-24) of group 3 configured for SGCP for port 2:
AS5300-TGW# show sgcp endpoint interface 2T1/2 ds0-group 3 timeslots 1-24AS5300-TGW#Table 3
T1/2 ds0-group ... timeslots ...
The ds0-group command configuration (group number and timeslot range) for the T1 line in slot 2.
show sgcp endpoint Field Descriptions
Related Commands
show sgcp statistics
To display global statistics for the SGCP packet count, success and failure counts, and other information, enter 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
Release Modification12.0(5)T
This command was introduced.
12.0(7)T
Support for this command was extended to the Cisco uBR924 cable modem.
Examples
See the following example for a display of SGCP packet statistics:
AS5300-TGW# show sgcp statisticsUDP 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 0ACK tx 0, NACK tx 0ACK rx 0, NACK rx 0See the following examples for information on how you can filter the command return for specific information:
AS5300-TGW# 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 0AS5300-TGW# 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 0AS5300-TGW# show sgcp statist | include ACKACK tx 0, NACK tx 0ACK rx 0, NACK rx 0Table 4
show sgcp statistics Field Descriptions
Related Commands
Command DescriptionDisplays Simple Gateway Control Protocol information.
Display all the active connections on the host AS5300.
Displays which timeslots have been configured as end points for SGCP.
snmp-server enable traps
To enable the router to send SNMP traps, use the snmp-server enable traps global configuration command. Use the no form of this command to disable SNMP traps.
snmp-server enable traps [trap-type] [trap-option]
no snmp-server enable traps [trap-type] [trap-option]
Syntax Description
Default
Disabled
Command Mode
Global configuration
Command History
Release Modification11.1
This command was introduced.
12.0(7)T
The xgcp option was added and support was extended to the uBR924 cable modem.
Usage Guidelines
Some trap types cannot be controlled with this command. These traps are either always enabled or enabled by some other means. For example, the linkUpDown messages are disabled by the no snmp trap link-status command.
If you enter this command with no keywords, the default is to enable all trap types.
This command is useful for disabling traps that are generating a large amount of uninteresting or useless noise.
If you do not enter an snmp-server enable traps command, no traps controlled by this command are sent. To configure the router to send these SNMP traps, you must enter at least one snmp-server enable traps command. If you enter the command with no keywords, all trap types are enabled. If you enter the command with a keyword, only the trap type related to that keyword is enabled. In order to enable multiple types of traps, you must issue a separate snmp-server enable traps command for each trap type and option.
The snmp-server enable traps command is used in conjunction with the snmp-server host command. Use the snmp-server host command to specify which host or hosts receive SNMP traps. To send traps, you must configure at least one snmp-server host command.
For a host to receive a trap controlled by this command, both the snmp-server enable traps command and the snmp-server host command for that host must be enabled. If the trap type is not controlled by this command, just the appropriate snmp-server host command must be enabled.
The trap types used in this command all have an associated MIB object that allows them to be globally enabled or disabled. Not all of the trap types available in the snmp-server host command have notificationEnable MIB objects, so some of these cannot be controlled using the snmp-server enable traps command.
Note
Occasionally, you may see a DS1 linkUp/linkDown trap generation alarm associated with the device. You can ignore the alarm and manually clear it.
Examples
The following example enables the router to send SNMP poor quality of voice traps:
router(config)# configure terminalrouter(config)# snmp-server enable trap voice poor-qovThe following example enables the router to send all traps to the host myhost.cisco.com using the community string public:
router(config)# snmp-server enable trapsrouter(config)# snmp-server host myhost.cisco.com publicThe following example enables the router to send Frame Relay and environmental monitor traps to the host myhost.cisco.com using the community string public:
router(config)# snmp-server enable traps frame-relayrouter(config)# snmp-server enable traps envmon temperaturerouter(config)# snmp-server host myhost.cisco.com publicThe following example will not send traps to any host. The BGP traps are enabled for all hosts, but the only traps enabled to be sent to a host are ISDN traps.
router(config)# snmp-server enable traps bgprouter(config)# snmp-server host bob public isdnThe following example enables XGCP traps.
router(config)# snmp-server enable traps xgcpRelated Commands
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 sgcp
debug xcctsp all
debug xcctsp error
debug xcctsp sessiondebug sgcp
To debug Simple Gateway Control Protocol, enter the debug sgcp EXEC command. To turn off debugging, enter the no debug sgcp.
debug sgcp {errors | events | packet}
no debug sgcp {errors | events | packet}Syntax Description
Default
No default behavior or values.
Command Mode
EXEC
Command History
Release Modification12.0(5)T
This command was introduced.
12.0(7)T
Support for this command was extended to the Cisco uBR924 cable modem.
Examples
See the following examples to enable and disable debugging at the specified level:
AS5300-TGW# debug sgcp errorsSimple Gateway Control Protocol errors debugging is onAS5300-TGW# no debug sgcp errorsSimple Gateway Control Protocol errors debugging is offAS5300-TGW#AS5300-TGW# debug sgcp eventsSimple Gateway Control Protocol events debugging is onAS5300-TGW# no debug sgcp eventsSimple Gateway Control Protocol events debugging is offAS5300-TGW#AS5300-TGW# debug sgcp packSimple Gateway Control Protocol packets debugging is onAS5300-TGW# no debug sgcp packSimple Gateway Control Protocol packets debugging is offAS5300-TGW#Related Commands
debug xcctsp all
To debug External Call Control TSP information, enter the debug xcctsp all EXEC command. To turn off debugging, enter the no form of this command.
debug xcctsp all
no debug xcctsp allSyntax Description
This command has no arguments or keywords.
Default
No default behavior or values.
Command Mode
EXEC
Command History
Release Modification12.0(5)T
This command was introduced.
12.0(7)T
Support for this command was extended to the Cisco uBR924 cable modem.
Examples
See the following examples to turn on and off external call control debugging:
AS5300-TGW# debug xcctsp allExternal call control all debugging is onAS5300-TGW# no debug xcct allExternal call control all debugging is offAS5300-TGW#Related Commands
Command DescriptionEnables debugging on external call control errors.
Enables debugging on external call control sessions.
debug xcctsp error
To debug External Call Control TSP error information, enter the debug xcctsp error EXEC command. To turn off error debugging, enter the no form of this command.
debug xcctsp error
no debug xcctsp error
Syntax Description
This command has no arguments or keywords.
Default
No default behavior or values.
Command Mode
EXEC
Command History
Release Modification12.0(5)T
This command was introduced.
12.0(7)T
Support for this command was extended to the Cisco uBR924 cable modem.
Examples
See the following examples to turn on and off error-level debugging
AS5300-TGW# debug xcctsp errorExternal call control error debugging is onAS5300-TGW# no debug xcctsp errorExternal call control error debugging is offRelated Commands
Command DescriptionEnables debugging on all external call control levels.
Enables debugging on external call control sessions.
debug xcctsp session
To debug External Call Control TSP session information, enter the debug xcctsp session EXEC command. To turn off debugging, enter the no form of this command.
debug xcctsp session
no debug xcctsp session
Syntax Description
This command has no arguments or keywords.
Default
No default behavior or values.
Command Mode
EXEC
Command History
Release Modification12.0(5)T
This command was introduced.
12.0(7)T
Support for this command was extended to the Cisco uBR924 cable modem.
Examples
See the following examples to turn on and off session-level debugging:
AS5300-TGW# debug xcct sessExternal call control session debugging is onAS5300-TGW# no debug xcct sessExternal call control session debugging is offAS5300-TGW#Related Commands
Command DescriptionEnables debugging on external call control levels.
Enables debugging on external call control errors.

