Cisco IOS Dial Technologies Configuration Guide, Release 12.4T
Configuring ISDN PRI
Downloads: This chapterpdf (PDF - 631.0KB) | Feedback

Configuring ISDN PRI

Table Of Contents

Configuring ISDN PRI

Signaling Overview

In-Band and Out-of-Band Signaling

Channelized E1 and T1 on Cisco Devices

How to Configure ISDN PRI

Requesting PRI Line and Switch Configuration from a Telco Service Provider

Configuring Channelized E1 ISDN PRI

Configuring Channelized T1 ISDN PRI

Configuring the Serial Interface

Specifying an IP Address for the Interface

Configuring Encapsulation on ISDN PRI

Configuring Network Addressing

Configuring ISDN Calling Number Identification

Overriding the Default TEI Value

Configuring a Static TEI

Configuring Incoming ISDN Modem Calls

Filtering Incoming ISDN Calls

Configuring the ISDN Guard Timer

Configuring Inclusion of the Sending Complete Information Element

Configuring ISDN PRI B-Channel Busyout

Configuring NSF Call-by-Call Support

Configuring Multiple ISDN Switch Types

Configuring B Channel Outgoing Call Order

Performing Configuration Self-Tests

Monitoring and Maintaining ISDN PRI Interfaces

How to Configure Robbed-Bit Signaling for Analog Calls over T1 Lines

How to Configure CAS

CAS on Channelized E1

Configuring CAS for Analog Calls over E1 Lines

Configuring CAS on a Cisco Router Connected to a PBX or PSTN

CAS on T1 Voice Channels

Configuring ANI/DNIS Delimiters for CAS Calls on CT1

How to Configure Switched 56K Digital Dial-In over Channelized T1 and Robbed-Bit Signaling

Switched 56K Scenarios

Switched 56K and Analog Modem Calls into T1 CAS

Basic Call Processing Components

ISDN BRI Calls into T1 CAS

How to Configure Switched 56K Services

How to Configure E1 R2 Signaling

E1 R2 Signaling Overview

Configuring E1 R2 Signaling

Configuring E1 R2 Signaling for Voice

Monitoring E1 R2 Signaling

Verifying E1 R2 Signaling

Troubleshooting E1 R2 Signaling

Enabling R1 Modified Signaling in Taiwan

R1 Modified Signaling Topology

R1 Modified Signaling Configuration Task List

Configuring R1 Modified Signaling on a T1 Interface

Configuring R1 Modified Signaling on an E1 Interface

Troubleshooting Channelized E1 and T1 Channel Groups

Interface Local Loopback

Interface Remote Loopback

Configuration Examples for Channelized E1 and Channelized T1

ISDN PRI Examples

Global ISDN, BRI, and PRI Switch Example

Global ISDN and Multiple BRI and PRI Switch Using TEI Negotiation Example

NSF Call-by-Call Support Example

PRI on a Cisco AS5000 Series Access Server Example

ISDN B-Channel Busyout Example

Multiple ISDN Switch Types Example

Outgoing B-Channel Ascending Call Order Example

Static TEI Configuration Example

Call Reject Configuration Examples

ISDN Cause Code Override and Guard Timer Example

PRI Groups and Channel Groups on the Same Channelized T1 Controller Example

Robbed-Bit Signaling Examples

Allocating All Channels for Robbed-Bit Signaling Example

Mixing and Matching Channels—Robbed-Bit Signaling and Channel Grouping

Switched 56K Configuration Examples

Switched 56K T1 Controller Procedure

Mixture of Switched 56K and Modem Calls over CT1 CAS Example

Switched 56K and Analog Modem Calls over Separate T1 CAS Lines Example

Comprehensive Switched 56K Startup Configuration Example

ISDN CAS Examples

Allocating All Channels for CAS Example

Mixing and Matching Channels—CAS and Channel Grouping Example

E1 R2 Signaling Procedure

R1 Modified Signaling Using an E1 Interface Example

R1 Modified Signaling for Taiwan Configuration Example


Configuring ISDN PRI


This chapter describes how to configure channelized E1 and channelized T1 for ISDN PRI and for two types of signaling to support analog calls over digital lines. This information is included in the following sections:

Signaling Overview

How to Configure ISDN PRI

Monitoring and Maintaining ISDN PRI Interfaces

How to Configure Robbed-Bit Signaling for Analog Calls over T1 Lines

How to Configure CAS

How to Configure Switched 56K Digital Dial-In over Channelized T1 and Robbed-Bit Signaling

How to Configure Switched 56K Services

How to Configure E1 R2 Signaling

Enabling R1 Modified Signaling in Taiwan

Configuration Examples for Channelized E1 and Channelized T1

In addition, this chapter describes how to run interface loopback diagnostics on channelized E1 and channelized T1 lines. For more information, see the "How to Configure Switched 56K Digital Dial-In over Channelized T1 and Robbed-Bit Signaling" section later in this chapter, and the Cisco IOS Interface Configuration Guide, Release 12.2.

For hardware technical descriptions and for information about installing the controllers and interfaces, refer to the hardware installation and maintenance publication for your particular product.

To identify the hardware platform or software image information associated with a feature, use the Feature Navigator on Cisco.com to search for information about the feature or refer to the software release notes for a specific release. For more information, see the "Identifying Supported Platforms" section in the "Using Cisco IOS Software" chapter.

For a complete description of the channelized E1/T1 commands in this chapter, refer to the Cisco IOS Dial Technologies Command Reference. To locate documentation of other commands that appear in this chapter, use the command reference master index or search online.

Signaling Overview

Channelized T1 and channelized E1 can be configured for ISDN PRI, synchronous serial, and asynchronous serial communications.

Channelized T1 and channelized E1 are supported by corresponding controllers. Each T1 or E1 controller has one physical network termination, but it can have many virtual interfaces, depending on the configuration.

In-Band and Out-of-Band Signaling

The terms in-band and out-of-band indicate whether various signals—which are used to set up, control, and terminate calls—travel in the same channel (or band) with voice calls or data made by the user, or whether those signals travel in a separate channel (or band).

ISDN, which uses the D channel for signaling and the B channels for user data, fits into the out-of-band signaling category.

Robbed-bit signaling, which uses bits from specified frames in the user data channel for signaling, fits into the in-band signaling category.

Channel-associated signaling (CAS), which uses E1 time slot 16 (the D channel) for signaling, fits into the out-of-band signaling category.

Channelized E1 and T1 on Cisco Devices

You can allocate the available channels for channelized E1 or T1 in the following ways:

All channels can be configured to support ISDN PRI. Channelized T1 ISDN PRI offers 23 B channels and 1 D channel. Channelized E1 ISDN PRI offers 30 B channels and 1 D channel. Channel 24 is the D channel for T1, and channel 16 is the D channel for E1.

If you are not running ISDN PRI, all channels can be configured to support robbed-bit signaling, which enables a Cisco modem to receive and send analog calls.

All channels can be configured in a single channel group. For configuration information about this leased line or nondial use, see the "Configuring Serial Interfaces" chapter in the Cisco IOS Interface Configuration Guide.

Mix and match channels supporting ISDN PRI and channel grouping.

Mix and match channels supporting ISDN PRI, robbed-bit signaling, and channel grouping across the same T1 line. For example, on the same channelized T1 line you can configure the pri-group timeslots 1-10 command, channel-group 11 timeslots 11-16 command, and cas-group 17 timeslots 17-23 type e&m-fgb command. This is a rare configuration because it requires you to align the correct range of time slots on both ends of the connection.

See the sections "PRI Groups and Channel Groups on the Same Channelized T1 Controller Example," "Robbed-Bit Signaling Examples," and the "ISDN CAS Examples" at the end of this chapter.

How to Configure ISDN PRI

This section describes tasks that are required to get ISDN PRI up and running. This section does not address routing issues, dialer configuration, and dial backup. For information about those topics, see the chapters in the "Dial-on-Demand Routing" part of this manual.

To configure ISDN PRI, perform the tasks in the following sections:

Requesting PRI Line and Switch Configuration from a Telco Service Provider (Required)

Configuring Channelized E1 ISDN PRI (As required)

Configuring Channelized T1 ISDN PRI (As required)

Configuring the Serial Interface (Required)

Configuring NSF Call-by-Call Support (Primary-4ESS Only)

Configuring Multiple ISDN Switch Types (Optional)

Configuring B Channel Outgoing Call Order (Optional)

Performing Configuration Self-Tests (Optional)

See the section "Monitoring and Maintaining ISDN PRI Interfaces" later in this chapter for tips on maintaining the ISDN PRI interface. See the end of this chapter for the "ISDN PRI Examples" section.


Note After the ISDN PRI interface and lines are operational, configure the D-channel interface for dial-on-demand routing (DDR). The DDR configuration specifies the packets that can trigger outgoing calls, specifies whether to place or receive calls, and provides the protocol, address, and phone number to use.


Requesting PRI Line and Switch Configuration from a Telco Service Provider

Before configuring ISDN PRI on your Cisco router, you need to order a correctly provisioned ISDN PRI line from your telecommunications service provider.

This process varies dramatically from provider to provider on a national and international basis. However, some general guidelines follow:

Verify if the outgoing B channel calls are made in ascending or descending order. Cisco IOS default is descending order however, if the switch from the service providers is configured for outgoing calls made in ascending order, the router can be configured to match the switch configuration of the service provider.

Ask for delivery of calling line identification. Providers sometimes call this CLI or automatic number identification (ANI).

If the router will be attached to an ISDN bus (to which other ISDN devices might be attached), ask for point-to-multipoint service (subaddressing is required) and a voice-and-data line.

Table 1 provides a sample of the T1 configuration attributes you might request for a PRI switch used in North America.

Table 1 North American PRI Switch Configuration Attributes  

Attribute
Value

Line format

Extended Superframe Format (ESF)

Line coding

Binary 8-zero substitution (B8ZS)

Call type

23 incoming channels and 23 outgoing channels

Speed

64 kbps

Call-by-call capability

Enabled

Channels

23 B + D

Trunk selection sequence

Either ascending order (from 1 to 23) or descending order (from 23 to 1)

B + D glare

Yield

Directory numbers

Only 1 directory number assigned by service provider

SPIDs required?

None


Configuring Channelized E1 ISDN PRI

To configure ISDN PRI on a channelized E1 controller, use the following commands beginning in global configuration mode:

 
Command
Purpose

Step 1 

Router(config)# isdn switch-type switch-type

Selects a service provider switch type that accommodates PRI. (See Table 2 for a list of supported switch type keywords.)

Step 2 

Router(config)# controller e1 slot/port

or

Router(config)# controller e1 number

Defines the controller location in the Cisco 7200 or Cisco 7500 series router by slot and port number.

Defines the controller location in the Cisco 4000 series or the Cisco AS5200 universal access server by unit number.1

Step 3 

Router(config-controller)# framing crc4

Defines the framing characteristics as cyclic redundancy check 4 (CRC4).

Step 4 

Router(config-controller)# linecode hdb3

Defines the line code as high-density bipolar 3 (HDB3).

Step 5 

Router(config-controller)# pri-group [timeslots range]

Configures ISDN PRI.

1 Controller numbers range from 0 to 2 on the Cisco 4000 series and from 1 to 2 on the Cisco AS5000 series access server.

If you do not specify the time slots, the specified controller is configured for 30 B channels and 1 D channel. The B channel numbers range from 1 to 31; channel 16 is the D channel for E1. Corresponding serial interfaces numbers range from 0 to 30. In commands, the D channel is interface serial controller-number:15. For example, interface serial 0:15.

Table 2 lists the keywords for the supported service provider switch types to be used in Step 1 above.

Table 2 ISDN Service Provider PRI Switch Types 

Switch Type Keywords
Description/Use
Voice/PBX Systems

 primary-qsig

Supports QSIG signaling per Q.931. Network side functionality is assigned with the isdn protocol-emulate command.

Australia and Europe

 primary-net5

NET5 ISDN PRI switch types for Asia, Australia, and New Zealand; ETSI-compliant switches for Euro-ISDN E-DSS1 signaling system.

Japan

 primary-ntt

Japanese NTT ISDN PRI switches.

North America

 primary-4ess

Lucent (AT&T) 4ESS switch type for the United States.

 primary-5ess

Lucent (AT&T) 5ESS switch type for the United States.

 primary-dms100

Nortel DMS-100 switch type for the United States.

 primary-ni

National ISDN switch type.

All Users

 none

No switch defined.



Note For information and examples for configuring ISDN PRI for voice, video, and fax applications, refer to the Cisco IOS Voice, Video, and Fax Applications Configuration Guide.


Configuring Channelized T1 ISDN PRI

To configure ISDN PRI on a channelized T1 controller, use the following commands beginning in global configuration mode:

 
Command
Purpose

Step 1 

Router(config)# isdn switch-type switch-type

Selects a service provider switch type that accommodates PRI. (Refer to Table 2 for a list of supported PRI switch type keywords.)

Step 2 

Router(config)# controller t1 slot/port


or

