|
|
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.
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. It provides three main configuration sections:
In addition, this chapter describes how to run interface loopback diagnostics on channelized E1 and channelized T1. For more information, see the "Troubleshoot Channelized E1 and Channelized T1" section.
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.
For a complete description of the channelized E1/T1 commands in this chapter, refer to the "Channelized E1 and Channelized T1 Setup Commands" chapter of the Dial Solutions Command Reference. To locate documentation of other commands that appear in this chapter, use the command reference master index or search online.
This section presents background information about signaling and about the use of channelized E1/T1 on the Cisco AS5200.
The terms in-band and out-of-band indicate whether various signals--used to set up, control, and terminate calls--travel in the same channel (or band) with users' voice calls or data, or whether those signals travel 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, which uses E1 timeslot 16 (the D channel) for signaling, fits into the out-of-band signaling category.
On a Cisco AS5200, you can allocate the available channels for channelized E1 or T1 in the following ways:
See the "PRI Groups and Channel Groups on the Same Channelized T1 Controller Example," "Robbed Bit Signaling Examples," and the "ISDN Channel-Associated Signaling Examples" sections at the end of this chapter.
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 "Dial-on-Demand Routing" part of this manual.
ISDN PRI is supported on the Cisco 7200 series and 7500 series routers using T1 or E1 versions of the Multichannel Interface Processor (MIP) card, on the Cisco 4000 series channelized E1/T1/PRI network processor module (NPM), and on the Cisco AS5200. 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.
For a complete description of the commands mentioned in this chapter, refer to the "Channelized E1 and Channelized T1 Setup Commands" chapter in the Dial Solutions Command Reference.
Perform the tasks in the following sections to configure ISDN PRI:
See the end of this chapter for the "ISDN PRI Examples" section.
For DDR configuration information, see the "Dial-on-Demand Routing" part of this manual. For command information, refer to the "Dial-on-Demand Routing" part of the Dial Solutions Command Reference.
This process varies dramatically from provider to provider on a national and international basis. However, some general guidelines follow:
When you order ISDN service, request the PRI switch configuration attributes displayed in Table 13.
| 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 | Descending from 23 to 1 |
| B + D glare | Yield |
| Directory numbers | Only 1 directory number assigned by service provider |
| ISDN call speed outside local exchange | Speed set to 56 kbps outside local exchange |
| SPIDs required? | None |
| Task | Command |
|---|---|
| Select a service provider switch type that accommodates PRI. (See Table 14 for a list of supported switch type keywords.) | isdn switch-type switch-type |
| Define the controller location in the Cisco7200 or Cisco 7500 series by slot and port number. or Define the controller location in the Cisco 4000 series or the Cisco AS5200 universal access server by unit number. 1 | controller e1 slot/port controller e1 number |
| Define the framing characteristics as cyclic redundancy check 4 (CRC4). | framing crc4 |
| Define the line code as high-density bipolar 3 (HDB3). | linecode hdb3 |
| Configure ISDN PRI. | pri-group [timeslots range] |
| Keywords by Area | Switch Type |
|---|---|
| none | No switch defined |
| Europe | |
| primary-net5 | European ISDN PRI switches; covers the Euro-ISDN E-DSS1 signaling system and is ETSI-compliant. |
| Japan | |
| primary-ntt | Japanese ISDN PRI switches |
| North America | |
| primary-4ess | AT&T 4ESS switch type for the U.S. |
| primary-5ess | AT&T 5ESS switch type for the U.S. |
| primary-dms100 | NT DMS-100 switch type for the U.S. |
| Task | Command |
|---|---|
| Select a service provider switch type that accommodates PRI. (See Table 14 for a list of supported PRI switch type keywords.) | isdn switch-type switch-type |
| Specify a T1 controller on a Cisco 7500 or Specify a T1 controller on a Cisco 4000.1 | controller t1 slot/port or controller t1 number |
| Define the framing characteristics as Extended Superframe Format (ESF). | framing esf |
| Define the line code as binary 8 zero substitution (B8ZS). | linecode b8zs |
| Configure ISDN PRI.
If you do not specify the time slots, this controller is configured for 23 B channels and 1 D channel. | pri-group [timeslots range]2 |
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 timeslots This interface is a logical entity is 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 (timeslots).
To configure the D channel serial interface, complete the tasks in the following sections:
To configure the D channel serial interface created for ISDN PRI, complete the following tasks beginning in global configuration mode:
| Task | Command |
|---|---|
| Step 1 Specify D channel on the serial interface for channelized T1. Specify D channel on the serial interface for channelized E1. | interface serial slot/port:23 interface serial number:23 interface serial slot/port:15 interface serial number:15 |
| Step 2 Specify an IP address for the interface. | ip address ip-address |
When you configure the D channel, its configuration is applied to all the individual B channels.
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:
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 following section:
| Task | Command |
|---|---|
| Configure PPP encapsulation. | encapsulation ppp |
See the "Configuring Frame Relay" chapter or "Configuring X.25 and LAPB" chapter for more information about addressing, encapsulation, and other tasks necessary to configure Frame Relay or X.25 networks.
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 a new CPP encapsulation type.
To enable routers to communicate over ISDN interfaces with Combinet bridges that support only CPP, perform the following tasks in interface configuration mode:
| Task | Command |
|---|---|
| Specify CPP encapsulation. | encapsulation cpp |
| Enable CPP callback acceptance. | cpp callback accept |
| Enable CPP authentication. | cpp authentication |
Now 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.
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 "Configure PPP Half-Bridging" section in the "Configuring Media-Independent PPP" chapter of 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.
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 five packets exchanged over the link, whichever is first.
To enable automatic detection of encapsulation type, perform the following task in interface configuration mode:
| Task | Command |
|---|---|
| Enable automatic detection of encapsulation type on the specified interface. | autodetect encapsulation encapsulation-type |
You can specify one or more encapsulations to detect. Cisco IOS software currently supports automatic detection of PPP and V.120 encapsulations.
When you configure networking, you specify how to reach the remote recipient. To configure network addressing, complete the following tasks beginning in interface configuration mode:
| Task | Command |
|---|---|
| Step 1 Define the remote recipient's protocol address, host name, and dialing string; optionally, provide the ISDN subaddress; set the dialer speed to 56 or 64 kbps, as needed. or (Australia) Use the spc keyword that enables ISDN semipermanent connections. | dialer map protocol next-hop-address name hostname speed 56|64 dial-string[:isdn-subaddress] dialer map protocol next-hop-address name hostname spc [speed 56 | 64] [broadcast] dial-string[:isdn-subaddress] |
| Step 2 Assign the interface to a dialer group to control access to the interface. | dialer-group group-number |
| Step 3 Associate the dialer group number with an access list number. | dialer-list dialer-group list access-list-number |
| Step 4 Define an access list permitting or denying access to specified protocols, sources, or destinations. | access-list access-list-number {deny | permit} protocol source address source-mask destination destination-mask |
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 in Step 4 are considered interesting and cause the router to place a call to the destination protocol address that is identified in both Step 1 and Step 4.
For more information about defining outgoing call numbers, see the "Configuring Legacy DDR" or "Configuring Dialer Profiles" chapter.
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, perform the following task in interface configuration mode:
| Task | Command |
|---|---|
| Specify the calling party number. | isdn calling-number calling-number |
This command can be used with all ISDN PRI switch types.
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 not required in other locations.
To configure the interface to include the Sending Complete information element in the outgoing call Setup message, complete the following task in interface configuration mode:
| Task | Command |
|---|---|
| Include the Sending Complete information element in the outgoing call Setup message. | isdn sending-complete |
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.
To enable the router to 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.
| Task | Command |
|---|---|
| Step 1 Specify the dialer map class, using the dialing-plan keyword as the classname. | map-class dialer classname |
| Step 2 (Optional) Enable voice calls. | dialer voice-call |
| Step 3 Configure the specific dialer map class to make outgoing calls. | dialer outgoing classname |
Table 15 lists the NSF dialing plans and supported services offered on AT&T Primary-4ESS switches.
| NSF Dialing Plan | Data | Voice | International |
|---|---|---|---|
| Software Defined Network (SDN)1 | Yes | Yes | GSDN (Global SDN) |
| MEGACOMM | No | Yes | Yes |
| ACCUNET | Yes | Yes | Yes |
To test the router's ISDN configuration, we suggest that you perform the following tasks:
| Task | Command |
|---|---|
| Check Layer 1 (physical layer) of the PRI over T1. | show controllers t1 slot/port |
| Check Layer 1 (physical layer) of the PRI over E1. | show controllers e1 slot/port |
| Check Layer 2 (data link layer). | debug q921 |
| Check Layer 3 (network layer). | debug isdn events |
See the Debug Command Reference for information about the debug commands.
Use the following commands to monitor and maintain ISDN interfaces:
| Task | Command |
|---|---|
| Display information about the physical attributes of the ISDN PRI over T1 B and D channels. | show interfaces serial slot/port bchannel channel-number (Cisco 7500 series ) show interfaces serial number bchannel channel-number (Cisco 4000 series) |
| Display information about the physical attributes of the ISDN PRI over E1 B and D channels. | show interfaces serial slot/port bchannel channel-number (Cisco 7500 series)
show interfaces serial number bchannel channel-number (Cisco 4000 series) |
| Display information about the T1 links supported on the ISDN PRI B and D channels. | show controllers t1 [slot/port] (Cisco 7500 series)
show controller t1 number (Cisco 4000 series) |
| Display information about the E1 links supported on the ISDN PRI B and D channels. | show controllers e1 [slot/port] (Cisco 7500 series)
show controllers e1 number (Cisco 4000 series) |
| Display 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.) | show isdn {active | history | memory | services | status [dsl | serial number] | timers} |
| Obtain general diagnostic information about the specified interface. | show dialer [interface type number] |
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 timeslot 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 is done to support channel banks in the network that convert various battery and ground operations on analog lines into signaling bits that are forwarded over digital lines.
Robbed bit signaling configured on the Cisco AS5200 enables the integrated modems in the access server to answer and transmit analog calls. To support analog signaling over T1 lines on the Cisco AS5200, robbed bit signaling must be enabled.
The Cisco AS5200 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, perform the following tasks beginning in global configuration mode:
| Task | Command |
|---|---|
| Step 1 Enable the T1 0 controller, and enter controller configuration mode. | controller t1 0 |
| Step 2 If the channelized T1 line connects to a smart jack instead of a CSU, set pulse equalization (use parameter values specified by your telco service provider). | cablelength long dbgain-value dbloss-value |
| Step 3 Set the framing to match your telco service provider's offering, which in most cases is esf. | framing esf |
| Step 4 Set the line code type to match your telco service provider's offering, which in most cases is b8zs. | linecode b8zs |
| Step 5 Configure one T1 line to serve as the primary or most stable clock source line. | clock source line primary |
| Step 6 Configure channels to accept voice calls.
This step creates interfaces that you can configure. | cas-group channel-number timeslots range type signal-type |
| Step 7 Set the facilities data link exchange standard for the CSU, as specified by your telco service provider. | fdl {att | ansi} |
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 1's line as the secondary clock source.
If you want to configure ISDN on the other controller, see the "Configure ISDN PRI" section of this chapter. If you want to configure channel groupings on the other controller, see the "Configuring Synchronous Serial Ports" chapter in this manual; specify the channel groupings when you specify the interface.
The Cisco AS5200 Universal Access Server now supports channel-associated signaling for channelized E1 lines, which are commonly deployed in networks in Latin America, Asia, and Europe. Channel-associated signaling 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.
Once channel-associated signaling is configured on a single E1 controller, up to 30 remote users can simultaneously dial in to the Cisco AS5200 through networks running the R2 protocol. The R2 protocol is an international signaling standard for analog connections. Because R2 signaling is not supported in the Cisco AS5200, an E1-to-E1 converter is required. See Figure 54.
Because the Cisco AS5200 has two physical E1 ports on its dual E1 PRI board, up to 60 simultaneous connections can be made through one dual E1 PRI board.
The dual E1 PRI card must be installed in the Cisco AS5200 before you attempt to configure channel-associated signaling.
To configure the Cisco AS5200's E1 controllers, perform the following tasks, beginning in global configuration mode:
| Task | Command |
|---|---|
| Step 1 Define the controller location in the Cisco AS5200 by unit number, ranging from 1 to 2. | controller e1 number |
| Step 2 Configure channel-associated signaling and the R2 signaling protocol on a specified number of timeslots. | cas-group channel-number timeslots range type signal-type |
| Step 3 Define the framing characteristics as cyclic redundancy check 4 (CRC4). | framing crc4 |
| Step 4 Define the line code as high-density bipolar 3 (HDB3). | linecode hdb3 |
| Step 5 Specify one E1 line to serve as the primary or most stable clock source line. | clock source line primary1 |
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.
If the problem is with a single channel group, you have a potential interface problem.
If the problem is with the T1 or E1 line, or with all channel groups, you have a potential controller problem.
The following sections describe how to determine whether the problem affects an interface or a controller.
When you troubleshoot E1 or T1 controllers, first check that the configuration is correct. The framing type and line code should match to what the service provider has specified. Then check channel group and PRI-group configurations, especially to verify that the timeslots and speeds are what the service provider has specified.
At this point, the show controller t1 or show controller e1 commands should be used to check for T1 or E1 errors. Use the command several times to determine if error counters are increasing, or if the line status is continually changing. If this is occurring, you need to work with the service provider.
Controller loopback tests are available for channelized T1 controllers and for channelized E1 controllers.
For the T1 controller, two loopbacks are available for testing:
All channel groups will be looped back; if the encapsulation on that channel group supports loopbacks (for example, HDLC and PPP), you can test that channel group by pinging the interface address. For example, if you have assigned an IP address to the serial interface defined for a channel group, you can ping that IP address.
To place the controller into local loopback, perform the following task in controller configuration mode.
| Task | Command |
|---|---|
| Loop the T1 controller toward the router and toward the line. | loopback local (controller) |
To test a channel group, perform the following task in EXEC mode:
| Ping the interface address. | ping protocol protocol-address |
Check errors by performing the following task in EXEC mode:
| Check errors. | show controller t1 |
If any errors occur, or the controller fails to change to the UP state, please contact the Cisco Technical Assistance Center (TAC).
Remote Loopback: The second T1 controller loopback is a remote loopback. This loopback can be used only if the entire T1 goes to a remote CSU. This is not the case with 99.9% of channelized T1. When the loopback remote controller command is executed, an inband CSU loop-up code will be sent over the entire T1, which will attempt to loop up the remote CSU. To place the controller in remote loopback, perform the following task in controller configuration mode:
| Task | Command |
|---|---|
| Place the T1 controller in remote loopback. | loopback remote (controller) |
For the E1 controller, only the local loopback is available. Local loopback operates the same as the local loopback on the T1 controller, forming a bidirectional loopback, both toward the router and toward the line. To place the E1 controller in local loopback, perform the following task in controller configuration mode:
| Task | Command |
|---|---|
| Place the E1 controller in local loopback toward the router and toward the line. | loopback (controller) |
All channel groups will be looped back; if the encapsulation on that channel group supports loopbacks (for example, HDLC and PPP), you can test that channel group by pinging the interface address. For example, if you have assigned an IP address to the serial interface defined for a channel group, you can ping that IP address.
To place the controller into local loopback, perform the following task in controller configuration mode.
| Task | Command |
|---|---|
| Loop the T1 controller toward the router and toward the line. | loopback local (controller) |
To test a channel group, perform the following task in EXEC mode:
| Ping the interface address. | ping protocol protocol-address |
Check errors if any. by performing the following task in EXEC mode:
| Check errors. | show controller t1 |
If any errors occur, it is most likely a hardware problem; please contact the Cisco TAC. In addition, you can ask the service provider to test the line by using a T1 BERT test set.
Two loopbacks are available for channel groups:
To place the serial interface (channel group) into local loopback, perform the following task in interface configuration mode:
| Task | Command |
|---|---|
| Place the serial interface (channel group) in local loopback. | loopback local |
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 timeslot), 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, perform the following task in interface configuration mode:
| Task | Command |
|---|---|
| Place the serial interface (channel group) in remote loopback. | loopback remote (interface) |
This section contains the following ISDN PRI examples:
The following example configures Network-Specific Facility (NSF), needed for an AT&T 4ESS switch when it is configured for Call-by-Call selection. 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 timeslots 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 7.1.1.1 255.255.255.0 encapsulation ppp dialer map ip 7.1.1.2 name tommyjohn class sdnplan 14193460913 dialer map ip 7.1.1.3 name angus class megaplan 14182616900 dialer map ip 7.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
! 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
! 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
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.
This section provides sample configurations for the Cisco AS5200's T1 controllers. 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. It provides the following sections:
The following example configures all 24 channels to support robbed bit signaling feature group B on a Cisco AS5200:
controller T1 0 cas-group 1 timeslots 1-24 type e&m-fgb
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 timeslots that you allocate must match the timeslot allocations that your central office chooses to use. This is a rare configuration due to the complexity of aligning the correct range of timeslots on both ends of the connection.
The following configuration creates serial interfaces 0 to 9, which correspond to ISDN PRI timeslots 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 a modem's phone number and determine if a modem is busy or available. The D channel is automatically created and assigned to timeslot 24.
controller T1 0 ! ISDN PRI is configured on timeslots 1 through 10. pri-group timeslots 1-10 ! Channelized T1 data is transmitted over timeslots 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 timeslots 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 timeslot range.
This section provides channelized E1 sample configurations for the Cisco AS5200. You can configure the 30 available channels with channel-associated signaling, channel grouping, or a combination of the two.
The following interactive example configures channels (also known as timeslots) 1-30 with ear and mouth channel signaling and feature group B support on a Cisco AS5200; it also shows that the router displays informative messages about each timeslot. Signaling messages are transmitted in the 16th timeslot; therefore, that timeslot is not brought up.
Router# %SYS-5-CONFIG_I: Configured from console by console Router#configure terminalEnter configuration commands, one per line. End with CNTL/Z. Router(config)#controller e1 0Router(config-controller)#cas-group 1 timeslots 1-31 type e&m-fgbRouter(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
The following interactive example shows you how to configure an E1 controller to support a combination of channel-associated signaling and channel grouping. The range of timeslots that you allocate must match the timeslot allocations that your central office chooses to use. This is a rare configuration because of the complexity of aligning the correct range of timeslots on both ends of the connection.
Timeslots 1 through 15 are assigned to channel group 1. In turn, these timeslots are assigned to serial interface 0 and virtual channel group 1 (shown as serial 0:1).
AS5200(config)#controller e1 0Router(config-controller)#channel-group 1 timeslots 1-15Router(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
Timeslots 17 to 31 are configured with channel associated signaling.
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)#
|
|