-
Cisco IOS Dial Technologies Configuration Guide, Release 12.4T
- Part 1: Dial Interfaces, Controllers, and Lines
-
Part 2: Modem Configuration and Management
-
Overview of Modem Interfaces
-
Configuring and Managing Integrated Modems
-
Configuring and Managing Integrated Modems
-
1- and 2-Port V.90 Modem WICs for Cisco 2600 and Cisco 3600 Series Multiservice Platforms
-
Call Tracker show Commands Extensions
-
Cisco NM-8AM-V2 and NM-16AM-V2 Analog Modem Network Modules with V.92
-
MICA and NextPort Modem Tech-Support Command Additions
-
PIAFS Wireless Data Protocol Version 2.1 for Cisco MICA Modems
-
V.92 and V.44 Support for Digital Modems
-
V.92 Modem on Hold for Cisco AS5300 and Cisco AS5800 Universal Access Servers
-
V.92 Modem on Hold for Cisco AS5350, Cisco AS5400, and Cisco AS5850 Universal Gateways and Cisco AS5800 Universal Access Servers
-
V.92 Quick Connect for Cisco AS5300 and Cisco AS5800 Universal Access Servers
-
V.92 Quick Connect for Cisco AS5350, Cisco AS5400, and Cisco AS5850 Universal Gateways and Cisco AS5800 Universal Access Servers
-
V.92 Reporting Using RADIUS Attribute v.92-info
-
-
Configuring and Managing Cisco Access Servers and Dial Shelves
-
Configuring and Managing External Modems
-
Modem Signal and Line States
- Creating and Using Modem Chat Scripts
-
Cisco Modem User Interface
-
- Part 3: ISDN Configuration
- Part 4: Signaling Configuration
- Part 5: Dial-on-Demand Routing Configuration
- Part 6: Dial-Backup Configuration
- Part 7: Dial-Related Addressing Services
- Part 8: Virtual Templates, Profiles, and Networks
- Part 9: PPP Configuration
- Part 10: Callback and Bandwidth Allocation Configuration
- Part 11: Dial Access Specialized Features
- Part 12: Dial Access Scenarios
- Appendix
Table Of Contents
Requesting BRI Line and Switch Configuration from a Telco Service Provider
Dynamic Multiple Encapsulations
Interface Configuration Options
Configuring the ISDN BRI Switch
Checking and Setting the Buffers
Multiple ISDN Switch Types Feature
Specifying Interface Characteristics for an ISDN BRI
Specifying the Interface and Its IP Address
Configuring Encapsulation on ISDN BRI
Configuring Network Addressing
Configuring TEI Negotiation Timing
Configuring Called Party Number Verification
Configuring ISDN Calling Number Identification
Configuring the Line Speed for Calls Not ISDN End to End
Configuring a Fast Rollover Delay
Overriding ISDN Application Default Cause Codes
Configuring Inclusion of the Sending Complete Information Element
Configuring DNIS-plus-ISDN-Subaddress Binding
Screening Incoming V.110 Modem Calls
Configuring ISDN Semipermanent Connections
Configuring ISDN BRI for Leased-Line Service
Configuring Leased-Line Service at Normal Speeds
Configuring Leased-Line Service at 128 Kbps
Monitoring and Maintaining ISDN Interfaces
Troubleshooting ISDN Interfaces
Configuration Examples for ISDN BRI
Global ISDN and BRI Interface Switch Type Example
BRI Connected to a PBX Example
Multilink PPP on a BRI Interface Example
Multilink PPP and Compression Example
DNIS-plus-ISDN-Subaddress Binding Example
Screening Incoming V.110 Modem Calls Example
ISDN BRI Leased-Line Configuration Example
Feature Information for Configuring ISDN BRI
Configuring ISDN BRI
First Published: February 26, 2003Last Updated: May 14, 2009
This chapter describes tasks that are required to use an Integrated Services Digital Network (ISDN) Basic Rate Interface (BRI) line. It provides an overview of the ISDN technologies currently available and describes features that you can configure in an ISDN BRI circuit-switched internetworking environment. This information is included in the following main sections:
•
Monitoring and Maintaining ISDN Interfaces
•
•
This chapter describes configuration of the ISDN BRI. See Configuring ISDN PRI in the Cisco IOS Dial Configuration Guide for information about configuring the ISDN PRI.
This chapter does not address routing issues, dialer configuration, and dial backup. For information about those topics, see the chapters in the "Dial-on-Demand Routing Configuration" part of this publication.
For hardware technical descriptions and for information about installing the router interfaces, refer to the appropriate hardware installation and maintenance publication for your particular product.
To identify the hardware platform or software image information associated with a feature, use the Feature Navigator on Cisco.com to search for information about the feature or refer to the software release notes for a specific release. For more information, see the "Identifying Supported Platforms" section in the "Using Cisco IOS Software" chapter.
For a complete description of the BRI commands in this chapter, refer to the Cisco IOS Dial Technologies Command Reference. To locate documentation of other commands that appear in this chapter, use the command reference master index or search online.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for Configuring ISDN BRI" section.
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
Information about ISDN
Cisco IOS software supports both the ISDN BRI and the ISDN PRI.
ISDN BRI provides two bearer (B) channels, each capable of transferring voice or data at 64 kbps, and one 16 kbps data (D) signaling channel, which is used by the telephone network to carry instructions about how to handle each of the B channels. ISDN BRI (also referred to as 2 B + D) provides a maximum transmission speed of 128 kbps, but many users use only half the available bandwidth. This section covers the following topics:
•
Requesting BRI Line and Switch Configuration from a Telco Service Provider
Before configuring ISDN BRI on your Cisco router, you must order a correctly configured ISDN line from your telecommunications service provider. This process varies from provider to provider on a national and international basis. However, some general guidelines follow:
•
•
•
•
When you order ISDN service for switches used in North America, request the BRI switch configuration attributes specified in Table 1.
Interface Configuration
The Cisco IOS software also provides custom features for configuring the ISDN BRI interface that provide such capability as call screening, called party number verification, ISDN default cause code override, and for European and Australian customers, Dialed Number Identification Service (DNIS)-plus-ISDN-subaddress binding to allow multiple binds between a dialer profile and an ISDN B channel.
Dynamic Multiple Encapsulations
Before Cisco IOS Release 12.1, encapsulation techniques such as Frame Relay, High-Level Data Link Control (HDLC), Link Access Procedure, Balanced- Terminal Adapter (LAPB-TA), and X.25 could support only one ISDN B-channel connection over the entire link. HDLC and PPP could support multiple B channels, but the entire ISDN link needed to use the same encapsulation. The Dynamic Multiple Encapsulations feature introduced in Cisco IOS Release 12.1 allows various encapsulation types and per-user configurations on the same ISDN B channel at different times according to the type of incoming call.
With the Dynamic Multiple Encapsulations feature, once calling line identification (CLID) binding is completed, the topmost interface is always used for all configuration and data structures. The ISDN B channel becomes a forwarding device, and the configuration on the D channel is ignored, thereby allowing the different encapsulation types and per-user configurations. Dynamic multiple encapsulations provide support for packet assembler/disassembler (PAD) traffic and X.25 encapsulated and switched packets. For X.25 encapsulations, the configurations reside on the dialer profile.
Dynamic multiple encapsulation is especially important in Europe, where ISDN is relatively expensive and maximum use of all 30 B channels on the same ISDN link is desirable. Further, the feature removes the need to statically dedicate channels to a particular encapsulation and configuration type, and improves channel usage.
Figure 1 shows a typical configuration for an X.25 network in Europe. The Dynamic Multiple Encapsulations feature allows use of all 30 B channels, and supports calls that originate in diverse areas of the network and converge on the same ISDN PRI.
Figure 1 European X.25 Network
Interface Configuration Options
You can also optionally configure snapshot routing for ISDN interfaces. Snapshot routing is a method of learning remote routes dynamically and keeping the routes available for a specified period of time, even though routing updates are not exchanged during that period. See the chapter "Configuring Snapshot Routing" later in this guide for detailed information about snapshot routing.
To place calls on an ISDN interface, you must configure it with dial-on-demand routing (DDR). For configuration information about ISDN using DDR, see the "Dial-on-Demand Routing Configuration" part of this publication. For command information, refer to the Cisco IOS Dial Technologies Command Reference.
To configure bandwidth on demand, see the chapters "Configuring Legacy DDR Spokes" or "Configuring Legacy DDR Hubs" later in this publication.
ISDN Cause Codes
A cause code is an information element (IE) that indicates why an ISDN call failed or was otherwise disconnected. When the originating gateway receives a Release Complete message, it generates a tone corresponding to the cause code in the message.
Table 2 lists the default cause codes that the VoIP (Voice over IP) gateway sends to the switch when a call fails at the gateway, and the corresponding tones that it generates.
For a complete list of ISDN cause codes that are generated by the switch, refer to "Appendix B: ISDN Switch Types, Codes and Values" in the Cisco IOS Debug Command Reference.
Although the VoIP gateway generates the cause codes listed in Table 2 by default, there are commands introduced in previous Cisco IOS releases that can override these defaults, allowing the gateway to send different cause codes to the switch. The following commands override the default cause codes:
•
•
•
When you implement these commands, the configured cause codes are sent to the switch; otherwise, the default cause codes of the voice application are sent. For a complete description of these commands, refer to the Cisco IOS Dial Technologies Command Reference.
How to Configure ISDN BRI
To configure ISDN lines and interfaces, perform the tasks in the following sections:
•
•
•
•
See the sections Monitoring and Maintaining ISDN Interfaces and Troubleshooting ISDN Interfaces later in this chapter for tips on maintaining your network. See the section Configuration Examples for ISDN BRI at the end of this chapter for configuration examples.
To configure ISDN BRI for voice, video, and fax applications, refer to the Cisco IOS Voice, Video, and Fax Applications Configuration Guide.
Configuring the ISDN BRI Switch
To configure the ISDN switch type, perform the following tasks:
•
Also see to the Multiple ISDN Switch Types Feature section for information about configuring multiple switch types.
Configuring the Switch Type
The isdn switch-type command enables the router to configure the switch type.
SUMMARY STEPS
1.
2.
3.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
Router(config)# isdn switch-type switch-type
Selects the service provider switch type; see Table 1 for switch types.
The section Global ISDN and BRI Interface Switch Type Example provides an example of configuring the ISDN BRI switch.
Table 3 lists the ISDN BRI service provider switch types.
Note
Checking and Setting the Buffers
When configuring a BRI, after the system comes up, make sure enough buffers are in the free list of the buffer pool that matches the maximum transmission unit (MTU) of your BRI interface. If not, you must reconfigure buffers in order for the BRI interfaces to function properly.
The show interfaces bri and show buffers commands enables you to check the MTU size and the buffers.
SUMMARY STEPS
1.
2.
3.
DETAILED STEPS
To configure the buffers and the MTU size, use the following commands in global configuration mode as needed:
Configuring Buffers and MTU Size
The buffers big permanent, buffers big max-free, buffers big min-free, and buffers big initial commands enable the router to configure the buffers.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Multiple ISDN Switch Types Feature
The Cisco IOS software provides an enhanced Multiple ISDN Switch Types feature that allows you to apply an ISDN switch type to a specific ISDN interface and configure more than one ISDN switch type per router. This feature allows both ISDN BRI and ISDN PRI to run simultaneously on platforms that support both interface types.
Specifying Interface Characteristics for an ISDN BRI
Perform the tasks in the following sections to set interface characteristics for an ISDN BRI, whether it is the only BRI in a router or is one of many. Each of the BRIs can be configured separately.
•
•
•
•
•
Specifying the Interface and Its IP Address
The interface bri and ip address commands enables the router to enter interface configuration mode, and specify an ISDN BRI respectively.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Specifying ISDN SPIDs
Some service providers use SPIDs to define the services subscribed to by the ISDN device that is accessing the ISDN service provider. The service provider assigns the ISDN device one or more SPIDs when you first subscribe to the service. If you are using a service provider that requires SPIDs, your ISDN device cannot place or receive calls until it sends a valid, assigned SPID to the service provider when accessing the switch to initialize the connection.
Currently, only the DMS-100 and NI switch types require SPIDs. The AT&T 5ESS switch type may support a SPID, but we recommend that you set up that ISDN service without SPIDs. In addition, SPIDs have significance at the local access ISDN interface only. Remote routers never receive the SPID.
A SPID is usually a seven-digit telephone number with some optional numbers. However, service providers may use different numbering schemes. For the DMS-100 switch type, two SPIDs are assigned, one for each B channel.
The isdn spid1 and isdn spid2 commands enable the router to define the SPIDs and the local directory number (LDN) on the router.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
The LDN is optional but might be necessary if the router is to answer calls made to the second directory number.
Configuring Encapsulation on ISDN BRI
Each ISDN B channel is treated as a synchronous serial line, and the default serial encapsulation is HDLC. The Dynamic Multiple Encapsulations feature allows incoming calls over ISDN to be assigned an encapsulation type such as Frame Relay, PPP, and X.25 based on CLID or DNIS. PPP encapsulation is configured for most ISDN communication.
The encapsulation command enables the router to configure encapsulation.
SUMMARY STEPS
1.
2.
3.
DETAILED STEPS
Verifying the Dynamic Multiple Encapsulations Feature
To verify dialer interfaces configured for binding and see statistics on each physical interface bound to the dialer interface, use the show interfaces EXEC command.
The following example shows that the output under the B channel keeps all hardware counts that are not displayed under any logical or virtual access interface. The line in the report that states "Interface is bound to Dialer0 (Encapsulation LAPB)" indicates that this B interface is bound to the dialer 0 interface and the encapsulation running over this connection is LAPB, not PPP, which is the encapsulation configured on the D interface and inherited by the B channel.
Router# show interfaces bri0:1BRI0:1 is up, line protocol is upHardware is BRIMTU 1500 bytes, BW 64 Kbit, DLY 20000 usec, rely 255/255, load 1/255Encapsulation PPP, loopback not set, keepalive not setInterface is bound to Dialer0 (Encapsulation LAPB)LCP Open, multilink OpenLast input 00:00:31, output 00:00:03, output hang neverLast clearing of "show interface" counters neverQueueing strategy: fifoOutput queue 0/40, 0 drops; input queue 0/75, 0 drops5 minute input rate 0 bits/sec, 1 packets/sec5 minute output rate 0 bits/sec, 1 packets/sec110 packets input, 13994 bytes, 0 no bufferReceived 91 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort135 packets output, 14175 bytes, 0 underruns0 output errors, 0 collisions, 12 interface resets0 output buffer failures, 0 output buffers swapped out8 carrier transitionsAny protocol configuration and states should be displayed from the dialer 0 interface.
Encapsulation Configuration Notes
The router might need to communicate with devices that require a different encapsulation protocol or the router might send traffic over a Frame Relay or X.25 network. The Dynamic Multiple Encapsulations feature provides bidirectional support of all serial encapsulations except Frame Relay.
To configure the router for automatic detection of encapsulation type on incoming calls, or to configure encapsulation for Cisco 700 and 800 series (formerly Combinet) router compatibility, see the section "Configuring Automatic Detection of Encapsulation Type" in the chapter "Configuring ISDN Special Signaling" later in this publication.
Configuring Network Addressing
The dialer map, dialer-list, and access-list commands enable the router to configure network addressing, use the following commands beginning in interface configuration mode:
The steps in this section support the primary goals of network addressing:
•
•
•
•
Intermediate steps that use shared argument values tie the host identification and dial string to the interesting packets to be sent to that host.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
DETAILED STEPS
German networks allow semipermanent connections between customer routers with BRIs and the 1TR6 basic rate switches in the exchange. Semipermanent connections are less expensive than leased lines.
Note
For more information about defining outgoing call numbers, see the chapters "Configuring Legacy DDR Hubs" and "Configuring Legacy DDR Spokes" later in this publication.
Configuring TEI Negotiation Timing
The isdn tei command enables the router to apply TEI negotiation to a specific BRI interface.
You can configure ISDN TEI negotiation on individual ISDN interfaces. TEI negotiation is useful for switches that may deactivate Layers 1 or 2 when there are no active calls. Typically, this setting is used for ISDN service offerings in Europe and connections to DMS-100 switches that are designed to initiate TEI negotiation.
By default, TEI negotiation occurs when the router is powered up. The TEI negotiation value configured on an interface overrides the default or global TEI value. For example, if you configure isdn tei first-call globally and isdn tei powerup on BRI interface 0, then TEI negotiation powerup is the value applied to BRI interface 0. It is not necessary to configure TEI negotiation unless you wish to override the default value (isdn tei powerup).
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Configuring CLI Screening
The isdn caller command enables the router to configure CLI screening.
CLI screening adds a level of security by allowing you to screen incoming calls. You can verify that the calling line ID is from an expected origin. CLI screening requires a local switch that is capable of delivering the CLI to the router.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Note
Note
Configuring Called Party Number Verification
The isdn answer1 command allows the router to configure verification.
When multiple devices are attached to an ISDN BRI, you can ensure that only a single device answers an incoming call by verifying the number or subaddress in the incoming call against the configured number or subaddress or both of the device.
You can specify that the router verify a called-party number or subaddress number in the incoming setup message for ISDN BRI calls, if the number is delivered by the switch. You can do so by configuring the number that is allowed.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Verifying the called-party number ensures that only the desired router responds to an incoming call. If you want to allow an additional number for the router, you can configure it, too.
To configure a second number to be allowed, use the following command in interface configuration mode:
Configuring ISDN Calling Number Identification
A router with an ISDN BRI interface 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, this information is included in the outgoing call Setup message.
The isdn calling-number enables the router to configure the interface to identify the billing number.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
This command can be used with all switch types except German 1TR6 ISDN BRI switches.
Configuring the Line Speed for Calls Not ISDN End to End
When calls are made at 56 kbps but delivered by the ISDN network at 64 kbps, the incoming data can be corrupted. However, on ISDN calls, if the receiving side is informed that the call is not an ISDN call from end to end, it can set the line speed for the incoming call.
TThe isdn not-end-to-end command enables the router to set the speed for incoming calls recognized as not ISDN end to end.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Configuring a Fast Rollover Delay
Sometimes a router attempts to dial a call on an ISDN B channel before a previous call is completely torn down. The fast rollover fails because the second call is made to a different number before the B channel is released from the unsuccessful call. This failure might occur in the following ISDN configurations:
•
•
You need to configure this delay if a BRI on a remote peer has two phone numbers configured one for each B channel you are dialing into this BRI, you have a dialer map for each phone number, and the first call succeeds but a second call fails with no channel available.
The isdn fast-rollover-delay command enables the router to configure a fast rollover delay.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
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. This pattern of failed second calls is a rare occurrence.
Overriding ISDN Application Default Cause Codes
The ISDN Cause Code Override function is useful for overriding the default cause code of ISDN applications. When this feature is implemented, the configured cause code is sent to the switch; otherwise, default cause codes of the application are sent.
The isdn disconnect-cause command enables the router to configure ISDN cause code overrides.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
ISDN Cause Code Override Configuration Example
The following example sends a BUSY cause code to the switch when an application fails to complete the call:
interface serial 0:23isdn disconnect-cause busyVerifying ISDN Cause Code Override
To verify that the ISDN Cause Code Override feature is operating correctly, enter the debug q931 command. The debug q931 command displays a report of any configuration irregularities.
Configuring Inclusion of the Sending Complete Information Element
In some geographic locations, such as Hong Kong and Taiwan, ISDN switches require that the Sending Complete information element be included in the outgoing Setup message to indicate that the entire number is included. This information element is generally not required in other locations.
The isdn sending-complete command enables the router to configure the interface to include the Sending Complete information element in the outgoing call Setup message.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Configuring DNIS-plus-ISDN-Subaddress Binding
The dialer called command enables the router to configure DNIS-plus-ISDN-subaddress binding.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Note
See the section "DNIS-plus-ISDN-Subaddress Binding Example" later in this chapter for a configuration example.
Screening Incoming V.110 Modem Calls
You can screen incomingV.110 modem calls and reject calls that do not have the communications settings configured as the network expects them to be.
The isdn v10 only command enables the router to selectively accept incoming V.110 modem calls based on data bit, parity, and stop bit modem communications.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Disabling V.110 Padding
In networks with devices such as terminal adapters (TAs) and global system for mobile communication (GSM) handsets that do not fully conform to the V.110 modem standard, you will need to disable V.110 padding. The no isdn v10 padding command disables the padded V.110 modem speed report required by the V.110 modem standard.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Configuring ISDN Semipermanent Connections
German networks allow semipermanent connections between customer routers with BRI interfaces and the 1TR6 basic rate switches in the exchange. Australian networks allow semipermanent connections between ISDN PRI interfaces and the TS-014 primary rate switches in the exchange. Semipermanent connections are offered at better pricing than leased lines.
Configuring BRI interfaces for semipermanent connection requires only that you use a keyword that indicates semipermanent connections when you are setting up network addressing as described in the previous section of this chapter.
To configure a BRI for semipermanent connections, follow this procedure:
Step 1
Step 2
The dialer map command enables the router to begin DDR network addressing.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Configuring ISDN BRI for Leased-Line Service
To configure ISDN BRI for leased line service, perform the tasks in one of the following sections as needed and available:
•
•
Note
Configuring Leased-Line Service at Normal Speeds
This service is offered in Japan and Germany and no call setup or teardown is involved. Data is placed on the ISDN interface similar to the way data is placed on a leased line connected to a serial port.
The isdn switch-type, and the isdn leased-line bri commands enable the router to configure the BRI to use the ISDN connection as a leased-line service. The no form of the isdn leased-line bri command enables the router to remove the leased line configuration from a specified ISDN BRI interface.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Configuring Leased-Line Service at 128 Kbps
The Cisco IOS software supports leased-line service at 128 kbps via ISDN BR. This service combines two B channels into a single pipe. This feature requires one or more ISDN BRI hardware interfaces that support channel aggregation and service provider support for ISDN channel aggregation at 128 kbps. When this software first became available, service providers offered support for ISDN channel aggregation at 128 kbps only in Japan.
The isdn switch-type, and the isdn leased-line bri commands enable the router to configure the BRI to use the ISDN connection as a leased-line service at 128kbps.
Note
The no form of the isdn leased-line bri command enables the router to remove the leased line configuration from a specified ISDN BRI interface.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
To complete the configuration of the interface, see the chapter "Configure a Synchronous Serial Ports" in this publication.
To remove the leased-line service configuration from a specified ISDN BRI, use the following command in global configuration mode:
Monitoring and Maintaining ISDN Interfaces
The show interfaces, show controllers, show isdn, and the show dialer interface bri commands enable the router to monitor and maintain ISDN interfaces, use the following commands in EXEC mode as needed:
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Troubleshooting ISDN Interfaces
The following commands can help verify the ISDN configuration of the router:
•
•
•
•
•
•
Refer to the Cisco IOS Debug Command Reference for more information about the debug commands.
Configuration Examples for ISDN BRI
This section provides the following ISDN BRI configuration examples:
•
•
•
•
•
•
•
•
•
•
Global ISDN and BRI Interface Switch Type Example
The following example shows a global National ISDN switch type (keyword basic-ni) and an interface-level NET3 ISDN switch type (keyword basic-net3). The basic-net3 keyword is applied to BRI interface 0 and overrides the global switch setting.
isdn switch-type basic-ni
!
interface BRI0
isdn switch-type basic-net3BRI Connected to a PBX Example
The following example provides a simple partial configuration of a BRI interface that is connected to a PBX. This interface is connected to a switch that uses SPID numbers.
interface BRI0description connected to pbx line 61885ip address 10.1.1.3 255.255.255.0encapsulation pppisdn spid1 123dialer map ip 10.1.1.1 name mutter 61886dialer map ip 10.1.1.2 name rudder 61884dialer map ip 10.1.1.4 name flutter 61888dialer-group 1no fair-queueppp authentication chapMultilink PPP on a BRI Interface Example
The following example enables Multilink PPP on BRI 0:
interface BRI0description Enables PPP Multilink on BRI 0ip address 10.1.1.1 255.255.255.0encapsulation pppdialer map ip 10.1.1.2 name coaster 14195291357dialer map ip 10.1.1.3 name roaster speed 56 14098759854ppp authentication chapppp multilinkdialer-group 1Dialer Rotary Groups Example
The following example configures BRI interfaces to connect into a rotary group (using the dialer-group command) and then configures a dialer interface for that dialer group. This configuration permits IP packets to trigger calls.
interface BRI 0description connected into a rotary groupencapsulation pppdialer rotary-group 1interface BRI 1no ip addressencapsulation pppdialer rotary-group 1interface BRI 2encapsulation pppdialer rotary-group 1interface BRI 3no ip addressencapsulation pppdialer rotary-group 1interface BRI 4encapsulation pppdialer rotary-group 1interface Dialer 0description Dialer group controlling the BRIsip address 10.1.1.1 255.255.255.0encapsulation pppdialer map ip 10.1.1.2 name angus 14802616900dialer-group 1ppp authentication chapdialer-list 1 protocol ip permitCompression Examples
The following example enables predictor compression on BRI 0:
interface BRI0description Enables predictor compression on BRI 0ip address 10.1.1.1 255.255.255.0encapsulation pppdialer map ip 10.1.1.2 name bon 14195291357compress predictorppp authentication chapdialer-group 1The following example enables stacker compression on BRI 0:
interface BRI0description Enables stac compression on BRI 0ip address 10.1.1.1 255.255.255.0encapsulation pppdialer map ip 10.1.1.2 name malcom 14195291357compress stacppp authentication chapdialer-group 1Multilink PPP and Compression Example
The following example enables Multilink PPP and stacker compression on BRI 0:
interface BRI0description Enables PPP Multilink and stac compression on BRI 0ip address 10.1.1.1 255.255.255.0encapsulation pppdialer map ip 10.1.1.2 name rudd 14195291357ppp authentication chapcompress stacppp multilinkdialer-group 1Voice over ISDN Examples
The following example allows incoming voice calls to be answered on BRI 0:
interface bri0description Allows incoming voice calls to be answered on BRI 0ip address 10.1.1.1 255.255.255.0encapsulation pppisdn incoming-voice datadialer map ip 10.1.1.2 name starstruck 14038182344ppp authentication chapdialer-group 1The following example allows outgoing voice calls on BRI 1:
interface bri1description Places an outgoing call as a voice call on BRI 1ip address 10.1.1.1 255.255.255.0encapsulation pppdialer map ip 10.1.1.2 name angus class calltype 19091238877ppp authentication chapdialer-group 1map-class dialer calltypedialer voice-callFor more configuration examples of voice calls over ISDN, refer to the Cisco IOS Voice, Video, and Fax Configuration Guide.
DNIS-plus-ISDN-Subaddress Binding Example
The following example configures a dialer profile for a receiver with DNIS 12345 and ISDN subaddress 6789:
dialer called 12345:6789For additional configuration examples, see the sections "Dynamic Multiple Encapsulations" and "Verifying the Dynamic Multiple Encapsulations Feature" in the chapter "Configuring Peer-to-Peer DDR with Dialer Profiles" in this publication.
Screening Incoming V.110 Modem Calls Example
The following example filters out all V.110 modem calls except those with communication settings of 8 data bits, no parity bit, and 1 stop bit:
interface serial 0:23isdn v110 only databits 8 parity none stopbits 1
ISDN BRI Leased-Line Configuration Example
The following example configures the BRI 0 interface for leased-line access at 128 kbps. Because of the leased-line-not dialed-environment, configuration of ISDN called and calling numbers are not needed and not used. The BRI 0 interface is henceforth treated as a synchronous serial interface, with the default HDLC encapsulation.
isdn leased-line bri 0 128Additional References
The following sections provide references related to the Modem Signal and Line State feature.
Related Documents
Standards
MIBs
•
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
RFCs
Technical Assistance
Feature Information for Configuring ISDN BRI
Table 4 lists the release history for this feature.
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Pulse, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, and Flip Gift Card are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Fast Step, Follow Me Browsing, FormShare, GainMaker, GigaDrive, HomeLink, iLYNX, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0908R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2003—2009 Cisco Systems, Inc. All rights reserved.