Router(config)# controller t1 number

Specifies a T1 controller on a Cisco 7500.

Specifies a T1 controller on a Cisco 4000.1

Step 3 

Router(config-controller)# framing esf

Defines the framing characteristics as Extended Superframe Format (ESF).

Step 4 

Router(config-controller)# linecode b8zs

Defines the line code as binary 8 zero substitution (B8ZS).

Step 5 

Router(config-controller)# pri-group [timeslots range]2

Configures ISDN PRI.

If you do not specify the time slots, the controller is configured for 23 B channels and 1 D channel.

1 Controller numbers range from 0 to 2 on the Cisco 4000 series and from 1 to 2 on the Cisco AS5000 series.

2 On channelized T1, time slots range from 1 to 24. You can specify a range of time slots (for example, pri-group timeslots 12-24) if other time slots are used for non-PRI channel groups.

If you do not specify the time slots, the specified controller is configured for 24 B channels and 1 D channel. The B channel numbers range from 1 to 24; channel 24 is the D channel for T1. Corresponding serial interfaces numbers range from 0 to 23. In commands, the D channel is interface serial controller-number:23. For example, interface serial 0:23.

Configuring the Serial Interface

When you configure ISDN PRI on the channelized E1 or channelized T1 controller, in effect you create a serial interface that corresponds to the PRI group time slots. This interface is a logical entity associated with the specific controller. After you create the serial interface by configuring the controller, you must configure the D channel serial interface. The configuration applies to all the PRI B channels (time slots).

To configure the D channel serial interface, perform the tasks in the following sections:

Specifying an IP Address for the Interface (Required)

Configuring Encapsulation on ISDN PRI (Required)

Configuring Network Addressing (Required)

Configuring ISDN Calling Number Identification (As Required)

Overriding the Default TEI Value (As Required)

Configuring a Static TEI (As Required)

Configuring Incoming ISDN Modem Calls (As Required)

Filtering Incoming ISDN Calls (As Required)

Configuring the ISDN Guard Timer (Optional)

Configuring Inclusion of the Sending Complete Information Element (Optional)

Configuring ISDN PRI B-Channel Busyout (Optional)

Specifying an IP Address for the Interface

To configure the D channel serial interface created for ISDN PRI, use the following commands beginning in global configuration mode:

 
Command
Purpose

Step 1 

Router(config)# interface serial slot/port:23

Router(config)# interface serial number:23

or

Router(config)# interface serial slot/port:15

Router(config)# interface serial number:15

Specifies D channel on the serial interface for channelized T1 and begins interface configuration mode.


Specifies D channel on the serial interface for channelized E1 and begins interface configuration mode.

Step 2 

Router(config-if)# ip address ip-address

Specifies an IP address for the interface.

When you configure the D channel, its configuration is applied to all the individual B channels.

Configuring Encapsulation on ISDN PRI

PPP encapsulation is configured for most ISDN communication. However, the router might require a different encapsulation for traffic sent over a Frame Relay or X.25 network, or the router might need to communicate with devices that require a different encapsulation protocol.

Configure encapsulation as described in one of the following sections:

Configuring PPP Encapsulation

Configuring Encapsulation for Frame Relay or X.25 Networks

Configuring Encapsulation for Combinet Compatibility

In addition, the router can be configured for automatic detection of encapsulation type on incoming calls. To configure this feature, complete the tasks in the "Configuring Automatic Detection of Encapsulation Type of Incoming Calls" section.


Note See the sections "Dynamic Multiple Encapsulations" and "Configuring Encapsulation on ISDN BRI" in the chapter "Configuring ISDN BRI" for information about the Cisco Dynamic Multiple Encapsulations feature.


Configuring PPP Encapsulation

Each ISDN B channel is treated as a serial line and supports HDLC and PPP encapsulation. The default serial encapsulation is HDLC. To configure PPP encapsulation, use the following command in interface configuration mode:

Command
Purpose

Router(config-if)# encapsulation ppp

Configures PPP encapsulation.


Configuring Encapsulation for Frame Relay or X.25 Networks

If traffic from this ISDN interface crosses a Frame Relay or X.25 network, the appropriate addressing and encapsulation tasks must be completed as required for Frame Relay or X.25 networks.

See the sections "Sending Traffic over Frame Relay, X.25, or LAPB Networks" in the chapter "Configuring Legacy DDR Spokes" for more information about addressing, encapsulation, and other tasks necessary to configure Frame Relay or X.25 networks.

Configuring Encapsulation for Combinet Compatibility

Historically, Combinet devices supported only the Combinet Proprietary Protocol (CPP) for negotiating connections over ISDN B channels. To enable Cisco routers to communicate with those Combinet bridges, the Cisco IOS software supports the CPP encapsulation type.

To enable routers to communicate over ISDN interfaces with Combinet bridges that support only CPP, use the following commands in interface configuration mode:

 
Command
Purpose

Step 1 

Router(config-if)# encapsulation cpp

Specifies CPP encapsulation.

Step 2 

Router(config-if)# cpp callback accept

Enables CPP callback acceptance.

Step 3 

Router(config-if)# cpp authentication

Enables CPP authentication.

Most Combinet devices support PPP. Cisco routers can communicate over ISDN with these devices by using PPP encapsulation, which supports both routing and fast switching.

Cisco 700 and 800 series routers and bridges (formerly Combinet devices) support only IP, IPX, and bridging. For AppleTalk, Cisco routers automatically perform half-bridging with Combinet devices. For more information about half-bridging, see the section "Configuring PPP Half-Bridging" in the "Configuring Media-Independent PPP and Multilink PPP" chapter in this publication.

Cisco routers can also half-bridge IP and IPX with Combinet devices that support only CPP. To configure this feature, you only need to set up the addressing with the ISDN interface as part of the remote subnet; no additional commands are required.

Configuring Automatic Detection of Encapsulation Type of Incoming Calls

You can enable a serial or ISDN interface to accept calls and dynamically change the encapsulation in effect on the interface when the remote device does not signal the call type. For example, if an ISDN call does not identify the call type in the Lower Layer Compatibility fields and is using an encapsulation that is different from the one configured on the interface, the interface can change its encapsulation type at that time.

This feature enables interoperation with ISDN terminal adapters that use V.120 encapsulation but do not signal V.120 in the call setup message. An ISDN interface that by default answers a call as synchronous serial with PPP encapsulation can change its encapsulation and answer such calls.

Automatic detection is attempted for the first 10 seconds after the link is established or the first 5 packets exchanged over the link, whichever is first.

To enable automatic detection of encapsulation type, use the following command in interface configuration mode:

Command
Purpose

Router(config-if)# autodetect encapsulation encapsulation-type

Enables automatic detection of encapsulation type on the specified interface.


You can specify one or more encapsulations to detect. Cisco IOS software currently supports automatic detection of PPP and V.120 encapsulations.

Configuring Network Addressing

When you configure networking, you specify how to reach the remote recipient. To configure network addressing, use the following commands in interface configuration mode:

 
Command
Purpose

Step 1 

Router(config-if)# dialer map protocol next-hop-address name hostname speed 56|64 dial-string[:isdn-subaddress]


or

Defines the protocol address of the remote recipient, host name, and dialing string; optionally, provides the ISDN subaddress; sets the dialer speed to 56 or 64 kbps, as needed.

 

Router(config-if)# dialer map protocol next-hop-address name hostname spc [speed 56 | 64] [broadcast] dial-string[:isdn-subaddress]

(Australia) Uses the spc keyword that enables ISDN semipermanent connections.

Step 2 

Router(config-if)# dialer-group group-number

Assigns the interface to a dialer group to control access to the interface.

Step 3 

Router(config-if)# dialer-list dialer-group list access-list-number

Associates the dialer group number with an access list number.

Step 4 

Router(config-if)# access-list access-list-number {deny | permit} protocol source address source-mask destination destination-mask

Defines an access list permitting or denying access to specified protocols, sources, or destinations.

Australian networks allow semipermanent connections between customer routers with PRIs and the TS-014 ISDN PRI switches in the exchange. Semipermanent connections are offered at better pricing than leased lines.

Packets that are permitted by the access list specified by the dialer-list command are considered interesting and cause the router to place a call to the identified destination protocol address.


Note The access list reference in Step 4 of this task list is an example of the access list commands allowed by different protocols. Some protocols might require a different command form or might require multiple commands. See the relevant chapter in the appropriate network protocol configuration guide (for example, the Cisco IOS AppleTalk and Novell IPX Configuration Guide) for more information about setting up access lists for a protocol.


For more information about defining outgoing call numbers, see the sections "Configuring Access Control for Outgoing Calls" in the chapters "Configuring Legacy DDR Spokes" or "Configuring Legacy DDR Hubs" later in this publication.

Configuring ISDN Calling Number Identification

A router might need to supply the ISDN network with a billing number for outgoing calls. Some networks offer better pricing on calls in which the number is presented. When configured, the calling number information is included in the outgoing Setup message.

To configure the interface to identify the billing number, use the following command in interface configuration mode:

Command
Purpose

Router(config-if)# isdn calling-number calling-number

Specifies the calling party number.


This command can be used with all ISDN PRI switch types.

Overriding the Default TEI Value

You can configure ISDN terminal endpoint identifier (TEI) negotiation on individual ISDN interfaces. TEI negotiation is useful for switches that may deactivate Layers 1 or 2 when there are no active calls. Typically, this setting is used for ISDN service offerings in Europe and connections to DMS 100 switches that are designed to initiate TEI negotiation.

By default, TEI negotiation occurs when the router is powered up. The TEI negotiation value configured on an interface overrides the default or global TEI value. On PRI interfaces connecting to DMS 100 switches, the router will change the default TEI setting to isdn tei first-call. To apply TEI negotiation to a specific PRI interface, use the following command in interface configuration mode:

Command
Purpose

Router(config-if)# isdn tei [first-call | powerup]

Determines when ISDN TEI negotiation occurs.


Configuring a Static TEI

Depending on the telephone company you subscribe to, you may have a dynamically or statically assigned terminal endpoint identifier (TEI) for your ISDN service. By default, TEIs are dynamic in Cisco routers. To configure the TEI as a static configuration, use the following command in interface configuration mode:

Command
Purpose

Router(config-if)# isdn static-tei tei-number

Configures a static ISDN Layer 2 TEI over the D channel.

Configuring Incoming ISDN Modem Calls

All incoming ISDN analog modem calls that come in on an ISDN PRI receive signaling information from the ISDN D channel. The D channel is used for circuit-switched data calls and analog modem calls.

To enable all incoming ISDN voice calls to access the call switch module and integrated modems, use the following command in interface configuration mode:

Command
Purpose

Router(config-if)# isdn incoming-voice {modem [56 | 64]}

Routes incoming ISDN modem calls to the call switch module.


The settings for the isdn incoming-voice interface command determine how a call is handled based on bearer capability information, as follows:

isdn incoming-voice voice—Calls bypass the modem and are handled as a voice call.

isdn incoming-voice data—Calls bypass the modem and are handled as digital data.

isdn incoming-voice modem—Calls are passed to the modem and the call negotiates the appropriate connection with the far-end modem.

Refer to the Cisco IOS Voice, Video, and Fax Configuration Guide and Cisco IOS Voice, Video, and Fax Command Reference, Release 12.2, for more information about using the isdn incoming-voice interface configuration command to configure incoming ISDN voice and data calls.

Filtering Incoming ISDN Calls

You may find it necessary to configure your network to reject an incoming call with some specific ISDN bearer capability such as nonspeech or nonaudio data. To filter out unwanted call types, use the following command in interface configuration mode:

Command
Purpose

Router(config-if)# isdn reject {{cause cause-code} |{data [56 | 64]} | piafs | v110 | v120 | vod | voice {[3.1khz | 7khz | speech]}}

Rejects an incoming ISDN BRI or PRI call based on type.



Note When the ISDN interface is configured for incoming voice with the isdn incoming-voice voice command (see the previous section "Configuring Incoming ISDN Modem Calls"), and bearer capability indicates the call as unrestricted digital data (i = 0x8890), the call is handled as voice over data (use vod keyword).


Verifying the Call Reject Configuration

To verify that calls are being rejected, perform the following steps:


Step 1 Enable the following debug commands at the privileged EXEC prompt:

debug isdn event

debug isdn event detail

debug isdn q931

debug isdn q931 l3trace

Step 2 Configure the appropriate isdn reject command. The following example configures the network to reject all incoming data calls on ISDN interfaces 4 through 23:

Router(config)# interface serial 4:23
Router(config-if)# isdn reject data
Router(config-if)# ^Z

Step 3 Build the configuration and then monitor the debug command output for the following string, which indicates that the call was rejected:

ISDN <TYPE:NUMBER>: Rejecting call id <CALLID> isdn calltype screening failed

Step 4 Enter the show isdn status EXEC command to display a detailed report of the ISDN configuration, including status of Layers 1 through 3, the call type, and the call identifier.

Step 5 Turn off the debugging messages by entering the no form of the debug command—no debug isdn event detail, for example— or by entering the undebug form of the command—undebug isdn q931, for example.


