-
Cisco IOS Dial Technologies Command Reference, Release 12.3 T
-
Introduction
-
Dial Technologies Commands: A through cas-group
-
Dial Technologies Commands: channel through cpp
-
Dial Technologies Commands: debounce through dial-tdm
-
Dial Technologies Commands: disconnect through group
-
Dial Technologies Commands: initiate through ipx
-
Dial Technologies Commands: isdn through isdn x25
-
Dial Technologies Commands: L
-
Dial Technologies Commands: M
-
Dial Technologies Commands: name through pptp
-
Dial Technologies Commands: pri through rotary
-
Dial Technologies Commands: script through show dial
-
Dial Technologies Commands: show dsc through show line
-
Dial Technologies Commands: show modem through show nbf
-
Dial Technologies Commands: show port through show resource
-
Dial Technologies Commands: show sessions through show vtemplate
-
Dial Technologies Commands: shutdown through x25 map
-
Table Of Contents
isdn bcac service audit interface
isdn bcac service audit trigger
isdn bcac service retry in-serv-on-fail
isdn bcac service update linkup
isdn bcac service update provision
isdn channel-id invert extended-bit
isdn outgoing ie redirecting-number
isdn overlap-receiving calltypes all
isdn tei-negotiation (interface)
isdn test disconnect interface
isdn all-incoming-calls-v120
To configure an ISDN BRI or PRI interface to answer all incoming calls as V.120 when the terminal adapter uses V.120 signaling but does not send the Lower-Layer Compatibility field in Setup messages, use the isdn all-incoming-calls-v120 command in interface configuration mode. To remove this configuration, use the no form of the command.
isdn all-incoming-calls-v120
no isdn all-incoming-calls-v120
Syntax Description
This command has no arguments or keywords.
Defaults
By default, ISDN interfaces answer calls as synchronous serial with PPP encapsulation.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use this command only when you want all incoming calls to be answered as V.120. If you want the interface to automatically detect whether the incoming call uses V.120 or PPP encapsulation, use the autodetect encapsulation command.
This command applies only when the incoming call originates on an asynchronous device and needs to terminate in an available vty on the router.
Examples
The following partial example shows that BRI 0 is configured to answer all calls as V.120:
interface bri 0isdn all-incoming-calls-v120Related Commands
autodetect encapsulation
Enables automatic detection of the encapsulation types in operation over a point-to-point link to a specified serial or ISDN interface.
isdn answer1, isdn answer2
To have 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, use the isdn answer1 command in interface configuration mode. 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 BRI calls, if the number is delivered by the switch, use the isdn answer2 command in interface configuration mode. 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
Defaults
The router does not verify the called party or subaddress number.
Command Modes
Interface configuration
Command History
Usage Guidelines
If you do not specify the isdn answer1 or isdn answer2 command, all calls are processed 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 configuring it as an x or X. In such a case, any incoming digit is allowed.
Examples
In the following example, 5552222 is the called-party number and 1234 is the subaddress:
interface bri 0isdn answer1 5552222:1234In the following example, only the subaddress is configured:
interface bri 0isdn answer1 :1234isdn autodetect
To enable the automatic detection of ISDN SPIDs and switch type, use the isdn autodetect command in interface configuration mode. To disable the automatic detection of ISDN SPIDs and switch type, use the no form of this command.
isdn autodetect
no isdn autodetect
Syntax Description
This command has no arguments or keywords.
Defaults
The automatic detection of ISDN SPIDs and switch type is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies to North America only. If you are outside of North America, you must use the isdn switch-type (BRI) or isdn switch-type (PRI) interface configuration command to specify the ISDN switch type.
Examples
The following example enables the automatic detection of ISDN SPIDs and switch type:
isdn autodetectRelated Commands
isdn bcac service audit
To enable service audits on an interface configured for B-Channel Availability Control (BCAC), use the isdn bcac service audit command in interface configuration mode. To disable service audits, use the no form of this command.
isdn bcac service audit
no isdn bcac service audit
Syntax Description
This command has no arguments or keywords.
Defaults
This command is disabled by default.
Command Modes
Interface configuration
Command History
Usage Guidelines
This commands starts service audits for all triggers. Use the isdn bcac service audit trigger command to selectively enable and disable audit triggers.
Examples
The following example shows how to configure service audits on serial interface 2:23:
interface serial 2:23isdn bcac service auditRelated Commands
isdn bcac service audit interface
To specify that B-Channel Availability Control (BCAC) service audit needs to be triggered on the entire interface, use the isdn bcac service audit interface command in interface configuration mode. To change or remove the specification, use the no form of this command.
isdn bcac service audit interface
no isdn bcac service audit interface
Syntax Description
This command has no arguments or keywords.
Defaults
The default can be to trigger audits on a single channel, a group of channels, or the entire interface, depending upon the type of trigger set. See the "Usage Guidelines" section for the isdn bcac service audit trigger command for the list of triggers.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use this command when the service audit needs to be triggered on the entire interface when a condition to trigger the service audit is triggered for any channel.
Examples
The following example shows how to configure service audits on serial interface 2:23:
interface serial 2:23isdn bcac service audit interfaceRelated Commands
isdn bcac service audit trigger
To re-enable individual B-Channel Availability Control (BCAC) service triggers, use the isdn bcac service audit trigger command in interface configuration mode. To disable individual service triggers, use the no form of this command.
isdn bcac service audit trigger number
no isdn bcac service audit trigger number
Syntax Description
number
A number from 1 to 6 that disables specific service triggers; see a list of these triggers in the "Usage Guidelines" section.
Defaults
All triggers are configured.
Command Modes
Interface configuration
Command History
Usage Guidelines
The service audit procedure can be used by the either the user or network side to bring both ends of the interface into agreement about the service status through an exchange of SERV and SERV ACK messages.
Following is the list of triggers with the conditions that cause them. Triggers 1 through 4 are triggered by single-channel audits. Trigger 5 occurs on the entire interface. Trigger 6 applies to a group of channels, which in some cases may apply to the entire interface.
•
Trigger 1: Upon receiving an incoming call indicating a channel that is in the out-of-service (OOS) or Maint (maintenance) state.
•
•
•
•
•
Examples
The following example shows how to disable service trigger 4 on serial interface 2:23:
interface serial 2:23no isdn bcac service audit trigger 4Related Commands
isdn bcac service retry in-serv-on-fail
To specify that the B-Channel Availability Control (BCAC) service state of the channel needs to be changed to In Service because no acknowledgment was received, use the isdn bcac service retry in-serv-on-fail command in interface configuration mode. To change or remove this specification, use the no form of this command.
isdn bcac service retry in-serv-on-fail
no isdn bcac service retry in-serv-on-fail
Syntax Description
This command has no arguments or keywords.
Defaults
Original service state is maintained.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use this command when there is a need to change the service state of a channel to In Service when no acknowledgment is received, even after retransmitting the service message the maximum number of allowed times. If this command is not configured, the original service state is maintained.
Examples
The following example shows how to configure an option whereby, on service message exchange failure, the service state of the concerned channel or channels will be set to In Service:
interface serial 2:23isdn bcac service retry in-serv-on-failRelated Commands
isdn bcac service retry max
To specify the maximum number of times a B-Channel Availability Control (BCAC) service message can be retransmitted when unacknowledged, use the isdn bcac service retry max command in interface configuration mode. To remove or change the specification, use the no form of this command.
isdn bcac service retry max retries
no isdn bcac service retry max retries
Syntax Description
retries
A number from 0 to 127 that determines the maximum number of times that a service message can be retransmitted when unacknowledged. Default is 2.
Defaults
Maximum retransmissions is 2.
Command Modes
Interface configuration
Command History
Usage Guidelines
When a SERV message is sent to the far side, SERV message timer T3M1 or T323 is started. If no SERV ACK message is received before these timers expire, the SERV message is retransmitted. This command determines how many times retransmission occurs.
Examples
The following example shows how to set the maximum service message retransmissions on serial interface 2:23 to 50:
interface serial 2:23isdn bcac service retry max 50Related Commands
isdn bcac service timer
To change the value of the B-Channel Availability Control (BCAC) T3M1 or T323 service message timer, use the isdn bcac service timer command in interface configuration mode. To change the timer value, use the no form of this command.
isdn bcac service timer timer-value
no isdn bcac service timer timer-value
Syntax Description
timer-value
Length, in milliseconds (ms), of the T3M1 or T323 service message timer. Valid range is from 500 to 120000 ms; default is 120000 ms.
Defaults
The T3M1 or T323 service message timer defaults to 120000 ms.
Command Modes
Interface configuration
Command History
Usage Guidelines
The T3M1 or T323 service message timer is started when a SERV message is sent to the far side.
Examples
The following example shows how to change the service timers to 600 ms on serial interface 2:23:
interface serial 2:23isdn bcac service timer 600Related Commands
isdn bcac service update linkup
To trigger updates of the B-Channel Availability Control (BCAC) service states between peer nodes through exchange of SERV and SERV ACK messages, use the isdn bcac service update linkup command in interface configuration mode. To disable triggering of updates, use the no form of this command.
isdn bcac service update linkup
no isdn bcac service update linkup
Syntax Description
This command has no arguments or keywords.
Defaults
This command is disabled by default.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command updates the service states of all the channels to the far side of the interface by exchanging SERV and SERV ACK messages whenever ISDN Layer 2 comes up.
Use the isdn bcac service update linkup command to bring the service state of the channels on the interface in synchronization with its peer through the exchange of SERV messages. This synchronizing of the service states will be triggered whenever ISDN Layer 2 comes up. This command can be used with the isdn service command in cases where the service state of the channels needs to be synchronized when the ISDN Layer 2 comes up, and in particular, when the ISDN Layer 2 comes up after the router has reloaded.
Examples
The following example shows how to trigger service state updates on serial interface 2:23:
interface serial 2:23isdn bcac service update linkupRelated Commands
isdn bcac service update provision
To enable functionality of service status for provisioning the ISDN B channels, use the isdn bcac service update provision command in interface configuration mode. To disable provisioning, use the no form of this command.
isdn bcac service update provision
no isdn bcac service update provision
Syntax Description
This command has no arguments or keywords.
Defaults
This command is disabled by default.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command enables functionality of service status for provisioning the B channels, which for the Cisco implementation happens only on reboot.
Examples
The following example shows how to enable the service service status for provisioning the B channels on serial interface 2:23:
interface serial 2:23isdn bcac service update provisionRelated Commands
isdn bchan-number-order
To configure an ISDN PRI interface to make outgoing call selection in ascending descending, or round-robin order, use the isdn bchan-number-order command in interface configuration mode. To restore the default, use the no form of this command or reconfigure the interface with the new value.
isdn bchan-number-order {ascending | descending} [round-robin]
no isdn bchan-number-order
Syntax Description
Defaults
Selection default is ascending for the network side; descending for the user side.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command supports ascending, descending, and round-robin B-channel selection schemes. This command is for PRI configuration only.
This command supports ascending and descending B-channel selection by instructing 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 B31 for an E1 (descending).
In the ascending B-channel selection scheme, for example, if the channel selected for the last call was channel 14, then if channel x, where x is any channel number less than or equal to 14, becomes available by the time a channel is selected for the next call, that channel will be selected for the call.
In the round-robin B-channel selection scheme, the next channel selected is the current channel number x plus 1 for ascending, or current channel number x minus 1 for descending configuration.
When the channel selection software routine reaches channel 1 (the bottom for descending) or channel 23 for T1 and channel 31 for E1 (the top for ascending), the software routine wraps around. An example for a descending configuration: After reaching channel 1, the routine goes back to channel 31 or 23 and then decrements the count from there.
Examples
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 serial 5:10 isdn bchan-number-order ascendingThe following example configures the outgoing B-channel order on a PRI interface to be round-robin in ascending order.
interface serial 4:23 isdn bchan-number-order ascending round-robinisdn busy
To set a false busy signal on an ISDN B channel, use the isdn busy command in interface configuration mode. To remove this condition, use the no form of this command.
isdn busy dsl number b_channel number
no isdn busy dsl number b_channel number
Syntax Description
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
This command gives the impression that a call is active when the channel is actually idle.
Use the b_channel 0 keywords to set a false busy signal on the entire interface.
Use the show isdn command with the status keyword to display the DSL number and channel state.
Examples
The following example sets the entire PRI interface to a false busy signal; the DSL number was obtained using the show isdn command with the status keyword, and then used in the command.
isdn busy dsl 3 b_channel 0 state 1The following example sets the false busy signal on B channel 11; the DSL number was obtained using the show isdn command with the status keyword, and then used in the command.
isdn busy dsl 3 b_channel 11 state 2Related Commands
isdn service
Takes an individual B channel or an entire PRI interface out of service or sets it to a different channel service state that is passed in to the switch.
isdn call interface
The isdn call interface command is replaced by the isdn test call interface command. See the isdn test call interface command for more information.
isdn caller
To configure ISDN caller ID screening and optionally to enable ISDN caller ID callback for legacy dial-on-demand routing (DDR), use the isdn caller command in interface configuration mode. To disable this feature, use the no form of this command.
isdn caller phone-number [callback] [exact]
no isdn caller phone-number [callback] [exact]
Syntax Description
Defaults
Disabled
Command Modes
Interface configuration
Command History
10.0
This command was introduced.
11.2 F
This command was implemented on additional Cisco router and access server platforms.
12.1
The exact keyword was added.
Usage Guidelines
This command configures the router to accept calls from the specified number.
Note
When the optional callback keyword is used and a call is received from one of the callback numbers, the initial call is rejected (hence, not subject to tolls) and a callback is initiated to that calling number.
When Xs are used in the callback number, dialer caller screening is based on a best match system that uses the number of Xs as a criterion. To make callback calls only to specified numbers or ranges of numbers but to accept any other incoming calls, make sure that the number of Xs in any configuration line that uses the callback keyword is less than the number of Xs in any configuration line that does not use the keyword.
For example, if you use at most four Xs in the configuration lines with the callback keyword, then to accept calls from other numbers use at least five Xs in a configuration line that does not use the keyword.
When a telephone number is entered without the exact keyword, the software compares each number going from right to left until matching numbers are detected. For example, if the phone-number argument is 4085551234, calls from telephone numbers 1234, 51234, 5551234, and 4085551234 would be accepted, but calls from telephone numbers 44 and 4155551234 would be rejected.
If you want to accept a telephone number exactly as it is configured, enter it with the exact keyword. For example, if the phone-number argument is 5551212 and the exact keyword is applied, only the telephone number 5551212 is accepted; calls from telephone numbers 408551212 and 51212 would be rejected.
The maximum length of each telephone number is 25 characters. There is no limit on the numbers you can specify per interface.
Examples
The following example configures the router to accept a call containing the numbers 415 555-1234:
isdn caller 4155551234The following example configures the router to accept a call only from telephone number 555-1234:
isdn caller 5551234 exactIn the above example, a call from telephone number 415 555-1234 would be rejected.
The following example configures the router to accept a call with telephone number containing 415 555-12 and any numbers in the last two positions:
isdn caller 41555512xxIn the following example, callback calls will be made only to numbers in the 555 and 556 exchanges, but any other telephone number can call in:
isdn caller 408555xxxx callbackisdn caller 408556xxxx callbackisdn caller xxxxxRelated Commands
show dialer
Displays general diagnostic information for interfaces configured for DDR.
isdn calling-number
To configure an ISDN PRI or BRI interface to present the number of the device making the outgoing call, use the isdn calling-number command in interface configuration mode. To remove a previously configured calling number, use the no form of this command.
isdn calling-number calling-number
no isdn calling-number
Syntax Description
Defaults
No calling number is presented.
Command Modes
Interface configuration
Command History
Usage Guidelines
An interface can have only one ISDN calling-number entry.
For ISDN BRI, this command is intended for use when the ISDN network offers TS014 tariffing, in which devices present the calling (billing) number.
For ISDN PRI, 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
Examples
The following example first configures the T1 interface, then configures the 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 10.1.1.1 255.255.255.0encapsulation pppisdn calling-number 4233570925dialer map ip 10.1.1.2 name dallas 14193460913In the following example, the ISDN BRI interface is configured to present the number 5551212 when it makes outgoing calls:
interface bri 0isdn calling-number 5551212Related Commands
isdn calling-pty
To specify whether the network-provided or user-provided calling party number is selected when two calling party numbers are sent from a primary NET5 switch on ISDN, use the isdn calling-pty command in interface configuration mode. To reset the default value, use the no form of this command.
isdn calling-pty {network-provided | user-provided}
no isdn calling-pty
Syntax Description
network-provided
Network-provided calling party number.
user-provided
User-provided calling party number.
Defaults
User-provided calling party number
Command Modes
Interface configuration
Command History
Usage Guidelines
The isdn calling-pty command is useful for customers that use network-provided and user-provided calling party numbers for accounting purposes. The selected number will be used by dialer filters such as that configured with the isdn caller command.
Examples
The following example configures the ISDN switch to accept network-provided calling party numbers:
interface Serial0:23no ip addressencapsulation pppdialer rotary-group 1isdn switch-type primary-net5isdn protocol-emulate networkisdn incoming-voice modemisdn calling-number 1111111isdn calling-pty network-providedisdn T310 40000no cdp enableRelated Commands
isdn channel-id invert extended-bit
To invert the value of the extend bit (0x80) in the last octet of the channel ID information element, use the isdn channel-id invert extended-bit command in interface configuration mode. To restore the default setting, use the no form of this command.
isdn channel-id invert extended-bit
no isdn channel-id invert extended-bit
Syntax Description
This command has no arguments or keywords.
Defaults
The last octet of the channel ID information element is not inverted.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use this command if you use a primary-DMS 100 switch type to ensure compatibility with a Setup or Call Proceeding message containing a channel ID information element. This command can be used only with ISDN PRI.
This command replaces the isdn-flip-chan-flag command.
Examples
The following example configures the router to invert the extended bit in the last octet of the channel ID information element:
isdn channel-id invert extended-bitisdn conference-code
To activate three-way call conferencing, use the isdn conference-code command in interface configuration mode. To disable three-way call conferencing, use the no form of this command.
isdn conference-code range
no isdn conference-code
Syntax Description
Defaults
The default code is 60.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use this command if your ISDN line is connected to an NI1 or a Nortel DMS-100 Custom switch. Your telephone service provider should provide an ISDN conference code when you order three-way call conferencing.
Examples
The following example specifies 61 as the ISDN conference code:
isdn conference-code 61isdn disconnect-cause
To send a specific ISDN cause code to the switch, use the isdn disconnect-cause command in interface configuration mode. To return to the default condition, use the no form of this command.
isdn disconnect-cause {cause-code-number | busy | not-available}
no isdn disconnect-cause
Syntax Description
Defaults
The default condition is no cause code override. If the isdn disconnect-cause command is not configured, the default cause codes for the application are sent.
Command Modes
Interface configuration
Command History
Usage Guidelines
The isdn disconnect-cause command overrides specific cause codes (such as modem availability and resource pooling) that are sent to the switch by ISDN applications. When the isdn disconnect-cause command is implemented, the configured cause codes are sent to the switch; otherwise, the default cause codes for the application are sent. ISDN protocol errors are still reflected in the cause codes and are not overridden.
Examples
The following example sends the CHANNEL-NOT-AVAILABLE code to the ISDN switch:
interface serial0:20 isdn disconnect-cause not-availableRelated Commands
isdn disconnect interface
The isdn disconnect interface command is replaced by the isdn test disconnect interface command. See the isdn test disconnect interface command for more information.
isdn fast-rollover-delay
To control the timing between successive dial attempts, use the isdn fast-rollover-delay command in interface configuration mode. To remove or change a value, use the no form of this command.
isdn fast-rollover-delay seconds
no isdn fast-rollover-delay
Syntax Description
Defaults
No default timer.
Command Modes
Interface configuration
Command History
Usage Guidelines
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.
The isdn fast-rollover-delay command is necessary on some ISDN switches because the new call may be attempted before the old call is completely torn down, which causes the second call or the callback to fail.
Use this command when all the following conditions are true:
•
•
•
•
When these conditions occur, set the isdn fast-rollover-delay command to 5 seconds and try again. A delay of 5 seconds should cover most cases. Configure sufficient delay to make sure that the ISDN RELEASE_COMPLETE message has been sent or received before the fast rollover call is made. Use the debug isdn q931 command to display this information.
When the isdn fast-rollover-delay command is configured on a client requesting callback, the callback client first confirms whether the callback server has placed a call back to the callback client before dialing any subsequent numbers.
Examples
The following partial example sets the fast-rollover delay that is suggested when all the conditions specified in the list in the "Usage Guidelines" are true:
isdn fast-rollover-delay 5Related Commands
isdn flip-chan-flag
The isdn flip-chan-flag command is replaced by the isdn channel-id invert extended-bit command. See the isdn channel-id invert extended-bit command for more information.
isdn guard-timer
To enable a managed timer for authentication requests, use the isdn guard-timer command in interface configuration mode. To reset the timer to its default value, use the no form of this command.
isdn guard-timer milliseconds [on-expiry {accept | reject}]
no isdn guard-timer
Syntax Description
Defaults
The default timer value is eight (8) seconds and calls are rejected when the timer expires.
Command Modes
Interface configuration
Command History
Usage Guidelines
The guard-timer starts when the DNIS number is sent to AAA for authentication. When the timer expires, authentication ends and the call is accepted or rejected based on the configured expiry action.
Examples
The following example sets the guard-timer to six (6) seconds and specifies that the call should be rejected if AAA does not respond within that interval:
interface serial 1/0/0:23isdn guard-timer 6000 on-expiry rejectRelated Commands
isdn incoming alerting add-PI
To add a Progress Indicator (PI) in an incoming ALERTING messages during ISDN B-channel cut-through, use the isdn incoming alerting add-PI command in interface configuration mode. To remove the indicator, use the no form of this command.
isdn incoming alerting add-PI
no isdn incoming alerting add-PI
Syntax Description
This command has no arguments or keywords.
Defaults
On North American ISDN switches, the default behavior is to add the PI in incoming ALERTING messages. On ISDN switches compliant with the European Telecommunications Standards Institute (ETSI), the default behavior is to not add the PI in incoming ALERTING messages.
Command Modes
Interface configuration
Command History
Usage Guidelines
The isdn incoming alerting add-PI and no isdn incoming alerting add-PI commands provide a way for switch types conforming to different standards to handle B-channel cut-through. These commands apply to both ISDN BRI and PRI connections.
North American switch types such as the 5ESS, 4ESS, DMS, and NI allow cut-through when an ALERTING message is received. ISDN B-channel cut-through for customer premises equipment (CPE) should happen upon receipt of a channel ID Information Element (IE) in the CALL_PROC message. For this reason, the default on North American ISDN switches is to add the PI in incoming ALERTING message.
On ETSI-compliant ISDN switches, the default behavior is to not add the PI in incoming ALERTING messages. But ETSI also specifies that when the remote device is playing tones or announcements, it should also include the PI in the ALERTING message. This is not the default behavior for ETSI-compliant switches, but the isdn incoming alerting add-PI command allows Cisco IOS software to support this behavior.
The isdn incoming alerting add-PI and no isdn incoming alerting add-PI commands can be used on switches that do not want to add the PI in incoming ALERTING messages and on those switches that cannot handle or do not want the PI in incoming ALERTING messages.
Examples
Because the the isdn incoming alerting add-PI command is the default for a North American ISDN switch, the following example shows that when the interface configuration is displayed, the isdn incoming alerting add-PI command is not listed, even if it was explicitly configured:
Router(config)# interface BRI1/0Router(config-if)# no ip addressRouter(config-if)# isdn switch-type basic-dms100Router(config-if)# isdn spid1 40876726760101 5459374Router(config-if)# isdn spid2 51076726760101 5459375Router(config-if)# isdn incoming-voice voiceRouter(config-if)# isdn incoming alerting add-PIRouter(config-if)# endRouter(config)# endRouter# show running interface BRI1/0Building configuration...Current configuration : 167 bytes!interface BRI1/0no ip addressisdn switch-type basic-dms100isdn spid1 40876726760101 5459374isdn spid2 51076726760101 5459375isdn incoming-voice voiceendThe following example shows that when the the no isdn incoming alerting add-PI command is configured on a North American ISDN switch, the command is listed in the interface configuration:
Router(config)# interface BRI1/0Router(config-if)# no isdn incoming alerting add-PIRouter(config-if)# endRouter(config)# endRouter# show running interface BRI1/0Building configuration...Current configuration : 201 bytes!interface BRI1/0no ip addressisdn switch-type basic-dms100isdn spid1 4087672676 5459374isdn spid2 51076726760101 5459375isdn incoming-voice voiceno isdn incoming alerting add-PIendBecause the default for ETSI-compliant ISDN switches is no isdn incoming alerting add-PI, the following example shows that when the the isdn incoming alerting add-PI command is added to the configuration for a NET3 switch, the command is listed in the interface configuration:
Router(config-if)# no ip addressRouter(config-if)# isdn switch-type basic-net3Router(config-if)# isdn spid1 40876726760101 5459374Router(config-if)# isdn spid2 51076726760101 5459375Router(config-if)# isdn incoming-voice voiceRouter(config-if)# isdn incoming alerting add-PIRouter(config-if)# endRouter(config)# endRouter# show running interface BRI1/0Building configuration...Current configuration : 165 bytes!interface BRI1/0no ip addressisdn switch-type basic-net3isdn spid1 40876726760101 5459374isdn spid2 51076726760101 5459375isdn incoming-voice voiceisdn incoming alerting add-PIendIf the configuration for the NET3 switch were changed back to contain no isdn incoming alerting add-PI, the command would not be listed in the interface configuration, because this is the default behavior for ETSI-compliant switches:
Current configuration : 165 bytes!interface BRI1/0no ip addressisdn switch-type basic-net3isdn spid1 40876726760101 5459374isdn spid2 51076726760101 5459375isdn incoming-voice voiceendisdn incoming-voice
To route all incoming voice calls to the modem and determine how they will be treated, use the isdn incoming-voice command in interface configuration mode. To disable the setting or return to the default, use the no form of this command.
isdn incoming-voice {voice | data [56 | 64] | modem [56 | 64]}
no isdn incoming-voice {voice | data [56 | 64] | modem [56 | 64]}
Syntax Description
Defaults
If you do not enter the 56 or 64 keywords after the data keyword, the default value will be 64 kbps.
Command Modes
Interface configuration
Command History
Usage Guidelines
Unless you specify otherwise, all calls received by the router and characterized as voice calls are treated as normal ISDN calls, which are handled as digital data and not passed over to the modem. 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.
If you use the voice keyword, incoming ISDN voice calls will be treated as voice calls and handled by either a modem or a voice DSP as directed by CSM.
If the default value is configured and the bearer capability of the incoming call is the voice keyword, the call will be rejected.
To answer incoming voice calls at a configured rate (overriding the incoming data rate in the call), use the data keyword.
To establish speedier connections for analog calls to the router, use the isdn incoming-voice command with the modem keyword to have voice calls routed through digital modems (as pulse-code modulated analog data) instead of being treated as digital data.
Configure this command on each D channel in the access server or router. Incoming circuit-switched data calls are not affected by this command.
Note
Examples
The following example designates incoming ISDN voice calls to be treated as voice calls:
interface 10isdn incoming-voice voiceThe following 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 56The following example routes all incoming voice calls through the modem as analog data:
interface BRI 0/0isdn incoming-voice modemThe 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 modemisdn layer1-emulate
To configure the Layer 1 operation of a BRI voice port as clock master (NT) or slave (TE), use the isdn layer1-emulate command in interface configuration mode. To restore the default (user), use the no form of this command.
isdn layer1-emulate {user | network}
no isdn layer1-emulate
Syntax Description
user
Physical interface operation in clock slave mode (as TE).
network
Physical interface operation in clock master mode (as NT).
Defaults
Layer 1 port operation is as user (TE functionality as clock slave).
Command Modes
Interface configuration
Command History
12.0(3)XG
This command was introduced on the MC3810.
12.1(3)XI
This command was implemented on the Cisco 2600 and Cisco 3600 series.
Usage Guidelines
If you use the no isdn layer1-emulate network command, the physical layer port operation defaults to user.
Examples
The following example configures the Layer 1 operation of a BRI voice port as QSIG clock slave (TE):
configure terminalinterface bri 1isdn layer1-emulate userRelated Commands
isdn leased-line bri
To configure an ISDN BRI for leased-line service, or to configure both 64-kbps leased-line and ISDN service on the same BRI, use the isdn leased-line bri command in global configuration mode. To remove or change channel configurations, use the no form of this command.
isdn leased-line bri number/number [b1 | b2 | 128 | 144 | Return-key]
no isdn leased-line bri number/number [b1 | b2 | 128 | 144 | Return-key]
Syntax Description
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
Use the isdn leased-line bri command to configure an ISDN BRI for leased-line service by aggregating two BRI B channels into a single pipe at a speed of 128 or 144 kbps, or configuring both a 64-kbps leased line and ISDN service on a single European Telecommunications Standards Institute (ETSI) NET3 switch on Cisco 800 series routers.
This command also supports two separate 64-kbps leased lines, where the BRI interface is configured as two separate leased lines instead of two B channels. No keyword is required for this configuration; just press the Return or Enter key at the end of the isdn leased-line bri number/number command string. This configuration is different than using the 128 keyword, which configures a single 128-kbps leased line.
When you use the no isdn leased-line bri command to change the channel configuration, you must also perform a system reload in order for the change to take effect.
When you use an ISDN BRI interface for access over leased lines, configure the ISDN BRI as a synchronous serial interface and do not configure ISDN calling and called numbers.
Examples
The following example configures the BRI interface for leased-line access at 128 kbps in Japan:
isdn leased-line bri0/0 128Because of the leased-line—not dialed—environment, configuration of ISDN called and calling numbers is not needed and not used. The BRI 0 interface is henceforth treated as a synchronous serial interface, with the default High-Level Data Link Control (HDLC) encapsulation.
The following example configures BRI channel B1 for 64-kbps leased-line service and channel B2 for ISDN service:
isdn switch-type basic-net3isdn leased-line bri0/0 b1!interface bri0/0ip address 10.1.1.1 255.255.255.0no ip addressdialer pool-member 1interface bri0/0:1ip address 10.1.1.2 255.255.255.0encapsulation pppno ip addressThe following example configures two 64-kbps leased lines:
isdn leased-line bri0/0Related Commands
isdn switch-type (BRI)
Specifies the central office switch type on the ISDN BRI interface.
isdn logging
To enable logging of ISDN syslog messages, use the isdn logging command in global configuration mode. To disable logging, use the no form of this command.
isdn logging
no isdn logging
Syntax Description
This command has no arguments or keywords.
Defaults
This command is disabled by default.
Command Modes
Global configuration
Command History
Usage Guidelines
This command supports syslog logging of the following ISDN events:
•
•
•
Examples
The following example shows how to configure ISDN syslog logging:
isdn loggingRelated Commands
isdn map
To override the default ISDN type and plan generated by the router with custom values, use the isdn map command in interface configuration mode. To revert to the default ISDN type and plan, use the no form of this command.
isdn map address {{address | reg-exp} plan plan type type | transparent}
no isdn map address {{address | reg-exp} plan plan type type | transparent}
Syntax Description
Defaults
The default is the ISDN type and plan generated by the router.
Command Modes
Interface configuration
Command History
12.0(6)T
This command was introduced.
12.3(7)T
The transparent keyword was added.
Usage Guidelines
The default ISDN type and plan can be overridden with custom values on a per-number basis or for numbers that match regular expression patterns.
If you use the isdn map command to configure custom values for the ISDN type and plan, these values take priority over any other ISDN type and plan values. The order of precedence for ISDN type and plan values is as follows, beginning with the highest precedence:
•
•
•
•
Configuring the isdn map command with the transparent keyword results in raw messages received from the ISDN originating gateway receiving priority over H.225 SETUP messages. When the isdn map command is configured with the transparent keyword, the order of precedence for ISDN type and plan values is as follows:
•
•
•
•
Examples
The following example overrides any plan and type used for any ISDN calls with a called or calling number that exactly matches 123:
interface serial1:23isdn map address 123 plan isdn type unknownThe following example overrides any plan and type used for ISDN calls with a called or calling number that begins with the numerals 12:
interface serial1:23isdn map address 12.* plan data type subscriberThe following example matches any number that ends with the number 7:
interface serial1:23isdn map address .*7 plan data type subscriberThe following example reverses the precedence of ISDN type and plan values received from the ISDN originating gateway and from the H.225 SETUP message:
interface serial1:23isdn map address transparentRelated Commands
isdn modem-busy-cause
The isdn modem-busy-cause command is replaced by the isdn disconnect-cause command. See the isdn disconnect-cause command for more information.
isdn negotiate-bchan
To enable the router to accept a B channel that is different from the B channel requested in the outgoing call setup message, use the isdn negotiate-bchan command in interface configuration mode. To restore the default condition, use the no form of this command.
isdn negotiate-bchan [resend-setup] [cause-codes cause-code1 [cause-code2...cause-code16]]
no isdn negotiate-bchan [resend-setup] [cause-codes cause-code1 [cause-code2...cause-code16]]
Syntax Description
Defaults
B channel negotiation is not enabled. Most PRI switch types set the default channel ID to Exclusive in the setup message. An exception is the NI2 switch, which sets the default to Preferred.
If the cause-codes keyword is not entered, it is assumed that you want ISDN cause code 44.
Command Modes
Interface configuration
Command History
Usage Guidelines
The isdn negotiate-bchan command enables the router to negotiate the B channel by setting the channel ID information element to Preferred in the setup message. If this command is not configured, the channel ID is set to the default of the switch, which is usually Exclusive. Exclusive means that only the requested B channel is accepted. If the requested B channel is not available, the call is cleared.
The isdn negotiate-bchan command is supported for all PRI switch types. The resend-setup keyword is supported only for NET5 and NI2 switches. This command is not supported for BRI interfaces.
The cause-codes keyword allows you to configure the gateway to reattempt a call when a cause code other than 44 is received from the PSTN.
Refer to the "ISDN Cause Codes" table in the appendix of the Cisco IOS Debug Command Reference for a list of ISDN cause codes.
Examples
The following example enables a call to be reattempted when a disconnect with cause code of 44 is received before alerting:
interface serial0:23isdn negotiate-bchan resend-setupThe following example shows that cause codes 34, 44, and 63 have been configured:
interface serial0:23isdn negotiate-bchan resend-setup cause-codes 34 44 63Related Commands
isdn not-end-to-end
To override the speed that the network reports it will use to deliver the call data, use the isdn not-end-to-end command in interface configuration mode. To disable the configured end-to-end speed, use the no form of this command.
isdn not-end-to-end {56 | 64}
no isdn not-end-to-end
Syntax Description
Defaults
The default line speed is 64 kbps.
Command Modes
Interface configuration
Command History
Usage Guidelines
Note
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.
Examples
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 in interface configuration mode. 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
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
This command is used specifically on a PRI (channelized T1) to request NSF services supported on primary AT&T 4ESS (primary-4ess) switch types only.
Examples
The following example sets outgoing voice calls to use AT&T SDN NSF:
interface serial 0:23isdn-nsf-service sdnRelated Commands
isdn number
To change the maximum number of digits in a called number information element, use the isdn number command in interface configuration mode.
isdn number [called enbloc limit]
Syntax Description
Defaults
20 digits
Command Modes
Interface configuration
Command History
Usage Guidelines
The maximum number of digits sent in the initial call SETUP is defaulted to 20 digits. The default of 20 digits chosen because some switches cannot handle more than 20 digits. Some countries in Europe are changing their calling plans and will require calls to be made using more than 20 digits.
The isdn number called enbloc command is used when the maximum number of octets in the called number information element in a SETUP message must be changed from the 20-digit default to the user desired limit. With this command, the user can configure the maximum number from 1 to 32 digits. This command is available for ISDN interfaces and applicable to both BRI and PRI interfaces.
Note
BRI_NET3_STYPE
PRI_NET5_SYTPEExamples
The following example configures the called number information element for 32 digits:
Router(config-if) isdn number called enbloc 32isdn outgoing ie
To specify that an information element (IE) may be passed in outgoing ISDN messages, use the isdn outgoing ie command in interface configuration mode. To specify that an IE may not be passed in outgoing ISDN messages, use the no form of this command.
isdn outgoing ie ie [codeset_0 {message message-type | shiftcodeset codeset_6 } | dms250 | nooct3 | transparent]
no isdn outgoing ie ie [codeset_0 {message message-type | shiftcodeset codeset_6 } | dms250 | nooct3 | transparent]
Syntax Description
ie
The IE to pass in outgoing ISDN messages. Valid values for the ie argument are listed in Table 9.
codeset_0
(Optional) Specifies that the IE will be packed in ISDN codeset 0. Codeset 0 is the International Telecommunication Union (ITU) standard codeset. Codeset 0 is the default codeset; however you must issue the codeset_0 keyword if you want to specify a message type.
message message-type
(Optional) Specifies a particular outgoing message to pass an IE in. Valid values for the message-type argument are listed in Table 10. If you do not specify a message type, the IE will be passed in all applicable message types.
dms250
(Optional) Specifies that octet 3 of the display IE is modified for compatibility with the DMS-250 switch type before it is packed in the setup message.
Note
nooct3
(Optional) Specifies that octet 3 of the display IE is stripped from the display IE before it is packed in the setup message. This is the default behavior for DMS-100 and DMS-250 switches.
Note
transparent
(Optional) Specifies that the display IE is packed in the setup message without modifying or inserting octet 3. This is the default behavior for non-DMS switches.
Note
shiftcodeset codeset_6
(Optional) Specifies that the display IE should be packed in codeset 6 in outgoing messages, rather than codeset 0.
Note
Command Default
Supported IEs are passed in applicable outgoing messages by default.
Command Modes
Interface configuration
Command History
12.3(7)T
The isdn outgoing ie command was introduced and replaces the isdn outgoing ie redirecting-number command.
Usage Guidelines
Incompatibility between ISDN switch types at the originating and terminating gateways can prevent provided IEs from being passed end-to-end. Cisco devices can be configured to transparently pass unsupported IEs, allowing full interworking between different switch types.
Use the isdn outgoing ie command to configure a Cisco router to transparently pass unsupported IEs to its peer. IEs may be packed in any codeset. However, the isdn outgoing ie command can manually control IEs packed in codeset 0 only. IEs will be passed only in applicable message types.
The router can be configured to not pass IEs using the no isdn outgoing ie command.
You may use the isdn gateway-max-interworking command to globally configure the Cisco router to transparently pass all unsupported IEs to its peer. However, the isdn outgoing ie command provides much finer control.
Note
Note
Options That Are Specific to the Display IE
DMS-100 and DMS-250 switch types format the display IE using an additional octet that is not used by other switch types, octet 3. Octet 3 specifies the calling party name, and is mandatory for DMS-100 and DMS-250 switch types. DMS-100 and DMS-250 switches each use a different value for octet 3. For these switch types to interoperate properly with each other or with other switch types, octet 3 must be modified. Use the dms250, nooct3, or transparent keyword to control the interoperation of a DMS-100 or DMS-250 switch with other switch types.
4ESS and 5ESS switch types do not support the display IE. If a message with a display IE packed in codeset 0 is passed out of a PRI interface with one of these switch types, the display IE will be dropped. However, these switches will pass any unknown IE that is packed in codeset 6. Use the shiftcodeset codeset_6 keywords to specify that the display IE should be packed in codeset 6 before being sent out a PRI interface with a 4ESS or 5ESS switch.
Table 9 lists the IEs that can be entered for the ie argument. Not all IEs can be controlled using the isdn outgoing ie command.
Table 10 lists the ISDN messages that can be entered for the message-type argument.
Examples
The following example enables the passing of the redirect number IE in for all applicable outgoing message types for a PRI-NI switch:
interface Serial 0:15no ip addressisdn switch-type primary-niisdn incoming-voice modemno cdp enableisdn outgoing ie redirecting-numberThe following example enables the passing of the called number IE in an outgoing alert message for a PRI-NI switch:
interface Serial 0:15no ip addressisdn switch-type primary-niisdn incoming-voice modemno cdp enableisdn outgoing ie called-number codeset_0 message alertingThe following example configures a DMS-100 switch to reformat octet 3 for interoperability with a DMS-250 switch:
interface Serial 0:23no ip addressdialer idle-timeout 999999isdn switch-type primary-dms100isdn incoming-voice modemno cdp enableisdn outgoing ie display dms250The following example configures a DMS-100 switch to drop octet from the display IE:
interface Serial0:23no ip addressdialer idle-timeout 999999isdn switch-type primary-dms100isdn incoming-voice modemno cdp enableisdn outgoing ie display nooct3The following example configures a DMS-100 switch to pack the display IE without modifying octet 3:
interface Serial0:23no ip addressdialer idle-timeout 999999isdn switch-type primary-dms100isdn incoming-voice modemno cdp enableisdn outgoing ie display transparentThe following example configures a switch to pack the display IE in codeset 6 before sending it out of an interface configured with a 4ESS switch:
interface Serial 0:23no ip addressisdn switch-type primary-4essisdn incoming-voice modemno cdp enableisdn outoing ie display codeset_0 shiftcodeset codeset_6Related Commands
isdn outgoing ie redirecting-number
Note
To enable passing of the redirect number information element (IE) in the setup message from the Cisco router to its peer, use the isdn outgoing ie redirecting-number command in interface configuration mode. To disable passing of the redirect number IE in the setup message from the Cisco router to its peer, use the no form of this command.
isdn outgoing ie redirecting-number
no isdn outgoing ie redirecting-number
Syntax Description
This command has no arguments or keywords.
Command Default
The redirecting number IE will be passed in the setup message for the following switch types only by default:
•
•
•
•
•
•
•
For all other switch types, the redirecting number IE will not be passed by default.
Command Modes
Interface configuration
Command History
12.2(15)T5
This command was introduced.
12.3(7)T
This command was replaced by the isdn outgoing ie command.
Usage Guidelines
Use the isdn outgoing ie redirecting-number command to enable passing of the redirect number IE in the setup message from the Cisco router to its peer. Some switch types do not support the redirect number IE, so to ensure compatibility with a peer that does support the redirect number IE you may enable the passing of the redirect number IE using the isdn outgoing ie redirecting-number command.
Note
Examples
The following example enables the passing of the redirect number IE for a NET5 switch on a serial interface:
interface Serial 0:15isdn outgoing ie redirecting-numberRelated Commands
isdn outgoing-voice
To set information transfer capability on outgoing calls for all switch types, use the isdn outgoing-voice command in interface configuration mode. To revert to the default state, use the no form of this command.
isdn outgoing-voice {info-transfer-capability {3.1kHz-audio | speech}}
no isdn outgoing-voice
Syntax Description
info-transfer-capability
Specifies information transfer capability for voice calls.
3.1kHz-audio
Sets capability to 3.1 kHz audio.
speech
Sets capability to speech.
Defaults
No information transfer capabilities set.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command is used on outgoing voice calls only, and sets standard information transfer capability.
Examples
The following example sets information transfer capability on outgoing voice calls to speech:
interface serial 0:23isdn outgoing-voice info-transfer-capability speechRelated Commands
isdn incoming-voice
Specifies how to process incoming ISDN voice and data calls.
isdn overlap-receiving
To enable overlap receiving on an ISDN interface, use the isdn overlap-receiving command in interface configuration mode. To disable overlap receiving on an ISDN interface, use the no form of this command.
isdn overlap-receiving [T302 milliseconds]
no isdn overlap-receiving
Syntax Description
Defaults
Overlap receiving is not enabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
In some situations, the default timer value of the T302 timer is too long. You can shorten the duration of the timer by specifying the T302 keyword with the number of milliseconds necessary.
When configuring outbound peer matching and overlap receiving, use the isdn overlap-receiving command with the destination-pattern command. You must configure the commands to allow the router to wait for all the digits to be received before the call is routed. To do this, use the T control character after the digits in the destination pattern specified with the destination-pattern command. Optionally, you can shorten the duration of the T302 timer when you specify the isdn overlap-receiving command.
Examples
The following example shows how to enable overlap receiving on the ISDN interface:
interface serial 0:23isdn overlap-receivingThe following example shows how to enable overlap receiving on the ISDN interface and set the T302 timer to 2 seconds:
interface serial 0:23isdn overlap-receiving T302 2000Related Commands
isdn overlap-receiving calltypes all
To enable overlap receiving for all call types, use the isdn overlap-receiving calltypes all command in interface configuration mode. To disable overlap receiving for all call types, use the no form of this command.
isdn overlap-receiving calltypes all
no isdn overlap-receiving calltypes all
Syntax Description
This commands has no arguments or keywords.
Defaults
Overlap receiving is not enabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
The isdn overlap-receiving calltypes all command enables overlap receiving for all nonvoice calls that use data dial peers, and it enables an ISDN interface to proceed with a call when a sufficient number of digits are received. These digits are determined by the destination-pattern command under the data dial peer configuration.
This command is supported on the Cisco AS5350, Cisco AS5400, and Cisco AS5850 routers.
Examples
The following example shows how to enable overlap receiving:
interface serial 0:23isdn overlap-receiving calltypes allRelated Commands
isdn piafs-enabled
To enable the PRI to take Personal Handyphone Internet Access Forum Standard (PIAFS) calls on MICA technologies modems, use the isdn piafs-enabled command in interface configuration mode. To disable the function, use the no form of this command.
isdn piafs-enabled
no isdn piafs-enabled
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Interface configuration
Command History
Examples
The following example shows how to enable the PRI to take PIAFS calls:
Router(config)# interface serial 0:23Router(config-if)# isdn piafs-enabledisdn point-to-point-setup
To configure the ISDN port to send SETUP messages on the static terminal endpoint identifier (TEI), use the isdn point-to-point-setup command in interface configuration mode. To restore the default, use the no form of this command.
isdn point-to-point-setup
no isdn point-to-point-setup
Syntax Description
This command has no arguments or keywords.
Defaults
The BRI port sends SETUP messages on the static TEI (TEI 127).
Command Modes
Interface configuration
Command History
Usage Guidelines
This command only applies if a static TEI has been activated with the isdn static-tei command.
Examples
The following example configures the BRI port to send SETUP messages on the static TEI:
interface bri 1isdn point-to-point-setupRelated Commands
isdn tei-negotiation (global)
Configures when Layer 2 becomes active and ISDN TEI negotiation occurs.
isdn protocol-emulate
To emulate the network side of an ISDN configuration for a PRI Net5 or PRI NTT switch type, use the isdn protocol-emulate command in interface configuration mode. To disable ISDN emulation, use the no form of this command.
isdn protocol-emulate {network | user}
no isdn protocol-emulate {network | user}
Syntax Description
Defaults
No default behavior or values
Command Modes
Interface configuration mode
Command History
Usage Guidelines
•
•
•
•
•
Examples
The following example configures the interface (configured for Net5) to emulate the network-side ISDN:
Router(config)# int s0:15Router(config-if)# isdn protocol-emulate networkThe following example configures the layer 2 and layer 3 function of T1 PRI interface 23 to act as the QSIG master (NT):
interface serial 1:23isdn protocol-emulate networkThe following example configures the layer 2 and layer 3 function of a BRI voice port to operate as QSIG slave (TE):
interface bri 1isdn protocol-emulate userThe following example configures the layer 2 and layer 3 function of an E1 PRI interface to operate as QSIG slave (TE):
interface serial 4:23isdn protocol-emulate userRelated Commands
isdn reject
To reject an incoming ISDN BRI or PRI call based on type, use the isdn reject command in interface configuration mode. To re-allow the incoming call type, use the no form of this command.
isdn reject {{cause cause-code} {data [56 | 64]} | piafs | v110 | v120 | vod | {voice [3.1khz | 7khz | speech]}}
no isdn reject {{cause cause-code} {data [56 | 64]} | piafs | v110 | v120 | vod | {voice [3.1khz | 7khz | speech]}}
Syntax Description
Defaults
Incoming calls are rejected based on D-channel bearer capability information (cause code 65).
Command Modes
Interface configuration
Command History
12.0
This command was introduced.
12.2
The cause cause-code keyword and argument were added.
Usage Guidelines
The isdn reject command rejects incoming calls based on D-channel bearer capability information.
If this command is configured with the cause cause-code keyword and argument, it will override the default value and use the configured cause code specified to reject the call. For example, if the isdn reject data command is configured so that data calls are rejected with cause code set to 65 ("bearer capability not implemented" and the default), you can change the cause code to 2, so that data calls will then be rejected with cause code 2. Refer to the ISDN Switch Types, Codes, and Values appendix in the Cisco IOS Debug Command Reference for a list of ISDN cause code values.
The settings for the isdn incoming-voice interface configuration command determine how the call is handled based on bearer capability information, as follows:
•
•
•
When the ISDN interface is configured for incoming voice with the isdn incoming-voice voice command and the ISDN bearer capability indicates the call as unrestricted digital data (i = 0x8890), the call is handled as voice over data.
You can assign as many reject incoming call type statements as needed to reject unwanted calls on the ISDN interface.
This command works on any Cisco platform that supports ISDN PRI and BRI interfaces.
Examples
The following example configuration rejects all incoming data and voice-over-data calls but accepts voice calls:
interface serial 2/0:23no ip addressno logging event link-statusdialer-group 1isdn switch-type primary-net5isdn incoming-voice voiceisdn map address 222 plan isdn type nationalisdn T309 80000isdn reject dataisdn reject vodisdn reject v120isdn reject v110isdn reject piafsThe following example sets the ISDN interface to reject incoming PIAFS calls:
interface serial 2/0:23isdn reject piafsThe following example sets cause code 21 to reject all incoming data calls:
interface serial 2/0:23isdn reject dataisdn reject cause 21Related Commands
isdn incoming-voice
Specifies how to process incoming ISDN voice and data calls.
isdn send-alerting
To specify that an Alerting message be sent before a Connect message when making ISDN calls, use the isdn send-alerting command in interface configuration mode. To disable the Alerting information element, use the no form of this command.
isdn send-alerting
no isdn send-alerting
Syntax Description
This command has no arguments or keywords.
Defaults
This command is disabled by default.
Command Modes
Interface configuration
Command History
Usage Guidelines
Some switches may want an Alerting message to be sent by the router before sending a Connect message. This is usually seen in a voice and data type of network.
Examples
In the following example, the isdn send-alerting command applies to an ISDN BRI interface:
interface BRI0description connected to PBX 61886ip address 172.26.1.1 255.255.255.0encapsulation pppisdn send-alertingisdn sending-completedialer idle-timeout 20dialer map ip 172.26.1.2 name rudder 61884dialer map ip 172.26.1.3 name bosun 61885dialer-group 1ppp authentication chapRelated Commands
isdn sending-complete
Specifies that the Sending Complete IE is included in the outgoing Setup message.
isdn sending-complete
To specify that the Sending Complete information element (IE) is included in the outgoing Setup message, use the isdn sending-complete command in interface configuration mode. To disable the Sending Complete information element, use the no form of this command.
isdn sending-complete
no isdn sending-complete
Syntax Description
This command has no arguments or keywords.
Defaults
This command is disabled by default.
Command Modes
Interface configuration
Command History
Usage Guidelines
The Sending Complete IE tells the switch that all the digits and information necessary for the call are contained in this Setup message.
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 required in Hong Kong and Taiwan, and the isdn sending-complete command forces it to be sent.
Examples
In the following example, the isdn sending-complete command applies to an ISDN BRI interface:
interface BRI0description connected to PBX 61886ip address 172.31.1.1 255.255.255.0encapsulation pppisdn sending-completedialer idle-timeout 20dialer map ip 172.31.1.2 name rudder 61884dialer map ip 172.31.1.3 name bosun 61885dialer-group 1ppp authentication chapThe following example enables sending complete IE information on a serial interface:
interface serial 0:15description connected to PBX 61886ip address 10.1.1.1 255.255.255.0encapsulation pppisdn sending-completedialer idle-timeout 20dialer map ip 10.1.1.2 name rudder 61884dialer map ip 10.1.1.3 name goodie 61885dialer-group 1ppp authentication chapRelated Commands
isdn send-alerting
Specifies that an Alerting message be sent before a Complete message when making ISDN calls.
isdn service
To take an individual B channel or an entire PRI interface out of service or set it to a different channel service state that is passed to a time-division multiplexing (TDM) switch at the Public Switched Telephone Network (PSTN), use the isdn service command in interface configuration mode. To remove the configuration, use the no form of the command.
isdn service [dsl number | nfas-int number] b_channel number {state {0 | 1 | 2} [hard | immediate | soft]}
no isdn service
Syntax Description
Defaults
Disabled
Command Modes
Interface configuration
Command History
11.3
This command was introduced.
12.2
The dsl keyword was made optional.
12.3
The hard, immediate, and soft keywords were added as state keyword options.
Usage Guidelines
Use this command to manage channels on ISDN NFAS and Primary Rate Interfaces (PRI) on Cisco routers.
Use the b_channel 0 keywords to set the entire PRI interface to the specified state value.
Use the optional soft and immediate state keywords to take switches down gracefully, without impacting calls in progress. The hard keyword sends an immediate service message to the connected switch that will disconnect active B channels and drop active calls.
To display the digital subscriber loop (DSL) number on NFAS interfaces, use the show isdn service EXEC command. To find the NFAS interface value, use the pri-group T1 controller configuration command.
This command can be used only on North American switch types, because it supports the service message.
Examples
The following example sets all the PRI B channel on the interface to the maintenance state:
isdn service b_channel 0 state 1The following example restores B channels 2 through 4; the DSL number was obtained using the show isdn command with the status keyword, and the DSL number was then used in the command:
isdn service dsl 2 b_channel 2-4 state 0The following example sets B channels 13 to 24 to the OOS state:
isdn service nfas-int 3 b_channel 13-24 state 1In the following example, the first statement sets B channels 17 through 20 to the maintenance state and marks any busy B channel (or channels) as pending; the channel will change to the service state only when it becomes idle. The second statement will cause the service message to be sent immediately and will clear the call. If there is no call, the second statement will have the same effect as the immediate keyword, that is, it will send the service message, but will not clear the call.
isdn service b_channel 17-20 state 1 softisdn service b_channel 21 state 1 hardRelated Commands
isdn silent-boot
To prevent the transmission and receipt of ISDN packets by the router during the boostrap loading process, use the isdn silent-boot command in global configuration mode. To allow the transmission and receipt of ISDN packets by the router during the boostrap loading process, use the no form of this command.
isdn silent-boot
no isdn silent-boot
Syntax Description
This command has no arguments or keywords.
Defaults
The transmission and receipt of ISDN packets by the router is allowed during the bootstrap process.
Command Modes
Global configuration
Command History
Usage Guidelines
ISDN traffic will not be sent from any interfaces on the router (ISDN BRI or PRI) when you use the isdn silent-boot command. Disabling the ISDN traffic on the router is appropriate when the router is part of a hunt group that is accepting incoming ISDN calls because you do not want the router to receive calls until after it has reloaded and is ready to accept the incoming calls.
Examples
The following example disables ISDN traffic:
Router(config)# isdn silent-bootisdn snmp busyout b-channel
To enable PRI B channels to be busied out via SNMP, use the isdn snmp busyout b-channel command in interface configuration mode. To prevent B channels from being busied out via SNMP, use the no form of this command.
isdn snmp busyout b-channel
no isdn snmp busyout b-channel
Syntax Description
This command has no arguments or keywords.
Defaults
The default value is TRUE; that is, setting busyout using SNMP is allowed.
Command Modes
Interface configuration
Command History
Usage Guidelines
To busy out B-channels on a PRI, the ISDN switch must support service messages. The isdn snmp busyout b-channel command sets the MIB object, cpmDS0BusyoutAllow, indicating whether or not the switch supports service messages, thereby allowing the busyout of B channels. When the network access server receives an SNMP request for a busyout, it checks the value of this object. If the no isdn snmp busyout b-channel command is configured, the busyout request fails.
Examples
The following example allows the busyout of B-channels for serial interface 0:23:
configure terminalinterface serial 0:23isdn snmp busyout b-channelisdn spid1, isdn spid2
To associate up to three ISDN local directory numbers (LDNs) provided by your telephone service provider to the first service profile identifier (SPID), use the isdn spid1 command in interface configuration mode. To disable the specified SPID and prevent access to the switch, use the no form of this command.
isdn spid1 spid-number ldn [ldn] [ldn]
no isdn spid1 spid-number ldn [ldn] [ldn]
To associate up to three ISDN LDNs provided by your telephone service provider to the second service SPID, use the isdn spid2 interface configuration command. To disable the specified SPID and prevent access to the switch, use the no form of this command.
isdn spid2 spid-number ldn [ldn] [ldn]
no isdn spid2 spid-number ldn [ldn] [ldn]
Syntax Description
Defaults
A default SPID number and ISDN local directory numbers are not defined.
Command Modes
Interface configuration
Command History
10.3
This command was introduced.
12.0(3)T
This command was enhanced with the option of associating the SPID with up to three LDNs.
Usage Guidelines
This command applies only to North America and is required for DMS-100 and National ISDN switches. Typically, DMS-100 and National ISDN switch implementations using BRI interfaces with SPIDS require two TEIs, two SPIDS, and two phone numbers. If you want to take advantage of both B channels, it is advised you configure the router with the LDN value after the SPID.
Note
If you want the SPID to be automatically detected, you can specify 0 for the spid-number argument.
The ISDN switch checks for the LDN to determine whether both channels can be used to transmit and receive data. If there is not an LDN present, then only the B1 channel can be used for full-duplex communication. However, the B2 channel can still be used to make outgoing calls.
If you include the local directory number in the no form of this command, access to the switch is permitted, but the other B channel may not be able to receive incoming calls.
Examples
The following example defines, on the router, a SPID and LDN for the B1 channel:
isdn spid1 41555512130101 5551213The following example shows how to specify that the SPID should be automatically detected, that the primary ISDN local directory number is 4085551111, and that the secondary number is 4085552222:
isdn spid1 0 4085551111 4085552222The following example defines, on the router, a SPID and LDN for the B2 channel:
isdn spid2 41555512140101 5551214The following example specifies that the SPID should be automatically detected, that the primary ISDN local directory number is 4085551111, and that the secondary number is 4085552222:
isdn spid2 0 4085551111 4085552222Related Commands
isdn static-tei
To configure a static ISDN Layer 2 terminal endpoint identifier (TEI) over the D channel, use the isdn static-tei command in interface configuration mode. To remove a static TEI configuration, use the no form of this command.
isdn static-tei tei-number
no isdn static-tei tei-number
Syntax Description
Defaults
Dynamic TEI (no isdn static-tei)
Command Modes
Interface configuration
Command History
Usage Guidelines
Depending on the telephone company you subscribe to, you may have a dynamically or statically assigned TEI for your ISDN service. The default TEI behavior is dynamic, and the isdn static-tei command changes that behavior to static for the specified service.
When you reconfigure a TEI with the isdn static-tei command, you must activate the configuration using the shutdown and no shutdown commands.
Examples
The following example configures German Anlagenanschluss ISDN lines. These lines are often provided in a group intended to be connected to single ISDN device such as a private branch exchange. To use the Anlagenanschluss ISDN lines on a Cisco router, you must set the TEI to 0, as follows:
Router# configure terminalRouter(config)# interface bri 0Router(config-if)# isdn static-tei 0Router(config-if)# shutdownRouter(config-if)# no shutdownRelated Commands
isdn switch-type (BRI)
To specify the central office switch type on the ISDN interface, use the isdn switch-type command in global or interface configuration mode. To remove an ISDN switch type, use the no form of this command.
isdn switch-type switch-type
no isdn switch-type switch-type
Syntax Description
switch-type
ISDN service provider switch type. Table 11 in the "Usage Guidelines" section lists the supported switch types.
Defaults
No ISDN switch type is specified.
Command Modes
Global configuration or interface configuration
Note
Command History
Usage Guidelines
For the Cisco AS5300 access server, you have the choice of configuring the isdn-switch-type command to support Q.SIG in either global configuration mode or interface configuration mode. When entered in global configuration mode, the setting applies to the entire Cisco AS5300 access server. When entered in interface configuration mode, the setting applies only to the T1/E1 interface specified. The interface configuration mode setting overrides the global configuration setting.
For example, if you have a Q.SIG connection on one line as well as on the PRI port, you can configure the ISDN switch type in one of the following combinations:
•
•
•
For the Cisco MC3810 router, if you are using different Cisco MC3810 BRI port interfaces with different ISDN switch types, you can use global and interface commands in any combination, as long as you remember that interface commands always override a global command.
For example, if you have a BRI QSIG switch interface on BRI voice ports 1, 2, 3 and 4, but a BRI 5ess switch interface on BRI backup port 0, you can configure the ISDN switch types in any of the following combinations:
•
isdn switch-type bri-5ess command on interface 0.•
isdn switch-type basic-qsig command on interfaces 1, 2, 3, and 4 individually.•
If you use the no isdn switch-type global configuration command, any switch type that was originally entered in global configuration mode is canceled; however, any switch type originally entered on an interface is not affected. If you use the no isdn switch-type interface configuration command, any switch type configuration on the interface is canceled.
Note
Note
If you are using the Multiple ISDN Switch Types feature to apply ISDN switch types to different interfaces, refer to the chapters "Configuring ISDN BRI" and "Configuring ISDN PRI" in the Cisco IOS Dial Technologies Configuration Guide for additional details.
The Cisco IOS command parser accepts the following switch types: basic-nwnet3, vn2, and basic-net3; however, when viewing the NVRAM configuration, the basic-net3 or vn3 switch types are displayed, respectively.
To remove an ISDN switch type from an ISDN interface, specify the no isdn switch-type switch-type command.
Table 11 lists supported BRI switch types by geographic area.
Examples
The following example configures the French VN3 ISDN switch type:
isdn switch-type vn3The following example uses the Multiple ISDN Switch Types feature and shows use of the global ISDN switch type basic-ni keyword (formerly basic-ni1) and the basic-net3 interface-level switch type keyword. ISDN switch type basic-net3 is applied to BRI interface 0 and overrides the global switch setting.
isdn switch-type basic-ni ! interface BRI0 isdn switch-type basic-net3The following example configures the Cisco MC3810 router to use BRI QSIG signaling for all of its BRI voice ports:
isdn switch-type basic-qsigThe following example configures the Cisco MC3810 to use BRI QSIG signaling for BRI voice
port 1. On port 1, this setting overrides any different signaling set in the previous example.interface bri 1isdn switch-type basic-qsigThe following example configures the Cisco AS5300 to support Q.SIG signaling:
isdn switch-type primary-qsigisdn switch-type (PRI)
To specify the central office switch type on the ISDN interface, or to configure the Cisco MC3810 PRI interface to support QSIG signaling, use the isdn switch-type command in global or interface configuration mode. To disable the switch or QSIG signaling on the ISDN interface, use the no form of this command.
isdn switch-type switch-type
no isdn switch-type switch-type
Syntax Description
switch-type
Service provider switch type; see Table 12 for a list of supported switches.
Defaults
The switch type defaults to none, which disables the switch on the ISDN interface.
Command Modes
Global configuration or interface configuration
Note
Command History
Usage Guidelines
You have a choice of configuring the isdn-switch-type command to support QSIG at either the global configuration level or at the interface configuration level. For example, if you have a QSIG connection on one line as well as on the BRI port, you can configure the ISDN switch type in one of the following combinations:
•
•
•
The voice-port codec command must be configured before any calls can be placed over the connection to the PINX. The default codec type is G729a.
To disable the switch on the ISDN interface, specify the isdn switch-type none command.
Table 12 lists supported PRI switch types by geographic area.
Note
Examples
The 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 the isdn switch-type primary-net5 command and BRI interface 0 is configured for the isdn switch-type basic-ni command (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-niThe following example configures T1 interface 23 on the Cisco AS5300 to support Q.SIG signaling:
interface serial 1:23isdn switch-type primary-qsigRelated Commands
isdn t306
To set a timer for disconnect messages received by a router, use the isdn t306 command in interface configuration mode. To reset to the default, use the default or no form of this command.
isdn t306 milliseconds
default isdn t306
no isdn t306
Syntax Description
milliseconds
Time, in milliseconds, that the router waits before disconnecting a call after it receives a disconnect message with a progress indicator of 8. Range is from 1 to 400000.
Defaults
Default depends on the switch, usually from 5000 to 30000 ms.
Command Modes
Interface configuration
Command History
Usage Guidelines
The T306 timer is designed for routers that are configured as an ISDN network-side switch. When a router receives a disconnect message with a progress indicator of 8, it disconnects the call after waiting for the specified number of milliseconds (ms) while the in-band announcement or error tone is playing. Be sure to set the timer long enough for the announcement to be heard or the tone to be recognized. This command is used only for disconnect messages with a progress indicator of 8; otherwise, the T305 timer is used. The disable and no forms of this command have the same result: the timer waits for the default number of ms before disconnecting the call.
Examples
The following example sets the T306 timer to 60000 ms for serial interface 0:23:
interface serial 0:23isdn t306 60000Related Commands
isdn t310
To set a timer for the call proceeding state, use the isdn t310 command interface configuration mode. To reset to the default, use the no form of this command.
isdn t310 milliseconds
no isdn t310
Syntax Description
milliseconds
Time, in milliseconds, that the router waits before disconnecting a call after receiving a call proceeding message. Range is from 1 to 400000.
Defaults
Default depends on the switch; usually from 5000 to 30000 ms.
Command Modes
Interface configuration
Command History
Usage Guidelines
The T310 timer starts when a router receives a call proceeding message; it stops when the call exits the call proceeding state, typically when the call moves to the alerting, connect, or progress state. If the timer expires while the call is in the call proceeding state, the router releases the call. Set the timer to match the specific characteristics of your network.
Examples
The following example sets the T310 timer to 40,000 ms for serial interface 0:23:
interface serial 0:23isdn t310 40000Related Commands
isdn tei-negotiation (global)
To configure when Layer 2 becomes active and ISDN terminal endpoint identifier (TEI) negotiation occurs, use the isdn tei-negotiation command in global configuration mode. To remove TEI negotiation configuration, use the no form of this command.
isdn tei-negotiation [first-call | powerup]
no isdn tei-negotiation
Syntax Description
first-call
(Optional) ISDN TEI negotiation should occur when the first ISDN call is placed or received.
powerup
(Optional) ISDN TEI negotiation should occur when the router is powered on.
Defaults
The powerup state is the default condition.
Command Modes
Global configuration
Command History
Usage Guidelines
This command is for BRI configuration only.
This command is useful for switches that may deactivate Layers 1 and 2 when there are no active calls or primary DMS-100 switches which activate TEI when the first ISDN call is placed or received.
Examples
The following example applies the isdn tei negotiation first-call command to BRI interface 0. BRI interface 1 will use the isdn tei negotiation powerup command, which is the default setting. Defaults settings do not appear in the router configuration.
isdn switch-type basic-net!interface bri0! Configure the ISDN switch type on this interface and set TEI negotiation to first-call.isdn switch-type basic-niisdn tei-negotiation first-call! BRI interface 1 uses the default TEI negotiation value.interface bri1isdn tei-negotiation (interface)
To configure when Layer 2 becomes active and ISDN terminal endpoint identifier (TEI) negotiation occurs, use the isdn tei-negotiation command in interface configuration mode. To remove TEI negotiation from an interface, use the no form of this command.
isdn tei-negotiation {first-call | powerup} {preserve | remove}
no isdn tei-negotiation {first-call | powerup} {preserve | remove}
Syntax Description
Defaults
The powerup state is the default condition. Depending upon the ISDN switch type configured, the default will be to preserve or remove the TEI negotiation options. See the "Usage Guidelines" and "Examples" sections for further explanation.
Command Modes
Interface configuration
Command History
11.3 T
This command was introduced as an interface command.
12.2
The preserve and remove keywords were added.
Usage Guidelines
This command is for BRI configuration only.
The first-call and powerup, and preserve and remove command pairs are mutually exclusive, that is, you must choose only one command from either the first-call and powerup or preserve and remove command pairs, per command line.
The no isdn tei-negotiation command returns the configuration to default to the powerup state.
The preserve keyword depends on the ISDN switch type configured, that is, the TEI negotiation configured will be preserved during ISN Layer 1 flaps, and when the clear interface or the shut and no shut EXEC commands are executed, on the switch types listed in Table 13.
For all other ISDN switch types, the TEI negotiation will be removed during ISDN Layer 1 flaps, and when the clear interface or the shut and no shut EXEC commands are executed. Use the remove keyword to specifically set one of the switches listed in Table 13 to the remove state.
Examples
The following example shows the ISDN TEI negotiation configuration with default settings. (Defaults settings do not appear in the router configuration.)
interface BRI0/0no ip addressisdn switch-type basic-nicdapi buffers regular 0cdapi buffers raw 0cdapi buffers large 0The following example shows how to set TEI negotiation timing to the first call:
Router(config-if)# isdn tei-negotiation first-callRouter(config-if)# exitRouter(config)# exitRouter# show startup-config...interface BRI0/0no ip addressisdn switch-type basic-niisdn tei-negotiation first-callcdapi buffers regular 0cdapi buffers raw 0cdapi buffers large 0interface BRI0/0The following example shows how to change TEI negotiation timing back to the default power-up state:
Router(config-if)# no isdn tei-negotiation first-callRouter(config-if)# exitRouter(config)# exitRouter# show startup-config...interface BRI0/0no ip addressisdn switch-type basic-nicdapi buffers regular 0cdapi buffers raw 0cdapi buffers large 0The following example shows how to remove TEI negotiation when ISDN Layer 1 flaps (the preserve state is the default for the National ISDN basic rate switch):
Router(config-if)# isdn tei-negotiation removeRouter(config-if)# exitRouter(config)# exitRouter# show startup-config...interface BRI0/0no ip addressisdn switch-type basic-niisdn tei-negotiation first-callisdn tei-negotiation removecdapi buffers regular 0cdapi buffers raw 0cdapi buffers large 0The following example shows how to return the National ISDN basic rate switch to its default preserve state:
Router(config-if)# no isdn tei-negotiation removeRouter(config-if)# exitRouter(config)# exitRouter# show startup-config...interface BRI0/0no ip addressisdn switch-type basic-niisdn tei-negotiation first-callcdapi buffers regular 0cdapi buffers raw 0cdapi buffers large 0isdn test call interface
To make an ISDN data call, use the isdn test call interface command in privileged EXEC mode.
isdn test call interface interface-number dialing-string [speed 56 | 64]
Syntax Description
interface-number
Interface number.
dialing-string
Telephone number used for making ISDN data call.
speed 56
speed 64
(Optional) Line speed (56 or 64 kbps) used for making ISDN data call.
Defaults
The default B-channel speed is 64 kbps.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
You can use the isdn test call interface command to test your DDR configuration. You can also use this command to verify the dialing string and speed without having to know the IP address of the remote router or without configuring a dialer map or string.
The isdn test call interface command replaces the isdn call interface command.
Examples
The following example makes an ISDN data call through interface bri 0 to 555-1111 and at a line speed of 56 kbps:
isdn test call interface bri 0 5551111 speed 56Related Commands
isdn test disconnect interface
To disconnect an ISDN data call without bringing down the interface, use the isdn test disconnect interface command in privileged EXEC mode.
isdn test disconnect interface interface-type interface-number {b1 | b2 | all}
Syntax Description
interface-type interface-number
Interface type and number, such as bri 0.
b1
B channel 1.
b2
B channel 2.
all
B channels 1 and 2.
Defaults
A default interface is not defined.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
You can use the isdn test disconnect interface command to disconnect any ongoing data calls placed manually or caused by DDR.
The isdn test disconnect interface command replaces the isdn disconnect interface command.
Examples
The following example disconnects an ISDN data call through interface bri 0 and B channel 1:
isdn test disconnect interface bri 0 b1Related Commands
isdn timer t309
To change the value of the T309 timer to clear the network connection and to release the B channel and call reference when a data-link disconnection has occurred, use the isdn timer t309 command in interface configuration mode. To restore the default value, use the no form of this command.
isdn timer t309 milliseconds
no isdn timer t309
Syntax Description
Command Default
90,000 ms (90 seconds)
Command Modes
Interface configuration
Command History
Usage Guidelines
When a data link layer malfunction occurs, calls that are not in the active state are cleared. For calls that are not in the active state, the T309 timer is started. The timer is stopped when the data link is reconnected. If the T309 timer expires prior to the reestablishment of the data link, the network clears the connection and call to the remote user, sending a disconnect cause of 27 to indicate that the call destination is out of order. The network releases and disconnects the B channel, and releases the call reference, entering the Null state. The T309 timer is mandatory for routers that are configured as an ISDN network-side switch and by default the timer is set to expire after 90,000 ms (90 seconds). The implementation of the T309 timer is optional for the user side of the network. The isdn timer t309 command is used for changing the value of the T309 timer.
Note
Examples
The following example sets the T309 timers to 60,000 ms (60 seconds) for serial interface 0:24:
interface serial 0:24isdn timer t309 60000Related Commands
isdn timer t321
To change the value of the timer for D channel switchover when the primary D channel fails, use the isdn timer t321 command in interface configuration mode. To restore the default value, use the no form of this command.
isdn timer t321 milliseconds
no isdn timer t321
Syntax Description
milliseconds
Number of milliseconds (ms) that the router waits before sending a DL-ESTABLISH request on both D channels to request a switchover. Values are from 0 to 30 ms.
Defaults
30 ms
Command Modes
Interface configuration
Command History
Usage Guidelines
The T321 timer must be implemented when you use the D channel backup procedure involving D channel switchover. The isdn timer t321 command is used for changing the value of the T321 timer.
Note
Examples
The following example sets the T321 timers to 25 ms for serial interface 0:23:
interface serial 0:23isdn timer t321 25Related Commands
isdn transfer-code
To activate call transferring, use the isdn transfer-code command in interface configuration mode. To disable call transferring, use the no form of this command.
isdn transfer-code range
no isdn transfer-code
Syntax Description
Defaults
The default code is 61.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use this command if your ISDN line is connected to a NI1 or a Nortel DMS-100 Custom switch. Your telephone service provider should issue an ISDN transfer code when you order call transferring.
Examples
The following example specifies 62 as the ISDN transfer code:
isdn transfer-code 62isdn twait-disable
To delay a National ISDN BRI switch a random time before activating the Layer 2 interface when the switch starts up, use the isdn twait-disable command in interface configuration mode. To remove the delay, use the no form of this command.
isdn twait-disable
no isdn twait-disable
Syntax Description
This command has no arguments or keywords.
Defaults
This command is enabled by default.
Command Modes
Interface configuration
Command History
Usage Guidelines
The random-length delay set by this command prevents mass power failures from causing the network ISDN switches to be overwhelmed when power returns and all the devices startup at the same time.
The random delay is in the range 1 to 300 seconds.
Examples
The following example configures a random wait period after a power failure:
isdn twait-disableisdn v110 only
To selectively accept incoming V.110 calls based on data bit, parity, and stop bit modem communication settings, use the isdn v110 only command in interface configuration mode. To change or disable the expected incoming V.110 modem call configuration, use the no form of this command.
isdn v110 only [databits {5 | 7 | 8}] [parity {even | mark | none | odd | space}]
[stopbits {1 | 1.5 | 2}]no isdn v110 only
Syntax Description
Defaults
No default behavior or values.
Command Modes
Interface configuration
Command History
Usage Guidelines
The isdn v110 only command provides a way to screen incoming V.110 modem calls and reject any calls that do not have the communication settings configured as the network expects them to be.
Examples
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 1isdn v110 padding
To disable the padded V.110 modem speed report required by the V.110 modem standard, use the no isdn v110 padding command in interface configuration mode. To reenable the padded V.110 modem speed report, use the isdn v110 padding command.
no isdn v110 padding
isdn v110 padding
Syntax Description
This command has no arguments or keywords.
Defaults
V.110 modem speed padding is enabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
The no isdn v110 padding command is useful for 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. The V.110 modem standard specifies that the incoming asynchronous data must be padded by adding stop elements to fit the nearest channel rate. For example, a 14400 bits per second (bps) user data signaling rate is adapted to a synchronous 19200-bps stream rate. The software reports the adapted rate (19200 bps) to the modem for an incoming V.110 call. However, for those devices that do not fully conform to the V.110 supplications, the software must report the speed as 14400 instead of 19200 to the modem for a successful connection. By setting the modem interface to no isdn v110 padding, padding is disabled and the actual bit rate can be reported to the modem.
Examples
The following example shows how to disable V.110 asynchronous-to-synchronous padding:
!interface Serial0:23no ip addressisdn switch-type primary-niisdn bchan-number-order ascendingno isdn v110 paddingno cdp enableisdn voice-priority
To control the priority of data and voice calls for the telephones, fax machines, and modems connected to the router telephone ports, use the isdn voice-priority command in interface configuration mode. To disable a specified ISDN voice priority setting and to use the default setting, use the no form of this command.
isdn voice-priority local-directory-number {in | out} {always | conditional | off}
no isdn voice-priority local-directory-number
Syntax Description
Defaults
A data call is never bumped for an incoming or outgoing voice call.
Command Modes
Interface configuration
Command History
Usage Guidelines
If an ISDN circuit endpoint is busy with a data call or calls and either a voice call comes in (incoming) or you attempt to place a voice call (outgoing), the data call is handled according to the setting of isdn voice-priority command.
If you are in North America and have multiple ISDN directory numbers associated with a SPID, the outgoing voice priority that you set for any of these directory numbers applies to the other directory numbers. For example, if you enter the following commands, the outgoing voice priority for all directory numbers specified in the isdn spid1 command is set to conditional:
isdn spid1 0 4085551111 4085552222 4085553333isdn voice-priority 5551111 out conditionalThe setting of the pots dialing-method command affects when you hear a busy signal in the following situation:
•
•
If the setting is overlap, you hear a busy signal when you pick up the handset. If the setting is enblock, you initially hear a dial tone and then a busy signal.
Examples
The following example specifies that a data call for the specified ISDN directory number never be bumped for an incoming or an outgoing voice call:
isdn voice-priority 5551111 in offisdn voice-priority 5551111 out offRelated Commands
isdn x25 dchannel
To create a configurable interface for X.25 traffic over the ISDN D channel, use the isdn x25 dchannel command in interface configuration mode. To remove the interface, use the no form of this command.
isdn x25 dchannel
no isdn x25 dchannel
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
This command creates a new, configurable interface, which can be specified as interface brix:0 in commands, where x is the original BRI interface number. For example, on a Cisco 4500 router
with an MBRI, if the isdn x25 dchannel command is configured on bri5, the new interface
is bri5:0 and can be used for configuring the other parameters for X.25 over the D channel. These parameters include the addresses, the map statements, and others. To display the new interface, use the more system:running-config command.Examples
The following example creates interface bri 1:0 and configures it for X.25 over the ISDN D channel. This example uses dynamic TEIs, not a static TEI.
interface bri1isdn x25 dchannelinterface bri1:0ip address 10.1.1.2 255.255.255.0x25 address 31107000000100x25 htc 1x25 suppress-calling-addressx25 facility windowsize 2 2x25 facility packetsize 256 256x25 facility throughput 9600 9600x25 map ip 10.1.1.3 31107000000200x25 map ip 10.1.1.4 31107000000800Related Commands
interface bri
Configures a BRI interface and enters interface configuration mode.
isdn x25 static-tei
To configure a static ISDN Layer 2 terminal endpoint identifier (TEI) for X.25 over the ISDN D channel, use the isdn x25 static-tei command in interface configuration mode. Use the no form of this command if dynamic TEIs will be used on the interface that is to carry X.25 traffic over the D channel.
isdn x25 static-tei tei-number
no isdn x25 static-tei tei-number
Syntax Description
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies to ISDN BRI interfaces only. Only one static TEI is allowed per BRI interface. If a second static TEI is configured, the first static TEI is overwritten.
Some switches require a static TEI be used for X.25 over the ISDN D channel.
When the isdn x25 dchannel command is invoked without the isdn x25 static-tei command, a dynamic TEI is chosen.
Examples
The following example creates static TEI 8 on the X.25-over-ISDN-D channel:
interface bri0isdn x25 dchannelisdn x25 static-tei 8Because the isdn x25 static-tei command is missing, the following example configuration sets dynamic TEIs for the ISDN channel:
interface bri0isdn x25 dchannelRelated Commands
interface bri
Configures a BRI interface and enters interface configuration mode.
isdn x25 dchannel
Creates a configurable interface for X.25 traffic over the ISDN D channel.
