- A through B
- C
- debounce-time rai through dialer rotor
- dialer string through group-range
- interface bri through isdn busy
- isdn call interface through isdn send-alerting
- isdn sending-complete through loopback remote (controller)
- map-class dialer through modem inout
- modem cts-alarm
- peer default ip address through ppp iphc max-header
- ppp iphc max-period through ppp multilink slippage
- ppp pap wait through rotary-group
- script activation through show dial-shelf
- show dial-shelf split through show nbf cache
- show nbf sessions through show tech-support spe
- show tgrm through x25 map ppp
- isdn sending-complete
- isdn service
- isdn silent-boot
- isdn snmp busyout b-channel
- isdn spid1, isdn spid2
- isd n spoofing
- isdn static-tei
- isdn switch-type (BRI)
- isdn switch-type (PRI)
- isdn t306
- isdn t310
- isdn tei-negotiation (global)
- isdn tei-negotiation (interface)
- isdn test call interface
- isdn test disconnect interface
- isdn test l2 flap interface
- isdn timer
- isdn timer t309
- isdn timer t321
- isdn transfer- code
- isd n transparent
- isdn twait-disable
- isdn v110 only
- isdn v110 padding
- isdn voice-priority
- isdn x25 dchannel
- isdn x25 static-tei
- lte failovertimer
- lte gps mode standalone
- lte gps nmea
- lte sim authenticate
- lte sim max-retry
- lte sim primary
- lte sim profile
- lte sim profile 3gpp 3gpp2
- lte sms archive
- l2tp tunnel retransmit initial retries
- limit base-size
- limit overflow-size
- line-power
- logging event nfas-status
- loopback (controller el)
- loopback local (controller)
- loopback local (interface)
- loopback remote (controller)
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.
Syntax Description
Command Default
Command Modes
Interface configuration (config-if)
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.
Note
The no isdn spoofing command is not applicable when the ISDN BRI interface is configured as a network side.
Examples
In the following example, the isdn sending-complete command applies to an ISDN BRI interface:
The following example enables sending complete IE information on a serial interface:
Related Commands
|
|
|
|---|---|
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 ]
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
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:
The 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:
The following example sets B channels 13 to 24 to the OOS state:
In 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.
Related 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.
Syntax Description
Command Default
The transmission and receipt of ISDN packets by the router is allowed during the bootstrap process.
Command Modes
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:
isdn snmp busyout b-channel
To enable PRI B channels to be busied out via Simple Network Management Protocol (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.
no isdn snmp busyout b-channel
Syntax Description
Command Default
The default value is TRUE; that is, setting busyout using SNMP is allowed.
Command Modes
Interface configuration (config-if)
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:
isdn 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
Command Default
A default SPID number and ISDN local directory numbers are not defined.
Command Modes
Interface configuration (config-if)
Command History
|
|
|
|---|---|
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 terminal endpoint identifiers (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 Some DMS-100 and National ISDN switch installations may be configured as a “hunt group” whereby all calls are initially forwarded to the primary number. Under these circumstances, you should not configure the LDN. You can determine this by enabling the debug isdn q931 command. If the endpoint identifier (EID) information element is delivered in the incoming setup message, then the switch is addressing the TEIs with the EID, instead of the LDN.
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:
The following example shows how to specify that the SPID should be automatically detected, that the primary ISDN local directory number is 4085550111, and that the secondary number is 4085550122:
The following example defines, on the router, a SPID and LDN for the B2 channel:
The following example specifies that the SPID should be automatically detected, that the primary ISDN local directory number is 4085550111, and that the secondary number is 4085550122:
Related Commands
|
|
|
|---|---|
Enables the automatic detection of ISDN SPIDs and switch type. |
isdn spoofing
To enable ISDN spoofing so that loss of Layer 1 or Layer 2 connectivity of the ISDN BRI interface is not detected by the Trunk Group Resource Manager (TGRM) or similar application, use the isdn spoofing command in interface configuration mode. To disable ISDN spoofing so the TGRM or similar application can detect when the BRI interface is not operational (when the Layer 1 or Layer 2 connection is down), use the no form of this command.
Syntax Description
Command Default
The ISDN BRI interface is spoofing, which means that applications always see the BRI interface connection as operational (unless the interface has been manually shut down [ADMINDOWN state]).
Command Modes
Interface configuration (config-if)
Command History
|
|
|
|---|---|
Usage Guidelines
The ISDN BRI interface is spoofing by default. Spoofing makes the ISDN BRI interface available (up) for operation (for dialing in ISDN), even if the interface is down. For an ISDN BRI interface to be set to a down condition, the interface must be manually shut down (IDBS_ADMINDOWN state). Spoofing enables upper layers to dial out even when the interface is down.
Some upper layer modules, such as TGRM and similar applications, allow dial-out only if the channel is available. If the record for TGRM or similar application is notified of the actual status of BRI, then the TGRM or similar application can dial out accordingly. In this case, the no isdn spoofing command is appropriate.
Note ISDN spoofing can be applied only to BRI interfaces—it does not apply to PRI interfaces.
Examples
The following example shows how to configure an ISDN BRI interface to disable ISDN spoofing:
Related Commands
|
|
|
|---|---|
Configures a BRI interface and enters interface configuration mode. |
|
Displays the status of all ISDN interfaces or a specific ISDN interface. |
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.
Syntax Description
Command Default
Command Modes
Interface configuration (config-if)
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 shutdow n 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:
Related Commands
|
|
|
|---|---|
Configures a BRI interface and enters interface configuration mode. |
|
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.
no isdn switch-type switch-type
Syntax Description
ISDN service provider switch type. Table 1 in the “Usage Guidelines” section lists the supported switch types. |
Defaults
Command Modes
Global configuration (config)
Interface configuration (config-if)
Command History
|
|
|
|---|---|
The basic-qsig and primary-qsig s witch type options were added to support BRI QSIG voice signaling. |
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.
Note This command can be entered in either global configuration or interface configuration mode. When entered in global configuration mode, the basic-qsig switch type command specifies that the Cisco MC3810 use QSIG signaling on all BRI interfaces; when entered in interface configuration mode, the command specifies that an individual BRI voice interface use QSIG signaling. The interface configuration mode setting overrides the global configuration setting on individual interfaces.
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:
- Set the global isdn-switch-type command to support Q.SIG and set the interface isdn-switch-type command for interface serial 0:23 to a PRI setting such as 5ess.
- Set the global isdn-switch-type command to support PRI 5ess and set the interface isdn-switch-type command for interface serial 1:23 to support Q.SIG.
- Configure the global isdn-switch-type command to another setting (such as switch type VN3), set the interface isdn-switch-type command for interface serial 0:23 to a PRI setting, and set the interface isdn-switch-type command for interface serial 1:23 to support Q.SIG.
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:
- Enter the isdn switch-type basic-qsig global configuration command, and enter the
isdn switch-type bri-5ess command on interface 0. - Enter the isdn switch-type bri-5ess global configuration command, and enter the
isdn switch-type basic-qsig command on interfaces 1, 2, 3, and 4 individually. - Enter the isdn switch-type bri-5ess command on interface 0, and enter the 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 In the Cisco MC3810, ISDN BRI voice ports support only switch type basic-qsig; ISDN BRI backup ports support all other listed switch types, but not basic-qsig.
Note The dial-peer codec command must be configured before any calls can be placed over the connection to the PINX. The default codec type is G729a.
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 1 lists supported BRI switch types by geographic area.
Examples
The following example configures the French VN3 ISDN switch type:
The 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.
!
interface BRI0
isdn switch-type basic-net3
The following example configures the Cisco MC3810 router to use BRI QSIG signaling for all of its BRI voice ports:
The 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.
isdn 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.
no isdn switch-type switch-type
Syntax Description
Service provider switch type; see Table 2 for a list of supported switches. |
Command Default
The switch type defaults to none, which disables the switch on the ISDN interface.
Command Modes
Global configuration (confi)
Interface configuration (config-if)
Note This command can be entered in either global configuration mode or in interface configuration mode. When entered in global configuration mode, the setting applies to the entire Cisco MC3810. 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.
Command History
|
|
|
|---|---|
The primary-qsig-slave and primary-qsig master switch type options were added to support PRI QSIG signaling. |
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:
- Set the global isdn-switch-type command to support QSIG, and set the interface isdn-switch-type command for the interface bri 0 command to a BRI setting such as 5ess.
- Set the global isdn-switch-type command to support BRI 5ess, and set the interface isdn-switch-type command for the interface serial 1:23 command to support QSIG.
- Configure the global isdn-switch-type command to another setting (such as switch type VN3), and then set the interface isdn-switch-type command for the interface bri 0 command to a BRI setting, and set the interface isdn-switch-type command for the interface serial 1:23 command to support QSIG.
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 2 lists supported PRI switch types by geographic area.
Note If you are using the Multiple ISDN Switch Types feature to apply the ISDN switch types to different interfaces, refer to the chapter “Setting Up Basic ISDN Service” in the Cisco IOS Dial Technologies Configuration Guide for additional details.
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-ni
The following example configures T1 interface 23 on the Cisco AS5300 to support Q.SIG signaling:
Related Commands
|
|
|
|---|---|
Configures the Layer 2 and Layer 3 port protocol of a BRI voice port or a PRI interface to emulate NT (network) or TE (user) functionality. |
|
isdn t306
Note Effective with Cisco IOS Release 12.4(11)T, the isdn t306 command is replaced by the isdn timer command. See the isdn timer command for more information.
To set a timer for disconnect messages sent 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.
Syntax Description
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. |
|
Command Default
Default depends on the switch, usually from 5000 to 30000 ms.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
The T306 timer is designed for routers that are configured as an ISDN network-side switch. When a router sends out 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 default 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:
Related Commands
isdn t310
Note Effective with Cisco IOS Release 12.4(11)T, the isdn t310 command is replaced by the isdn timer command. See the isdn timer command for more information.
To set a timer for the call proceeding state, use the isdn t310 comman in interface configuration mode. To reset to the default, use the no form of this command.
Syntax Description
Time, in milliseconds, that the router waits before disconnecting a call after receiving a call proceeding message. Range is from 1 to 400000. |
Command Default
Default depends on the switch; usually from 5000 to 30000 ms.
Command Modes
Interface configuration (config-if)
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:
Related 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 ]
Syntax Description
(Optional) ISDN TEI negotiation should occur when the first ISDN call is placed or received. |
|
(Optional) ISDN TEI negotiation should occur when the router is powered on. |
Command Default
Command Modes
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 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 }
Syntax Description
Command Default
The powerup state is the default condition. Depending on the ISDN switch type configured, the default action is to preserve or remove the TEI negotiation options.
Command Modes
Interface configuration (config-if)
Command History
|
|
|
|---|---|
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.
Use of the preserve keyword causes different behavior depending on the ISDN switch type configured, that is, the TEI negotiation configured will be preserved during ISDN Layer 1 flaps, and when the clear interface or the shutdown and no shutdown EXEC commands are executed, on the switch types listed in Table 3 .
|
|
|
|---|---|
For all other ISDN switch types, the TEI negotiation will be removed during ISDN Layer 1 flaps, and when the clear interface or the shutdown and no shutdown EXEC commands are executed. Use the remove keyword to specifically set one of the switches listed in Table 3 to the remove state.
The first-call keyword and its functionality are not supported on U.S. switch types (basic-ni, basic-5ess, basic-dms100, primary-ni, primary-4ess, primary-5ess, and primary-dms100), especially for service profile identifier (SPID) negotiations. The first-call keyword and its functionality are supported on European switch types (basic-net3 and primary-net5) to prevent Layer 2 activity when there are no Layer 3 calls.
Examples
The following example shows the ISDN TEI negotiation configuration with default settings. (Defaults settings do not appear in the router configuration.)
The following example shows how to set TEI negotiation timing to the first call:
The following example shows how to change TEI negotiation timing back to the default power-up state:
The 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):
The following example shows how to return the National ISDN basic rate switch to its default preserve state:
isdn 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
(Optional) Line speed (56 or 64 kbps) used for making ISDN data call. |
Command Default
Command Modes
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-0111 and at a line speed of 56 kbps:
Related Commands
|
|
|
|---|---|
Disconnects an ISDN data call without bringing down the interface. |
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 type number { b1 | b2 | all }
Syntax Description
Command Default
Command Modes
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:
Related Commands
|
|
|
|---|---|
isdn test l2 flap interface
To simulate an ISDN Layer 2 interface flap without sending a DISC frame, use the isdn test l2 flap interface command in privileged EXEC mode.
isdn test l2 flap interface serial slot / port
Syntax Description
Specifies the slot and port on the serial interface on which the flap will occur. The slash is required. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Examples
The following example shows how to simulate an ISDN Layer 2 interface flap:
Related Commands
|
|
|
|---|---|
Sends RESTART or STATUS ENQUIRY messages over the ISDN PRI line when a Layer 2 link flap and recovery occurs. |
isdn timer
Note Effective with Cisco IOS Release 12.4(11)T, the isdn timer command replaces the isdn t-activate, isdn t306, isdn t310, isdn timer t309, and isdn timer t321 commands. If any of these replaced commands are entered, the command-line interface responds with a message indicating the new syntax and a request that you update the startup configuration with the running configuration.
To identify and configure an ISDN timer and change the value of the timer for network and call connect and disconnect waiting periods, use the isdn timer command in interface configuration mode. To restore the default value, use the no form of this command.
no isdn timer timer milliseconds
Syntax Description
Command Default
The default values vary according to the type of ISDN timer and, in some cases, are switch-dependent. To restore a specific default value, use the no isdn timer command.
Command Modes
Command History
Usage Guidelines
Selection of the different timers serves different purposes in the ISDN configuration. The functions of the different ISDN timers are as follows:
- t-activate —The T-activate timer starts when the voice gateway sends a Facility message to the public switched telephone network (PSTN). If a response is not received within the specified time, the Tool Command Language (TCL) Interactive Voice Response (IVR) script for Malicious Call Identification (MCID) is notified. Depending on how the script is written, it could reinvoke MCID or perform some other action, such as playing a message if the MCID attempt fails. The ISDN interface must use the NET5 switch type, which is set using the isdn switch-type primary-net5 command. Protocol emulation must be set to user, which is the default for the isdn protocol-emulate command.
- t200 —The T200 timer defines the wait period until the retransmission of a message will occur. This wait period must exceed the time it takes to send a frame and receive its acknowledgment.
- t203 —The T203 timer specifies the maximum wait period between exchanges of Q.921 frames. Although the default is 10,000 ms, most switches allow modification of this timer as needed. In cases of long distances and delay, this timer should be modified for continued operation.
- t300s —The T300S timer is specific to Cisco IOS software configurations. The T300S timer specifies the wait period between attempts to initiate ISDN Layer 2 communication.
- t301 —The T301 timer is configured on the user side and the network side. On the user side, the timer indicates Call Delivered—Alerting Received. On the network side, this timer indicates Call Received—Alerting Received.
- t303 —The T303 timer starts when a calling party initiates call establishment by transferring a setup message on the assigned signaling virtual channel across the interface. If no response to the setup message is received by the user side before the first expiry of the T303 timer, the setup message will be retransmitted and the T303 timer restarted. If the user side has not received any response to the setup message after the final expiry of timer T303, the user side manually clears the call internally.
- t306 —The T306 timer is configured on the network side. The T306 timer defines a wait period only for disconnect messages with a progress indicator of 8. When a router sends out a disconnect message with a progress indicator of 8, it disconnects the call after waiting for the specified number of milliseconds while the in-band announcement or error tone is playing. The timer must be set with sufficient duration for the announcement to be heard or the tone to be recognized.
- t307 —The T307 timer is configured on the network side for BRI switch-types (Primary-net5, Primary-NI, and Primary-NI2C) for Suspend—Remove message processing.
- t309 —The T309 timer defines a wait period before clearing the network connection and releasing the B channel and call reference when a data-link disconnection has occurred. 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, thereby entering the Null state. The T309 timer is mandatory for routers that are configured as ISDN network-side switches. The implementation of the T309 timer is optional for the user side of the network.
- t310 —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.
- t321 —The T321 timer specifies a wait period for D-channel switchover when the primary D channel fails. The T321 timer must be implemented when you use the D-channel backup procedure involving D-channel switchover.
- t322 —The T322 timer facilitates q.931 debug tracing during a flap because this tracing can cause unintended retransmissions. The T322 timer starts when a STATUS-ENQUIRY message is sent. If no response is received before the first expiry of the T322 timer, the STATUS-ENQUIRY message will be retransmitted. If no response is received after the final expiry of timer T322, the call is cleared.
Examples
The following example sets the T309 timer to 60,000 ms (60 seconds) for serial interface 0:24:
The following example sets the T321 timer expiration to 0 ms so that it will never expire for serial interface 0:24:
Related Commands
isdn timer t309
Note Effective with Cisco IOS Release 12.4(11)T, the isdn timer t309 command is replaced by the isdn timer command. See the isdn timer command for more information.
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.
Syntax Description
Number of milliseconds (ms) that the router waits before clearing the network connection, and releasing the B channel and call reference. Values are from 0 to 86,400,000 ms (0 to 86,400 seconds). |
Command Default
Command Modes
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 Setting the timer to 0 causes the timer expiry to become infinite so the wait period never expires.
Examples
The following example sets the T309 timers to 60,000 ms (60 seconds) for serial interface 0:24:
Related Commands
isdn timer t321
Note Effective with Cisco IOS Release 12.4(11)T, the isdn timer t321command is replaced by the isdn timer command. See the isdn timer command for more information.
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.
Syntax Description
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 86,400,000. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The T321 timer must be set 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 Setting the timer to 0 causes the timer expiry to become infinite so that the wait period never expires.
Examples
The following example sets the T321 timers to 25 ms for serial interface 0:23:
Related 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.
Syntax Description
Command Default
Command Modes
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 transparent
To configure an ISDN interface to pass specified cause-code values transparently from VoIP to PSTN on the terminating gateway without mapping the values, use the isdn transparent command in interface configuration mode. To disable the transparent handling of specified cause codes, use the no form of this command.
isdn transparent cause-value cause-value
no isdn transparent cause-value cause-value
Syntax Description
Sends a cause-code value number (submitted as an integer in the range of 1 through 127) to the switch. You can include up to 16 cause-code values in each command. |
Command Default
When the isdn transparent command is not enabled, all ISDN cause-code values are mapped according to the configuration when they are passed from VoIP to PSTN on the terminating gateway.
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
This command must be enabled under the serial D-channel to pass specified cause-code values transparently. The command syntax allows you to configure up to 16 cause-code values to be passed transparently at the terminating gateway.
Examples
The following example shows how to configure the serial D-channel interface 7/7:23 to pass ISDN cause codes 4, 42, and 95 transparently at the terminating gateway:
Related Commands
|
|
|
|---|---|
Specifies a serial interface created on a channelized E1 or channelized T1 controller (for ISDN PRI, CAS, or robbed-bit signaling). |
isdn 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.
Syntax Description
Command Default
Command Modes
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.
Examples
The following example configures a random wait period after a power failure:
isdn 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 }]
Syntax Description
Command Default
Command Modes
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:
isdn v110 padding
To enable the padded V.110 modem speed report required by the V.110 modem standard, use the isdn v110 padding command in interface configuration mode. To disable the padded V.110 modem speed report, use the no form of this command.
Syntax Description
Command Default
Command Modes
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:
isdn 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
Local ISDN directory number assigned by your telephone service provider. |
|
Bump a data call only if there is more than one call to the same destination. |
|
Command Default
A data call is never bumped for an incoming or outgoing voice call.
Command Modes
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:
The 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:
Related 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 [ q931-broadcast ]
no isdn x25 dchannel [ q931-broadcast ]
Syntax Description
(Optional) Enables a gateway to share the same terminal endpoint identifier (TEI) for sending X.25 Set Asynchronous Balanced Mode Extended (SABME) and ITU Q.931 packet mode responses. |
Command Default
Command Modes
Command History
Usage Guidelines
This command creates a new, configurable interface, which can be specified as interface bri x :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 interface BRI 5, 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 and the map statements. To display the new interface, use the more system:running-config command.
The optional q931-broadcast keyword is supported only on the ISDN BRI interface user side. Although regular X.25 and ISDN configuration commands may be sufficient to enable this feature, the Japanese NTT ISDN switch types expect the same TEI to be shared. By default, Cisco gateways will try to use two different TEIs and expect the switch to establish an X.25 link on the TEI that responds. The Japanese NTT switch does not follow this procedure and expects the Cisco router to share the same TEI. Cisco recommends that deployments interworking with the Japanese NTT switch type use the optional q931-broadcast keyword to enable sharing of the TEI and avoid interworking incompatibilities. The optional q931-broadcast keyword can also be used in configurations for other switch types such as the European NET3 that require sharing of the TEIs.
You can verify the X.25 call accept procedure using the debug isdn events , debug isdn command with the optional mgmnt keyword, and debug isdn q931 EXEC commands.
Examples
The following example creates BRI interface 0 and configures it for X.25 over the ISDN D channel. This example uses dynamic TEIs, not a static TEI.
The following is a typical configuration that enables SAPI 0 procedures that accept X.25 calls on the ISDN D channel, on ISDN BRI interface 0:
Related Commands
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
Command Default
Command Modes
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:
Because the isdn x25 static-tei command is missing, the following example configuration sets dynamic TEIs for the ISDN channel:
Related Commands
|
|
|
|---|---|
Configures a BRI interface and enters interface configuration mode. |
|
Creates a configurable interface for X.25 traffic over the ISDN D channel. |
lte failovertimer
To specify the failover timeout value before a switch-over occurs from the primary SIM to the secondary SIM, use the lte failovertimer command in cellular controller configuration mode. To return to the default value, use the no form of this command.
lte failovertimer timeout-period
no lte failovertimer timeout-period
Syntax Description
Specifies the failover timeout value between 1 and 7 minutes. |
Defaults
Command Modes
Cellular controller configuration mode (config-controller)
Command History
|
|
|
|---|---|
Usage Guidelines
If the active SIM loses network connectivity, the active SIM waits for the configured failover time period before it starts the switch-over process to the secondary SIM.
Examples
The following example shows that the failover time period has been configured for 6 minutes:
Related Commands
|
|
|
|---|---|
| Configures an encrypted or unencrypted PIN used to activate the CHV1 code that authenticates a modem. |
|
Applies the configured 3GPP and 3GPP2 profile numbers to a SIM. |
lte gps mode standalone
To enable standalone GPS mode, use the lte gps mode standalone command in controller cellular configuration mode.
Syntax Description
Defaults
Command Modes
Controller cellular configuration mode (config-controller)#
Command History
|
|
|
|---|---|
Usage Guidelines
GPS standalone mode (satellite-based GPS) is supported on the EHWIC-4G-LTE-V, EHWIC-4G-LTE-A, and EHWIC-4G-LTE-G4G modem SKUs and the Cisco 819HG-4G and Cisco 819G-4G LTE ISRs. Once standalone GPS mode is entered, National Marine Electronics Association (NMEA) interface streaming options can be configured with the lte gps nmea command.
Examples
The following example shows how to enable standalone GPS mode and configure NMEA streaming over an IP interface:
Related Commands
|
|
|
|---|---|
Displays the message contents of incoming texts received by a modem. |
|
lte gps nmea
To enable National Marine Electronics Association (NMEA) streaming, use the lte gps nmea command in controller cellular configuration mode. To disable NMEA streaming, use the no form of this command.
For the Cisco 819 ISR, the following command syntax is supported:
For the 4G EHWIC, the following command syntax is supported:
Syntax Description
Specifies NMEA over an asynchronous serial interface on the Cisco 819 ISR. |
Defaults
Command Modes
Controller cellular configuration mode (config-controller)#
Command History
|
|
|
|---|---|
Usage Guidelines
GPS standalone mode (satellite-based GPS) is supported on the EHWIC-4G-LTE-V, EHWIC-4G-LTE-A, and EHWIC-4G-LTE-G4G modem SKUs and the Cisco 819HG-4G and Cisco 819G-4G LTE ISRs. Once standalone GPS mode is entered, NMEA streaming options can be configured with the lte gps nmea command.
Note IP NMEA streaming is supported only on the EHWIC platforms. Both IP and Serial NMEA streaming is supported on the Cisco 819 ISRs.
Examples
The following example shows how to enable standalone GPS mode and configure NMEA streaming over an IP interface on the Cisco 819 ISR:
Related Commands
|
|
|
|---|---|
Displays the message contents of incoming texts received by a modem. |
|
lte sim authenticate
To configure an encrypted or unencrypted Personal Identification Number (PIN) used to activate the Card Holder Verification (CHV1) code that authenticates a modem, use the lte sim authenticate command in cellular controller configuration mode. To remove the PIN, use the no form of this command.
lte sim authenticate [ 0 | 7 ] pin
no lte sim authenticate [ 0 | 7 ] pin
Syntax Description
Specifies that the following PIN is not encrypted (clear text). |
|
| Note The PIN must be four to eight digits if it is encrypted. |
Defaults
Command Modes
Cellular controller configuration (config-controller)
Command History
|
|
|
|---|---|
Usage Guidelines
The configured encrypted or unencrypted PIN is sent to the modem for authentication with each subsequent LTE connection. If authentication passes based on the configured PIN, the data call is allowed. If authentication fails, the modem does not initiate the data call.
Examples
The following example shows the configuration of an encrypted PIN. The username and password is created by configuring password encryption, defining the username and associated password, copying the resulting scrambled password, and using this scrambled password in the SIM authentication command.
Note After the scrambled PIN is obtained and used in SIM authentication, the username created can optionally be deleted from the Cisco IOS configuration.
Related Commands
|
|
|
|---|---|
| Specifies the failover timeout value before a switch-over occurs from the primary SIM to the secondary SIM. |
|
Applies the configured 3GPP and 3GPP2 profile numbers to a SIM card. |
lte sim max-retry
To specify the maximum number of failover retries, use the lte sim max-retry command in controller configuration mode. To return to the default value, use the no form of this command.
Syntax Description
Specifies the maximum number of failover retries from 1 to 65535. |
Defaults
Command Modes
Controller configuration (config-controller)
Command History
|
|
|
|---|---|
Usage Guidelines
The lte sim max-retry command is used in a Dual SIM configuration and functions if a failover situation persists on Cisco 819HG-4G and Cisco 819G-4G LTE ISRs that support 4G LTE cellular and 3G cellular networks.
Examples
The following example configures the ISR for 20 retries:
Related Commands
lte sim primary
To specify the slot number for the primary SIM, use the lte sim primary command in controller configuration mode. To return to the default value, use the no form of this command.
Syntax Description
Defaults
Command Modes
Controller configuration (config-controller)
Command History
|
|
|
|---|---|
Usage Guidelines
The lte sim primary command is used with the Dual SIM, auto-switch and failover functions on Cisco 819HG-4G and Cisco 819G-4G LTE ISRs that support 4G LTE cellular and 3G cellular networks. This feature is enabled by default with SIM slot 0 being the primary slot and slot 1 being the secondary (failover) slot.
Examples
The following example specifies slot 1 for the primary SIM:
Related Commands
lte sim profile
To apply the configured profile number to a Subscriber Identity Module (SIM) card, use the lte sim profile command in cellular controller configuration mode. To remove the profile number, use the no form of this command.
lte sim profile number [ ims number slot { 0 | 1 }]
no lte sim profile number [ ims number slot { 0 | 1 }]
Syntax Description
The IP Multimedia Subsystem (IMS) profile number used to establish a session. |
|
Defaults
Command Modes
Controller configuration (config-controller)
Command History
|
|
|
|---|---|
Usage Guidelines
This command with the ims keyword and number argument is required if dual SIMs are used. An IMS profile number is configured for each SIM from 1 to 6 if you have a MC7750 modem, and 1 to 16 if you have a MC7710 or MC7700 modem.
IMS profiles are used to establish a session, and are part of the modem configuration that is stored in the modem's NVRAM. An IMS network is access-independent and standard-based IP connectivity service that enables different types of multimedia services to end-users using common Internet-based protocols.
Examples
The following example applies the configured profile 2 and IMS profile number 4 to the primary and secondary SIM slots:
Related Commands
lte sim profile 3gpp 3gpp2
To apply the configured 3rd Generation Partnership Project (3GPP) and 3GPP2 profile numbers to a Subscriber Identity Module (SIM) card, use the lte sim profile 3gpp 3gpp2 command in cellular controller configuration mode. To remove the profile number, use the no form of this command.
lte sim profile 3gpp number 3gpp2 number slot { 0 | 1 }
no lte sim profile 3gpp number 3gpp2 number slot { 0 | 1 }
Syntax Description
Defaults
Command Modes
Controller configuration (config-controller)
Command History
|
|
|
|---|---|
Usage Guidelines
This step is required if dual SIMs are used with the 3rd Generation Partnership Project (3GPP) and 3GPP2 authentication technologies. The profile numbers for 3GPP and 3GPP2 are applied to the primary and secondary SIM slot in a dual SIM configuration.
For the MC7750 modem, a maximum of 16 profiles can be supported in 3GPP technology mode (for example, LTE). However, in 3GPP2 technology mode (for example EVDO), the modem is only capable of supporting a maximum of 6 profiles.
Examples
The following example applies the configured 3GPP profile 2 and 3GPP2 profile number 4 to the primary and secondary SIM slots:
Related Commands
lte sms archive
To specify an FTP server folder path to send all incoming and outgoing SMS messages, use the lte sms archive command in global configuration mode. To remove the FTP server folder path, use the no form of this command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Once the folder path is identified, it is appended automatically with an outbox and inbox folder for the path to which SMS messages are sent and received. For example:
Examples
The following example shows the configuration of the SMS FTP server folder path and success messages for the automatic setup of an outbox and inbox for SMS messages:
Device(config)# lte sms archive ftp://172.25.211.175/SMS-LTE
*Jun 30 22:39:15.947: %CELLWAN-5-SMS_OUTBOX_ARCH_DONE:Cellular 0/1/0 archived an outgoing SMS to FTP server successfully
*Jun 30 22:39:15.947: %CELLWAN-5-OUTGOING_SMS_SENT: Cellular 0/1/0 sent an outgoing SMS successfully.
Related Commands
l2tp tunnel retransmit initial retries
To configure the number of times that the router will attempt to send out the initial Layer 2 Tunnel Protocol (L2TP) control packet for tunnel establishment before considering a peer busy, use the l2tp tunnel retransmit initial retries command in VPDN group or VPDN template configuration mode. To restore the default value, use the no form of this command.
l2tp tunnel retransmit initial retries number
no l2tp tunnel retransmit initial retries
Syntax Description
Number of retransmission attempts. Valid values range from 1 to 1000. The default value is 2. |
Command Default
The router will resend the initial L2TP control packet twice.
Command Modes
VPDN group configuration
VPDN template configuration
Command History
|
|
|
|---|---|
This command was implemented on the Cisco 1760, Cisco AS5300, Cisco AS5400, and Cisco AS5800 platforms. |
|
This command was integrated into Cisco IOS Release 12.2(28)SB. |
Usage Guidelines
Use the l2tp tunnel retransmist initial retries command to configure the number of times a device will attempt to resend the initial control packet used to establish an L2TP tunnel.
Examples
The following example configures the router to attempt to send the initial L2TP control packet five times for tunnels associated with the virtual private dialup network (VPDN) group named group1:
Related Commands
limit base-size
To define the base number of simultaneous connections that can be done in a single customer or virtual private dialup network (VPDN) profile, use the limit base-size command in customer profile configuration or VPDN profile configuration mode. To remove the limitation, use the no form of this command.
limit base-size { base-number | all }
no limit base-size { base-number | all }
Syntax Description
Command Default
Command Modes
Customer profile configuration
VPDN profile configuration
Command History
|
|
|
|---|---|
Usage Guidelines
Use the limit base-size command to define the base number of simultaneous connections in a single customer or VPDN profile. The session limit applies to all the physical resource groups and pools configured in a single customer profile. If you want to define the number of overflow calls granted to a customer profile by using the limit overflow-size command, do not use the all keyword in the limit base-size command; instead, specify a base number.
Examples
The following example shows the total number of simultaneous connections limited to a base size of 48:
Related Commands
|
|
|
|---|---|
Defines the number of overflow calls granted to one customer or VPDN profile. |
|
limit overflow-size
To define the number of overflow calls granted to one customer or virtual private dialup network (VPDN) profile, use the limit overflow-size command in customer profile configuration or VPDN profile configuration mode. To remove the overflow configuration, use the no form of this command.
limit overflow-size { overflow-calls | all }
no limit overflow-size { overflow-calls | all }
Syntax Description
Number of overflow calls to grant, in the range from 0 to 1000. Default is 0. |
|
Command Default
Command Modes
Customer profile configuration
VPDN profile configuration
Command History
|
|
|
|---|---|
Usage Guidelines
Use the limit overflow-size customer or VPDN profile configuration command to define the number of overflow calls granted to one customer or VPDN profile. The overflow is not applied if the limit base-size command is set using the all keyword.
Examples
The following example shows 20 overflow calls granted to the customer profile called customer1_isp:
Related Commands
|
|
|
|---|---|
Defines the base number of simultaneous connections that can be done in a single customer or VPDN profile. |
|
line-power
To configure an ISDN BRI port to supply line power to the terminal equipment (TE), use the line-power command in interface configuration mode. To disable the line power supply, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
Usage Guidelines
This command is supported only if an installed BRI voice module (BVM) or BRI VIC is equipped to supply line power (phantom power).
This command is used only on a BRI port operating in NT mode. A BRI port operating in TE mode is automatically disabled as a source of line power, and the line-power command is rejected.
When you use the line-power command, the line power provision is activated on a BRI port if the port is equipped with the hardware to supply line power. When you enter the no line-power command, the line power provision is deactivated on a BRI port.
Note If the BRI port is operating in NT mode, the line-power command will be accepted, but will have no effect if a BVM is not equipped to supply line power.
Examples
The following example configures a BRI port to supply power to an attached TE device (only if the BVM is equipped to supply line power):
logging event nfas-status
To enable the production of log messages when ISDN layer 2 changes occur on NFAS D-channels. (Primary or Backup D-channels up/down, and active/alternate D-channel changes), use the logging event nfas-status command in interface configuration mode. To disable notification, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
This configuration command should be entered on each ISDN serial interface.
This configuration command should be entered when the user wishes to see the NFAS D-channel status changes. Should “logging event link-status” not be configured, no indication may be provided when the NFAS D-channel status changes.
Examples
The following example shows how to enable the production of log messages when ISDN layer 2 changes occur on NFAS D-channels using the logging event nfas-status command.
loopback (controller el)
To loop an entire E1 line (including all channel groups defined on the controller) toward the line and back toward the router or access server, use the loopback command in controller configuration mode. To remove the loop, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
This command is useful for testing the DCE channel service unit/data service unit (CSU/DSU) itself.
To display interfaces currently in loopback operation, use the show interfaces loopback EXEC command.
Examples
The following example configures the loopback test on the E1 line:
Related Commands
|
|
|
|---|---|
loopback local (controller)
To loop an entire T1 line (including all channel groups defined on the controller) toward the line and the router or access server, use the loopback local command in controller configuration mode. To remove the loop, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
This command is useful for testing the DCE channel service unit/data service unit (CSU/DSU) itself.
To display interfaces currently in loopback operation, use the show interfaces loopback EXEC command.
Examples
The following example configures the loopback test on the T1 line:
Related Commands
|
|
|
|---|---|
loopback local (interface)
To loop a channelized T1 or channelized E1 channel group, use the loopback local command in interface configuration mode. To remove the loop, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
This command is useful for looping a single channel group in a channelized environment without disrupting the other channel groups.
To display interfaces currently in loopback operation, use the show interfaces loopback EXEC command.
Examples
The following example configures the loopback test on the T1 line:
loopback local
Related Commands
|
|
|
|---|---|
loopback remote (controller)
To loop packets from a MultiChannel Interface Processor (MIP) through the channel service unit/data service unit (CSU/DSU), over a dedicated T1 link, to the remote CSU at the single destination for this T1 link and back, use the loopback remote command in controller configuration mode. To remove the loop, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
This command applies only when the device supports the remote function. It is used for testing the data communication channels.
For MIP cards, this controller configuration command applies if only one destination exists at the remote end of the cloud, the entire T1 line is dedicated to it, and the device at the remote end is a CSU (not a CSU/DSU). This is an uncommon case; MIPs are not usually used in this way.
To display interfaces currently in loopback operation, use the show interfaces loopback EXEC command.
Examples
The following example configures a remote loopback test:
Related Commands
|
|
|
|---|---|
Feedback