Configuring the ISDN Guard Timer

Beginning in Cisco IOS Release 12.2, the ISDN guard timer feature implements a new managed timer for ISDN calls. Because response times for authentication requests can vary, for instance when using DNIS authentication, the guard timer allows you to control the handling of calls.

To configure the ISDN guard timer, use the following command in interface configuration mode:

Command
Purpose

Router(config-if)# isdn guard-timer msecs

Enables the guard timer and sets the number of milliseconds for which the access server waits for RADIUS to respond before rejecting or accepting (optional) a call.

For more information about configuring RADIUS, and to see sample ISDN PRI guard timer configurations, refer to the Cisco IOS Security Configuration Guide.

Configuring Inclusion of the Sending Complete Information Element

In some geographic locations, such as Hong Kong and Taiwan, ISDN switches require that the Sending Complete information element be included in the outgoing Setup message to indicate that the entire number is included. This information element is generally not required in other locations.

To configure the interface to include the Sending Complete information element in the outgoing call Setup message, use the following command in interface configuration mode:

Command
Purpose

Router(config-if)# isdn sending-complete

Includes the Sending Complete information element in the outgoing call Setup message.


Configuring ISDN PRI B-Channel Busyout

To allow the busyout of individual ISDN PRI B channels, use the following commands beginning in global configuration mode:

 
Command
Purpose

Step 1 

Router(config)# interface serial controller:timeslot

Enters interface configuration mode for a D-channel serial interface.

Step 2 

Router(config-if)# isdn snmp busyout b-channel

Allows the busyout of individual PRI B channels via SNMP.

Configuring NSF Call-by-Call Support

Network-Specific Facilities (NSF) are used to request a particular service from the network or to provide an indication of the service being provided. Call-by-call support means that a B channel can be used for any service; its use is not restricted to a certain preconfigured service, such as incoming 800 calls or an outgoing 800 calls. This specific NSF call-by-call service supports outgoing calls configured as voice calls.

This NSF call-by-call support feature is vendor-specific; only routers connected to AT&T Primary-4ESS switches need to configure this feature. This feature is supported on channelized T1.

To enable the router for NSF call-by-call support and, optionally, to place outgoing voice calls, complete the following steps:


Step 1 Configure the controller for ISDN PRI.

Step 2 Configure the D channel interface to place outgoing calls using the dialer map command with a dialing-plan keyword. You can enter a dialer map command for each dialing plan to be supported.

Step 3 Define the dialer map class for that dialing plan.

To define the dialer map class for the dialing plan, use the following commands beginning in global configuration mode:

 
Command
Purpose

Step 1 

Router(config)# map-class dialer classname

Specifies the dialer map class, using the dialing-plan keyword as the class name, and begins map class configuration mode.

Step 2 

Router(config-map-class)# dialer voice-call

(Optional) Enables voice calls.

Step 3 

Router(config-map-class)# dialer outgoing classname

Configures the specific dialer map class to make outgoing calls.


Note To set the called party type to international, the dialed number must be prefaced by 011.



Table 3 lists the NSF dialing plans and supported services offered on AT&T Primary-4ESS switches.

Table 3 NSF Supported Services on AT&T Primary-4ESS Switches

NSF Dialing Plan
Data
Voice
International

Software Defined Network (SDN)1

Yes

Yes

Global SDN

MEGACOMM

No

Yes

Yes

ACCUNET

Yes

Yes

Yes

1 The dialing plan terminology in this table is defined and used by AT&T.


Configuring Multiple ISDN Switch Types

You can apply an ISDN switch type on a per-interface basis, thus extending the existing global isdn switch-type command to the interface level. This allows PRI and BRI to run simultaneously on platforms that support both interface types.

A global ISDN switch type is required and must be configured on the router before you can configure a switch type on an interface.

To configure multiple ISDN switch types for a PRI interface using a channelized E1 or channelized T1 controller, use the following command in global configuration mode:

Command
Purpose

Router(config)# isdn switch-type switch-type

Applies a global ISDN switch type.

You must ensure that the ISDN switch type is valid for the ISDN interfaces on the router. Table 2 lists valid ISDN switch types for BRI and PRI interfaces.


Note When you configure an ISDN switch type on the channelized E1 or T1 controller, this switch type is applied to all time slots on that controller. For example, if you configure channelized T1 controller 1:23, which corresponds to serial interface 1, with the ISDN switch type keyword primary-net5, then all time slots on serial interface 1 (and T1 controller 1) will use the Primary-Net5 switch type.


The following restrictions apply to the Multiple ISDN Switch Types feature:

You must configure a global ISDN switch type using the existing isdn switch-type global configuration command before you can configure the ISDN switch type on an interface. Because global commands are processed before interface level commands, the command parser will not accept the isdn switch-type command on an interface unless a switch type is first added globally. Using the isdn switch-type global command allows for backward compatibility.

If an ISDN switch type is configured globally, but not at the interface level, then the global switch type value is applied to all ISDN interfaces.

If an ISDN switch type is configured globally and on an interface, the interface level switch type supersedes the global switch type at initial configuration. For example, if the global BRI switch-type keyword basic-net3 is defined and the interface-level BRI switch-type keyword is basic-ni, the National ISDN switch type is the value applied to that BRI interface.

The ISDN global switch type value is only propagated to the interface level on initial configuration or router reload. If you reconfigure the global ISDN switch type, the new value is not applied to subsequent interfaces. Therefore, if you require a new switch type for a specific interface, you must configure that interface with the desired ISDN switch type.

If an ISDN global switch type is not compatible with the interface type you are using or you change the global switch type and it is not propagated to the interface level, as a safety mechanism, the router will apply a default value to the interface level, as indicated in Table 4.

Table 4 ISDN PRI and ISDN BRI Global Switch Type Keywords 

Global Switch Type
PRI Interface
BRI Interface

primary-4ess

primary-4ess

basic-ni

primary-5ess

primary-5ess

basic-ni

primary-dms100

primary-dms100

basic-ni

primary-net5

primary-net5

basic-net3

primary-ni

primary-ni

basic-ni

primary-ntt

primary-ntt

basic-ntt

primary-qsig

primary-qsig

basic-qsig

primary-ts014

primary-ts014

basic-ts013

basic-1tr6

primary-net5

basic-1tr6

basic-5ess

primary-ni

basic-5ess

basic-dms100

primary-ni

basic-dms100

basic-net3

primary-net5

basic-net3

basic-ni

primary-ni

basic-ni

basic-ntt

primary-ntt

basic-ntt

basic-qsig

primary-qsig

basic-qsig

basic-ts013

primary-ts014

basic-ts013

basic-vn3

primary-net5

basic-vn3


If, for example, you reconfigure the router to use global switch type keyword basic-net3, the router will apply the primary-net5 ISDN switch type to PRI interfaces and the basic-net3 ISDN switch type to any BRI interfaces. You can override the default switch assignment by configuring a different ISDN switch type on the associated interface.

Configuring B Channel Outgoing Call Order

You can configure the router to select the first available B channel in ascending order (channel B1) or descending order (channel B23 for a T1 and channel B30 for an E1). To configure the optional task of selecting B channel order for outgoing calls for PRI interface types, use the following command in interface configuration mode:

Command
Purpose

Router(config-if)# isdn bchan-number-order {ascending | descending}

Enables B channel selection for outgoing calls on a PRI interface (optional).


Before configuring the ISDN PRI on your router, check with your service vendor to determine if the ISDN trunk call selection is configured for ascending or descending order. If there is a mismatch between the router and switch with regard to channel availability, the switch will send back an error message stating the channel is not available. By default, the router will select outgoing calls in descending order.

Performing Configuration Self-Tests

To test the ISDN configuration, use the following EXEC commands as needed. Refer to the Cisco IOS Debug Command Reference for information about the debug commands.

Command
Purpose

Router> show controllers t1 slot/port

Checks Layer 1 (physical layer) of the PRI over T1.

Router> show controllers e1 slot/port

Checks Layer 1 (physical layer) of the PRI over E1.

Router> show isdn status

Checks the status of PRI channels.

Router# debug q921

Checks Layer 2 (data link layer).

Router# debug isdn events

or

Router# debug q931

or

Router# debug dialer

or

Router> show dialer

Checks Layer 3 (network layer).


Monitoring and Maintaining ISDN PRI Interfaces

To monitor and maintain ISDN interfaces, use the following EXEC commands as needed:

Command
Purpose
Cisco 7500 series routers

Router> show interfaces serial slot/port bchannel channel-number


or

Cisco 4000 series routers

Router> show interfaces serial number bchannel channel-number

Displays information about the physical attributes of the ISDN PRI over T1 B and D channels.

Cisco 7500 series routers

Router> show interfaces serial slot/port bchannel channel-number


or

Cisco 4000 series routers

Router> show interfaces serial number bchannel channel-number

Displays information about the physical attributes of the ISDN PRI over E1 B and D channels.

Cisco 7500 series routers

Router> show controllers t1 [slot/port]


or

Cisco 4000 series routers

Router> show controllers t1 number

Displays information about the T1 links supported on the ISDN PRI B and D channels.

Cisco 7500 series routers

Router> show controllers e1 [slot/port]


or

Cisco 4000 series routers

Router> show controllers e1 number

Displays information about the E1 links supported on the ISDN PRI B and D channels.

Router> show isdn {active | history | memory | services | status [dsl | serial number] | timers}

Displays information about current calls, history, memory, services, status of PRI channels, or Layer 2 or Layer 3 timers. (The service keyword is available for PRI only.)

Router> show dialer [interface type number]

Obtains general diagnostic information about the specified interface.


How to Configure Robbed-Bit Signaling for Analog Calls over T1 Lines

Some Cisco access servers support robbed-bit signaling for receiving and sending analog calls on T1 lines. Robbed-bit signaling emulates older analog trunk and line in-band signaling methods that are sent in many networks.

In countries that support T1 framing (such as the United States and Canada), many networks send supervisory and signaling information to each other by removing the 8th bit of each time slot of the 6th and 12th frame for superframe (SF) framing. For networks supporting extended superframe (ESF) framing, the 6th, 12th, 18th, and 24th frames are affected. This additional signaling information is added to support channel banks in the network that convert various battery and ground operations on analog lines into signaling bits.

Robbed-bit signaling configured on a Cisco access server enables integrated modems to answer and send analog calls. Robbed bits are forwarded over digital lines. To support analog signaling over T1 lines, robbed-bit signaling must be enabled.


Note The signal type configured on the access server must match the signal type offered by your telco provider. Ask your telco provider which signal type to configure on each T1 controller.


The Cisco access server has two controllers: controller T1 1 and controller T1 0, which must be configured individually.

To configure robbed-bit signaling support for calls made and received, use the following commands beginning in global configuration mode:

 
Command
Purpose

Step 1 

Router(config)# controller t1 0

Enables the T1 0 controller and begins controller configuration mode.

Step 2 

Router(config-controller)# cablelength long dbgain-value dbloss-value

If the channelized T1 line connects to a smart jack instead of a CSU, sets pulse equalization (use parameter values specified by your telco service provider).

Step 3 

Router(config-controller)# framing esf

Sets the framing to match that of your telco service provider, which in most cases is esf.

Step 4 

Router(config-controller)# linecode b8zs

Sets the line-code type to match that of your telco service provider, which in most cases is b8zs.

Step 5 

Router(config-controller)# clock source line primary

Configures one T1 line to serve as the primary or most stable clock source line.

Step 6 

Router(config-controller)# cas-group channel-number timeslots range type signal

Configures channels to accept voice calls.

This step creates interfaces that you can configure.

Step 7 

Router(config-controller)# fdl {att | ansi}

Sets the facilities data-link exchange standard for the CSU, as specified by your telco service provider.

If you want to configure robbed-bit signaling on the other T1 controller, repeat Steps 1 through 7, making sure in Step 5 to select T1 controller line 1 as the secondary clock source.

If you want to configure ISDN on the other controller, see the section "How to Configure ISDN PRI" in this chapter. If you want to configure channel groupings on the other controller, see the chapter "Configuring Synchronous Serial Ports" in this publication; specify the channel groupings when you specify the interface.

See the section "Robbed-Bit Signaling Examples" at the end of this chapter for configuration examples.

How to Configure CAS

The following sections describe how to configure channel-associated signaling in Cisco networking devices for both channelized E1 and T1 lines:

CAS on Channelized E1

CAS on T1 Voice Channels

CAS on Channelized E1

Cisco access servers and access routers support CAS for channelized E1 lines, which are commonly deployed in networks in Latin America, Asia, and Europe. CAS is configured to support channel banks in the network that convert various battery and ground operations on analog lines into signaling bits, which are forwarded over digital lines.

CAS is call signaling that is configured on an E1 controller and enables the access server to send or receive analog calls. The signaling uses the16th channel (time slot); thus, CAS fits in the out-of-band signaling category.

Once CAS is configured on a single E1 controller, remote users can simultaneously dial in to the Cisco device through networks running the R2 protocol (see specifications for your particular network device for the number of dialins supported).

