-
Cisco IOS Release 12.0 Dial Solutions Command Reference
-
About This Manual
-
Using Cisco IOS Software
- Part 1: Dial-In Port Setup
- Part 2: Dial-In Terminal Service & Remote Node Config
- Part 3: Dial-on-Demand Routing
- Part 4: Dial Backup
- Part 5: NASI Client Commands
- Part 6: Large-Scale Dial Solutions
- Part 7: Cost-Control Solutions
- Part 8: Virtual Private Dialup Networks
- Part 9: Other Network Traffic on ISDN Channels
- Part 10: Dial-Related Addressing Services
- Part 11: Appendixes
-
Index
-
Table Of Contents
Channelized E1 and Channelized T1 Setup Commands
show controllers e1 call-counters
show controllers t1 call-counters
show interfaces serial bchannel
Channelized E1 and Channelized T1 Setup Commands
This chapter describes commands needed to configure channelized E1 and channelized T1 for the following:
•
ISDN PRI on any platform that supports Primary Rate Interface
•
•
In Cisco IOS Release 11.3, all commands supported on the Cisco 7500 series are also supported on the Cisco 7000 series.
autodetect encapsulation
To enable automatic detection of the encapsulation types in operation over a point-to-point link to a specified serial or ISDN interface, use the autodetect encapsulation interface configuration command. To disable automatic, dynamic detection of the encapsulation types in operation on a link, use the no form of this command.
autodetect encapsulation encapsulation-type
no autodetect encapsulationSyntax Description
Default
Disabled
Command Mode
Interface configuration
Usage Guidelines
This command first appeared in Release 11.2.
At least one encapsulation type is required in the command, but you can specify additional encapsulation types.
Use this command to enable the specified 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 dynamically.
This command 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.
Related Commands
You can use the master indexes or search online to find documentation of related commands.
encapsulation
cas-custom
To customize E1 R2 signaling parameters for a particular E1 channel group on a channelized E1 line, use the cas-custom controller configuration command. Use the no form of this command to disable the signaling customization.
cas-custom channel
no cas-custom channelSyntax Description
channel
Specifies a single channel group number, which can be between 0 and 30. This channel group number must match the channel number specified in the cas-group command.
Default
No customized signaling parameters are set. If you do not specify a country name using the country name command, which is described in , ITU is the selected default signal.
Command Mode
Controller configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.2 P.
The customization parameters set by the cas-custom channel command are applied to the same channel group number used in the cas-group channel timeslots range type signal command. These channel group numbers must match. Otherwise, the customized features specified by the cas-custom command will not be applied to the cas-group command's configuration. The signaling customization will not take effect. See Example 1.
However, you will not need to configure or set more than one channel group number per E1 line in most cases. Though rarely used, it is possible to split a single E1 (timeslots 1 to 31) into two groups (for example, 1 to 15 on group 1 and timeslots 17 to 31 in group 2).
Cisco strongly recommends that you use the use-defaults option when specifying a particular country type. See the country name command in . This additional keyword ensures that all the local country settings are correctly enabled. For example, issue the country greece use-defaults command. If the use-defaults option is not specified, generic ITU will be the default setting for all countries. See Example 2.
You can configure the system to deviate from a country's default settings as defined by Cisco. To do this, choose from the following list of commands described in : ani-digits min number max number, answer-signal {group-a | group-b} number, caller-digits number, category number, dnis-digits min number max number, invert-abcd, ka number, kd number, metering, nc-congestion, and unused-abcd value. To return a country back to its country specific default settings, issue the country name use-defaults command. To return a country back to the ITU standard, issue the default country name use-defaults command. See Example 3 and Example 4.
Note
shows a list of command options in cas-custom mode, which is used to customize R2 signaling settings. Some switches require you to fine tune your R2 settings. Do not tamper with these commands unless you understand exactly how your switch will be affected.
Example 1
The following example displays the available signaling parameters after you enter cas-custom mode. Notice that the same channel group 1 is specified in the cas-group command and the cas-custom command.
router# configure terminalEnter configuration commands, one per line. End with CNTL/Zrouter(config)# controller e1 1router(config-controller) cas-group 1 timeslots 1-31 type r2-digital r2-compelledrouter(config-controller) cas-custom 1router(config-ctrl-cas)# ?CAS custom commands:ani-digits Expected number of ANI digitsanswer-signal Answer signal to be usedcaller-digits Digits to be collected before requesting CallerIDcategory Category signalcountry Country Namedefault Set a command to its defaultsdnis-digits Expected number of DNIS digitsexit Exit from cas custom modeinvert-abcd invert the ABCD bits before tx and after rxka KA Signalkd KD Signalmetering R2 network is sending metering signalnc-congestion Non Compelled Congestion signalno Negate a command or set its defaultsrequest-category DNIS digits to be collected before requesting categoryunused-abcd Unused ABCD bit valuesExample 2
You can localize your R2 configuration for a specific country. Don't forget to include the use-defaults option as described in . For example, use the country argentina use-defaults command for a R2 scenario in Argentina.
router(config-ctrl-cas)# country ?argentina Argentinaaustralia Australiabrazil Brazilchina Chinacolumbia Columbiacostarica Costa Ricaeasteurope East Europeecuador-itu Ecuador ITUecuador-lme Ecuador LMEgreece Greeceguatemala Guatemalahongkong-china Hong Kong (China variant)indonesia Indonesiaisrael Israelitu ITUkorea Koreamalaysia Malaysianewzealand New Zealandparaguay Paraguayperu Peruphilippines Philippinessaudiarabia Saudi Arabiasingapore Singaporesouthafrica-panaftel South Africa Panafteltelmex Telmextelnor Telnorthailand Thailanduruguay Uruguayvenezuela Venezuelavietnam Vietnamrouter(config-ctrl-cas)# country argentina ?use-defaults Use Country defaults<cr>router(config-ctrl-cas)# country argentina use-defaultsExample 3
The following example customizes the signaling for channel group 1. The configuration collects 3 digits before it requests ANI information for analog calls received on a Cisco AS5300 in Argentina.
router(config-controller)# cas-custom 1router(config-ctrl-cas)# country argentina use-defaultsrouter(config-ctrl-cas)# caller-digits 3router(config-controller)# ^zrouter(config)#Example 4
Because cas-custom mode gives you the flexibility to customize R2 parameters, the margin for user error increases. Therefore, the Cisco IOS software enables you to return a country back to its default R2 settings using the use-defaults option. The following example begins by bringing up Argentina's default settings, changing a few customization parameters, then returning the Argentina R2 setting back to its original state.
router(config-ctrl-cas)# country argentina use-defaultsrouter(config-ctrl-cas)# caller-digits 3router(config-ctrl-cas)# unused-abcd 1router(config-ctrl-cas)# meteringrouter(config-ctrl-cas)# country argentina use-defaultsRelated Command
You can use the master indexes or search online to find documentation of related commands.
cas-group (controller E1)
cas-group (controller e1)
To configure channel associated signaling on an E1 controller, use the cas-group controller configuration command. Use the no form of this command to disable channel associated signaling for one or more timeslots.
cas-group channel timeslots range type signal
no cas-group channel timeslots range type signalSyntax Description
Default
For ISDN PRI, the cas-group command is disabled.
If the channelized E1 is not configured as a PRI, the default value for line signaling is e&m-fgb and the default value for tone signaling is DTMF.
The R1 signaling default is ani-dnis.
R2 signaling types have DNIS turned on by default.
Command Mode
Controller configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.2 P.
The R1 options first appeared in Cisco IOS Release 11.3 P.
The R2 options first appeared in Cisco IOS Release 11.3 T.Use this command to configure support for incoming and outgoing call signals (such as on-hook and off-hook) on each E1 controller.
If you specify the timeslot range 1-31, the system software automatically uses the 16th timeslot to transmit the channel associated signaling.
The signaling you configure on the access server must match the signaling used by the central office. For example if the central office switch is forwarding R2 analog signaling to a Cisco AS5300, then the access server's E1 controller must also be configured for R2 analog signaling (r2-analog).
All R2 signaling options have 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. DNIS is the number being called. ANI is the caller's number. For example, if you are configuring router A to call router B, then the DNIS number is router B, the ANI number is router A. ANI is very similar to Caller ID.
To customize the R2 signaling parameters, refer to the cas-custom controller configuration command. When you enable the cas-group command, the cas-custom command is automatically setup to be polled for configuration information. However, unless you enable or turn on specific features with the cas-custom command, the cas-custom feature has an empty set of signaling parameters.
Note
DNIS is automatically collected for modem pools and R2 tone signaling. You do not need to specify the collection of DNIS information with the cas-group command. However, if you are using non-R2 tone signaling, the system must be manually configured to collect DNIS information. For non-R2 cas signaling, DNIS collection is done only for E&M-fgb.
Examples
In most cases, you will configure the same channel associated signaling on each E1 controller. The following examples configure signaling and customized parameters on controller E1 2 using the cas-group and cas-custom controller configuration commands. The actual channel associated signaling is configured on the 16th timeslot, which is the reason why this timeslot does not come up in the following output.
router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.router(config)# controller e1 2router(config-controller)# cas-group 1 timeslots 1-31 type r2-digital r2-compelled anirouter(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 upThe following example shows all the supported E1 signaling types on a Cisco AS5300.
router(config-controller)# cas-group 1 timeslots 1-31 type ?e&m-fgb E & M Type II FGBe&m-fgd E & M Type II FGDe&m-immediate-start E & M Immediate Startfxs-ground-start FXS Ground Startfxs-loop-start FXS Loop Startp7 P7 Switchr2-analog R2 ITU Q411r2-digital R2 ITU Q421r2-pulse R2 ITU Supplement 7sas-ground-start SAS Ground Startsas-loop-start SAS Loop Startrouter(config-controller)# cas-group 1 timeslots 1-31 type r2-analog ?dtmf DTMF tone signallingr2-compelled R2 Compelled Register Signallingr2-non-compelled R2 Non Compelled Register Signallingr2-semi-compelled R2 Semi Compelled Register Signalling<cr>R2 signaling parameters can be customized with the cas-custom controller configuration command:
router(config-controller)# cas-custom 1router(config-ctrl-cas)# ?CAS custom commands:caller-digits Digits to be collected before requesting CallerIDcategory Category signalcountry Country Namedefault Set a command to its defaultsexit Exit from cas custom modeinvert-abcd invert the ABCD bits before tx and after rxmetering R2 network is sending metering signalnc-congestion Non Compelled Congestion signalno Negate a command or set its defaultsThe following example would configure R1 Signaling on a Cisco AS5200 (T1 interface) and specify the collection of both ani and dnis information:
5200(config-controller)# cas-group 1 timeslots 1-24 type r1-modified ani-dniscas-group (controller t1)
To configure channelized T1 timeslots with robbed bit signaling, use the cas-group controller configuration command. Use the no form of this command to disable robbed bit signaling for one or more timeslots.
cas-group channel timeslots range type signal
no cas-group channel timeslots range type signalSyntax Description
Default
For ISDN PRI, the cas-group command is disabled.
If the channelized T1 is not configured as a PRI, the default value for line signaling is e&m-fgb and the default value for tone signaling is DTMF.
The R1 signalling default value is ani-dnis.
Command Mode
Controller configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.2.
The service, data, and voice signaling options first appeared in Cisco IOS Release 11.3 T.
The R1 options first appeared in Cisco IOS Release 11.3 P.Use the cas-group command to configure T1 controllers with different types of robbed bit signaling, such as on-hook and off-hook for E&M feature group B (e&m-fgb).
If you want to collect DNIS information on a T1 controller, you must manually configure it on the access server. DNIS collection is performed only for E&M-fgb. To collect DTMF DNIS for E&M-fgb under a controller T1 configuration, issue the cas-group 0 timeslots 1-24 type e&m-fgb dtmf dnis command. To collect MF DNIS for E&M-fgb, issue the cas-group 0 timeslots 1-24 type e&m-fgb mf dnis command.
Examples
The following example configures all 24 channels with ear and mouth robbed bit signaling with feature group B support:
router(config)# controller T1 0router(config-controller)# cas-group 1 timeslots 1-24 type e&m-fgbrouter(config-controller)#%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%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 9 is up%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 10 is up%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 11 is up%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 12 is up%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 13 is up%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 14 is up%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 15 is up%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 16 is up%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 17 is up%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 18 is up%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 19 is up%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 20 is up%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 21 is up%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 22 is up%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 23 is up%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 24 is upThe following example configures the required signaling to support modem pooling and the digital number identification service (DNIS) over channelized T1 lines on a Cisco AS5300. The only supported signaling and tone types for modem pooling over CT1 RBS are E&M feature group B, DTMF tones, and MF tones. By configuring DNIS as part of the cas-group command, the system can collect DNIS digits for incoming calls, which can be redirected to specific modem pools setup for different customers or services. Additionally, you must be running MICA modems in the system and have at least 10% of your total modems in the default modem pool. Free modems are needed in the default pool to detect the incoming called number or DNIS before handing the call off to the appropriate modem pool. Therefore, two modems are actually needed to handle each incoming call.
Note
router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.router(config)# controller t1 0router(config-controller)# cas-group 0 timeslots 1-24 type e&m-fgb dtmf dnisrouter(config-controller)# exitrouter(config)#router(config)# modem-pool accounts1router(config-modem-pool)# pool-range 30-50router(config-modem-pool)# called-number 2000 max-conn 21router(config-modem-pool)# exitrouter(config)#The next example configures a Cisco AS5200 to accept switched 56K digital calls on both of its T1 controllers:
router(config)# controller T1 0router(config-controller)# cas-group 1 timeslots 1-24 type e&m-fgb service datarouter(config-controller)# framing esfrouter(config-controller)# clock source line secondaryrouter(config-controller)# linecode b8zsrouter(config-controller)# exitrouter(config)# controller T1 1router(config-controller)# cas-group 1 timeslots 1-24 type e&m-fgb service datarouter(config-controller)# framing esfrouter(config-controller)# clock source line primaryrouter(config-controller)# linecode b8zsrouter(config-controller)# exitrouter(config)# copy running-config startup-configThe next example configures switched 56K digital services and analog modem services on one controller. Each service is assigned its own range of timeslots. Switched 56K calls are assigned to timeslots 1 through 15. Analog modem calls are assigned to timeslots 16 through 24. However, you must use different channel group numbers in each cas-group command entry.
router(config)# controller T1 0router(config-controller)# cas-group 0 timeslots 1-15 type e&m-fgb service datarouter(config-controller)# cas-group 1 timeslots 16-24 type e&m-fgb service voicerouter(config-controller)# framing esfrouter(config-controller)# clock source line secondaryrouter(config-controller)# linecode b8zsrouter(config-controller)# exitThe following example would configure R1 Signaling on a Cisco AS5200 (T1 interface) and specify the collection of both ani and dnis information:5200(config-controller)# cas-group 1 timeslots 1-24 type r1-modified ani-dnis
channel-group
Use the channel-group controller configuration command to define the timeslots that belong to each T1 or E1 circuit. Use the no form of this command to clear the timeslots for the T1 or E1 circuit.
channel-group number timeslots range [speed {48 | 56 | 64}]
no channel-group [number timeslots range]Syntax Description
Default
The default line speed when configuring a T1 controller is 56 kbps.
The default line speed when configuring an E1 controller is 64 kbps.
Command Mode
Controller configuration
Usage Guidelines
This command first appeared in Release 11.3MA.
Use this command in configurations where the router or access server must communicate with a T1 or E1 fractional data line. The channel-group number may be arbitrarily assigned and must be unique for the controller. The timeslot range must match the timeslots assigned to the channel group. The service provider defines the timeslots that comprise a channel group.
On the Cisco MC3810 access concentrator, only one channel group can be configured on a controller.
Example
The following example defines three channel groups. Channel-group 0 consists of a single timeslot, channel-group 8 consists of 7 timeslots and runs at a speed of 64 kbps per timeslot, and channel-group 12 consists of a single timeslot.
channel-group 0 timeslots 1channel-group 8 timeslots 5,7,12-15,20 speed 64channel-group 12 timeslots 2Related Commands
You can use the master indexes or search online to find documentation of related commands.
framing
linecodeclear controller
Use the clear controller EXEC command to reset the T1 or E1 controller.
clear controller {t1 | e1} slot/port (Cisco 7200 series and Cisco 7500 series)
clear controller {t1 | e1} number (on the Cisco AS5200 and Cisco AS5300 series)Syntax Description
Command Mode
EXEC
Examples
The following example resets the T1 controller at slot 4, port 0 on a Cisco 7500 series router:
clear controller t1 4/0The following example resets the E1 controller at NIM 0:
clear controller e1 0Related Commands
You can use the master indexes or search online to find documentation of related commands.
controller e1
controller t1clock source (controller)
Use the clock source controller configuration command to set the E1 line clock source for the Cisco AS5200.
clock source line {primary | secondary}
no clock source line {primary | secondary}Syntax Description
line
E1 line from which the clocking is taken.
primary
Primary TDM clock source.
secondary
Secondary TDM clock source.
Default
Primary TDM clock source is taken from the E1 controller 0 on the Cisco AS5200.
Secondary TDM clock source is taken from the E1 controller 1 on the Cisco AS5200.
Command Mode
Controller configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.1.
Configure the clock source line primary command on the controller that takes the most reliable clocking from an E1 line. Configure the clock source line secondary command on the controller that has the next best known clocking. With this configuration, the primary line clocking is backed up to the secondary line if the primary clocking shuts down.
Examples
The following example configures the Cisco AS5200 to use the E1 controller 0 as the primary clocking source and the E1 controller 1 as the secondary clocking source:
controller e1 0framing esflinecode hdb3pri-group timeslots 1-23clock source line primary!controller e1 1framing esflinecode hdb3pri-group timeslots 1-23clock source line secondaryRelated Commands
You can use the master indexes or search online to find documentation of related commands.
framing
linecodeclock source (Cisco AS5200)
To select the clock source for the time-division multiplexing (TDM) bus in a Cisco AS5200/AS5300 access server, use the clock source interface configuration command. The no form of this command configures the clock source to its default setting.
clock source {line {primary | secondary} | internal}
no clock source line {primary | secondary}Syntax Description
line
Clock source on the active line.
primary
Primary TDM clock source.
secondary
Secondary TDM clock source.
internal
Free-running clock (also known as internal clock) as the clock source.
Defaults
Primary TDM clock source from the T1 0 controller
Secondary TDM clock source from the T1 1 controller
Command Mode
Interface configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.1.
To use the clocking coming in from a T1 line, configure the clock source line primary command on the T1 interface that has the most reliable clocking. Configure the clock source line secondary command on the T1 interface that has the next best known clocking. With this configuration, the primary line clocking is backed up to the secondary line if the primary clocking shuts down.
Example
The following example configures the Cisco AS5200 access server to use T1 controller 0 as the primary clock source and T1 controller 1 as the secondary clock source:
controller t1 0clock source line primarycontroller t1 1clock source line secondarycontroller
To configure a T1 or E1 controller and enter controller configuration mode, use the controller global configuration command.
controller {t1 | e1} slot/port (on the Cisco 7200 and Cisco 7500 series)
controller {t1 | e1} number (on the Cisco AS5200 and Cisco AS5300 series)Syntax Description
Default
No T1 or E1 controller is configured.
Command Mode
Global configuration
Usage Guidelines
This command first appeared in Release 10.0; the e1 keyword was added in Release 10.3
This command is used in configurations where the router or access server is intended to communicate with a T1 or E1 fractional data line. Additional parameters for the T1 or E1 line must be configured for the controller before the T1 or E1 circuits can be configured by means of the interface global configuration command.
This command is used on a Cisco 7500 series router.
This command does not apply to the Cisco 7200 series.
Examples
The following example configures the MIP in slot 4, port 0 of a Cisco 7500 as a T1 controller:
controller t1 4/0The following example configures NIM 0 of a Cisco 4000 as a T1 controller:
controller t1 0Related Commands
You can use the master indexes or search online to find documentation of related commands.
channel-group
clear controller lex
clear controller t1
clock source (controller)
framing
linecode
show controllers e1
show controller t1cpp authentication
To enable negotiation of authentication with a router or bridge that supports the Combinet Proprietary Protocol (CPP) and that is calling in to this router, use the cpp authentication interface configuration command. To disable negotiation of CPP authentication, use the no form of this command.
cpp authentication
no cpp authenticationSyntax Description
This command has no arguments or keywords.
Default
Disabled
Command Mode
Interface configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.2.
Use this command for authenticating the device that is calling in to this router.
Use this command to communicate over an ISDN interface with Combinet devices that do not support Point-to-Point Protocol (PPP) but do support the Combinet Proprietary Protocol (CPP).
Currently, most Combinet devices do support PPP. Cisco routers can communicate over ISDN with these devices by using PPP encapsulation, which supports both routing and fast switching.
This command is supported on ISDN and dialer interfaces.
This command uses names and passwords from the username password command. It does not support the Terminal Access Controller Access Control System (TACACS).
Example
The following example configures a Primary Rate Interface to communicate with a Combinet bridge that does not support PPP:
controller t1 1/1framing esflinecode b8zspri-group timeslots 1-23isdn switchtype primary-4essinterface Serial1/1:23encapsulation cppcpp callback accept cpp authenticationRelated Commands
You can use the master indexes or search online to find documentation of related commands.
cpp callback accept
encapsulation cpp
username passwordcpp callback accept
To enable the router to accept callback from a Combinet router or bridge that supports the Combinet Proprietary Protocol (CPP), use the cpp callback accept interface configuration command. use the no form of this command to disable callback acceptance.
cpp callback accept
no cpp callback acceptSyntax Description
This command has no arguments or keywords.
Default
Disabled
Command Mode
Interface configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.2.
Use this command to communicate over an ISDN interface with Combinet devices that do not support PPP but do support CPP.
Currently, most Combinet devices do support PPP. Cisco routers can communicate over ISDN with these devices by using PPP encapsulation, which supports both routing and fast switching.
This command is supported on ISDN and dialer interfaces.
Example
The following example configures the PRI interface serial1/1:23 to communicate with a Combinet router or bridge that does not support PPP:
controller t1 1/1framing esflinecode b8zspri-group timeslots 1-23isdn switchtype primary-4ess!interface Serial1/1:23encapsulation cppcpp callback acceptcpp authenticationRelated Commands
You can use the master indexes or search online to find documentation of related commands.
cpp authentication
encapsulation cppdescription (controller)
Toadd a description to an E1 or T1 controller, use the description controller configuration command. Use the no form of this command to remove the description.
description string
no descriptionSyntax Description
Default
No description is added.
Command Mode
Controller configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.2.
The description command is meant solely as a comment to be put in the configuration to help you remember what certain E1 or T1 controllers are used for. The description affects the MIP interfaces only and appears in the output of the show controllers e1, show controllers t1, and more system:running-config EXEC commands.
Example
The following example describes a 3174 controller:
controller t1 description 3174 Controller for test labRelated Commands
You can use the master indexes or search online to find documentation of related commands.
more system:running-config
show controllers e1
show controller t1
description (interface)
To add a description to an interface configuration, use the description interface configuration command. Use the no form of this command to remove the description.
description string
no descriptionSyntax Description
Default
No description is added.
Command Mode
Interface configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 9.21.
The description command is meant solely as a comment to be put in the configuration to help you remember what certain interfaces are used for. The description appears in the output of the following EXEC commands: more nvram:startup-config, show interfaces, and more system:running-config.
Example
The following example shows how to add a description for a T1 interface:
interface serial 0 description Fractional T1 line to Mountain View -- 128 kbpsRelated Commands
You can use the master indexes or search online to find documentation of related commands.
more nvram:startup-config
more system:running-config
show interfacesdialer outgoing
To configure the dialer map class for a Network Specific Facilities (NSF) dialing plan to support outgoing calls, use the dialer outgoing map-class dialer configuration command.
dialer outgoing classname
Syntax Description
classname
Keyword for a specified AT&T Primary-4ESS NSF dialing plan; the following keywords are supported: sdn, megacomm, and accunet.
Default
This command is disabled; no classname is provided.
Command Mode
Map-class dialer configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.0.
Use this command only to define a dialer map class for an NSF call-by-call service offered by AT&T on Primary-4ESS ISDN switches. This command is not used for other vendors and switch types.
Example
The following partial example shows a class called sdn to support the Software Defined Network (SDN) dialing plan. For a more complete example using all the related commands, see the map-class dialer command.
dialer outgoing sdnRelated Commands
You can use the master indexes or search online to find documentation of related commands.
dialer map class
dialer voice-call
isdn nsf-service
map-class dialerdialer voice-call
To configure the dialer map class for an NSF dialing plan to support outgoing voice calls, use the dialer voice-call map-class dialer configuration command.
dialer voice-call
Syntax Description
This command has no arguments and keywords.
Default
This command is disabled.
Command Mode
Map-class dialer configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.0.
Example
The following partial example defines a dialer map class to support the SDN dialing plan and to support outgoing voice calls. For a more complete example using all the related commands, see the map-class dialer command.
map-class dialer sdnplandialer voice-calldialer outgoing sdnRelated Commands
You can use the master indexes or search online to find documentation of related commands.
dialer map class
map-class dialer
dialer outgoingencapsulation cpp
To enable encapsulation for communication with routers or bridges using the Combinet Proprietary Protocol (CPP), use the encapsulation cpp interface configuration command. Use the no form of this command to disable CPP encapsulation.
encapsulation cpp
no encapsulation cppSyntax Description
This command has no arguments or keywords.
Default
Disabled
Command Mode
Interface configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.2.
Use this command to communicate over an ISDN interface with Combinet devices that do not support PPP but do support CPP.
Currently, most Combinet devices do 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.
This command is supported on ISDN BRIs and Primary Rate Interfaces (PRIs) only.
Example
The following example configures PRI interface serial 1/1:23 to communicate with a Combinet router or bridge that does not support PPP:
controller t1 1/1framing esflinecode b8zspri-group timeslots 1-23isdn switchtype primary-4ess!interface Serial1/1:23encapsulation cppcpp callback accept cpp authenticationRelated Commands
You can use the master indexes or search online to find documentation of related commands.
cpp authentication
cpp callback acceptframing
Use the framing controller configuration command to select the frame type for the T1 or E1 data line.
framing {sf | esf} (for T1 lines)
framing {crc4 | no-crc4} [australia] (for E1 lines)Syntax Description
Defaults
Super Frame is the default on a T1 line.
CRC4 frame is the default on an E1 line.
Command Mode
Controller configuration
Usage Guidelines
Use this command in configurations where the router or access server is intended to communicate with T1 or E1 fractional data line. The service provider determines which framing type, either sf, esf, or crc4, is required for your T1/E1 circuit.
Example
The following example selects Extended Super Frame as the T1 frame type:
framing esfRelated Commands
You can use the master indexes or search online to find documentation of related commands.
channel-group
linecodeinterface serial
To specify a serial interface created on a channelized E1 or channelized T1 controller (for ISDN PRI, channel-associated signaling, or robbed-bit signaling), use the interface serial global configuration command.
interface serial slot/port:timeslot (on the Cisco 7200 and Cisco 7500 series)
interface serial number:timeslot (on the Cisco AS5200 and Cisco 4000 series)Syntax Description
Default
You must explicitly specify a serial interface.
Command Mode
Global configuration
Usage Guidelines
This command first appeared prior to Release 10.0.
The D channel is always the :23 channel for T1 and the :15 for E1.
Examples
The following example configures channel groups on timeslots 1 to 11 and ISDN PRI on timeslots 12 to 24 of T1 controller 0. Then the examples configures the first two channel groups as serial interfaces 0:0 and 0:1.
controller t1 0channel-group 0 timeslot 1-6channel-group 1 timeslot 7channel-group 2 timeslot 8channel-group 3 timeslot 9-11pri-group timeslots 12-24!interface serial 0:0ip address 131.108.13.2 255.255.255.0encapsulation ppp!interface serial 0:1ip address 131.108.13.3 255.255.255.0encapsulation pppThe following example configures ISDN PRI on T1 controller 4/1 and then configures the D channel on the resulting serial interface 4/1:23:
controller t1 4/1framing crc4linecode hdb3pri-group timeslots 1-24interface serial 4/1:23ip address 131.108.13.1 255.255.255.0encapsulation pppRelated Commands
You can use the master indexes or search online to find documentation of related commands.
circuit
controller
show interfaces
show controllers t1 call-countersisdn answer1, isdn answer2
To have the router verify a called-party number or subaddress number in the incoming setup message for ISDN PRI calls, if the number is delivered by the switch, use the isdn answer1 interface configuration command. To remove the verification request, use the no form of this command.
isdn answer1 [called-party-number][:subaddress]
no isdn answer1 [called-party-number][:subaddress]To have the router verify an additional called-party number or subaddress number in the incoming setup message for ISDN PRI calls, if the number is delivered by the switch, use the isdn answer2 interface configuration command. To remove this second verification request, use the no form of this command.
isdn answer2 [called-party-number][:subaddress]
no isdn answer2 [called-party-number][:subaddress]Syntax Description
Default
The router does not verify the called-party or subaddress number.
Command Mode
Interface configuration
Usage Guidelines
If you do not specify the isdn answer1 or isdn answer2 command, all calls are processed and/or accepted. If you specify the isdn answer1 or isdn answer2 command, the router must verify the incoming called-party number and the subaddress before processing and/or accepting the call. The verification proceeds from right to left for the called-party number; it also proceeds from right to left for the subaddress number.
You can configure just the called-party number or just the subaddress. In such a case, only that part is verified. To configure a subaddress only, include the colon (:) before the subaddress number.
You can declare a digit a "don't care" digit by entering it as an x or X. In such a case, any incoming digit is allowed.
Examples
In the following partial configuration example, 5552222 is the called-party number and 1234 is the subaddress:
interface serial 4/1:0isdn answer1 5552222:1234In the following partial configuration example, only the subaddress is configured:
interface serial 4/1:0isdn answer1 :1234isdn bchan-number-order
To configure a PRI ISDN interface to make outgoing call selection in ascending or descending order, use the isdn bchan-number-order interface configuration command. To restore the default (descending order), either use the no form of this command or simply reconfigure the interface with the new value.
isdn bchan-number-order {ascending | descending}
no isdn bchan-number-orderSyntax Description
Default
Descending
Command Mode
Interface configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.3 T.
This command instructs the router to select the lowest or highest available B channel starting at either channel B1 (ascending) or channel B23 for a T1 and channel B30 for an E1 (descending).
This command is for PRI configuration only.
Example
The following example configures the outgoing B channel order on a PRI interface to be in ascending order. The router will select the lowest available B channel beginning with channel B1.
interface serial5:10 isdn bchan-number-order ascendingisdn caller
To configure ISDN caller ID screening, use the isdn caller interface configuration command. To disable this feature, use the no form of this command.
isdn caller number
no isdn caller numberSyntax Description
number
Telephone number for which to screen. Specify an x or X to represent a single "don't-care" character. The maximum length of each number is 25 characters.
Default
Disabled
Command Mode
Interface configuration
Usage Guidelines
This command first appeared in Release 11.2 F.
This command configures the router to accept calls from the specified number.
Caller ID screening is available on Cisco 7200 and 7500 series, Cisco 4000 series, Cisco 3000 series, and Cisco 2500 series routers that have one or more BRIs.
The maximum length of each number is 25 characters. There is no limit on the numbers you can specify per interface.
Note
Examples
The following example configures the router to accept a call with a delivered caller ID equal to 4155551234:
isdn caller 4155551234The following example configures the router to accept a call with a delivered caller ID having 41555512 and any numbers in the last two positions:
isdn caller 41555512xxRelated Commands
You can use the master indexes or search online to find documentation of related commands.
show dialer
isdn calling-number
To configure an ISDN PRI serial interface to present a billing number of the device making the outgoing call, use the isdn calling-number interface configuration command. To remove a previously configured calling number, use the no form of this command.
isdn calling-number calling-number
no isdn calling numberSyntax Description
calling-number
Number of the device making the outgoing call; only one entry is allowed and it is limited to 16 digits.
Default
No calling number is presented.
Command Mode
Interface configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 10.3.
An interface can have only one ISDN calling-number entry.
This command is intended for use when the network offers better pricing on calls in which devices present the calling number (that is, the billing number). The calling number information is included in the outgoing Setup message.
Note
Example
The following example first configures the T1 and then, configures D channel interface to present the billing number 4233570925 when it makes outgoing calls:
controller t1 1/1framing esflinecode b8zspri-group timeslots 1-23isdn switchtype primary-4ess!interface serial 1/1:23ip address 7.1.1.1 255.255.255.0encapsulation pppisdn calling-number 4233570925dialer map ip 7.1.1.2 name dallas 14193460913Related Commands
You can use the master indexes or search online to find documentation of related commands.
isdn modem-busy-cause
To send a specific ISDN cause code to the switch, use the isdn modem-busy-cause interface configuration command. To return to the default condition, use the no form of this command.
isdn modem-busy-cause {cause-code-number | busy | not-available}
no isdn modem-busy-cause {cause-code-number | busy | not-available}Syntax Description
Default
No calling number is presented.
Command Mode
Interface configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.3.
The isdn modem-busy-cause command overrides the specific cause codes (such as modem availability and resource pooling) that are sent to the switch by ISDN applications. When the isdn modem-busy-cause command is entered, the configured cause codes are sent to the switch; otherwise, the default cause codes for the application are sent. ISDN protocol error are still reflected in the codes and are not overridden.
Example
The following example sends the CHANNEL-NOT-AVAILABLE code to the ISDN switch:
interface serial0:20isdn busy-cause-code not-availableisdn fast-rollover-delay
To specify the time delay between successive attempts to dial out to a number, use the isdn fast-rollover-delay interface configuration command. Use the no form of this command to disable the fast-rollover-delay feature.
isdn fast-rollover-delay seconds
no isdn fast-rollover-delaySyntax Description
seconds
Number of seconds to delay before dialing the next dialer map after receiving an ISDN message indicating the current call will not succeed.
Default
This command is disabled by default. If enabled, the default value of the timer is 0 seconds.
Command Mode
Interface configuration
Usage Guidelines
This command first appeared at Cisco IOS Release 11.1.
This command provides a timer separate from the dialer wait-for-carrier timer to control the amount of time that elapses before calls are redialed. This delay is provided to allow the old call to be torn down completely before the new call is attempted.
When using PPP callback, this command specifies the time delay before the callback is done. This command is necessary on some ISDN switches because the new call may be attempted before the old call is completely torn down. This causes the call back to fail.
Use this command when all the following conditions are true:
•
•
•
If this has occurred, set isdn fast-rollover-delay to 5 seconds and try again.
A delay of 5 seconds should cover most cases. Configure sufficient delay to make sure the ISDN RELEASE_COMPLETE message has been sent or received before making the fast rollover call. Use the debug isdn q931 command to display this information.
Example
The following partial example sets the fast-rollover delay that is suggested when all the conditions specified above are true.
isdn fast-rollover-delay 5Related Commands
You can use the master indexes or search online to find documentation of related commands.
dialer map
dialer wait-for-carrier
ppp callbackisdn incoming-voice data
To answer incoming voice calls at a configured rate (overriding the incoming data rate in the call), use the isdn incoming-voice data interface configuration command. Use the no form of this command to disable ISDN incoming-voice data.
isdn incoming-voice data [56 | 64]
no isdn incoming-voice dataSyntax Description
Default
ISDN incoming-voice data is not applied.
Command Mode
Interface configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.2.
When used without a keyword, this command checks the bearer capacity.
If this command is used, the dialing side must dial at 56 kbps.
Ordinarily, a data device ignores incoming voice calls, but the tariff structure for data and voice calls might make it less expensive to do "data over voice" calls.
Example
The following partial example for channelized T1 configures the D channel (hence, all B channels) to answer all incoming voice calls at 56 kbps:
interface serial 0:23isdn incoming-voice data 56isdn incoming-voice modem
To allow all incoming ISDN voice calls to access onboard modems, use the isdn incoming-voice modem interface configuration command. Use the no form of this command to stop all incoming voice calls from accessing the modems.
isdn incoming-voice modem [56 | 64]
no isdn incoming-voice modemSyntax Description
Default
Disabled
Command Mode
Interface configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.1 AA.
Configure this command on each D channel in the access server or router. Incoming circuit switched data calls are not affected by this command.
This command is not used for channelized T1 or channelized E1 network scenarios. These networks use traditional analog trunks that have in-band signaling. Use the isdn incoming-voice modem command only when you are using ISDN.
Example
The following example enables incoming and outgoing ISDN calls to route to the modems using the D channel serial interface:
interface serial 0:23isdn incoming-voice modem 56isdn not-end-to-end
For incoming calls, to override the speed that the network reports it will use to deliver the call data, use the isdn not-end-to-end interface configuration command.
isdn not-end-to-end {56 | 64}
Syntax Description
Default
The default line speed is 64 kbps.
Command Mode
Interface configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 10.3.
This command might be needed to handle incoming calls properly. Although a call might originate at a speed of 56 kbps, the network or internetworking networks might improperly deliver the call to the user at a speed of 64 kbps. This creates a speed mismatch and causes the data to be garbled. Enabling this command makes the router look more closely at the information elements of the incoming call to determine a speed.
A speed mismatch can occur when the source and destination ISDN ports do not belong to the same network.
Example
The following example sets the line speed for incoming calls to 56 kbps:
isdn not-end-to-end 56isdn nsf-service
To configure Network Specific Facilities (NSF) on an ISDN PRI for outgoing calls configured as voice calls, use the isdn nsf-service command. To remove NSF on an ISDN PRI, use the no form of this command.
isdn nsf-service {megacom | sdn}
no isdn nsf-service [megacom | sdn]Syntax Description
Default
Disabled
Command Mode
Interface configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.3(5)T.
This command is used on a PRI (channelized T1) to request NSF services supported on AT&T 4ESS switch types only.
Example
The following example sets outgoing voice calls to use AT&T SDN NSF:
int s0:23isdn-nsf-service sdnRelated Commands
You can use the master indexes or search online to find documentation of related commands.
dialer map class
dialer voice-call
map-class dialerisdn sending-complete
To specify that the Sending Complete information element (IE) is included in the outgoing SETUP message, use the isdn sending-complete interface configuration command. Use the no form of this command to disable the Sending Complete IE.
isdn sending-complete
no isdn sending-completeSyntax Description
This command has no arguments and keywords.
Default
This command is disabled by default.
Command Mode
Interface configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.3.
Some switches in some countries want a Sending Complete information element to be included in the outgoing SETUP message to indicate that the entire number is included. The Sending Complete IE is needed for some countries, such as Hong Kong and Taiwan, and the isdn sending-complete command forces it to be sent.
Example
The following example enables sending complete IE information:
interface serial 0:15description connected to PBX 61886ip address 7.1.1.1 255.255.255.0encapsulation pppisdn sending-completedialer idle-timeout 20dialer map ip 7.1.1.2 name rudder 61884dialer map ip 7.1.1.3 name goodie 61885dialer-group 1ppp authentication chapisdn switch-type
To specify the central office switch type on the ISDN interface, use the isdn switch-type global and interface configuration command. Use the no form of this command to disable the switch on the ISDN interface.
isdn switch-type switch-type
no isdn switch-typeSyntax Description
Default
The switch type defaults to none, which disables the switch on the ISDN interface.
Command Mode
This command first appeared as a global command in Cisco IOS Release 9.21
This command first appeared as an interface command in Cisco IOS Release 11.3 T.Usage Guidelines
To disable the switch on the ISDN interface, specify isdn switch-type none.
lists supported PRI switch types by geographic area.
Note
Table 46 ISDN Service Provider PRI Switch Types
Note
Examples
The first example configures the French VN3 ISDN switch type:
isdn switch-type vn3The following example demonstrates the Multiple ISDN Switch Type Feature. The global ISDN switch type setting is basic-net3. The PRI interface (channelized T1 controller), is configured to use isdn switch-type primary-net5 and BRI interface 0 is configured for isdn switch-type basic-ni (formerly isdn switch-type basic-ni1).
isdn switch-type basic-net3 ! interface serial0:23 isdn switch-type primary-net5 ip address 172.21.24.85 255.255.255.0 ! interface BRI0 isdn switch-type basic-nilinecode
Use the linecode controller configuration command to select the line-code type for the T1 or E1 line.
linecode {ami | b8zs | hdb3}
Syntax Description
Defaults
AMI is the default for T1 lines.
High-density bipolar 3 is the default for E1 lines.
Command Mode
Controller configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 10.3.
Use this command in configurations where the router or access server must communicate with T1 fractional data lines. The T1 service provider determines which line-code type, either ami or b8zs, is required for your T1 circuit. Likewise, the E1 service provider determines which line-code type, either ami or hdb3, is required for your E1 circuit.
Example
The following example specifies B8ZS as the line-code type:
linecode b8zsloopback (controller e1)
To loop an entire E1 line (including all channel-groups defined on the controller) toward the line and back toward the router or access server, use the loopback controller configuration command. To remove the loop, use the no form of this command.
loopback
no loopbackSyntax Description
This command has no arguments or keywords.
Default
Disabled
Command Mode
Controller configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.1.
This command is useful for testing the DCE device (CSU/DSU) itself.
To show interfaces currently in loopback operation, use the show interfaces loopback EXEC command.
Example
The following example configures the loopback test on the E1 line:
controller e1 0 loopbackloopback local (controller)
To loop an entire T1 line (including all channel-groups defined on the controller) toward the line and the router or access server, use the loopback local controller configuration command. To remove the loop, use the no form of this command.
loopback local
no loopback localSyntax Description
This command has no arguments or keywords.
Default
Disabled
Command Mode
Controller configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.1.
This command is useful for testing the DCE device (CSU/DSU) itself.
To show interfaces currently in loopback operation, use the show interfaces loopback EXEC command.
Example
The following example configures the loopback test on the T1 line:
controller t1 0 loopback localloopback local (interface)
To loop a channelized T1 or channelized E1 channel-group, use the loopback local interface configuration command. To remove the loop, use the no form of this command.
loopback local
no loopback localSyntax Description
This command has no arguments or keywords.
Default
Disabled
Command Mode
Interface configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.1.
This command is useful for looping a single channel-group in a channelized environment without disrupting the other channel-groups.
To show interfaces currently in loopback operation, use the show interfaces loopback EXEC command.
Example
The following example configures the loopback test on the T1 line:
interface serial 1/0:22 loopback localRelated Commands
You can use the master indexes or search online to find documentation of related commands.
show interfaces loopback
loopback remote (controller)
To loop packets from a MIP through the CSU/DSU, over a dedicated T1 link, to the remote CSU at the single destination for this T1 link and back, use the loopback remote controller configuration command. To remove the loop, use the no form of this command.
loopback remote
no loopback remoteSyntax Description
This command has no arguments or keywords.
Default
Disabled
Command Mode
Controller configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.1.
This command applies only when the device supports the remote function. It is used for testing the data communication channels.
For MIP cards, this controller configuration command applies if only one destination exists at the remote end of the cloud, the entire T1 line is dedicated to it, and the device at the remote end is a CSU (not a CSU/DSU). This is an uncommon case; MIPs are not usually used in this way.
To show interfaces currently in loopback operation, use the show interfaces loopback EXEC command.
Example
The following example configures a remote loopback test:
interface serial 0 loopback remoteRelated Commands
You can use the master indexes or search online to find documentation of related commands.
show interfaces loopback
loopback remote (interface)
To loop packets through a CSU/DSU, over a DS-3 link or a channelized T1 link, to the remote CSU/DSU and back, use the loopback remote interface configuration command. To remove the loop, use the no form of this command.
loopback remote
no loopback remoteDefault
This command is disabled.
Command Mode
Interface configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.1.
This command applies only when the remote CSU/DSU device supports the function. It is used for testing the data communication channels. The loopback usually is performed at the line port, rather than the DTE port, of the remote CSU/DSU.
For a multiport interface processor (MIP) connected to a network via a channelized T1 link, the loopback remote interface configuration command applies if the remote interface is served by a DDS line (56 kbps or 64 kbps) and the device at the remote end is a CSU/DSU. In addition, the CSU/DSU at the remote end must react to latched DDS CSU loopback codes. Destinations that are served by other types of lines or that have CSU/DSUs that do not react to latched DDS CSU codes cannot participate in an interface remote loopback. Latched DDS CSU loopback code requirements are described in AT&T specification TR-TSY-000476, "OTGR Network Maintenance Access and Testing."
To show interfaces currently in loopback operation, use the show interfaces loopback EXEC command.
Example
The following example configures a remote loopback test:
interface serial 0 loopback remoteRelated Commands
You can use the master indexes or search online to find documentation of related commands.
show interfaces loopback
map-class dialer
To define a class of shared configuration parameters for outgoing calls from an ISDN interface, use the map-class dialer global configuration command.
map-class dialer classname
Syntax Description
Default
Disabled; no class name is provided.
Command Mode
Global configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.0.
The classname in the map-class dialer command used to specify the class must be the same as a classname used in a dialer map command.
This command is used to define classes of calls for PPP callback for DDR, for ISDN Advice of Charge, and for Network Specific Facilities (NSF) call-by-call dialing plans.
For NSF call-by-call support on ISDN Primary-4ESS switches only, use one of the dialing-plan keywords listed in Table 47.
Table 47 NSF Keywords and Supported Services
sdnplan
SDN
Yes
Yes
GSDN (Global SDN)
megaplan
MEGACOMM
No
Yes
Yes
accuplan
ACCUNET
Yes
Yes
Yes
Examples
The following example configures the PPP callback server on an ISDN BRI interface on a router in Atlanta. The callback server requires an enable timeout and a map class to be defined.
interface BRI0ip address 7.1.1.7 255.255.255.0encapsulation pppdialer callback-securedialer enable-timeout 2dialer map ip 7.1.1.8 name atlanta class dial1 81012345678901dialer-group 1ppp callback acceptppp authentication chap!map-class dialer dial1dialer callback-server usernameThe following example configures the ISDN switch type to Primary-4ESS and configures ISDN PRI on T1 controller 1/0, and sets the D channel for dialer map classes that reference the NSF dialing plans. Finally, the map-class dialer command uses a dialing plan keyword and the dialer outgoing command refers to the same plan.
isdn switch-type primary-4ess!!controller T1 1/0framing esflinecode b8zspri-group timeslots 1-24!interface Serial1/0:23description This is the DMS D-channel 415-390-9503ip address 6.1.1.3 255.255.255.0encapsulation pppno keepalivedialer map ip 6.1.1.1 name tommyjohn class sdnplan 14085770715dialer map ip 6.1.1.2 name angus class megaplan 14085773775dialer map ip 6.1.1.4 name angus class accuplan 14085773778dialer-group 1ppp authentication chap!map-class dialer sdnplandialer outgoing sdn!map-class dialer megaplandialer voice-calldialer outgoing mega!map-class dialer accuplandialer outgoing accuRelated Commands
You can use the master indexes or search online to find documentation of related commands.
dialer map class
map-class dialer
dialer outgoingpri-group
To specify ISDN Primary Rate Interface (PRI) on a channelized T1 or channelized E1 controller, use the pri-group controller configuration command. Use the no form of this command to remove the ISDN PRI configuration.
pri-group [timeslots range]
no pri-groupSyntax Description
timeslots range
(Optional) Specifies a single range of values from 1 to 23 for channelized T1 and from 1 to 31 for channelized E1.
Default
This command is disabled.
Command Mode
Controller configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 10.3.
Before you enter the pri-group command, you must specify an ISDN PRI switch type and an E1 or T1 controller.
Examples
The following example configures ISDN PRI on all timeslots of the T1 controller in slot 1 port 0 on a Cisco 7200 series router:
isdn switch-type primary-4esscontrollers t1 1/0 framing esflinecode b8zs pri-group timeslots 1-24The following example configures E1 controller 0 on a Cisco 4000 series router for ISDN PRI on all timeslots:
isdn switch-type primary-net5 controllers e1 0/0 framing esflinecode b8zs pri-group timeslots 1-31Related Commands
You can use the master indexes or search online to find documentation of related commands.
controllers e1
controllers t1
framing
isdn switch-type
linecode b8zsshow controllers e1
Use the show controllers e1 privileged EXEC command to display information about the E1 links supported by the Network Processor Module (NPM) (Cisco 4000) or MultiChannel Interface Processor (MIP) (Cisco 7500 series).
show controllers e1 [slot/port] (on the Cisco 7500 series)
show controller e1 number (on the Cisco 4000 series)Syntax Description
Command Mode
Privileged EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 11.2.
The NPM or MIP can query the port adapters to determine their current status. Issue a show controllers e1 command to display statistics about the E1 link.
If you specify a slot and port number, each 15-minute period will be displayed.
This command displays controller status that is specific to the controller hardware. The information displayed is generally useful for diagnostic tasks performed by technical support personnel only.
Sample Displays
The following is sample output from the show controllers e1 command on the Cisco 7500 series:
Router# show controllers e1e1 0/0 is up.Applique type is Channelized E1 - unbalancedFraming is CRC4, Line Code is HDB3No alarms detected.Data in current interval (725 seconds elapsed):0 Line Code Violations, 0 Path Code Violations0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail SecsTotal Data (last 24 hours)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 SecsFollowing is an example of the show controllers e1 display including the board identifier type:
Router# show controllers e1E1 4/1 is up.No alarms detected.Framing is CRC4, Line Code is hdb3Data in current interval (0 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 SecsTotal Data (last 79 15 minute intervals):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 Secsdescribes the show controllers e1 display fields.
show controllers e1 call-counters
To view the total number of calls and call durations on a E1 controller, use the show controllers e1 call-counters Privileged EXEC command.
show controllers e1 number call-counters
Syntax Description
Command Mode
Privileged EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 11.3 T.
This command displays the E1 controller status as calls, such as switched 56K digital calls, pass through the hardware.
Sample Display
The following is sample display output for the show controller e1 1 call-counters command.
router# show controller E1 1 call-countersE1 1:DS0's Active: 0DS0's Active High Water Mark: 0TimeSlot Type TotalCalls TotalDuration1 cas 0 00:00:002 cas 0 00:00:003 cas 0 00:00:004 cas 0 00:00:005 cas 0 00:00:006 cas 0 00:00:007 cas 0 00:00:008 cas 0 00:00:009 cas 0 00:00:0010 cas 0 00:00:0011 cas 0 00:00:0012 cas 0 00:00:0013 cas 0 00:00:0014 cas 0 00:00:0015 cas 0 00:00:0016 cas 0 00:00:0017 cas 0 00:00:0018 cas 0 00:00:0019 cas 0 00:00:0020 cas 0 00:00:0021 cas 0 00:00:0022 cas 0 00:00:0023 cas 0 00:00:0024 cas 0 00:00:00Total DS0's Active High Water Mark: 7describes the sample display output for the show controller e1 1 call-counters command.
Table 49
Show Controllers E1 Call-Counters Field Descriptions
Related Commands
You can use the master indexes or search online to find documentation of related commands.
show controllers e1 cas-data
cas-group (controller e1)show controllers e1 cas-data
To display internal call switching module information about the switched 56k data channels, use the show controllers e1 cas-data Privileged EXEC command.
show controllers e1 number cas-data
Syntax Description
Command Mode
Privileged EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 11.3 T.
Sample Display
The following is sample output for the show controller e1 1 cas-data command.
router# show controller e1 1 cas-dataDevice Pool: Dev-SW56-poolNumber of SW56 vdev in pool: 48Number of active connections: 0No free SW56 device in pool: 0SW56 max allocated messages: 96E1 1:SW56(slot/subcont/bchan)=0/1/0, hwidb=0x00867348csm_state(0x00000100)=CSM_IDLE_STATE, csm_event_proc=0x0006CCC2total_call_duration=00:00:00invalid_event_count=0, wdt_timeout_count=0ic_failure=0, ic_complete=0, remote_link_disc=0csm_status(0): VDEV_STATUS_UNLOCKEDwdt_timestamp_started is not activatedSW56(slot/subcont/bchan)=0/1/1, hwidb=0x0086EC58csm_state(0x00000100)=CSM_IDLE_STATE, csm_event_proc=0x0006CCC2total_call_duration=00:00:00invalid_event_count=0, wdt_timeout_count=0ic_failure=0, ic_complete=0, remote_link_disc=0csm_status(0): VDEV_STATUS_UNLOCKEDwdt_timestamp_started is not activatedSW56(slot/subcont/bchan)=0/1/2, hwidb=0x00876568csm_state(0x00000100)=CSM_IDLE_STATE, csm_event_proc=0x0006CCC2total_call_duration=00:00:00invalid_event_count=0, wdt_timeout_count=0ic_failure=0, ic_complete=0, remote_link_disc=0csm_status(0): VDEV_STATUS_UNLOCKEDwdt_timestamp_started is not activatedSW56(slot/subcont/bchan)=0/1/3, hwidb=0x0087DE78csm_state(0x00000100)=CSM_IDLE_STATE, csm_event_proc=0x0006CCC2total_call_duration=00:00:00invalid_event_count=0, wdt_timeout_count=0ic_failure=0, ic_complete=0, remote_link_disc=0csm_status(0): VDEV_STATUS_UNLOCKEDwdt_timestamp_started is not activatedSW56(slot/subcont/bchan)=0/1/4, hwidb=0x00885788csm_state(0x00000100)=CSM_IDLE_STATE, csm_event_proc=0x0006CCC2total_call_duration=00:00:00invalid_event_count=0, wdt_timeout_count=0ic_failure=0, ic_complete=0, remote_link_disc=0csm_status(0): VDEV_STATUS_UNLOCKEDwdt_timestamp_started is not activateddescribes the sample display output for the show controller e1 1 cas-data command.
Table 50
Show Controllers E1 Cas-Data Field Descriptions
Related Commands
You can use the master indexes or search online to find documentation of related commands.
show controllers e1 call-counters
cas-group (controller e1)show controllers t1
To display information about the T1 links, use the show controllers t1 privileged EXEC command.
show controllers t1 [slot/port] (Cisco 7500 series)
show controllers t1 number (Cisco 4000 series)Syntax Description
Command Mode
Privileged EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 11.2.
This command displays controller status that is specific to the controller hardware. The information displayed is generally useful for diagnostic tasks performed by technical support personnel only.
The NPM or MIP can query the port adapters to determine their current status. Issue a show controllers t1 command to display statistics about the T1 link.
If you specify a slot and port number, each 15 minute period will be displayed.
Sample Display
The following is sample output from the show controllers t1 command on the Cisco 7500 series:
Router# show controllers t1T1 4/1 is up.No alarms detected.Framing is ESF, Line Code is AMI, Clock Source is lineData in current interval (0 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 SecsTotal Data (last 79 15 minute intervals):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 Secsdescribes the show controllers t1 display fields.
show controllers t1 call-counters
To view the total number of calls and call durations on a T1 controller, use the show controllers t1 call-counters Privileged EXEC command.
show controllers t1 number call-counters
Syntax Description
Command Mode
Privileged EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 11.3 T.
This command displays the T1 controller status as calls, such as switched 56K digital calls, pass through the hardware.
Sample Display
The following is sample output for the show controllers t1 1 call-counters command.
router# show controllers t1 1 call-countersT1 1:DS0's Active: 0DS0's Active High Water Mark: 0TimeSlot Type TotalCalls TotalDuration1 cas 0 00:00:002 cas 0 00:00:003 cas 0 00:00:004 cas 0 00:00:005 cas 0 00:00:006 cas 0 00:00:007 cas 0 00:00:008 cas 0 00:00:009 cas 0 00:00:0010 cas 0 00:00:0011 cas 0 00:00:0012 cas 0 00:00:0013 cas 0 00:00:0014 cas 0 00:00:0015 cas 0 00:00:0016 cas 0 00:00:0017 cas 0 00:00:0018 cas 0 00:00:0019 cas 0 00:00:0020 cas 0 00:00:0021 cas 0 00:00:0022 cas 0 00:00:0023 cas 0 00:00:0024 cas 0 00:00:00Total DS0's Active High Water Mark: 7describes the sample output for the show controllers t1 1 call-counters command.
Table 52
Show Controllers T1 Call-Counters Field Descriptions
Related Commands
You can use the master indexes or search online to find documentation of related commands.
show controllers t1 cas-data
cas-group (controller t1)show controllers t1 cas-data
To display internal call switching module information about the switched 56k data channels, use the show controllers t1 cas-data Privileged EXEC command.
show controllers t1 number cas-data
Syntax Description
Command Mode
Privileged EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 11.3 T.
Sample Display
The following is sample output for the show controllers t1 1 cas-data command.
router# show controllers t1 1 cas-dataDevice Pool: Dev-SW56-poolNumber of SW56 vdev in pool: 48Number of active connections: 0No free SW56 device in pool: 0SW56 max allocated messages: 96T1 1:SW56(slot/subcont/bchan)=0/1/0, hwidb=0x00867348csm_state(0x00000100)=CSM_IDLE_STATE, csm_event_proc=0x0006CCC2total_call_duration=00:00:00invalid_event_count=0, wdt_timeout_count=0ic_failure=0, ic_complete=0, remote_link_disc=0csm_status(0): VDEV_STATUS_UNLOCKEDwdt_timestamp_started is not activatedSW56(slot/subcont/bchan)=0/1/1, hwidb=0x0086EC58csm_state(0x00000100)=CSM_IDLE_STATE, csm_event_proc=0x0006CCC2total_call_duration=00:00:00invalid_event_count=0, wdt_timeout_count=0ic_failure=0, ic_complete=0, remote_link_disc=0csm_status(0): VDEV_STATUS_UNLOCKEDwdt_timestamp_started is not activatedSW56(slot/subcont/bchan)=0/1/2, hwidb=0x00876568csm_state(0x00000100)=CSM_IDLE_STATE, csm_event_proc=0x0006CCC2total_call_duration=00:00:00invalid_event_count=0, wdt_timeout_count=0ic_failure=0, ic_complete=0, remote_link_disc=0csm_status(0): VDEV_STATUS_UNLOCKEDwdt_timestamp_started is not activatedSW56(slot/subcont/bchan)=0/1/3, hwidb=0x0087DE78csm_state(0x00000100)=CSM_IDLE_STATE, csm_event_proc=0x0006CCC2total_call_duration=00:00:00invalid_event_count=0, wdt_timeout_count=0ic_failure=0, ic_complete=0, remote_link_disc=0csm_status(0): VDEV_STATUS_UNLOCKEDwdt_timestamp_started is not activatedSW56(slot/subcont/bchan)=0/1/4, hwidb=0x00885788csm_state(0x00000100)=CSM_IDLE_STATE, csm_event_proc=0x0006CCC2total_call_duration=00:00:00invalid_event_count=0, wdt_timeout_count=0ic_failure=0, ic_complete=0, remote_link_disc=0csm_status(0): VDEV_STATUS_UNLOCKEDwdt_timestamp_started is not activateddescribes the sample display output for the show controller t1 1 cas-data command.
Table 53
Show Controllers T1 Cas-Data Field Descriptions
Related Commands
You can use the master indexes or search online to find documentation of related commands.
show controllers t1 call-counters
cas-group (controller t1)show interfaces serial bchannel
To display information about the physical attributes of the ISDN PRI over channelized E1 or channelized T1 B and D channels, use the show interfaces serial bchannel EXEC command.
show interfaces serial slot/port bchannel channel-number
show interfaces serial number bchannel channel-numberSyntax Description
Command Mode
EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 11.2 F.
show isdn
To display the information about memory, Layer 2 and Layer 3 timers, and the status of PRI channels, use the show isdn global configuration command.
show isdn {active | history | memory | services | status [dsl | serial number] | timers}
Syntax Description
Command Mode
Global configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.1.
Sample Displays
The following is sample output from the show isdn active command:
Router# show isdn active-------------------------------------------------------------------------------ISDN ACTIVE CALLS-------------------------------------------------------------------------------History Table MaxLength = 320 entriesHistory Retain Timer = 15 Minutes-------------------------------------------------------------------------------Call Calling Called Duration Remote Time until Recorded ChargesType Number Number Seconds Name Disconnect Units/Currency-------------------------------------------------------------------------------Out 9876543222 Active(10) idacom 11 u(E)Out 9876543210 Active(34) idacom 115 5 u(D)-------------------------------------------------------------------------------The following is sample output from the show isdn history command:
rudder# show isdn history-------------------------------------------------------------------------------ISDN CALL HISTORY-------------------------------------------------------------------------------History Table MaxLength = 320 entriesHistory Retain Timer = 15 Minutes-------------------------------------------------------------------------------Call Calling Called Duration Remote Time until Recorded ChargesType Number Number Seconds Name Disconnect Units/Currency-------------------------------------------------------------------------------Out 47887654 240 blackcanary 5 u(D)In 67893 90 deloreanOut 56745678 Active(90) blackcanary 240 13 u(D)-------------------------------------------------------------------------------describes the fields in the show isdn active and show isdn history output displays.
Table 54 Show ISDN Active and Show ISDN History Field Descriptions
The following sample display shows the output of the show isdn service command when PRI is configured on a T1 controller:
Router# show isdn servicePRI Channel Statistics:ISDN Se0:15, Channel (1-31)Activated dsl 8State (0=Idle 1=Propose 2=Busy 3=Reserved 4=Restart 5=Maint)0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0Channel (1-31) Service (0=Inservice 1=Maint 2=Outofservice)0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0describes the fields in the sample output of the show isdn service command.
Table 55 Show ISDN Service Field Descriptions
ISDN Se1/0:23
ISDN PRI interface corresponding to serial interface 1/0:23.
Channel (1-31)
Channel range "1-31" is a standard format for both T1 and E1 outputs, but the state value shown identifies whether the channel is used.
Activated dsl 0
The digital signal link (DSL) value is 0.
State (0=Idle 1=Propose 2=Busy 3=Reserved 4=Restart 5=Maint)
Current state of each channel. Channels 24 through 31 are marked as reserved when the output is from T1.
Channel (1-31) Service (0=Inservice 1=Maint 2=Outofservice)
Service state assigned to each channel. Channel 24 is marked as out of service.1
1 If channel 24 (marked as out of service) is configured as the NFAS primary D channel, NFAS will roll over to the backup D channel if one is configured. If channel 24 is a B channel, it will not accept calls.
The following shows sample output from the show isdn status command for PRI interfaces configured on two different ports of the same controller. This example shows one active call.
Router# show isdn statusrudder#show isdn statusGlobal ISDN Switchtype = basic-5essISDN BRI0 interfacedsl 0, interface ISDN Switchtype = basic-5essLayer 1 Status:ACTIVELayer 2 Status:TEI = 64, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHEDLayer 3 Status:0 Active Layer 3 Call(s)Activated dsl 0 CCBs = 0ISDN BRI1 interfacedsl 1, interface ISDN Switchtype = basic-5essLayer 1 Status:DEACTIVATEDLayer 2 Status:Layer 2 NOT ActivatedLayer 3 Status:0 Active Layer 3 Call(s)Activated dsl 1 CCBs = 0ISDN BRI2 interfacedsl 2, interface ISDN Switchtype = basic-5essLayer 1 Status:DEACTIVATEDLayer 2 Status:Layer 2 NOT ActivatedLayer 3 Status:0 Active Layer 3 Call(s)Activated dsl 2 CCBs = 0ISDN BRI3 interfacedsl 3, interface ISDN Switchtype = basic-5essLayer 1 Status:ACTIVELayer 2 Status:TEI = 75, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHEDLayer 3 Status:0 Active Layer 3 Call(s)Activated dsl 3 CCBs = 0ISDN BRI4 interfacedsl 4, interface ISDN Switchtype = basic-5essLayer 1 Status:DEACTIVATEDLayer 2 Status:Layer 2 NOT ActivatedLayer 3 Status:0 Active Layer 3 Call(s)Activated dsl 4 CCBs = 0ISDN BRI5 interfacedsl 5, interface ISDN Switchtype = basic-5essLayer 1 Status:DEACTIVATEDLayer 2 Status:Layer 2 NOT ActivatedLayer 3 Status:0 Active Layer 3 Call(s)Activated dsl 5 CCBs = 0ISDN BRI6 interfacedsl 6, interface ISDN Switchtype = basic-5essLayer 1 Status:DEACTIVATEDLayer 2 Status:Layer 2 NOT ActivatedLayer 3 Status:0 Active Layer 3 Call(s)Activated dsl 6 CCBs = 0ISDN BRI7 interfacedsl 7, interface ISDN Switchtype = basic-5essLayer 1 Status:DEACTIVATEDLayer 2 Status:Layer 2 NOT ActivatedLayer 3 Status:0 Active Layer 3 Call(s)Activated dsl 7 CCBs = 0ISDN Serial0:15 interfacedsl 8, interface ISDN Switchtype = primary-niLayer 1 Status:ACTIVELayer 2 Status:TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHEDLayer 3 Status:0 Active Layer 3 Call(s)Activated dsl 8 CCBs = 0Total Allocated ISDN CCBs = 0describes significant fields in the output of the show isdn status command.
