Table Of Contents
Support for IUA with SCTP for Cisco Access Servers
Prerequisites for the Support for IUA with SCTP for Cisco Access Servers Feature
Information About the Support for IUA with SCTP for Cisco Access Servers Feature
Multiple Non-Facility Associated Signaling
IUA and SCTP with the Cisco PGW2200
How to Configure the Support for IUA with SCTP for Cisco Access Servers Feature
Creating NFAS Groups and Binding NFAS Groups to the Application Server
Migrating from RLM to IUA with SCTP
Modifying a PRI Group on an MGC
Configuration Examples for Support for IUA with SCTP for Cisco Access Servers
AS and ASP Example Configuration
Creating a Trunk Group and Binding the Trunk Group to an AS Example
Migrating from RLM to IUA for SCTP Example
Modifying a PRI Group on an MGC Example
show ip sctp association parameters
Support for IUA with SCTP for Cisco Access Servers
This document describes support for the IDSN User Adaptation Layer (IUA) with Stream Control Transmission Protocol (SCTP) for the Cisco AS5x00 network access servers (NASs) and the Cisco 2420, Cisco 2600 series, and Cisco 3600 series using Cisco IOS Release 12.2(15)T. This feature is to be used as an alternative to the existing IP-based User Datagram Protocol (UDP)-to-Reliable Link Manager (RLM) transport between the Cisco PGW2200 and Cisco gateways.
This feature supports the Internet Engineering Task Force (IETF) Signaling Transport (Sigtran) standard, IUA with SCTP, to act as the call signaling IP transport mechanism in a Voice Gateway solution. SCTP and IUA are used for Signaling System 7 (SS7) Interconnect solutions, which allows required flexibility in connecting Inter-Machine Trunks (IMTs) from more than one public switched telephone network (PSTN) switch (multiple trunk groups) to the Cisco AS5x00 series gateways, the Cisco 2460, Cisco 2600 series, and Cisco 3600 series. This feature also allows you to interconnect with multiple carriers on high-capacity Cisco AS5x00 gateways for load balancing and redundancy.
Note
This feature does not support the Cisco 2600XM or Cisco 2691.
The IUA and SCTP protocols provide the following:
•
•
•
Feature Specifications for the Support for IUA with SCTP for Cisco Access Servers Feature
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.
Contents
•
•
•
•
Prerequisites for the Support for IUA with SCTP for Cisco Access Servers Feature
You must have Cisco IOS Release 12.2(15)T or later installed and running on your system.
For additional information about IUA with SCTP configuration on the Cisco Media Gateway Controller (MGC), refer to the following feature documents:
•
•
Restrictions
•
•
Information About the Support for IUA with SCTP for Cisco Access Servers Feature
To help you configure the Support for IUA with SCTP for Cisco Access Servers feature, you should understand the following concepts:
•
•
•
•
SCTP
SCTP allows you to terminate multiple switches and trunk groups on a gateway to add scalability. Adding trunk groups does not require more memory or processing resources because SCTP supports multiple streams in a single SCTP association. SCTP is a reliable transport protocol for message-oriented communications; SCTP is specifically designed to support PSTN signaling messages over IP networks.
SCTP allows you to configure at least one trunk group per T1 or E1 interface available on a given platform. For example, a gateway platform with four T1 or E1 interfaces can control four unique trunk groups per device. Certain platforms, such as the Cisco AS5800 and Cisco AS5850, can deliver the individual T1 or E1 trunk groups over a high-speed interface, such as T3, which operates at 45 Mbps. Table 1 lists the number of trunk groups supported per gateway platform.
Table 1 SS7 Interconnect for Voice Gateway Solutions Supported Trunk Groups per Gateway1
Cisco AS5300
4
Verify both T1 and E1 cards.
Cisco AS5350
8
Verify both T1 and E1 cards. Also, verify with Integrated SLT option. Refer to the Integrated Signaling Link Terminal, Cisco IOS Release 12.2(11)T feature document.
Cisco AS5350 CT3
28
CT3 DS-3 card. Also, verify with Integrated SLT option.
Cisco AS5400
16
Verify both T1 and E1 cards. Also, verify with Integrated SLT option.
Cisco AS5400 CT3
28
CT3 DS-3 card. Also, verify with Integrated SLT option.
Cisco AS5850
112
Verify E1 cards and CT3 DS-3 cards.
Note
1 There is no degradation or change in the number of circuit identification codes (CICs) supported on any of the gateways listed.
In a typical network topology, there is only one SCTP association configured between a signaling controller and a gateway. Multiple IP addresses on either side can be designated to the same association for the purpose of link redundancy, or multihoming. On a gateway, signaling messages for all trunk groups are carried over on the same SCTP association to the same signaling controller. Trunk groups on a gateway can also be controlled through different signaling controllers. In such cases, multiple associations can be configured on a gateway and directed to different signaling controllers.
SCTP is based on RFC2960 and offers the following support:
•
•
•
•
•
•
•
•
Figure 1 shows the IUA with SCTP transport stack supported by this feature.
Figure 1 IUA with SCTP Transport Stack
IUA
IUA is the adaptation layer that makes SCTP services available to Q.921 services users, such as Q.931, Q Signaling (QSIG), and National ISDN-2 with Cisco extensions (Cisco NI2+). IUA supports the standard inter-layer primitives provided by Q.921. As a result, an upper layer protocol (ULP) that typically used Q.921 services can be easily migrated to IUA.
IUA service points are represented to the upper-layer protocol as application servers (ASs). Each AS is bound to an SCTP local endpoint managed by an SCTP instance. A remote signaling controller is known as an application server process (ASP). An ASP is connected to the local endpoint through a single SCTP association.
To use IUA services, the AS and ASP should be made available, and a trunk group must be bound to an AS for its Layer 2 server. For more information, see the configuration tasks in the "How to Configure the Support for IUA with SCTP for Cisco Access Servers Feature" section.
Multiple Non-Facility Associated Signaling
If all interfaces on a gateway are controlled through a single signaling controller, all interfaces are bound to the same AS. On a gateway, trunk groups are defined as Non-Facility Associated Signaling (NFAS) groups. An NFAS group is a group of ISDN PRI trunks with a single dedicated D channel. In a Voice Gateway solution, the D channel in a trunk group is symbolic because SS7 is used as the signaling mechanism. The D channels defined for each NFAS group are actually DS0 bearer channels for voice or modem calls. Therefore, each NFAS has a corresponding D channel for which it is allocated.
A symbolic D channel interface is dedicated to a trunk group. Each D channel interface is bound to an AS and a dedicated stream is associated with this interface. Thus, the NFAS group identification can be recovered on each side of the SCTP association through this two-stage mapping as long as both sides share the same configuration information. The multiplexing of multiple trunk groups through a single association is accomplished this way, for example.
The SCTP stream is a logical identification of the grouping of messages and consumes little additional memory and processing power. Each association can support as many as 65,355 streams.
Figure 2 shows the mapping between the trunk group, D channel interface, and SCTP stream.
Figure 2 Mapping Between Trunk Group, Interface, and Stream
Figure 3 shows the NFAS group and SCTP association.
Figure 3 NFAS Group and SCTP Association
See the "Creating NFAS Groups and Binding NFAS Groups to the Application Server" section.
IUA and SCTP with the Cisco PGW2200
This feature enables support of the IUA transport protocol using SCTP on the Cisco PGW2200. The Cisco PGW2200 can now use IUA to communicate with Cisco access servers.
IUA and SCTP on the Cisco PGW2200 provides the following:
•
•
•
•
•
•
For more information about IUA and SCTP on the Cisco PGW2200, refer to the Support for IUA with SCTP feature document on Cisco.com
How to Configure the Support for IUA with SCTP for Cisco Access Servers Feature
This section contains the following procedures:
•
•
•
•
Configuring IUA
An AS and the ASP should be configured first to allow an NI2+ to be bound to the IUA transport layer protocol. The AS is a logical representation of the SCTP local endpoint. The local endpoint can have more than one IP address but must use the same port number.
To configure IUA, you must create the AS and the ASP by using the following commands.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
Step 1
enable
Example:Router> enable
Enables higher privilege levels, such as privileged EXEC mode.
•
Step 2
configure {terminal}
Example:Router# configure terminal
Enters global configuration mode.
Step 3
Router(config)# iuaEnters IUA configuration mode and specifies backhaul using SCTP. There are no arguments for this command.
Step 4
as as-name {localip1 [localip2]} [local-sctp-port]
Example:Router(config-iua)# as as5400-3 10.1.2.34 10.1.2.35 2577Defines an application server (AS) on a gateway.
•
Step 5
Defines an application server process (ASP). To disable, use the no form of this command.
Note
Step 6
(Optional) IP address to enable and disable keep alives and control SCTP keepalives on destination IP addresses.
Step 7
(Optional) IP precedence level for protocol data units (PDUs). To disable, use the no form of this command.
•
•
Note
Step 8
(Optional) Changes the failover timer value (1 to 10 seconds) in milliseconds. Valid values range from 1000 to 10000 ms. Default is 4000 ms.
•
•
•
Step 9
Router(config-iua)# exitExits IUA configuration mode and completes IUA configuration.
Configuring SCTP
To configure the SCTP T1 initiation timer, use the following commands.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables higher privilege levels, such as privileged EXEC mode.
•
Step 2
configure {terminal}
Example:Router# configure terminal
Enters global configuration mode.
Step 3
Router(config)# iuaEnters IUA configuration mode and specifies backhaul using SCTP. There are no arguments for this command.
Step 4
as as-name {localip1 [localip2]} [local-sctp-port]
Example:Router(config-iua)# as as5400-3 10.1.2.34 10.1.2.35 2577Defines an application server (AS) on a gateway.
•
Step 5
(Optional) Changes the failover timer value (1 to 10 seconds) in milliseconds. Valid values range from 1000 to 10000 msec. Default is 4000 msec.
•
•
Step 6
as as-name sctp-startup-rtx number
Example:Router(config-iua)# as as5400-3 sctp-startup-rtx 8
Configures the SCTP maximum startup retransmission timer.
•
Step 7
as as-name sctp-streams number
Example:Router(config-iua)# as as5400-3 sctp-streams 56
Configures the number of SCTP streams for this AS.
•
•
Note
Step 8
as as-name sctp-t1init number
Example:Router(config-iua)# as as1 sctp-t1init 1000
Configures the SCTP T1 initiation timer.
•
Step 9
asp asp-name as as-name ip-address
Example:Router(config-iua)# asp asp1 as as1 10.4.8.68 10.4.9.68
Creates an ASP and specifies to which AS this ASP belongs.
Step 10
Specifies the IP precedence level for protocol data units (PDUs). To disable, use the no form of this command.
•
•
Note
Step 11
Defines an application server process (ASP).
Note
Step 12
(Optional) Specifies the IP address to enable and disable keep alives and control SCTP keepalives on destination IP addresses.
Step 13
asp asp-name sctp-max-association ip-address number
Example:Router(config-iua)# asp asp1 sctp-max-association 10.10.10.10 20
Sets the maximum association retransmissions for this ASP.
•
Step 14
asp asp-name sctp-path-retransmission ip-address number
Example:Router(config-iua)# asp asp1 sctp-path-retransmission 10.10.10.10 2Sets the SCTP path retransmissions for this ASP.
•
Step 15
asp asp-name sctp-t3-timeout ip-address number
Example:Router(config-iua)# asp asp1 sctp-t3-timeout 10.10.10.10 60000Sets the SCTP T3 retransmission timeout for this ASP.
•
Step 16
Exits IUA-SCTP configuration mode and completes the configuration.
Creating NFAS Groups and Binding NFAS Groups to the Application Server
Use the procedure in this section to configure two T1 interfaces into two NFAS groups, or trunk groups, that are served by the same AS with two different SCTP streams (ASPs). These steps allow you to configure the NFAS primary D channel and bind the D channel to an IUA AS.
Note
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
Step 1
enable
Example:Router> enable
Enables higher privilege levels, such as privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
controller t1 1/0/0
Example:Router(config)# controller t1 1/0/0
Enters controller configuration mode on the first T1 controller.
Step 4
pri-group timeslots 1-23 nfas-d primary nfas-int 0 nfas-group number iua as-name
Example:Router(config-controller)# pri-group timeslots 1-23 nfas-d primary nfas-int 0 nfas-group 1 iua as-1
Configures the NFAS primary D channel on one channelized T1 controller, and binds the D channel to an IUA AS.
•
•
Step 5
exit
Example:Router(config-controller)# exit
Exits controller configuration mode on the first controller.
Step 6
controller t1 1/0/1
Example:Router# controller t1 1/0/1
Enters controller configuration mode on the second T1 controller.
Step 7
pri-group timeslots 1-23 nfas-d primary nfas-int 0 nfas-group number iua as-name
Example:Router(config-controller)# pri-group timeslots 1-23 nfas-d primary nfas-int 0 nfas-group 1 iua as-1
Configures the NFAS primary D channel on another channelized T1 controller, and binds the D channel to an IUA AS.
•
Step 8
Returns to global configuration mode and completes the configuration.
Migrating from RLM to IUA with SCTP
To migrate from RLM to IUA with SCTP, you must perform the following tasks in privileged EXEC mode. You must link to IUA instead of RLM.
Restrictions
The following changes have been made between RLM and IUA with SCTP:
•
•
•
•
See the "Migrating from RLM to IUA for SCTP Example" section for more information about this migration task.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Modifying a PRI Group on an MGC
Before you can modify a PRI group on an MGC, you must first shut down the D channel beginning in global configuration mode.
Restrictions
The isdn bind commands must be removed from the D channel. The binding of the NFAS groups now takes place when you use the pri-group commands for IUA with SCTP. See the "Modifying a PRI Group on an MGC Example" section.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Troubleshooting Tips
•
•
•
•
•
Configuration Examples for Support for IUA with SCTP for Cisco Access Servers
This section contains the following configuration examples:
•
•
•
•
AS and ASP Example Configuration
The following is an example of an AS configuration on a gateway:
as as5400-3 10.4.8.69 10.4.9.69 2577In the configuration above, an AS named as-named as5400-3 is configured to use two local IP addresses and a port number of 2577. IP address values that are set apply to all IP addresses of the ASP.
The following configuration example defines a remote signaling controller asp1 at two IP addresses for the AS named as5400-3. The remote SCTP port number is 2577:
Router(config-iua)# as as5400-3 10.4.8.69 10.4.9.69 2477Router(config-iua)# asp asp1 as as5400-3 10.4.8.68 10.4.9.68 2577Multiple ASPs can be defined for a single AS for the purpose of redundancy, but only one ASP can be active. The other ASP is inactive and only becomes active after fail-over.
In the Cisco MGC solution, a signaling controller is always the client that initiates the association with a gateway. During the initiation phase, you can request outbound and inbound stream numbers, but the gateway only allows a number that is at least one digit higher than the number of interfaces (T1/E1) allowed for the platform.
The number of streams to assign to a given association is implementation dependent. During the initialization of the IUA association, you need to specify the total number of streams that can be used. Each D channel is associated with a specific stream within the association. With multiple trunk group support, every interface can potentially be a separate D channel.
At startup, the IUA code checks for all the possible T1, E1, or T3 interfaces and sets the total number of inbound and outbound streams supported accordingly. In most cases, there is only a need for one association between the GW and the MGC. For the rare case that you are configuring multiple AS associations to various MGCs, the overhead from the unused streams would have minimal impact. The NFAS D channels are configured for one or more interfaces, where each interface is assigned a unique stream ID.
The total number of streams for the association needs to include an additional stream for the SCTP management messages. So during startup the IUA code adds one to the total number of interfaces (streams) found.
You have the option to manually configure the number of streams per association. In the backhaul scenario, if the number of D channel links is limited to one, allowing the number of streams to be configurable avoids the unnecessary allocation of streams in an association that will never be used. For multiple associations between a GW and multiple MGCs, the configuration utility is useful in providing only the necessary number of streams per association. The overhead from the streams allocated but not used in the association is negligible.
If the number of streams is manually configured through the CLI, the IUA code cannot distinguish between a startup event, which automatically sets the streams to the number of interfaces, or if the value is set manually during runtime. If you are configuring the number of SCTP streams manually, you must add one plus the number of interfaces using the sctp-streams keyword with the as command. Otherwise, IUA needs to always add one for the management stream, and the total number of streams increments by one after every reload.
When you set the SCTP stream with the CLI, you cannot change the inbound and outbound stream support once the association is established with SCTP. The value takes effect when you first remove the IUA AS configuration and then configure it back as the same AS or a new one. The other option is to reload the router.
The following is an example of an AS configuration on a gateway. The configuration shows that an AS named as5400-3 is configured to use two local IP addresses and a port number of 2577:
Router(config-iua)# as as5400-3 10.1.2.34 10.1.2.35 2577The following example sets the failover time (in milliseconds) between 1 and 10 seconds. Entering a value of 1000 would equal one second. Entering a value of 10000 would equal 10 seconds. In this example, the failover timer has been set to 10 seconds:
Router(config-iua)# as as5400-3 fail-over 10000The following example specifies the number of SCTP streams for this association. In this example, 57 is the maximum number of SCTP streams allowed:
Router(config-iua)# as as5400-3 sctp-streams 57The following example sets the SCTP maximum startup retransmission interval. In this example, 20 is the maximum interval allowed:
Router(config-iua)# as as5400-3 sctp-startup 20The following example sets the SCTP T1 initiation timer in milliseconds. In this example, 60000 is the maximum time allowed:
Router(config-iua)# as as5400-3 sctp-t1init 60000The following example specifies the IP address to enable and disable keepalives:
Router(config-iua)# asp asp1 sctp-keepalive 10.1.2.34The following example specifies the keepalive interval in milliseconds. Valid values range from 1000 to 60000. In this example, the maximum value of 60000 ms is used:
Router(config-iua)# asp asp1 sctp-keepalive 10.10.10.10 60000The following example specifies the IP address for the SCTP maximum association and the maximum association value. Valid values range from 2 to 20. The default is 20, which is the maximum value allowed:
Router(config-iua)# asp asp1 sctp-max-association 10.10.10.10 20The following example specifies the IP address for the SCTP path retransmission and the maximum path retransmission value. Valid values range from 2 to 10. The default is 10, which is the maximum value allowed:
Router(config-iua)# asp asp1 sctp-path-retransmissions 10.10.10.10 10The following examples specifies the IP address for SCTP T3 timeout and specifies the T3 timeout value in milliseconds. Valid timeout values range from 300 to 60000. Default is 60000, which is the maximum timeout value allowed:
Router(config-iua)# asp asp1 sctp-t3-timeout 10.10.10.10 60000The following example configuration is described below. Figure 4 shows the configuration in diagram form.
Router(config-iua)# as as5300-17 10.0.0.07 10.1.1.17 2097Router(config-iua)# asp pgwa AS as5300-17 10.0.0.00 10.1.1.10 2097Router(config-iua)# asp pgwb AS as5300-17 10.0.0.06 10.1.1.16 2097•
•
•
•
•
Figure 4 Specific ASP Example Configuration
The following sample is how the output from the above configuration would look:
iuaAS as5300-17 10.0.0.07 10.1.1.17 2097ASP pgwa AS as5300-17 10.0.0.00 10.1.1.10 2097ASP pgwb AS as5300-17 10.0.0.06 10.1.1.16 2097!!controller E1 0framing NO-CRC4clock source line primarypri-group timeslots 1-31 nfas-d primary nfas-int 0 nfas-group 1 iua as5300-17!controller E1 1framing NO-CRC4clock source line secondary 1pri-group timeslots 1-31 nfas-d none nfas-int 1 nfas-group 1!controller E1 2framing NO-CRC4pri-group timeslots 1-31 nfas-d primary nfas-int 0 nfas-group 2 iua as5300-17!controller E1 3framing NO-CRC4pri-group timeslots 1-31 nfas-d none nfas-int 1 nfas-group 2!!interface Ethernet0description the ip is 10.0.0.06 for interface e0ip address 10.0.0.06 255.255.255.0no ip route-cacheno ip mroute-cache!interface FastEthernet0description the primary ip is 10.1.1.16 for interface f0ip address 10.1.1.10 255.255.255.0no ip route-cacheno ip mroute-cacheduplex autospeed auto!interface Dchannel0no ip addresstrunk-group 11isdn timer t309 100isdn timer t321 30000isdn incoming-voice modemisdn T303 20000isdn negotiate-bchan resend-setupno cdp enable!interface Dchannel2no ip addresstrunk-group 22isdn timer t309 100isdn timer t321 30000isdn incoming-voice modemisdn T303 20000isdn negotiate-bchan resend-setupno cdp enable!trunk group 11!trunk group 22!dial-peer voice 1 potsincoming called-numberdestination-pattern 997001direct-inward-dialtrunk-group 11forward-digits all!dial-peer voice 2 potsincoming called-numberdestination-pattern 997002direct-inward-dialtrunk-group 22forward-digits all!Creating a Trunk Group and Binding the Trunk Group to an AS Example
You can configure the NFAS primary D channel on one channelized T1 controller, and bind the D channel to an IUA AS by using the pri-group (pri-slt) command.
This example uses the Cisco AS5400 and applies to T1, which has 24 timeslots and is used mainly in North America and Japan. You can choose any timeslot other than 24 to be the virtual container for the D channel parameters for ISDN.
Router(config-controller)# pri-group timeslots 1-23 nfas-d primary nfas-int 0 nfas-group 1 iua as5400-4-1The following example applies to E1, which has 32 timeslots and is used by the rest of the world. You can choose any timeslot other than 32 to be the virtual container for the D channel parameters for ISDN.
Router(config-controller)# pri-group timeslots 1-31 nfas-d primary nfas-int 0 nfas-group 1 iua as5400-4-1SCTP Configuration Example
You can implicitly configure the number of streams in SCTP by specifying only the serial interfaces that are configured to use IUA. The number of streams is bound to the actual number of interfaces supporting IUA. To support Cisco MGC solutions, you can configure any number of streams for each NFAS D channel, up to the total number of interfaces available in a given GW. For platforms using the PRI backhaul with SCTP and the ISDN Q.921 User Adaptation Layer (UAL), such as the Cisco 3660, you can configure the number of streams to match the number of PRIs that are actually backhauled to the Telcordia session manager.
The following example sets the failover time (in milliseconds) between 1 and 10 seconds. Entering a value of 1000 would equal one second. Entering a value of 10000 would equal 10 seconds. In this example, the failover timer has been set to 10 seconds. The default value is 4000 msec. Once you have set the failover timer to a value, you can return it to its default of 4000 msec by using the no form of this command.
Router(config-iua)# as as5400-3 fail-over 10000The following example sets the SCTP maximum startup retransmission interval. Valid values are from 2 to 20:
Router(config-iua)# as as1 sctp-startup-rtx 20The following example specifies the number of SCTP streams for an association. Valid values are from 1 to 56:
Router(config-iua)# as as1 sctp-streams 56The following example sets the SCTP T1 initiation timer in milliseconds. Valid values are from 1000 to 60000:
Router(config-iua)# as as1 sctp-t1init 60000Migrating from RLM to IUA for SCTP Example
The following changes have been made between RLM and IUA with SCTP. Use the examples in this section to help you with your configuration:
•
For RLM, the following format was used:
interface Serial3/0:1:23
Note
For IUA, the following format is used:
interface Dchannel3/0:1•
For RLM, remove the "isdn rlm-group 1" line shown in bold:
interface Serial3/0:1:23no ip addressisdn switch-type primary-niisdn incoming-voice modemisdn T321 30000isdn T303 20000isdn T200 2000isdn rlm-group 1isdn negotiate-bchan resend-setupisdn bchan-number-order ascendingno cdp enableFor IUA, use the following format:
interface Dchannel3/0:1no ip addressisdn timer t309 100isdn timer t321 30000isdn incoming-voice modemisdn T303 20000no isdn send-status-enquiryisdn negotiate-bchan resend-setupisdn bchan-number-order ascendingno cdp enableModifying a PRI Group on an MGC Example
To modify a PRI group on an MGC using this feature, the isdn bind commands must be removed from the D channel. The binding of the NFAS groups now takes place when you use the pri-group commands for IUA with SCTP.
Use the following examples to help you with your configuration:
•
controller T1 3/0:1framing esfpri-group timeslots 1-23 nfas-d primary nfas-int 0 nfas-group 1•
controller T1 3/0:1framing esfpri-group timeslots 1-23 nfas-d primary nfas-int 0 nfas-group 1 iua as-1Additional References
The following sections provide additional references related to the Support for IUA with SCTP for Cisco Access Servers feature:
•
•
Related Documents
Cisco IOS commands to support voice, video, and fax applications
Cisco IOS Voice, Video, and Fax Command Reference, Release 12.2 T
How to configure your Cisco router or access server to support voice, video, and fax applications
Cisco IOS Voice, Video, and Fax Configuration Guide, Release 12.2T
Install and configure the Cisco MGC
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
Cisco MGC software Release 9 informational events, alarms, and log messages.
Cisco Media Gateway Controller Software Release 9 Messages Reference Guide
Cisco MGC software Release 9 Man-Machine Language (MML) commands
Cisco Media Gateway Controller Software Release 9 MML Command Reference
Operating, maintaining, and troubleshooting the core elements of the MGC node
Cisco Media Gateway Controller Software Release 9 Operations, Maintenance, and Troubleshooting Guide
Provisioning the Cisco MGC
Cisco Media Gateway Controller Software Release 9 Provisioning Guide
Cisco SLT information
Distributed system that provides SS7 connectivity for Voice-over-IP (VoIP) gateways by using the Cisco PGW 2200.
Cisco SS7 Interconnect for Voice Gateways Solution, Release 2.0
IP Transfer Point (ITP) information
IP Transfer Point (ITP), Cisco IOS Release 12.2(2)MB
PRI/Q.921 signaling backhaul
PRI Backhaul Using the Stream Control Transmission Protocol and the ISDN Q.921 User Adaptation Layer
SCTP feature information
IUA with SCTP information
Standards
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
—
MIBs
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
http://tools.cisco.com/ITDIT/MIBS/servlet/index
If Cisco MIB Locator does not support the MIB information that you need, you can also obtain a list of supported MIBs and download MIBs from the Cisco MIBs page at the following URL:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
To access Cisco MIB Locator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions found at this URL:
RFCs
RFC3057 (IUA)2
RFC2960 (SCTP)2
1 Not all supported RFCs are listed.
2 CRC32 is the checksum supported.
Technical Assistance
Command Reference
This section documents new and modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.2 T command reference publications.
New Commands
•
Modified Commands
•
•
•
•
as
To define an application server (AS) for backhaul, use the as command in IUA configuration mode. To disable, use the no form of this command.
Note
as as-name {localip1 [localip2]} [local-sctp-port] [fail-over-timer] [sctp-startup-rtx] [sctp-streams] [sctp-t1init]
no as as-name
Syntax Description
Defaults
No AS is defined.
Command Modes
IUA configuration
Command History
Usage Guidelines
A maximum of two local IP addresses can be specified. (Note that SCTP has built-in support for multihomed machines.)
The default value of the SCTP streams is determined by the hardware that you have installed. The value of the failover timer is found in the show iua as all command output.
The number of streams to assign to a given association is implementation dependent. During the initialization of the IUA association, you need to specify the total number of streams that can be used. Each D channel is associated with a specific stream within the association. With multiple trunk group support, every interface can potentially be a separate D channel.
At startup, the IUA code checks for all the possible T1, E1, or T3 interfaces and sets the total number of inbound and outbound streams supported accordingly. In most cases, there is only a need for one association between the gateway (GW) and the Media Gateway Controller (MGC). For the rare case that you are configuring multiple AS associations to various MGCs, the overhead from the unused streams would have minimal impact. The NFAS D channels are configured for one or more interfaces, where each interface is assigned a unique stream ID.
The total number of streams for the association needs to include an additional stream for the SCTP management messages. So during startup, the IUA code adds one to the total number of interfaces (streams) found.
You have the option to manually configure the number of streams per association. In the backhaul scenario, if the number of D channel links is limited to one, allowing the number of streams to be configurable avoids the unnecessary allocation of streams in an association that will never be used. For multiple associations between a GW and multiple MGCs, the configuration utility is useful in providing only the necessary number of streams per association. The overhead from the streams allocated but not used in the association is negligible.
If the number of streams is manually configured through the CLI, the IUA code cannot distinguish between a startup event, which automatically sets the streams to the number of interfaces, or if the value is set manually during runtime. If you are configuring the number of SCTP streams manually, you must add one plus the number of interfaces using the sctp-streams keyword. Otherwise, IUA needs to always add one for the management stream, and the total number of streams increments by one after every reload.
When you set the SCTP stream with the CLI, you cannot change the inbound and outbound stream support once the association is established with SCTP. The value takes effect when you first remove the IUA AS configuration and then configure it back as the same AS or a new one. The other option is to reload the router.
Additional keywords for this command are as follows:
•
•
•
•
Examples
An AS and the application server process (ASP) should be configured first to allow a National ISDN-2 with Cisco extensions (NI2+) to be bound to this transport layer protocol. The AS is a logical representation of the SCTP local endpoint. The local endpoint can have more than one IP address but must use the same port number.
The following is an example of an AS configuration on a gateway. The configuration shows that an AS named as5400-3 is configured to use two local IP addresses and a port number of 2577:
Router(config-iua)# as as5400-3 10.1.2.34 10.1.2.35 2577The following output shows that the AS (as1) is defined for backhaul:
AS as1 10.21.0.2 9900Related Commands
asp
To define an application server process (ASP) for backhaul, use the asp command in IUA configuration mode. To disable the ASP, use the no form of this command.
Note
asp asp-name as as-name {remoteip1 [remoteip2]} [remote-sctp-port] [ip-precedence [sctp-keepalives] [sctp-max-associations] [sctp-path-retransmissions] [sctp-t3-timeout]
no asp asp-name
Syntax Description
asp-name
Names the current ASP.
as
Application server to which the ASP belongs.
as-name
Name of the application server to which the ASP belongs.
remoteip1
Remote IP address for this Simple Control Transmission Protocol (SCTP) association.
remoteip2
Designates the remote IP address for this SCTP association.
remote-sctp-port
Connects to a remote SCTP port rather than the IUA well-known port.
ip-precedence
(Optional) Sets IP Precedence bits for protocol data units (PDUs).
•
show ip sctp association parameters output. The default type of service (ToS) value is 0.•
sctp-keepalives
(Optional) Modifies the keepalive behavior of an IP address in a particular ASP.
•
sctp-max-associations
(Optional) Sets the SCTP maximum association retransmissions for a particular ASP. Valid values range from 2 to 20. The default is 3.
sctp-path-
retransmissions(Optional) Sets the SCTP path retransmissions for a particular ASP. Valid values range from 2 to 10. The default is 10.
sctp-t3-timeout
(Optional) Sets the SCTP T3 retransmission timeout for a particular ASP. The default value is 900 ms. Valid timeout values range from 300 to 60000. Default is 60000.
Defaults
No ASP is defined.
Command Modes
IUA configuration
Command History
Usage Guidelines
You can configure the precedence value in IUA in the range of 0 to 7 for a given IP address. Within IUA, the upper three bits representing the IP precedence in the ToS byte (used in the IP header) is set based on the user input before passing down the value to SCTP. In turn, SCTP passes the ToS byte value to IP. The default value is 0 for "normal" IP precedence handling.
The asp-name argument specifies the name of this ASP. The ip-precedence keyword sets the precedence and ToS field. The remote-ip-address argument specifies the IP address of the remote end-point (the address of MGC, for example). The number argument can be any IP precedence bits in the range 1 to 255.
When you use the sctp-keepalives keyword, the number argument specifies the keepalive interval (in milliseconds) when an IP address has been selected. Valid values range from 1000 to 6000 ms. Keepalives are enabled by default.
The no form of the command results in precedence bits not being explicitly set by SCTP.
In the case of a hot-standby Cisco PGW2200 pair, there is usually one ASP active and another in the INACTIVE state. The ASP_UP message is used to bring the ASP state on the GW to the INACTIVE state, followed by the ASPTM message, ASP_ACTIVE to ready the IUA link for data exchange. (Eventually the QPTM Establish Request message actually initiates the start of the D channel for the given interface.) In the event that the GW detects a failure on the active ASP, it can send a NTFY message to the standby ASP to request that it become active.
Examples
An ASP is a local representation of an SCTP association because it specifies a remote endpoint that will be in communication with an AS local endpoint. An ASP is defined for a given AS. For example, the following configuration defines a remote signaling controller asp-name at two IP addresses for AS as1. The remote SCTP port number is 2577:
Router(config-iua) as as1 10.4.8.69, 10.4.9.69 2477Router(config-iua) asp asp1 as as1 10.4.8.68 10.4.9.68 2577Multiple ASPs can be defined for a single AS for the purpose of redundancy, but only one ASP can be active. The ASPs are inactive and only become active after fail-over.
In the Cisco Media Gateway Controller (MGC) solution, a signaling controller is always the client that initiates the association with a gateway. During the initiation phase, you can request outbound and inbound stream numbers, but the gateway only allows a number that is at least one digit higher than the number of interfaces (T1/E1) allowed for the platform.
The following example specifies the IP precedence level on the specified IP address. This example uses IP precedence level 7, which is the maximum level allowed:
Router(config-iua)# asp asp1 ip-precedence 10.1.2.345 7The following example specifies the IP address to enable and disable keepalives:
Router(config-iua)# asp asp1 sctp-keepalive 10.1.2.34The following example specifies the keepalive interval in milliseconds. In this example, the maximum value of 60000 ms is used:
Router(config-iua)# asp asp1 sctp-keepalive 10.10.10.10 60000The following example specifies the IP address for the SCTP maximum association and the maximum association value. In this example, a maximum value of 20 is used:
Router(config-iua)# asp asp1 sctp-max-association 10.10.10.10 20The following example specifies the IP address for the SCTP path retransmission and the maximum path retransmission value. In this example, a maximum value of 20 is used:
Router(config-iua)# asp asp1 sctp-path-retransmissions 10.10.10.10 10The following example specifies the IP address for SCTP T3 timeout and specifies the T3 timeout value in milliseconds. In this example, the maximum value of 60000 is used:
Router(config-iua)# asp asp1 sctp-t3-timeout 10.10.10.10 60000Related Commands
debug iua as
To display debug messages for the IDSN User Adaptation Layer (IUA) application server (AS), use the debug iua as command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug iua as {user | state} {all | name as-name}
no debug iua as
Syntax Description
user
Application program interfaces (APIs) usage and events between the ISDN layer and IUA.
state
AS state transitions.
all
Enables debug for all the configured AS.
name as-name
Name of the AS.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following example shows debug output when an ISDN backhaul connection is initially established. The output shows that state debugging is turned on for all ASs and that the AS is active.
Router# debug iua as state allIUA :state debug turned ON for ALL AS00:11:52:IUA:AS as1 number of ASPs up is 100:11:57:IUA:AS as1 xsition AS-Up --> AS-Active, cause - ASP asp1Related CommandsActive
debug iua asp
To display debug messages for the IDSN User Adaptation Layer (IUA) application server process (ASP), use the debug iua asp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug iua asp {pak | peer-msg | sctp-sig | state} {all | name asp-name}
no debug iua as
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following example shows debug output when an ISDN backhaul connection is initially established. The output shows that peer message debugging is turned on for all DSPs and that the ASP is active.
Router# debug iua asp peer-msg allIUA :peer message debug turned ON for ALL ASPsRouter#00:04:58:IUA :recieved ASP_UP message on ASP asp100:04:58:IUA:ASP asp1 xsition ASP-Down --> ASP-Up , cause - rcv peermsgASP-UP00:04:58:IUA:sending ACK of type 0x304 to asp asp100:05:03:IUA:recv ASP_ACTIVE message for ASP asp100:05:03:IUA:ASP asp1 xsition ASP-Up --> ASP-Active, cause - rcv peermsgASP-ActiveRelated Commands
iua
To specify backhaul using Stream Control Transmission Protocol (SCTP) and to enter IDSN User Adaptation Layer (IUA) configuration mode, use the iua command in terminal configuration mode.
iua
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Terminal configuration
Command History
Usage Guidelines
You must first enter IUA configuration mode to access SCTP configuration mode. First enter IUA configuration mode by using the example below and then enter the sctp command at the Router(config-iua)# prompt to bring up SCTP configuration mode. See the sctp command.
Examples
The following example shows how to enter iua configuration mode:
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# iuaRouter(config-iua)#The following example shows how to configure the failover-timer by setting the failover time (in milliseconds) to 1 second for a particular AS:
Router(config-iua)# as as5400-3 fail-over-timer 1000The following example configures the number of SCTP streams for this AS to 57, which is the maximum value allowed:
Router(config-iua)# as as5400-3 sctp-streams 57Related Commands
isdn bind-l3 iua-backhaul
ISDN backhaul using SCTP for an interface.
Information about the current condition of an AS.
Information about the current condition of an ASP.
pri-group (pri-slt)
To specify an ISDN PRI on a channelized T1 or E1 controller, use the pri-group (pri-slt) command in controller configuration mode. To remove the ISDN PRI configuration, use the no form of this command.
pri-group [timeslots timeslot-range [nfas_d [backup | none | primary [nfas_int number]] [nfas-group number [iua as-name]]]
no pri-group
Syntax Description
Defaults
No ISDN-PRI group is configured.
Command Modes
Controller configuration
Command History
Usage Guidelines
This command provides another way to bind a D channel to a specific IUA AS. This option allows the RLM group to be configured at the pri-group level instead of in the D channel configuration. For example, a typical configuration would look like the following:
controller t1 1/0/0pri-group timeslots 1-24 nfas_d pri nfas_int 0 nfas_group 1 iua asnameBefore you enter this command, you must specify an ISDN-PRI switch type and an E1 or T1 controller.
When configuring NFAS, use this extended version of the pri-group command to specify the following values for the associated channelized T1 controllers configured for ISDN:
•
•
•
The iua keyword is used to bind an NFAS group to the IUA AS.
When binding the D channel to an IUA AS, the as-name must match the name of an AS set up during IUA configuration.
Before you can modify a PRI group on a Media Gateway Controller (MGC), you must first shut down the D channel.
The following shows how to shut down the D channel:
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# interface Dchannel3/0:1Router(config-if)# shutdownExamples
The following example configures the NFAS primary D channel on one channelized T1 controller, and binds the D channel to an IUA AS. This example uses the Cisco AS5400 and applies to T1, which has 24 timeslots and is used mainly in North America and Japan:
Router(config-controller)# pri-group timeslots 1-23 nfas-d primary nfas-int 0 nfas-group 1 iua as5400-4-1The following example applies to E1, which has 32 timeslots and is used by the rest of the world:
Router(config-controller)# pri-group timeslots 1-31 nfas-d primary nfas-int 0 nfas-group 1 iua as5400-4-1The following example configures ISDN-PRI on all time slots of controller E1 on a Cisco 2600 series router:
Router(config)# controller E1 4/1Router(config-controller)# pri-group timeslots 1-7,16In the following example, the rlm-timeslot keyword automatically creates interface serial 4/7:11 (4/7:0:11 if you are using the CT3 card) for the D channel object on a Cisco AS5350. You can choose any timeslot other than 24 to be the virtual container for the D channel parameters for ISDN.
Router(config-controller)# pri-group timeslots 1-23 nfas-d primary nfas-int 0 nfas-group 0 rlm-timeslot 3Related Commands
isdn switch-type
Configures the Cisco 2600 series router PRI interface to support QSIG signaling.
sctp
To enter the Stream Control Transmission Protocol (SCTP) configuration, use the sctp command in IDSN User Adaptation Layer (IUA) configuration mode. To disable, use the no form of this command.
sctp [[t1-init milliseconds][t3-rtx-min seconds][t3-rtx-max milliseconds][startup-rtx number][assoc-rtx number][path-rtx number]]
no sctp
Syntax Description
Defaults
No default behavior or values.
Command Modes
IUA configuration
Command History
Usage Guidelines
To enter SCTP configuration commands, you must first enter IUA configuration mode and then enter sctp at the Router(config-iua)# prompt to enter SCTP configuration mode.
Examples
The following example shows how to enter IUA configuration mode:
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# iuaRouter(config-iua)#The following is an example of how to set failover time (in milliseconds) between 1 and 10 seconds as part of SCTP configuration of the T1 initiation timer. This example uses the lowest failover timer value allowed (1 second):
Router(config-iua)# as as5400-3 fail-over 1000The following is an example of how to set SCTP maximum startup retransmission interval. This example uses the maximum startup retransmission interval value allowed:
Router(config-iua)# as as5400-3 sctp-startup 20The following is an example of how to configure the number of SCTP streams for this AS. This example uses the maximum SCTP streams allowed:
Router(config-iua)# as as5400-3 sctp-streams 57The following is an example of how to configure the SCTP T1 initiation timer (in milliseconds). This example uses the maximum timer value allowed:
Router(config-iua)# as as5400-3 sctp-t1init 60000Related Commands
show ip sctp association parameters
To display the parameters configured for the association defined by association ID, use the
show ip sctp association parameters command in privileged EXEC mode.show ip sctp association parameters [assoc-id]
Syntax Description
assoc-id
(Optional) Association identifier. Shows the associated ID statistics for the Stream Control Transmission Protocol (SCTP) association.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command provides information to determine the stability of SCTP associations, dynamically calculated statistics about destinations, values to assess network congestion. This command also displays parameter values for the specified association.
This command requires an association identifier. Association identifiers can be obtained from the output of the show ip sctp association list command.
There are many parameters that are defined for each association. Some are configured parameters, and others are calculated. There are three main groupings of parameters displayed by this command:
•
•
•
The association configuration section displays information similar to that in the show ip sctp association list command, including association identifiers, state, and local and remote port and address information. The current primary destination is also displayed.
Examples
The following sample output shows the IP SCTP association parameters for association 0:
Router# show ip sctp association parameters 0** SCTP Association Parameters **AssocID: 0 Context: 0 InstanceID: 1Assoc state: ESTABLISHED Uptime: 19:05:57.425Local port: 8181Local addresses: 10.1.0.3 10.2.0.3Remote port: 8181Primary dest addr: 10.5.0.4Effective primary dest addr: 10.5.0.4Destination addresses:10.5.0.4: State: ACTIVEHeartbeats: Enabled Timeout: 30000 msRTO/RTT/SRTT: 1000/16/38 ms TOS: 0 MTU: 1500cwnd: 5364 ssthresh: 3000 outstand: 768Num retrans: 0 Max retrans: 5 Num times failed: 010.6.0.4: State: ACTIVEHeartbeats: Enabled Timeout: 30000 msRTO/RTT/SRTT: 1000/4/7 ms TOS: 0 MTU: 1500cwnd: 3960 ssthresh: 3000 outstand: 0Num retrans: 0 Max retrans: 5 Num times failed: 0Local vertag: 9A245CD4 Remote vertag: 2A08D122Num inbound streams: 10 outbound streams: 10Max assoc retrans: 5 Max init retrans: 8CumSack timeout: 200 ms Bundle timeout: 100 msMin RTO: 1000 ms Max RTO: 60000 msLocalRwnd: 18000 Low: 13455 RemoteRwnd: 15252 Low: 13161Congest levels: 0 current level: 0 high mark: 325Table 2 describes significant fields shown in this output.
Related Commands
show isdn
To display the information about memory, Layer 2 and Layer 3 timers, and the status of PRI channels, use the show isdn command in privileged EXEC mode.
show isdn {active [dsl | serial-number] | history [dsl | serial-number] | memory | service [dsl | serial-number] | status [dsl | serial-number] | timers [dsl | serial-number]}
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the show isdn status command to check the serial interface.
Examples
The following is sample output from the show isdn active command:
Router# show isdn active-------------------------------------------------------------------------------ISDN ACTIVE CALLS-------------------------------------------------------------------------------History Table MaxLength = 320 entriesHistory Retain Timer = 15 Minutes-------------------------------------------------------------------------------Call Calling Called Duration Remote Time until Recorded ChargesType Number Number Seconds Name Disconnect Units/Currency-------------------------------------------------------------------------------Out 9876543222 Active(10) idacom 11 u(E)Out 9876543210 Active(34) idacom 115 5 u(D)-------------------------------------------------------------------------------The following is sample output from the show isdn history command:
Router# show isdn history-------------------------------------------------------------------------------ISDN CALL HISTORY-------------------------------------------------------------------------------History Table MaxLength = 320 entriesHistory Retain Timer = 15 Minutes-------------------------------------------------------------------------------Call Calling Called Duration Remote Time until Recorded ChargesType Number Number Seconds Name Disconnect Units/Currency-------------------------------------------------------------------------------Out 47887654 240 blackcanary 5 u(D)In 67893 90 deloreanOut 56745678 Active(90) blackcanary 240 13 u(D)-------------------------------------------------------------------------------Table 3 describes the fields in the show isdn active and show isdn history output displays.
The following output shows PRI configured on a T1 controller:
Router# show isdn servicePRI Channel Statistics:ISDN Dc0 SC, Channel [1-31]Configured Isdn Interface (dsl) 0Channel State (0=Idle 1=Proposed 2=Busy 3=Reserved 4=Restart 5=Maint_Pend)Channel : 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4State : 2 2 2 2 2 2 2 2 2 0 0 0 0 2 2 2 2 2 2 2 2 2 0 0Service State (0=Inservice 1=Maint 2=Outofservice)Channel : 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4State : 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0Channel blocked? (0=No 1=Yes)Channel : 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 40 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0Table 4 describes the fields in the show isdn service output display.
Table 4 show isdn service Field Descriptions
Channel (1-31)
Channel range "1-31" is a standard format for both T1 and E1 outputs, but the state value shown identifies whether the channel is used.
Configured ISDN Interface (dsl 0)
Digital signal link (DSL) value is 0.
State (0=Idle 1=Propose 2=Busy 3=Reserved 4=Restart 5=Maint-Pend)
Current state of each channel. Channels 24 to 31 are marked as reserved when the output is from T1.
Channel (1-31) Service State (0=Inservice 1=Maint 2=Outofservice)
Service state assigned to each channel. Channel 24 is marked as out of service.1
1 If channel 24 (marked as out of service) is configured as the NFAS primary D channel, NFAS will roll over to the backup D channel if one is configured. If channel 24 is a B channel, it will not accept calls.
The following is sample output from the show isdn status command on the Cisco AS5300 with one active call. Changes in the output are shown in bold. Use this command to check the serial interface.
Router# show isdn statusGlobal ISDN Switchtype = primary-niISDN Serial0:23 interface iua as5300-7-1Transport Link Status:ACTIVEdsl 0, interface ISDN Switchtype = primary-ni :Primary D channel of nfas group 1L2 Protocol = IUA L3 Protocol(s) = Q.931Layer 1 Status:ACTIVELayer 2 Status:Not ApplicableLayer 3 Status:0 Active Layer 3 Call(s)Active dsl 0 CCBs = 0The Free Channel Mask: 0x80FFFFFFNumber of L2 Discards = 0, L2 Session ID = 1ISDN Serial1:23 interface iua as5300-7-2Transport Link Status:...Table 5 describes important fields in the show isdn status output display.
The following is sample output from the show isdn timers:
Router# show isdn timersISDN BRI0 Timers (dsl 0) Switchtype = basic-net3ISDN Layer 2 valuesK = 1 outstanding I-framesN200 = 3 max number of retransmitsN202 = 2 max number of retransmits of TEI ID RequestT200 = 1 secondsT202 = 2 secondsT203 = 10 secondsISDN Layer 3 valuesT303 = 4 secondsT305 = 30 secondsT308 = 4 secondsT309 = 0 secondsT310 = 40 secondsT313 = 4 secondsT316 = 0 secondsT318 = 4 secondsT319 = 4 secondsTable 6 displays some typical values of the timers shown in this command display. The values of the timers depend on the switch type and typically are used only for homologation purposes.
Refer to Q.921 and Q.931 specifications for detailed technical definitions of the Layer 2 and Layer 3 timers.
Related Commands
show iua as
To show information about the current condition of an application server (AS), use the show iua as command in privileged EXEC mode.
show iua as {all | name as-name}
Syntax Description
all
Displays information about all configured ASs.
name as-name
Name of a particular AS. Displays information about just that AS.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the show iua as all command to find the failover timer value. You will need to know the failover timer value currently set before you use the as as-name fail-over-timer command to set the failover timer value to fit your application.
Examples
The following typical output for show iua as all shows that the current state of the AS (as1) is active and that there are four PRI interfaces configured to use this AS:
Router# show iua as allName of AS :as1Total num of ASPs configured :2asp1asp2Current state : ACTIVEActive ASP :asp1Number of ASPs up :1Fail-Over time : 4000 millisecondsLocal address list : 10.1.2.345 10.2.3.456Local port:2139Interface IDs registered with this ASInterface ID0 (Dchannel0)3 (Dchannel3)2 (Dchannel2)1 (Dchannel1)Table 7 describes the fields shown in the display.
Related Commands
show iua asp
To provide information about the current condition of an application server process (ASP), use the show iua asp privileged EXEC command.
show iua asp {all | name asp-name}
Syntax Description
all
Displays information about all configured ASPs.
name asp-name
Name of a particular ASP. Displays information about just that ASP.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Examples
The following typical output for the show iua asp all command shows that the current state of the ASP (asp1) is active. This command also gives information about the SCTP association being used by this ASP.
Router# show iua asp allName of ASP :asp1Current State of ASP:ASP-ActiveCurrent state of underlying SCTP Association IUA_ASSOC_ESTAB , assoc id 0SCTP Association information :Local Receive window :9000Remote Receive window :9000Primary Dest address requested by IUA 10.11.2.33Effective Primary Dest address 10.11.2.33Remote address list :10.22.3.44Remote Port :9900Statistics :Invalid SCTP signals Total :0 Since last 0SCTP Send failures :0Table 8 describes the fields shown in the display.
Related CommandsSCTP Send failures :0
Glossary
API—application program interface. The means by which an application program talks to communications software. Standardized APIs allow application programs to be developed independently of the underlying method of communication. A set of standard software interrupts, calls, and data formats that computer application programs use to initiate contact with other devices (for example, network services, mainframe communications programs, or other program-to-program communications). Typically, APIs make it easier for software developers to create the links that an application needs to communicate with the operating system or with the network.
AS—application server.
ASP—application server process .
CIC—circuit identification code.
DPC—destination point code.
DPNSS—Digital Private Network Signaling System
ECN—Explicit Congestion Notification
GW—Gateway Access Server (for example Cisco AS5850).
IETF—Internet Engineering Task Force. Task force consisting of more than 80 working groups responsible for developing Internet standards.
IMT—Inter-Machine Trunk.
IUA—ISDN Q.921 User Adaptation Layer.
LAN—local-area network.
MGC—Media Gateway Controller (for example Cisco PGW2200).
MTU—maximum transmission unit.
NFAS—Non-Facility Associated Signaling.
NI2+—National ISDN-2 with Cisco extensions.
OPC—own point code. Point code of the Cisco PGW2200 signaling controller.
PDU—protocol data unit. OSI term for packet.
POTS—plain old telephone service.
PSTN—public switched telephone network. General term referring to the variety of telephone networks and services in place worldwide. Sometimes called POTS.
RLM—Redundant Link Manager.
QSIG—Q (point of the ISDN model) Signaling. Signaling standard. Common channel signaling protocol based on ISDN Q.931 standards and used by many digital PBXs.
SCTP—Simple Control Transmission Protocol.
SG—signaling gateway.
SIG—signaling transport protocol stack including SCTP, IUA, and Q.931 signaling.
sigtran—IETF Signaling Transport (Sigtran) standard, including SCTP and IUA.
SS7—Signaling System 7. Standard CCS system used with BISDN and ISDN. Developed by Bellcore.
ToS—type of service.
UAL—user adaptation layer.
UDP—User Datagram Protocol.
ULP—upper layer protocol.
VoIP—Voice over IP.
Note