The R2 protocol is an international signaling standard for analog connections. Because R2 signaling is not supported in the Cisco access servers, an E1-to-E1 converter is required.

Figure 1 illustrates that, because the Cisco access servers have more than one physical E1 port on the dual E1 PRI board, up to 60 simultaneous connections can be made through one dual E1 PRI board.

Figure 1 Remote PC Accessing Network Resources Through the Cisco AS5000 Series Access Server


Note For information on how to configure an Anadigicom E1-to-E1 converter, see to the documentation that came with the converter.



Note The dual E1 PRI card must be installed in the Cisco access server before you can configure CAS. To identify the hardware platform or software image information associated with a feature, use the Feature Navigator on Cisco.com to search for information.


Configuring CAS for Analog Calls over E1 Lines

To configure the E1 controllers in the Cisco access servers, use the following commands beginning in global configuration mode:

 
Command
Purpose

Step 1 

Router(config)# controller e1 number

Defines the controller location in the Cisco access server by unit number (choices for the number argument are 1 or 2) and begins controller configuration mode.

Step 2 

Router(config-controller)# cas-group channel-number timeslots range type signal

Configures CAS and the R2 signaling protocol on a specified number of time slots.

Step 3 

Router(config-controller)# framing crc4

Defines the framing characteristics as CRC4.

Step 4 

Router(config-controller)# linecode hdb3

Defines the line code as HDB3.

Step 5 

Router(config-controller)# clock source line primary1

Specifies one E1 line to serve as the primary or most stable clock source line.

1 Specify the other E1 line as the secondary clock source using the clock source line secondary command.

If you do not specify the time slots, CAS is configured on all 30 B channels and one D channel on the specified controller.

See the section "ISDN CAS Examples" for configuration examples.

Configuring CAS on a Cisco Router Connected to a PBX or PSTN

To define E1 channels for the CAS method by which the router connects to a PBX or PSTN, use the following commands beginning in global configuration mode:

 
Command
Purpose

Step 1 

Router(config)# controller e1 slot/port

Specifies the E1 controller that you want to configure with R2 signaling and begins controller configuration.

Step 2 

Router(config-controller)# ds0-group ds0-group-no 
timeslots timeslot-list type {e&m-immediate | 
e&m-delay | e&m-wink | fxs-ground-start | 
fxs-loop-start |fxo-ground-start | fxo-loop-start}

Configures channel-associated signaling and the signaling protocol on a specified number of time slots.

Step 3 

Router(config-controller)# framing crc4

Defines the framing characteristics as cyclic redundancy check 4 (CRC4).

Step 4 

Router(config-controller)# linecode hdb3

Defines the line code as high-density bipolar 3 (HDB3).

Step 5 

Router(config-controller)# clock source line primary1 

Specifies one E1 line to serve as the primary or most stable clock source line.

1 Specify the other E1 line as the secondary clock source using the clock source line secondary command.

If you do not specify the time slots, channel-associated signaling is configured on all 30 B channels and one D channel on the specified controller.

CAS on T1 Voice Channels

Various types of CAS signaling are available in the T1 world. The most common forms of CAS signaling are loop-start, ground-start, and recEive and transMit (E&M). The biggest disadvantage of CAS signaling is its use of user bandwidth to perform signaling functions. CAS signaling is often referred to as robbed-bit-signaling because user bandwidth is being "robbed" by the network for other purposes. In addition to receiving and placing calls, CAS signaling also processes the receipt of DNIS and ANI information, which is used to support authentication and other functions.

This configuration allows the Cisco access servers to provide the automatic number identification/dialed number identification service (ANI/DNIS) delimiter on incoming T1/CAS trunk lines. The digit collection logic in the call switching module (CSM) for incoming T1 CAS calls in dual tone multifrequency (DTMF) is modified to process the delimiters, the ANI digits, and the DNIS digits.

As part of the configuration, a CAS signaling class with the template to process ANI/DNIS delimiters has to be defined. This creates a signaling class structure which can be referred to by its name.

This feature is only functional in a T1 CAS configured for E&M-feature group b (wink start). E&M signaling is typically used for trunks. It is normally the only way that a central office (CO) switch can provide two-way dialing with direct inward dialing. In all the E&M protocols, off-hook is indicated by A=B=1, and on-hook is indicated by A=B=0. If dial pulse dialing is used, the A and B bits are pulsed to indicate the addressing digits.

For this feature, here is an example of configuring for E&M-feature group b:

ds0-group 1 timeslots 1-24 type e&m-fgb dtmf dnis

In the original Wink Start protocol, the terminating side responds to an off-hook from the originating side with a short wink (transition from on-hook to off-hook and back again). This wink tells the originating side that the terminating side is ready to receive addressing digits. After receiving addressing digits, the terminating side then goes off-hook for the duration of the call. The originating endpoint maintains off-hook for the duration of the call.

Configuring ANI/DNIS Delimiters for CAS Calls on CT1

To configure the signaling class and ANI/DNIS delimiters, use the following commands beginning in global configuration mode:

 
Command
Purpose

Step 1 

Router(config)# signaling-class cas name

Names the signaling class and begins interface configuration mode.

Step 2 

Router(config-if)# profile incoming template

Defines the template to process the ANI/DNIS delimiter.

Step 3 

Router(config-if)# exit

Return to global configuration mode.

Step 4 

Router(config)# controller t1 slot/port/number

Enables this feature for a T1 controller and begins controller configuration mode.

Step 5 

Router(config-controller)# cas-custom channel

Specifies a single channel group number.

Step 6 

Router(config-ctrl-cas)# class name

Enables the ANI/DNIS delimiter feature by specifying the template.

To disable the delimiter, use the command no class under the cas-custom configuration.

To remove the signaling class, use the configuration command no signaling-class cas. When removing a signaling class, make sure the signaling class is no longer used by any controllers; otherwise, the following warning will be displayed:

% Can't delete, signaling class test is being used

How to Configure Switched 56K Digital Dial-In over Channelized T1 and Robbed-Bit Signaling

Internet service providers (ISPs) can provide switched 56-kbps access to their customers using a Cisco AS5000 series access server. Switched 56K digital dial-in enables many services for ISPs. When using traditional ISDN PRI, the access server uses the bearer capability to determine the type of service. However when providing switched 56K over a CT1 RBS connection, the digital signal level 0 (DS0s) in the access server can be configured to provide either modem or 56-kbps data service. The dial-in user can access a 56-kbps data connection using either an ISDN BRI connection or a 2- or 4-wire switched 56-kbps connection. The telco to which the access server connects must configure its switches to route 56-kbps data calls and voice (modem) calls to the appropriate DS0.

Likewise, an enterprise can provide switched 56-kbps digital dial-in services to its full time telecommuters or small remote offices using ISDN PRI or a CT1 RBS connection.

Switched 56K digital dial-in offers the following benefits:

Enables ISDN BRI clients to connect to a Cisco access server over switched 56K and T1 CAS.

Provides switched 56K dial-in services over T1 CAS to remote clients that do not have access to ISDN BRI, for example, a remote PC making digital calls over a 2- or 4-wire switched 56-kbps connection and a CSU.

The following prerequisites apply to the Switched 56K Digital Dial-In feature:

The remote device could be an ISDN BRI end point such as a terminal adapter or BRI router. In this scenario, the CSU/DSU is irrelevant. For 2- or 4-wire switched 56K remote clients, the remote endpoint must be compatible with the service of the carrier. Different carriers may implement different versions of switched 56K end points.

A CSU/DSU must be present at the remote client side of the connection. Otherwise, switched 56K connections are not possible. The Cisco access servers have built-in CSU/DSUs.

The telco must configure its side of the T1 connection to deliver 56-kbps data calls to the correct range of DS0s. If you do not want to dedicate all the DS0s or time slots on a single T1 to switched 56K services, be sure to negotiate with the telco about which DS0s will support switched 56K and which DS0s will not.

Cisco IOS Release 11.3(2)T or later must be running on the access server.

The following restrictions apply to Switched 56K digital dial-in:

A Cisco access server only supports incoming switched 56K calls. Dialing out with switched 56K is not supported at this time.

Switched 56K over E1 is not supported. Only switched 56K over T1 is supported.

Analog modem calls are not supported over DS0s that are provisioned for switched 56K. For a configuration example, see the section "Switched 56K and Analog Modem Calls over Separate T1 CAS Lines Example" later in this chapter.

Certain types of T1 lines, such as loop start and ground start, might not support this service. Contact your telco vendor to determine if this feature is available.

Switched 56K Scenarios

The following scenarios are provided to show multiple applications for supporting switched 56K over T1 CAS:

Switched 56K and Analog Modem Calls into T1 CAS

Basic Call Processing Components

ISDN BRI Calls into T1 CAS

Switched 56K and Analog Modem Calls into T1 CAS

Figure 2 shows a sample network scenario using switched 56K. Two remote PCs are dialing in to the same Cisco access server to get access to the Internet. The desktop PC is making switched 56K digital calls through an external CSU/DSU. The laptop PC is making analog modem calls through a 28.8-kbps modem. The Cisco access server dynamically assigns IP addresses to each node and forwards data packets off to the switched 56K channels and onboard modems respectively.

Figure 2 PCs Making Switched 56K and Analog Modem Calls into a Cisco AS5000 Series Access Server

For the startup running configuration on the Cisco access server shown in Figure 2, see the section "Comprehensive Switched 56K Startup Configuration Example" later in this chapter.

Basic Call Processing Components

Figure 3 shows the basic components that process switched 56K calls and analog modem calls on board a Cisco access server. Switched 56K and modem calls are signaling using robbed-bit signaling. Digital switched 56K calls utilize logical serial interfaces just like in ISDN PRI. Modem calls utilize asynchronous interfaces, lines, and modems.


Note The BRI terminal must originate its calls with a bearer capability of 56 kbps.


Figure 3 Processing Components for Switched 56K Calls Versus Analog Modem Calls


Note The Cisco IOS software does enable you to configure one T1 controller to support both switched 56K digital calls and analog modem calls. In this scenario, Figure 3 would show all calls coming into the access server through one T1 line and controller. However, you must negotiate with the telco which DS0s will support switched 56K services and which DS0s will not. On the access server, analog modem calls are not supported over DS0s that are provisioned for switched 56K. For an example software configuration, see the section "Mixture of Switched 56K and Modem Calls over CT1 CAS Example" at the end of this chapter.


ISDN BRI Calls into T1 CAS

Figure 4 shows how switched 56K functionality can be used to forward ISDN BRI network traffic to a Cisco access server that is configured for switched 56K robbed-bit signaling over CT1.


Note The BRI terminal must originate its calls with a bearer capability of 56 kbps.


Figure 4 Remote PC Making BRI Digital Calls via Switched 56K to a Cisco AS5000 Series Access Server

For a configuration example on the Cisco access server, see the section "Comprehensive Switched 56K Startup Configuration Example" at the end of this chapter.

How to Configure Switched 56K Services

This section describes how to configure switched 56K services on a Cisco access server. After the cas-group command is enabled for switched 56K services, a logical serial interface is automatically created for each 56K channel, which must also be configured.

To configure an access server to support switched 56K digital calls, use the following commands beginning in global configuration mode:

 
Command
Purpose

Step 1 

Router(config)# controllers t1 number

Specifies a T1 controller and begins controller configuration mode.

Step 2 

Router(config-controller)# framing {sf | esf}

Sets the framing.

Step 3 

Router(config-controller)# linecode {ami | b8zs}

Defines the line code.

Step 4 

Router(config-controller)# clock source {line {primary | secondary} | internal}

Specifies the clocking.

Step 5 

Router(config-controller)# cas-group channel timeslots range type signal

Configures robbed-bit signaling for a range of time slots. A logical serial interface is automatically created for each switched 56K channel.

Step 6 

Router(config-controller)# exit

Exits controller configuration mode.

Step 7 

Router(config)# interface serial number:number

Specifies logical serial interface, which was dynamically created when the cas-group command was issued, and configures the core protocol characteristics for the serial interface.

For configuration examples, see the section "Switched 56K Configuration Examples" later in this chapter.

How to Configure E1 R2 Signaling

R2 signaling is an international signaling standard that is common to channelized E1 networks. However, there is no single signaling standard for R2. The International Telecommunication Union Telecommunication Standardization Sector (ITU-T) Q.400-Q.490 recommendation defines R2, but a number of countries and geographic regions implement R2 in entirely different ways. Cisco addresses this challenge by supporting many localized implementations of R2 signaling in its Cisco IOS software.

The following sections offer pertinent information about the E1 R2 signaling feature:

E1 R2 Signaling Overview

Configuring E1 R2 Signaling

Configuring E1 R2 Signaling for Voice

Monitoring E1 R2 Signaling

Verifying E1 R2 Signaling

Troubleshooting E1 R2 Signaling

E1 R2 Signaling Overview

R2 signaling is channelized E1 signaling used in Europe, Asia, and South America. It is equivalent to channelized T1 signaling in North America. There are two types of R2 signaling: line signaling and interregister signaling. R2 line signaling includes R2 digital, R2 analog, and R2 pulse. R2 interregister signaling includes R2 compelled, R2 noncompelled, and R2 semicompelled. These signaling types are configured using the cas-group command for Cisco access servers, and the ds0-group command for Cisco routers.

Many countries and regions have their own E1 R2 variant specifications, which supplement the ITU-T Q.400-Q.490 recommendation for R2 signaling. Unique E1 R2 signaling parameters for specific countries and regions are set by entering the cas-custom channel command followed by the country name command.

The Cisco E1 R2 signaling default is ITU, which supports the following countries: Denmark, Finland, Germany, Russia (ITU variant), Hong Kong (ITU variant), and South Africa (ITU variant). The expression "ITU variant" means that there are multiple R2 signaling types in the specified country, but Cisco supports the ITU variant.

Cisco also supports specific local variants of E1 R2 signaling in the following regions, countries, and corporations:

Argentina

Laos1

Australia

Malaysia

Bolivia1

Malta1

Brazil

New Zealand

Bulgaria1

Paraguay

China

Peru

Colombia

Philippines

Costa Rica

Saudi Arabia

East Europe2

Singapore

Ecuador ITU

South Africa (Panaftel variant)

Ecuador LME

Telmex corporation (Mexico)

Greece

Telnor corporation (Mexico)

Guatemala

Thailand

Hong Kong (uses the China variant)

Uruguay

Indonesia

Venezuela

Israel

Vietnam

Korea

 

1 Cisco 3620 and 3640 series routers only.

2 Includes Croatia, Russia, and Slovak Republic.



Note Only MICA technologies modems support R2 functionality. Microcom modems do not support R2.


The following are benefits of E1 R2 signaling:

R2 custom localization—R2 signaling is supported for a wide range of countries and geographical regions. Cisco is continually supporting new countries.

Broader deployment of dial access services—The flexibility of a high-density access server can be deployed in E1 networks.

Cisco's implementation of R2 signaling has DNIS support turned on by default. If you enable the ani option, the collection of DNIS information is still performed. Specifying the ani option does not disable DNIS collection. DNIS is the number being called. ANI is the number of the caller. For example, if you are configuring router A to call router B, then the DNIS number is assigned to router B, the ANI number is assigned to router A. ANI is similar to Caller ID.

Figure 5 shows a sample network topology for using E1 R2 signaling with a Cisco AS5800. All four controllers on the access server are configured with R2 digital signaling. Additionally, localized R2 country settings are enabled on the access server.

Figure 5 Service Provider Using E1 R2 Signaling and a Cisco AS5800

Figure 6 shows a sample network topology for using E1 R2 signaling for voice transfers with a Cisco 2600, 3600, or 7200 series router. All the controllers on the router are configured with R2 digital signaling. Additionally, localized R2 country settings are enabled on the router.

Figure 6 E1 R2 Connections for the Cisco 2600/3600/7200 Series Routers

Configuration examples are supplied in the "Configuration Examples for Channelized E1 and Channelized T1" section at the end of this chapter.

Configuring E1 R2 Signaling

To configure support for E1 R2 signaling on the Cisco access servers, use the following commands beginning in global configuration mode:

 
Command
Purpose

Step 1 

Router(config)# controller e1 slot/port

Specifies the E1 controller that you want to configure with R2 signaling and begins controller configuration mode.

Step 2 

Router(config-controller)# cas-group channel timeslots range type signal

Replace the signal argument with any of the following choices under R2 analog, R2 digital, or R2 pulse:

r2-analog [dtmf | r2-compelled [ani] | r2-non-compelled [ani] | r2-semi-compelled [ani]]

or

r2-digital [dtmf | r2-compelled [ani] | r2-non-compelled [ani] | r2-semi-compelled [ani]]

or

r2-pulse [dtmf | r2-compelled [ani] | r2-non-compelled [ani] | r2-semi-compelled [ani]]

Configures R2 channel associated signaling on the E1 controller. For a complete description of the available R2 options, see the cas-group command.

The R2 part of this command is defined by the signal argument in the cas-group command.

For an E1 R2 configuration example, see the section "E1 R2 Signaling Procedure."

Configuring E1 R2 Signaling for Voice

To configure E1 R2 signaling on systems that will be configured for voice, use the following commands beginning in global configuration mode:

 
Command
Purpose

Step 1 

Router(config)# controller E1 slot/port

Specifies the E1 controller that you want to configure with R2 signaling and begins controller configuration mode.

Step 2 

Router(config-controller)# ds0-group channel 
timeslots range type signal

Replace the signal argument with any of the following choices under R2 analog, R2 digital, or R2 pulse:

r2-analog [dtmf | r2-compelled [ani] | 
r2-non-compelled [ani] | r2-semi-compelled [ani]] 

or

r2-digital [dtmf | r2-compelled [ani] | 
r2-non-compelled [ani] | r2-semi-compelled [ani]] 

or

r2-pulse [dtmf | r2-compelled [ani] | 
r2-non-compelled [ani] | r2-semi-compelled [ani]] 

Configures R2 channel-associated signaling on the E1 controller. For a complete description of the available R2 options, see the ds0-group (controller e1) command reference page.

Step 3 

Router(config-controller)# cas-custom channel

Enters cas-custom mode. In this mode, you can localize E1 R2 signaling parameters, such as specific R2 country settings for Hong Kong.

For the customization to take effect, the channel number used in the cas-custom command must match the channel number specified by the ds0-group command.

Step 4 

Router(config-ctrl-cas)# country name use-defaults

Specifies the local country, region, or corporation specification to use with R2 signaling. Replaces the name variable with one of the supported country names.

Cisco strongly recommends that you include the use-defaults option, which engages the default settings for a specific country. The default setting for all countries is ITU.

See the cas-custom command reference page for the list of supported countries, regions, and corporation specifications.

Step 5 

Router(config-ctrl-cas)# ani-digits

Router(config-ctrl-cas)# answer-signal

Router(config-ctrl-cas)# caller-digits

Router(config-ctrl-cas)# category

Router(config-ctrl-cas)# default

Router(config-ctrl-cas)# dnis-digits

Router(config-ctrl-cas)# invert-abcd

Router(config-ctrl-cas)# ka

Router(config-ctrl-cas)# kd

Router(config-ctrl-cas)# metering

Router(config-ctrl-cas)# nc-congestion

Router(config-ctrl-cas)# unused-abcd

Router(config-ctrl-cas)# request-category

(Optional) Further customizes the R2 signaling parameters. Some switch types require you to fine tune your R2 settings. Do not tamper with these commands unless you fully understand your switch's requirements.

For nearly all network scenarios, the country name use-defaults command fully configures your country's local settings. You should not need to perform Step 5.

See the cas-custom command reference page for more information about each signaling command.

Monitoring E1 R2 Signaling

To monitor E1 R2 signaling, use the following commands in EXEC mode as needed:

Command
Purpose
Router> show controllers e1

or

Router> show controllers e1 number

Displays the status for all controllers or a specific controller. Be sure the status indicates the controller is up and there are no alarms or errors (lines 2, 4, 9, and 10, as shown immediately below in the "Monitoring E1 R2 Using the show controllers e1 Command" section).

Router> show modem csm [slot/port| group number]

Displays status for a specific modem, as shown below in the "Monitoring E1 R2 Signaling Using the show modem csm Command" section.

Monitoring E1 R2 Using the show controllers e1 Command

Router# show controllers e1 0

E1 0 is up.
  Applique type is Channelized E1 - balanced
  No alarms detected.
  Version info of Slot 0:  HW: 2, Firmware: 4, PLD Rev: 2
 
Manufacture Cookie is not programmed.
 
  Framing is CRC4, Line Code is HDB3, Clock Source is Line Primary.
  Data in current interval (785 seconds elapsed):
     0 Line Code Violations, 0 Path Code Violations
     0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
  Total Data (last 13 15 minute intervals):
     0 Line Code Violations, 0 Path Code Violations,
     0 Slip Secs, 12 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 12 Unavail Secs

Monitoring E1 R2 Signaling Using the show modem csm Command

Router# show modem csm 1/0

MODEM_INFO: slot 1, port 0, unit 0, tone r2-compelled, modem_mask=0x0000, 
modem_port_offset=0
tty_hwidb=0x60E63E4C, modem_tty=0x60C16F04, oobp_info=0x00000000, modem_pool=0x60BC60CC
modem_status(0x0002): VDEV_STATUS_ACTIVE_CALL.
csm_state(0x0205)=CSM_IC5_CONNECTED, csm_event_proc=0x600CFF70, current call thru CAS line
invalid_event_count=0, wdt_timeout_count=0
wdt_timestamp_started is not activated
wait_for_dialing:False, wait_for_bchan:False
pri_chnl=TDM_PRI_STREAM(s0, u3, c7), modem_chnl=TDM_MODEM_STREAM(s1, c0)
dchan_idb_start_index=0, dchan_idb_index=0, call_id=0x0239, bchan_num=6
csm_event=CSM_EVENT_DSX0_CONNECTED, cause=0x0000
ring_no_answer=0, ic_failure=0, ic_complete=3
dial_failure=0, oc_failure=0, oc_complete=0
oc_busy=0, oc_no_dial_tone=0, oc_dial_timeout=0
remote_link_disc=2, stat_busyout=2, stat_modem_reset=0
oobp_failure=0
call_duration_started=00:04:56, call_duration_ended=00:00:00, total_call_duration=00:01:43
The calling party phone number = 
The called party phone number  = 9993003
total_free_rbs_timeslot = 0, total_busy_rbs_timeslot = 0, total_dynamic_busy_rbs_timeslot 
= 0, total_static_busy_rbs_timeslot = 0, min_free_modem_threshold = 0

Verifying E1 R2 Signaling

To verify the E1 R2 signaling configuration, enter the show controller e1 command to view the status for all controllers, or enter the show controller e1 slot/port command to view the status for a particular controller. Make sure that the status indicates that the controller is up (line 2 in the following example) and that no alarms (line 6 in the following example) or errors (lines 9, 10, and 11 in the following example) have been reported.

Router# show controller E1 1/0

E1 1/0 is up.
  Applique type is Channelized E1
  Cablelength is short 133
  Description: E1 WIC card Alpha
  No alarms detected.
  Framing is CRC4, Line Code is HDB3, Clock Source is Line Primary.
  Data in current interval (1 seconds elapsed):
     0 Line Code Violations, 0 Path Code Violations
     0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs  

Troubleshooting E1 R2 Signaling

If a connection does not come up, check for the following:

Loose wires, splices, connectors, shorts, bridge taps, and grounds

Backward send and receive

Mismatched framing types (for example, CRC-4 versus no CRC-4)

Send and receive pair separation (crosstalk)

Faulty line cards or repeaters

Noisy lines (for example, power and crosstalk)

If you see errors on the line or the line is going up and down, check the following:

Mismatched line codes (HDB3 versus AMI)

Receive level

Frame slips due to poor clocking plan

If problems persist, enable the modem management Call Switching Module (CSM) debug mode, using the debug modem csm command, as shown immediately below in the "Debug E1 R1 Signaling Using the debug modem Command" section.

Debug E1 R1 Signaling Using the debug modem Command

Router# debug modem csm 1/0

*May 15 04:05:46.675: VDEV_ALLOCATE: slot 2 and port 39 is allocated.
 
*May 15 04:05:46.675: CSM_RX_CAS_EVENT_FROM_NEAT:(04BF):  EVENT_CALL_DIAL_IN at slot 2 and 
port 39
 
*May 15 04:05:46.675: CSM_PROC_IDLE: CSM_EVENT_DSX0_CALL at slot 2, port 39
 
*May 15 04:05:46.675: Mica Modem(2/39): Configure(0x0) 
*May 15 04:05:46.675: Mica Modem(2/39): Configure(0x3) 
*May 15 04:05:46.675: Mica Modem(2/39): Configure(0x6) 
*May 15 04:05:46.675: Mica Modem(2/39): Call Setup
*May 15 04:05:46.891: Mica Modem(2/39): State Transition to Call Setup
*May 15 04:05:46.891: Mica Modem(2/39): Went offhook
*May 15 04:05:46.891: CSM_PROC_IC1_RING: CSM_EVENT_MODEM_OFFHOOK at slot 2, port 39

When the E1 controller comes up, you will see the following messages:

%CONTROLLER-3-UPDOWN: Controller E1 0, changed state to up
It also shows these messages for individual timeslots:
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 1 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 2 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 3 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 4 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 5 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 6 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 7 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 8 is up

Enabling R1 Modified Signaling in Taiwan

Enabling R1 modified signaling allows a Cisco universal access server to communicate with central office trunks that also use R1 modified signaling. R1 modified signaling is an international signaling standard that is common to channelized T1/E1 networks. Cisco IOS Release 12.1 supports R1 modified signaling customized for Taiwan only. You can configure a channelized T1/E1 interface to support different types of R1 modified signaling, which is used in older analog telephone networks.

This feature allows enterprises and service providers to fully interoperate with the installed Taiwanese telecommunications standards, providing interoperability in addition to the vast array of Cisco IOS troubleshooting and diagnostic capability. This feature will provide customers with a seamless, single-box solution for their Taiwan signaling requirements.


Note This type of signaling is not the same as ITU R1 signaling; it is R1 signaling modified for Taiwan specifically. In the future, R1 modified signaling will be supported by the Cisco AS5800 access server, and will also be available in Turkey.


The following restrictions are for the use of R1 modified signaling:

Because different line signaling uses different A/B/C/D bit definitions to represent the line state, you must understand the configuration of the T1/E1 trunk before configuring the CAS group. If the wrong type of provision is configured, the access server might interpret the wrong A/B/C/D bit definitions and behave erratically.

Cisco access servers (Cisco AS5300, and Cisco AS5800) with Microcom modems cannot support this feature.

You must know the configuration of the T1/E1 trunk before configuring the cas-group. If there is a trunk provisioning mismatch, performance problems may occur.

R1 Modified Signaling Topology

Figure 7 illustrates a service provider using R1 signaling with E1 and a Cisco AS5200 access server. The network topology would be the same for T1 or a Cisco AS5300 access server.

Figure 7 Service Provider Using E1 R1 Signaling with a Cisco AS5200 Access Server

Figure 8 illustrates a service provider using R1 modified signaling with E1 and a Cisco AS5800 access server.

Figure 8 Service Provider Using E1 R1 Modified Signaling with a Cisco AS5800 Access Server

R1 Modified Signaling Configuration Task List

This section describes how to enable R1 modified signaling on your Cisco access server on both a T1 and E1 interface.

Before beginning the tasks in this section, check for the following hardware and software in your system:

Cisco AS 5200, Cisco AS5300, or Cisco AS5800 access server (without a Microcom modem)

Cisco IOS Release 12.1 or later software

MICA feature module

Portware Version 2.3.1.0 or later

For information on upgrading your Cisco IOS images, modem portware, or modem code, go to the following locations and then select your access server type (Cisco AS5200, Cisco AS5300, or Cisco AS5800) and port information:

On Cisco.com:
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/

Or, follow this path:
Cisco Product Documentation/Access Servers and Access Routers/Access Servers

On the Documentation CD-ROM:
Cisco Product Documentation/Access Servers and Access Routers/Access Servers

To configure R1 modified signaling, perform the tasks in the following sections, as required:

Configuring R1 Modified Signaling on a T1 Interface

Configuring R1 Modified Signaling on an E1 Interface


Note The sample prompts and output are similar for the Cisco AS5200, Cisco AS5300 and Cisco AS5800 access servers.


Configuring R1 Modified Signaling on a T1 Interface

To configure R1 modified signaling on a T1 interface, use the following commands beginning global configuration mode:

 
Command
Purpose

Step 1 

Cisco AS5800 access server

Router(config)# vty-async(config)# controller t1 shelf/slot/port

Router(config)# vty-async(config-controller)#


or

Cisco AS5200 and AS5300 access servers

Router(config)# vty-async(config)# controller t1 [0 | 1 | 2 | 3]

Router(config)# vty-async(config-controller)#

Specifies the T1 controller that you want to configure and begins controller configuration mode. Refer to the Cisco AS5800 Universal Access Server Software Installation and Configuration Guide for port details.



The T1 controller ports are labeled 0 to 3 on the quad T1/PRI cards in the Cisco AS5200 and AS5300 access servers.

Step 2 

Router(config)# vty-async (config-controller)# framing {sf|esf}

Entering framing sf configures framing to T1 with sf.

Entering framing esf configures framing to T1 only.

Step 3 

Router(config)# vty-async (config-controller)# linecode {ami|b8zs}

Entering linecode ami configures line code to AMI1 encoding.

Entering linecode b8zs configures line code to b8zs encoding.

Step 4 

Router(config)# vty-async (config-controller)# clock source {internal | line [primary | secondary]}

Entering clock source internal configures the clock source to the internal clock.

Entering clock source line primary configures the clock source to the primary recovered clock.

Entering clock source secondary configures the clock source to the secondary recovered clock.

Step 5 

Router(config)# vty-async(config-controller)# cas-group 1 timeslots 1-24 type {r1-modified {ani-dnis | dnis} | r1-itu {dnis}}

Configures the time slots that belong to each E1 circuit for r1-modified or for r1-itu signaling.2

The cas-group # ranges from 0 to 23 for CT1.

The timeslot # ranges from 1 to 24 for CT1.

For the type, each CAS group can be configured as one of the Robbed Bit Signaling provisions.

ani-dnis indicates R1 will collect ani and dnis information; dnis indicates R1 will collect only dnis information.

Step 6 

Router(config)# vty-async(config-if)# ^Z

Router(config)# vty-async#

%SYS-5-CONFIG_I: Configured from console by console

Returns to enable mode by simultaneously pressing the Ctrl key and the z key. (This message returned is expected and does not indicate an error.)

1 AMI = alternate mark inversion.

2 For a more detailed description of the syntax and arguments of this command, refer to the Cisco IOS Dial Technologies Command Reference.

Configuring R1 Modified Signaling on an E1 Interface

To configure R1 modified signaling on an E1 interface, use the following commands beginning in global configuration mode:

 
Command
Purpose

Step 1 

Cisco AS5800 access server

Router(config)# controller e1 shelf/slot/port



or


Cisco AS5200 and AS5300 access servers

Router(config)# controller e1 [0 | 1 | 2 | 3]


Specifies the T1 controller that you want to configure and begins controller configuration mode.

Refer to the Cisco AS5800 Universal Access Server Software Installation and Configuration Guide for port details.

The T1 controller ports are labeled 0 to 3 on the quad T1/PRI cards in the Cisco AS5200 and AS5300 access servers.

Step 2 

Router (config-controller)# framing {crc4 | no-crc4}

Entering framing crc4 configures framing to E1 with CRC.1

Entering framing no-crc4 configures framing to E1 only.

Step 3 

Router (config-controller)# linecode {ami | hdb3}

Entering linecode ami configures line code to AMI2 encoding.

Entering linecode hdb3 configures line code to HDB3 encoding.

Step 4 

Router (config-controller)# clock source {internal | line [primary | secondary]}

Entering clock source internal configures the clock source to the internal clock.

Entering clock source line primary configures the clock source to the primary recovered clock.

Entering clock source secondary configures the clock source to the secondary recovered clock.

Step 5 

Router(config-controller)# cas-group 1 timeslots 1-15, 17-31 type r1-modified {ani-dnis | dnis}

Configures the time slots that belong to each E1 circuit for R1 modified signaling.4

The cas-group number ranges from 0 to 30 for CE1.

The timeslot number ranges from 1 to 31 for CE1.

For the type, each CAS group can be configured as one of the robbed bit signaling provisions.

ani-dnis indicates R1 will collect ANI and DNIS information; dnis indicates R1 will collect only DNIS information.

Step 6 

Router(config-controller-cas)# cas-custom 1

(Optional) Enters the channel number to customize.

Step 7 

Router(config-controller-cas)# ^Z

Router#

%SYS-5-CONFIG_I: Configured from console by console

Returns to enable mode by simultaneously pressing the Ctrl key and the Z key.

This message is normal and does not indicate an error.

1 CRC = cyclic redundancy check.

2 AMI = alternate mark inversion.

3 HDB = high-density bipolar 3.

4 For a more detailed description of the syntax and arguments of this command, refer to the Cisco IOS Dial Technologies Command Reference.

Troubleshooting Channelized E1 and T1 Channel Groups

Each channelized T1 or channelized E1 channel group is treated as a separate serial interface. To troubleshoot channel groups, first verify configurations and check everything that is normally checked for serial interfaces. You can verify that the time slots and speed are correct for the channel group by checking for CRC errors and aborts on the incoming line.


Note None of the Cisco channelized interfaces will react to any loop codes. To loop a channelized interface requires that the configuration command be entered manually.


Two loopbacks are available for channel groups and are described in the following sections:

Interface Local Loopback

Interface Remote Loopback

Interface Local Loopback

Interface local loopback is a bidirectional loopback, which will loopback toward the router and toward the line. The entire set of time slots for the channel group is looped back. The service provider can use a BERT test set to test the link from the central office to your local router, or the remote router can test using pings to its local interface (which will go from the remote site, looped back at your local site, and return to the interface on the remote site).

To place the serial interface (channel group) into local loopback, use the following command in interface configuration mode:

Command
Purpose

Router(config-if)# loopback local

Places the serial interface (channel group) in local loopback.


Interface Remote Loopback

Remote loopback is the ability to put the remote DDS CSU/DSU in loopback. It will work only with channel groups that have a single DS0 (1 time slot), and with equipment that works with a latched CSU loopback as specified in AT&T specification TR-TSY-000476, "OTGR Network Maintenance Access and Testing." To place the serial interface (channel group) in remote loopback, use the following command in interface configuration mode:

Command
Purpose

Router(config-if)# loopback remote interface

Places the serial interface (channel group) in remote loopback.


Using the loopback remote interface command sends a latched CSU loopback command to the remote CSU/DSU. The router must detect the response code, at which time the remote loopback is verified.

Configuration Examples for Channelized E1 and Channelized T1

ISDN PRI Examples

PRI Groups and Channel Groups on the Same Channelized T1 Controller Example

Robbed-Bit Signaling Examples

Switched 56K Configuration Examples

ISDN CAS Examples

E1 R2 Signaling Procedure

R1 Modified Signaling Using an E1 Interface Example

R1 Modified Signaling for Taiwan Configuration Example

ISDN PRI Examples

This section contains the following ISDN PRI examples:

Global ISDN, BRI, and PRI Switch Example

Global ISDN and Multiple BRI and PRI Switch Using TEI Negotiation Example

NSF Call-by-Call Support Example

PRI on a Cisco AS5000 Series Access Server Example

ISDN B-Channel Busyout Example

Multiple ISDN Switch Types Example

Outgoing B-Channel Ascending Call Order Example

Static TEI Configuration Example

Call Reject Configuration Examples

ISDN Cause Code Override and Guard Timer Example

Global ISDN, BRI, and PRI Switch Example

The following example shows BRI interface 0 configured for a NET3 ISDN switch type (basic-net3 keyword) that will override the National ISDN switch type configured globally. The PRI interface (channelized T1 controller) is configured for ISDN switch type Primary-Net5 and is applied only to the PRI.

isdn switch-type basic-ni
!
interface BRI0
 isdn switch-type basic-net3

interface serial0:23
! Apply the primary-net5 switch to this interface only.
 isdn switch-type primary-net5

Global ISDN and Multiple BRI and PRI Switch Using TEI Negotiation Example

In the following example, the global ISDN switch type setting is NET3 ISDN (basic-net3 keyword) and the PRI interface (channelized T1 controller) is configured to use isdn switch-type primary-net5. BRI interface 0 is configured for isdn switch-type basic-ni and isdn tei first-call. TEI first-call negotiation configured on BRI interface 0 overrides the default value (isdn tei powerup).

isdn switch-type basic-net 
! 
interface serial0:23 
 isdn switch-type primary-net5 
 ip address 172.21.24.85 255.255.255.0
! 
interface BRI0 
 isdn switch-type basic-ni 
 isdn tei first-call

NSF Call-by-Call Support Example

The following example configures NSF, which is needed for an AT&T 4ESS switch when it is configured for call-by-call support. In call-by-call support, the PRI 4ESS switch expects some AT&T-specific information when placing outgoing ISDN PRI voice calls. The options are accunet, sdn, and megacom.

This example shows both the controller and interface commands required to make the ISDN interface operational and the DDR commands, such as the dialer map, dialer-group, and map-class dialer commands, that are needed to configure the ISDN interface to make outgoing calls.

! The following lines configure the channelized T1 controller; all time slots are
! configured for ISDN PRI.
!
controller t1 1/1
 framing esf 
 linecode b8zs
 pri-group timeslots 1-23
 isdn switchtype primary-4ess 
!
! The following lines configure the D channel for DDR. This configuration applies
! to all B channels on the ISDN PRI interface.
interface serial 1/1:23
 description Will mark outgoing calls from AT&T type calls.
 ip address 10.1.1.1 255.255.255.0
 encapsulation ppp
 dialer map ip 10.1.1.2 name tommyjohn class sdnplan 14193460913
 dialer map ip 10.1.1.3 name angus class megaplan 14182616900
 dialer map ip 10.1.1.4 name angus class accuplan 14193453730

dialer-group 1
 ppp authentication chap

map-class dialer sdnplan
 dialer outgoing sdn

map-class dialer megaplan
 dialer voice-call
 dialer outgoing mega

map-class dialer accuplan
 dialer outgoing accu

PRI on a Cisco AS5000 Series Access Server Example

The following example configures ISDN PRI on the appropriate interfaces for IP dial-in on channelized T1:

! T1 PRI controller configuration

controller T1 0
 framing esf
 linecode b8zs
 clock source line primary
 pri-group timeslots 1-24
!
controller T1 1
 framing esf
 linecode b8zs
 clock source line secondary
 pri-group timeslots 1-24
!
interface Serial0:23
 isdn incoming-voice modem
 dialer rotary-group 1
!
interface Serial1:23 
 isdn incoming-voice modem
 dialer rotary-group 1
!
interface Loopback0
 ip address 172.16.254.254 255.255.255.0
!
interface Ethernet0
 ip address 172.16.1.1 255.255.255.0
!
interface Group-Async1
 ip unnumbered Loopback0
 ip tcp header-compression passive
 encapsulation ppp
 async mode interactive
 peer default ip address pool default
 dialer-group 1
 ppp authentication chap pap default 
 group-range 1 48
!
interface Dialer1
 ip unnumbered Loopback0
 encapsulation ppp
 peer default ip address pool default
 ip local pool default 172.16.254.1 172.16.254.48
 dialer in-band
 dialer-group 1
 dialer idle-timeout 3600
 ppp multilink
 ppp authentication chap pap default

The following example configures ISDN PRI on the appropriate interfaces for IP dial-in on channelized E1:

! E1 PRI controller configuration

controller E1 0
 framing crc4
 linecode hdb3
 clock source line primary
 pri-group timeslots 1-31
!
controller E1 1
 framing crc4
 linecode hdb3
 clock source line secondary
 pri-group timeslots 1-31

interface serial0:15
 isdn incoming-voice modem
 dialer rotary-group 1
!
interface serial1:15
 isdn incoming-voice modem
 dialer rotary-group 1
!
interface loopback0
 ip address 172.16.254.254 255.255.255.0
!
interface ethernet0
 ip address 172.16.1.1 255.255.255.0
!
! The following block of commands configures DDR for all the ISDN PRI interfaces 
! configured above. The dialer-group and dialer rotary-group commands tie the
! interface configuration blocks to the DDR configuration.
! 
interface dialer1
 ip unnumbered loopback0
 encapsulation ppp
 peer default ip address pool default
 ip local pool default 172.16.254.1 172.16.254.60 
 dialer in-band
 dialer-group 1
 dialer idle-timeout 3600
 ppp multilink
 ppp authentication chap pap default 

ISDN B-Channel Busyout Example

interface Serial0:23
   ip address 172.16.0.0 192.168.0.0
   no ip directed-broadcast
   encapsulation ppp
   no keepalive
   dialer idle-timeout 400
   dialer load-threshold 1 either
   dialer-group 1
   isdn switch-type primary-5ess
   isdn incoming-voice modem
   isdn snmp busyout b-channel
   no fair-queue
   no cdp enable

Multiple ISDN Switch Types Example

The following example configures ISDN switch type keyword primary-4ess on channelized T1 controller 0 and a switch type keyword primary-net5 for channelized T1 controller 1.

controller t1 0
 framing esf
 linecode b8zs
 isdn switchtype primary-4ess 
!
controller t1 1
 framing esf
 linecode b8zs
 isdn switchtype primary-net5

The following example shows BRI interface 0 configured for switch type keyword basic-net3 (NET3 ISDN) that will override the global switch type keyword basic-ni (National ISDN). The PRI interface (channelized T1 controller), is configured for ISDN switch type keyword primary-net5 and is applied only to the PRI interface.

isdn switch-type basic-ni
!
interface BRI0
 isdn switch-type basic-net3

interface serial0:23
! Apply the primary-net5 switch to this interface only.
 isdn switch-type primary-net5

Outgoing B-Channel Ascending Call Order Example

The following example configures the router to use global ISDN switch-type keyword primary-ni and configures the ISDN outgoing call channel selection to be made in ascending order:

isdn switch-type primary-ni 
! 
interface serial0:23 
 isdn bchan-number-order ascending

Static TEI Configuration Example

The following example shows a static TEI configuration:

interface bri 0
 isdn static-tei 1

Call Reject Configuration Examples

The following example configures the network to accept incoming ISDN voice calls and reject data calls:

interface Serial4:23
  description Connected to V-Sys R2D2
  no ip address
  isdn switch-type primary-5ess
  isdn incoming-voice modem
  isdn reject data
  no cdp enable
 end

The following example sets cause code 21 to reject all incoming data calls:

interface serial 2/0:23
 isdn reject data
 isdn reject cause 21

ISDN Cause Code Override and Guard Timer Example

The following example shows how to configure cause code override and the ISDN guard timer:

interface Serial0:23
 no ip address
 no ip directed-broadcast
 encapsulation ppp
 dialer rotary-group 0
 isdn switch-type primary-5ess
 isdn incoming-voice modem
 isdn disconnect-cause 17 
 isdn guard-timer 3000 on-expiry accept
 isdn calling-number 8005551234
 no fair-queue
 no cdp enable

PRI Groups and Channel Groups on the Same Channelized T1 Controller Example

The following example shows a channelized T1 controller configured for PRI groups and for channel groups. The pri-group command and the channel-group command cannot have overlapping time slots; note the correct time slot configuration in this example.

controller t1 0
channel-group 0 timeslot 1-6
channel-group 1 timeslot 7
channel-group 2 timeslot 8
channel-group 3 timeslot 9-11
pri-group timeslot 12-24

The same type of configuration also applies to channelized E1.

Robbed-Bit Signaling Examples

This section provides sample configurations for the T1 controllers on the Cisco access server. You can configure the 24 channels of a channelized T1 to support ISDN PRI, robbed-bit signaling, channel grouping, or a combination of all three. The following samples are provided:

Allocating All Channels for Robbed-Bit Signaling Example

Mixing and Matching Channels—Robbed-Bit Signaling and Channel Grouping

Allocating All Channels for Robbed-Bit Signaling Example

The following example configures all 24 channels to support robbed-bit signaling feature group B on a Cisco access server:

controller T1 0
 cas-group 1 timeslots 1-24 type e&m-fgb

Mixing and Matching Channels—Robbed-Bit Signaling and Channel Grouping

The following example shows you how to configure all 24 channels to support a combination of ISDN PRI, robbed-bit signaling, and channel grouping. The range of time slots that you allocate must match the time slot allocations that your central office chooses to use. This is a rare configuration due to the complexity of aligning the correct range of time slots on both ends of the connection.

The following configuration creates serial interfaces 0 to 9, which correspond to ISDN PRI time slots 1 to 10 (shown as serial 1:0 through serial 1:9). The serial line 1:23 is the D channel, which carries the analog signal bits that dial the phone number of the modem and determine if a modem is busy or available. The D channel is automatically created and assigned to time slot 24.

controller T1 0
! ISDN PRI is configured on time slots 1 through 10.
 pri-group timeslots 1-10
! Channelized T1 data is transmitted over time slots 11 through 16.
 channel-group 11 timeslots 11-16
! The channel-associated signal ear and mouth feature group B is configured on
! virtual signal group 17 for time slots 17 to 23, which are used for incoming 
! and outgoing analog calls. 
 cas-group 17 timeslots 17-23 type e&m-fgb

There is no specific interface, such as the serial interface shown in the earlier examples, that corresponds to the time-slot range.

Switched 56K Configuration Examples

The following switched 56K configuration examples are provided:

Switched 56K T1 Controller Procedure

Mixture of Switched 56K and Modem Calls over CT1 CAS Example

Switched 56K and Analog Modem Calls over Separate T1 CAS Lines Example

Comprehensive Switched 56K Startup Configuration Example

Switched 56K T1 Controller Procedure

The following procedure shows how to configure one T1 controller on a Cisco access server to support switched 56K digital calls. The Cisco access server has four controllers, which are numbered 0 to 3. If you want all four T1 controllers to support switched 56K calls, then repeat this procedure on each controller.


Step 1 Enter global configuration mode using the configure terminal command:

Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.

Step 2 Specify a T1 controller with the controller t1 number command. Replace the number variable with a controller number from 0 to 3.

Router(config)# controller t1 1

Step 3 Configure robbed-bit signaling on a range of time slots, then specify switched 56K digital services using the cas-group command. In this example, all calls coming into controller T1 1 are expected to be switched 56K data calls, not analog modem calls.

Router(config-controller)# cas-group 1 timeslots 1-24 type e&m-fgb service data

Note Be sure your signaling type matches the signaling type specified by the central office or telco on the other end. For a list of supported signaling types and how to collect DNIS, refer to the cas-group command description for the E1 controller card in the Cisco IOS Dial Technologies Command Reference.


Step 4 Set the framing for your network environment. You can choose ESF (enter framing esf) or SF (enter framing sf).

Router(config-controller)# framing esf

Step 5 Set the line-code type for your network environment. You can choose AMI encoding (enter linecode ami) or B8ZS encoding (enter linecode b8zs).

Router(config-controller)# linecode b8zs


Mixture of Switched 56K and Modem Calls over CT1 CAS Example

The following example configures one T1 controller to accept incoming switched 56K digital calls and analog modem calls over the same T1 CAS line. Time slots 1 through 10 are provisioned by the telco to support switched 56K digital calls. Time slots 11 through 24 are provisioned to support analog modem calls. Due to the DS0s provisioning, it is impossible for analog modems calls to be sent over the DS0s that map to time slots 1 through 10.

controller T1 0
 cas-group 1 timeslots 1-10 type e&m-fgb service data
 cas-group 1 timeslots 11-24 type e&m-fgb service voice
 framing esf
 clock source line primary
 linecode b8zs
 exit

Switched 56K and Analog Modem Calls over Separate T1 CAS Lines Example

The following example configures one Cisco access server to accept 50 percent switched 56K digital calls and 50 percent analog modem calls. The controllers T1 0 and T1 1 are configured to support the switched 56K digital calls using the cas-group 1 timeslots 1-24 type e&m-fgb service digital command. Controllers T1 2 and T1 3 are configured to support analog modem calls.

controller T1 0
 cas-group 1 timeslots 1-24 type e&m-fgb service data
 framing esf
 clock source line primary
 linecode b8zs
 exit
controller T1 1
 cas-group 1 timeslots 1-24 type e&m-fgb service data
 framing esf
 clock source line secondary
 linecode b8zs
 exit
controller T1 2
 cas-group 1 timeslots 1-24 type e&m-fgb service voice
 framing esf
 clock source internal
 linecode b8zs
 exit
controller T1 3
 cas-group 1 timeslots 1-24 type e&m-fgb service voice
 framing esf
 clock source internal
 linecode b8zs
 exit
copy running-config startup-config

Comprehensive Switched 56K Startup Configuration Example

The startup configuration in this section runs on the Cisco access server, as shown in Figure 2. This configuration is for an IP dial-in scenario with a mix of switched 56K calls and modem calls. Switched 56K digital calls come into controllers T1 0 and T1 1. Analog modem calls come into controllers T1 2 and T1 3.

In this example, the switched 56K clients are single endpoints in a remote node configuration. If each switched 56K client were instead a router with a LAN behind it without port address translation (PAT) turned on, then a static address, subnet mask, and route must be configured for each remote endpoint. This configuration would best done through RADIUS.

After a T1 time slot is configured with robbed-bit signaling using the cas-group command with the service data option, a logical serial interface is instantly created for each switched 56K channel. For example, signaling configured on all 24 time slots of controller T1 1 dynamically creates serial interfaces S0:0 through S0:23. You must then configure protocol support on each serial interface. No interface group command exists for serial interfaces, unlike asynchronous interfaces via the interface group-async command. Each serial interface must be individually configured. In most cases, the serial configurations will be identical. To streamline or shorten this configuration task, you might consider using a dialer interface, as shown in the following example.


Note In the following example, only analog modem calls encounter the group asynchronous and line interfaces. Switched 56K calls encounter the logical serial interfaces and dialer interface.


version xx.x
service timestamps debug datetime msec 
service timestamps log datetime msec
service password-encryption
no service udp-small-servers
no service tcp-small-servers
!
hostname 5300
!
aaa new-model
aaa authentication login default local
aaa authentication login console enable
aaa authentication login vty local
aaa authentication login dialin radius
aaa authentication ppp default local
aaa authentication ppp dialin if-needed radius
aaa authorization exec local radius
aaa authorization network radius
aaa accounting network start-stop radius
aaa accounting exec start-stop radius
!
enable secret cisco
!
username admin password cisco
async-bootp dns-server 10.1.3.1 10.1.3.2
!
!
! Switched 56K calls come into controllers T1 0 and T1 1. Take note of the keywords  
! "service data" in the cas-group command.
!
controller T1 0
 framing esf
 clock source line primary
 linecode b8zs
 cas-group 0 timeslots 1-24 type e&m-fgb service data
!
controller T1 1
 framing esf
 clock source line secondary
 linecode b8zs
 cas-group 1 timeslots 1-24 type e&m-fgb service data
!
! Analog modem calls come into controllers T1 2 and T1 3.
!
controller T1 2
 framing esf
 clock source line internal
 linecode b8zs
 cas-group 2 timeslots 1-24 type e&m-fgb 
!
controller T1 3
 framing esf
 clock source line internal
 linecode b8zs
 cas-group 3 timeslots 1-24 type e&m-fgb 
!
interface loopback0
 ip address 10.1.2.62 255.255.255.192
!
interface Ethernet0
 no ip address 
 shutdown
!
interface FastEthernet0
 ip address 10.1.1.11 255.255.255.0
 ip summary address eigrp 10.10.1.2.0 255.255.255.192
!
! Interface serial0:0 maps to the first switched 56K channel. The dialer pool-member 
! command connects this channel to dialer interface 1.
!
interface Serial0:0 
 dialer rotary-group 1
! 
interface Serial0:1 
 dialer rotary-group 1
!
interface Serial0:2
 dialer rotary-group 1
!
interface Serial0:3
 dialer rotary-group 1
!
interface Serial0:4
 dialer rotary-group 1
!
interface Serial0:5
 dialer rotary-group 1
!
interface Serial0:6
 dialer rotary-group 1
!
interface Serial0:7
 dialer rotary-group 1
!
interface Serial0:8
 dialer rotary-group 1
!
interface Serial0:9
 dialer rotary-group 1
!
interface Serial0:10
 dialer rotary-group 1
!
interface Serial0:11
 dialer rotary-group 1
!
interface Serial0:12
 dialer rotary-group 1
!
interface Serial0:13
 dialer rotary-group 1
!
interface Serial0:14
 dialer rotary-group 1
!
interface Serial0:15
 dialer rotary-group 1
!
interface Serial0:16
 dialer rotary-group 1
!
interface Serial0:17
 dialer rotary-group 1
!
interface Serial0:18
 dialer rotary-group 1
!
interface Serial0:19
 dialer rotary-group 1
!
interface Serial0:20
 dialer rotary-group 1
!
interface Serial0:21
 dialer rotary-group 1
!
interface Serial0:22
 dialer rotary-group 1
!
! Interface serial 0:23 is the last switched 56K channel for controller T1 0.
!
interface Serial0:23
 dialer rotary-group 1
!
! The switched 56K channels for controller T1 1 begin with interface serial 1:0 and end  
! with interface serial 1:23.
!
interface Serial1:0
 dialer rotary-group 1
!
interface Serial1:1
 dialer rotary-group 1
!
interface Serial1:2
 dialer rotary-group 1
!
interface Serial1:3
 dialer rotary-group 1
!
interface Serial1:4
 dialer rotary-group 1
!
interface Serial1:5
 dialer rotary-group 1
!
interface Serial1:6
 dialer rotary-group 1
!
interface Serial1:7
 dialer rotary-group 1
!
interface Serial1:8
 dialer rotary-group 1
!
interface Serial1:9
 dialer rotary-group 1
!
interface Serial1:10
 dialer rotary-group 1
!
interface Serial1:11
 dialer rotary-group 1
!
interface Serial1:12
 dialer rotary-group 1
!
interface Serial1:13
 dialer rotary-group 1
!
interface Serial1:14
 dialer rotary-group 1
!
interface Serial1:15
 dialer rotary-group 1
!
interface Serial1:16
 dialer rotary-group 1
!
interface Serial1:17
 dialer rotary-group 1
!
interface Serial1:18
 dialer rotary-group 1
!
interface Serial1:19
 dialer rotary-group 1
!
interface Serial1:20
 dialer rotary-group 1
!
interface Serial1:21
 dialer rotary-group 1
!
interface Serial1:22
 dialer rotary-group 1
!
interface Serial1:23
 dialer rotary-group 1
!
interface Group-Async1
 ip unnumbered Loopback0
 encapsulation ppp
 async mode interactive
 peer default ip address pool dialin_pool
 no cdp enable
 ppp authentication chap pap dialin
 group-range 1 96
!
interface Dialer1 
 ip unnumbered Loopback0
 no ip mroute-cache
 encapsulation ppp
 peer default ip address pool dialin_pool
 no fair-queue
 no cdp enable
 ppp authentication chap pap dialin
!
router eigrp 10
 network 10.0.0.0
 passive-interface Dialer0
 no auto-summary
!
ip local pool dialin_pool 10.1.2.1 10.1.2.96
ip default-gateway 10.1.1.1
ip classless
!
dialer-list 1 protocol ip permit
radius-server host 10.1.1.23 auth-port 1645 acct-port 1646
radius-server host 10.1.1.24 auth-port 1645 acct-port 1646
radius-server key cisco
!
line con 0
 login authentication console
line 1 96
 autoselect ppp
 autoselect during-login
 login authentication dialin
 modem DialIn
line aux 0
 login authentication console
line vty 0 4
 login authentication vty
 transport input telnet rlogin
!
end

ISDN CAS Examples

This section provides channelized E1 sample configurations for the Cisco access server. You can configure the 30 available channels with CAS, channel grouping, or a combination of the two. The following examples are provided:

Allocating All Channels for CAS Example

Mixing and Matching Channels—CAS and Channel Grouping Example

Allocating All Channels for CAS Example

The following interactive example configures channels (also known as time slots) 1 to 30 with ear and mouth channel signaling and feature group B support on a Cisco access server; it also shows that the router displays informative messages about each time slot. signaling messages are sent in the 16th time slot; therefore, that time slot is not brought up.

Router#
%SYS-5-CONFIG_I: Configured from console by console
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# controller e1 0
Router(config-controller)# cas-group 1 timeslots 1-31 type e&m-fgb
Router(config-controller)#
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 1 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 2 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 3 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 4 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 5 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 6 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 7 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 8 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 9 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 10 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 11 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 12 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 13 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 14 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 15 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 17 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 18 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 19 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 20 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 21 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 22 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 23 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 24 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 25 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 26 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 27 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 28 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 29 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 30 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 31 is up

Mixing and Matching Channels—CAS and Channel Grouping Example

The following interactive example shows you how to configure an E1 controller to support a combination of CAS and channel grouping. The range of time slots that you allocate must match the time slot allocations that your central office chooses to use. This configuration is rare because of the complexity of aligning the correct range of time slots on both ends of the connection.

Time slots 1 through 15 are assigned to channel group 1. In turn, these time slots are assigned to serial interface 0 and virtual channel group 1 (shown as serial 0:1).

Router(config)# controller e1 0
Router(config-controller)# channel-group 1 timeslots 1-15
Router(config-controller)#
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0:1, changed state to down
%LINK-3-UPDOWN: Interface Serial0:1, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0:1, changed state to up

Time slots 17 to 31 are configured with CAS:

Router(config-controller)# cas-group 2 timeslots 17-31 type e&m-fgb
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0:1, changed state to down
Router(config-controller)#
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 17 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 18 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 19 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 20 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 21 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 22 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 23 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 24 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 25 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 26 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 27 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 28 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 29 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 30 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 31 is up
Router(config-controller)#

E1 R2 Signaling Procedure

The following procedure configures R2 signaling and customizes R2 parameters on controller E1 2 of a Cisco AS5300 access server. In most cases, the same R2 signaling type is configured on each E1 controller.


Step 1 Enter global configuration mode using the configure terminal command:

Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.

Step 2 Specify the E1 controller that you want to configure with R2 signaling using the controller e1 number global configuration command. A controller informs the access server how to distribute or provision individual time slots for a connected channelized E1 line. You must configure one E1 controller for each E1 line.

Router(config)# controller e1 2

Step 3 Configure CAS with the cas-group channel timeslots range type signal command. The signaling type forwarded by the connecting telco switch must match the signaling configured on the Cisco AS5300 access server. The Cisco IOS configuration options are r2-analog, r2-digital, or r2-pulse.

Router(config-controller)# cas-group 1 timeslots 1-31 type ?
  e&m-fgb              E & M Type II FGB
  e&m-fgd              E & M Type II FGD
  e&m-immediate-start  E & M Immediate Start
  fxs-ground-start     FXS Ground Start
  fxs-loop-start       FXS Loop Start
  p7                   P7 Switch
  r2-analog            R2 ITU Q411
  r2-digital           R2 ITU Q421
  r2-pulse             R2 ITU Supplement 7
  sas-ground-start     SAS Ground Start
  sas-loop-start       SAS Loop Start

The following example specifies R2 ITU Q421 digital line signaling (r2-digital). This example also specifies R2 compelled register signaling and provisions the ANI ADDR option.

Router(config-controller)# cas-group 1 timeslots 1-31 type r2-digital r2-compelled ani
Router(config-controller)#
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 1 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 2 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 3 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 4 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 5 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 6 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 7 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 8 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 9 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 10 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 11 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 12 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 13 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 14 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 15 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 17 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 18 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 19 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 20 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 21 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 22 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 23 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 24 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 25 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 26 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 27 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 28 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 29 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 30 is up
%DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 31 is up


Note The actual R2 CAS is configured on the 16th time slot, which is why the time slot does not come up in the example output. For a description of the supported R2 signaling options, refer to the cas-group command for the E1 controller in the Cisco IOS Dial Technologies Command Reference.


Step 4 Customize some of the E1 R2 signaling parameters with the cas-custom channel controller configuration command. This example specifies the default R2 settings for Argentina. For custom options, refer to the cas-custom command in the Cisco IOS Dial Technologies Command Reference.

Router(config-controller)# cas-custom 1
Router(config-ctrl-cas)# ?
CAS custom commands:
  ani-digits        Expected number of ANI digits
  answer-signal     Answer signal to be used
  caller-digits     Digits to be collected before requesting CallerID
  category          Category signal
  country           Country Name
  default           Set a command to its defaults
  dnis-digits       Expected number of DNIS digits
  exit              Exit from cas custom mode
  invert-abcd       invert the ABCD bits before tx and after rx
  ka                KA Signal
  kd                KD Signal
  metering          R2 network is sending metering signal
  nc-congestion     Non Compelled Congestion signal
  no                Negate a command or set its defaults
  request-category  DNIS digits to be collected before requesting category
  unused-abcd       Unused ABCD bit values

Router(config-ctrl-cas)# country ?
  argentina             Argentina
  australia             Australia
  brazil                Brazil
  china                 China
  colombia              Colombia
  .
  .
  .
Router(config-ctrl-cas)# country argentina ?
  use-defaults   Use Country defaults
  <cr>

Router(config-ctrl-cas)# country argentina use-defaults

Note We highly recommend that you specify the default settings of your country. To display a list of supported countries, enter the country? command. The default setting for all countries is ITU.



R1 Modified Signaling Using an E1 Interface Example

The following example shows a configuration sample for R1 modified signaling on a Cisco access sever, using an E1 interface:

version xx.x
service timestamps debug datetime msec
no service password-encryption
!
hostname router
!
enable secret 5 $1$YAaG$L0jTcQ.nMH.gpFYXaOU5c.
!
no modem fast-answer
ip host dirt 10.255.254.254
ip multicast rpf-check-interval 0
isdn switch-type primary-dms100
!
!
controller E1 0
 clock source line primary
 cas-group 1 timeslots 1-15,17-31 type r1-modified  ani-dnis
!
controller E1 1
 clock source line secondary
 cas-group 1 timeslots 1-15,17-31 type r1-modified  ani-dnis
!
controller E1 2
 clock source internal
!
controller E1 3
 clock source internal
!
interface Ethernet0
 ip address 10.19.36.7 255.255.0.0
 no ip mroute-cache
!
interface FastEthernet0
 no ip address
 no ip route-cache
 no ip mroute-cache
 shutdown
!
interface Group-Async1
 ip unnumbered Ethernet0
 encapsulation ppp
 dialer in-band
 dialer idle-timeout 480
 dialer-group 1
 async dynamic address
 async mode interactive
 peer default ip address pool DYNAMIC
 no fair-queue
 no cdp enable
 group-range 1 108
!
router igrp 200
 network 10.0.0.0
 network 192.168.254.0
!
no ip classless
ip route 0.0.0.0 0.0.0.0 Ethernet0
logging source-interface Ethernet0
!
line con 0
 exec-timeout 0 0
line 1 108
 exec-timeout 0 0
 modem InOut
 transport input all
line aux 0
line vty 0 4
!
end

R1 Modified Signaling for Taiwan Configuration Example

The following example shows how to configure R1 modified signaling for Taiwan:

service timestamps debug datetime msec
no service password-encryption
!
hostname router
!
enable secret 5 $1$YAaG$L0jTcQ.nMH.gpFYXaOU5c.
!
no modem fast-answer
ip host dirt 192.168.254.254
ip multicast rpf-check-interval 0
isdn switch-type primary-dms100
!
!
controller T1 1/1/0
 framing esf
 linecode b8zs
 cablelength short 133
 pri-group timeslots 1-24
 fdl att
!
controller T1 1/1/1
 framing esf
 linecode b8zs
 cablelength short 133
 cas-group 1 timeslots 1-24 type r1-modified
 fdl att
!
controller T1 1/1/2
 framing esf
 linecode b8zs
 cablelength short 133
 pri-group timeslots 1-24
 fdl att
!
controller T1 1/1/3
 framing esf
 linecode b8zs
 cablelength short 133
 pri-group timeslots 1-24
 fdl att
!