Download to read offline
![C H A P T E R 1
Overview of ISDN Voice Interfaces
This chapter provides an overview of ISDN Basic Rate Interface (BRI) and Primary Rate Interface (PRI)
for support of voice traffic. With those ports so configured, you can do the following:
• Bypass PSTN tariffed services such as trunking and administration.
• Connect your PBXs directly to a Cisco router and route PBX station calls automatically to the WAN.
• Configure a voice interface on a Cisco router to emulate either a terminal-equipment (TE) or
network-termination (NT) interface. All types of PBXs can send calls through a router and deliver
those calls across the customer network.
• Configure Layer 2 operation as point-to-point (static terminal endpoint identifier [TEI]) or
point-to-multipoint (automatic TEI).
• Finding Feature Information, page 1
• Prerequisites for Configuring ISDN Voice Interfaces, page 2
• Restrictions for Configuring ISDN Voice Interfaces, page 2
• Information About ISDN Voice Interfaces, page 3
• Additional References, page 8
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest caveats and
feature information, see Bug Search Tool and the release notes for your platform and software release. To
find information about the features documented in this module, and to see a list of the releases in which each
feature is supported, see the feature information table at the end of this module.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support.
To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
1](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-13-2048.jpg)
![Configuring BRI NT and TE Interfaces
To configure BRI NT and TE interfaces, perform the following steps.
Set up each channel for either user side or network side.Note
SUMMARY STEPS
1. enable
2. configure terminal
3. isdn switch-type switch-type
4. Cisco MC3810
5. no ip address
6. isdn overlap-receiving
7. isdn twait-disable
8. isdn spid1 spid-number [ldn]
9. isdn spid2 spid-number [ldn]
10. isdn incoming-voice {voice | modem}
11. shutdown
12. Do one of the following:
• isdn layer1-emulate user
•
•
• isdn layer1-emulate network
13. no shutdown
14. network-clock-priority {low | high}
15. Cisco MC3810 Only
16. Do one of the following:
• isdn protocol-emulate user
•
•
• isdn protocol-emulate network
17. isdn sending-complete
18. isdn static-tei tei-number
19. isdn point-to-point-setup
20. exit
21. Cisco MC3810
22. Repeat the appropriate steps for the other BRI NT/TE interfaces.
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
19
Basic ISDN Voice-Interface Configuration
Configuring a Router for ISDN BRI Voice-Interface Support](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-31-2048.jpg)
![PurposeCommand or Action
Specifies that there is no IP address for this interface.no ip address
Example:
Router(config-if)# no ip address
Step 5
(Optional) Activates overlap signaling to send to the destination
PBX. In this mode, the interface waits for possible additional
call-control information.
isdn overlap-receiving
Example:
Router(config-if)# isdn overlap-receiving
Step 6
(Optional) Delays a national ISDN BRI switch for a random
length of time before activating the Layer 2 interface at switch
isdn twait-disable
Example:
Router(config-if)# isdn twait-disable
Step 7
startup. Use this command when the ISDN switch type is
basic-ni1. Twait time is enabled by default.
(Optional; TE only) Service-profile identifier (SPID) and optional
local directory number for the B1 channel. Currently, only
isdn spid1 spid-number [ldn]
Example:
Router(config-if)# isdn spid1 40855501220101
Step 8
DMS-100 and NI-1 switch types require SPIDs. Although some
switch types might support a SPID, Cisco recommends that you
set up ISDN service without SPIDs.
(Optional; TE only) Specifies SPID and optional local directory
number for the B2 channel.
isdn spid2 spid-number [ldn]
Example:
Router(config-if)# isdn spid2 40855501220102
Step 9
Configures the port to treat incoming ISDN voice calls as voice
calls that are handled by either a modem or a voice DSP, as
directed by the call-switching module.
isdn incoming-voice {voice | modem}
Example:
Router(config-if)# isdn incoming-voice voice
Step 10
Turns off the port (before setting port emulation).shutdown
Example:
Router(config-if)# shutdown
Step 11
(User side only) Configures Layer 1 port mode emulation and
clock status for the user--that is, the TE (clock slave).
Do one of the following:Step 12
• isdn layer1-emulate user
or
•
(Network side only) Configures Layer 1 port mode emulation
and clock status for the network--that is, the NT (clock master).
•
• isdn layer1-emulate network
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
21
Basic ISDN Voice-Interface Configuration
Configuring a Router for ISDN BRI Voice-Interface Support](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-33-2048.jpg)
![PurposeCommand or Action
Example:
Other Supported Routers
Example:
clear interface bri
slot/port
Example:
Router# clear interface bri 1/1
--Repeat the appropriate steps for the other BRI NT/TE
interfaces.
Step 22
What to Do Next
To complete voice configuration, set up your voice ports and dial peers.Note
Verifying BRI Interfaces
To verify BRI interfaces, perform the following steps (listed alphabetically).
SUMMARY STEPS
1. show controllers bri number or show controllers bri slot/port
2. show interfaces bri
3. show isdn {active [serial-number] | history [serial-number]}
4. show isdn {memory | status | timers
5. show isdn status
6. show running-config
7. show voice port slot/port | summary
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
24
Basic ISDN Voice-Interface Configuration
Configuring a Router for ISDN BRI Voice-Interface Support](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-36-2048.jpg)
![DETAILED STEPS
Step 1 show controllers bri number or show controllers bri slot/port
Use this command to display information about the specified BRI port, connector, or interface card number (location of
voice module) or slot/port (location of voice network module and voice interface card).
Step 2 show interfaces bri
Use this command to display information about the physical attributes of the BRI B and D channels. In the output, look
for the term spoofing , which indicates that the interface presents itself to the Cisco IOS software as operational.
Step 3 show isdn {active [serial-number] | history [serial-number]}
Use this command to display current (active keyword) or both historic and current (history keyword) call information
for all ISDN interfaces or, optionally, a specific ISDN PRI interface (created and configured as a serial interface).
Information displayed includes called number, remote node name, seconds of connect time, seconds of connect time
remaining, seconds idle, and advice of charge (AOC) charging time units used during the call.
Step 4 show isdn {memory | status | timers
Use this command to display information about memory, status, and Layer 2 and Layer 3 timers.
Step 5 show isdn status
Use this command to display the status of all ISDN interfaces, including active layers, timer information, and switch-type
settings.
Step 6 show running-config
Use this command to display basic router configuration.
Step 7 show voice port slot/port | summary
Use this command to display information about BRI voice ports.
Examples
This section provides the following output examples:
Sample Output for the show running-config Command
The following is sample output from a Cisco 2600 series system. Note that BRI1/0 and BRI1/1 are configured
as ISDN user side and BRI2/0 and BRI2/1 are configured as ISDN network side. The table below describes
significant fields shown in this output
Router# show running-config
Building configuration...
Current configuration:
!
version 12.2
!
no service udp-small-servers
service tcp-small-servers
!
hostname Router
!
username xxxx password x 11x5xx07
no ip domain-lookup
ip host Labhost 172.22.66.11
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
25
Basic ISDN Voice-Interface Configuration
Configuring a Router for ISDN BRI Voice-Interface Support](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-37-2048.jpg)
![SUMMARY STEPS
1. show isdn {active [serial-number] | history [serial-number]}
2. show isdn status
3. show vfc slot version
4. show voice port slot/port | summary
DETAILED STEPS
Step 1 show isdn {active [serial-number] | history [serial-number]}
Use this command to display current (active keyword) or both historic and current (history keyword) call information
for all ISDN interfaces or, optionally, a specific ISDN PRI interface (created and configured as a serial interface).
Information displayed includes called number, remote node name, seconds of connect time, seconds of connect time
remaining, seconds idle, and advice of charge (AOC) charging time units used during the call.
Step 2 show isdn status
Use this command to display the status of all ISDN interfaces, including active layers, timer information, and switch-type
settings.
Step 3 show vfc slot version
Use this command to display the version of software residing on the voice feature card in the specified slot.
Step 4 show voice port slot/port | summary
Use this command to display configuration information about a specific voice port.
Troubleshooting Tips
• Verify that you have dial tone and connectivity.
• If you have not configured your device to support Direct Inward Dialing (DID), do the following:
• Dial in to the router and verify that you have dial tone.
• Enter a dual-tone multifrequency (DTMF) digit. If dial tone stops, you have verified two-way voice
connectivity with the router.
• If you have trouble connecting a call and suspect that the problem is associated with voice-port
configuration, do the following:
• Confirm connectivity by pinging the associated IP address.
For more information, see the Cisco IOS IP Configuration Guide chapter on configuring IP.Note
1 Determine if the voice feature card (VFC) is installed correctly.
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
37
Basic ISDN Voice-Interface Configuration
Configuring ISDN PRI Voice-Interface Support](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-49-2048.jpg)
![PurposeCommand or Action
Exits the current mode.exit
Example:
Router(config-if)# exit
Step 14
Verify the QSIG Configuration
To verify the QSIG configuration, perform the following steps (listed alphabetically).
SUMMARY STEPS
1. show call history voice record
2. show cdapi
3. show controllers t1 or show controllers e1
4. show dial-peer voice
5. show isdn
6. show isdn {active [serial-number] | history [serial-number]}
7. show isdn service
8. show isdn status
9. show rawmsg
10. show running-config
11. show voice port slot/port | summary
DETAILED STEPS
Step 1 show call history voice record
Use this command to display information about calls made to and from the router.
Step 2 show cdapi
Use this command to display Call Distributor Application Programming Interface (CDAPI) information.
Step 3 show controllers t1 or show controllers e1
Use this command to display information about T1 and E1 controllers.
Step 4 show dial-peer voice
Use this command to display how voice dial peers are configured.
Step 5 show isdn
Use this command to display information about switch type, memory, status, and Layer 2 and Layer 3 timers.
Step 6 show isdn {active [serial-number] | history [serial-number]}
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
49
Basic ISDN Voice-Interface Configuration
Configuring QSIG Support](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-61-2048.jpg)
![How to Configure Expanded Scope for Cause-Code-Initiated
Call-Establishment Retries
Configuring Expanded Scope for Cause-Code-Initiated Call-Establishment
Retries
To configure expanded scope for cause-code-initiated call-establishment retries, perform the following steps.
SUMMARY STEPS
1. enable
2. configure terminal
3. interface type slot/port
4. isdn negotiate-bchan [resend-setup] [cause-codes {cause-code1 [cause-code2...cause-code16]}]
5. exit
DETAILED STEPS
PurposeCommand or Action
Enters privileged EXEC mode. Enter your password when
prompted.
enable
Example:
Router> enable
Step 1
Enters global configuration mode.configure terminal
Example:
Router# configure terminal
Step 2
Configures an interface type and enters interface configuration
mode for the specified slot/port.
interface type slot/port
Example:
Router(config)# interface serial 0/4
Step 3
Enables the router to accept a B channel that is different from
the B channel requested in the outgoing call-setup message and
specifies the cause codes for which the call is reattempted.
isdn negotiate-bchan [resend-setup] [cause-codes
{cause-code1 [cause-code2...cause-code16]}]
Example:
Router(interface)# isdn negotiate-bchan
resend-setup cause-codes 34 44 63
Step 4
You must have ISDN trunks configured on your router
before you can configure the cause codes.
Note
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
81
Expanded Scope for Cause-Code-Initiated Call-Establishment Retries
How to Configure Expanded Scope for Cause-Code-Initiated Call-Establishment Retries](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-93-2048.jpg)
![How to Configure High-Density Analog and Digital Extension
Module for Voice Fax
Configuring Analog FXS FXO and DID Voice Ports
Perform this task to configure analog FXS/FXO and DID voice ports.
SUMMARY STEPS
1. enable
2. configure terminal
3. voice-port slot/subunit/port
4. shutdown
5. Do one of the following:
• signal {loopStart | groundStart}
•
•
•
• signal did (immediate-start| wink-start | delay-start}
6. cptone locale
7. compand-type {u-law| a-law}
8. input gain decibels
9. output attenuation decibels
10. echo-cancel enable
11. echo-cancel coverage {24| 32 | 48| 64}
12. timeouts initial seconds
13. timeouts interdigit seconds
14. impedance {600c | 600r | 900c | 900r | complex1 | complex2}
15. ring frequency {25 | 50}
16. ring cadence {[pattern01 | pattern02| pattern03 | pattern04 | pattern05 | pattern06 | pattern07 |
pattern08 | pattern09 | pattern10 | pattern11 | pattern12] | define pulse-interval}
17. description string
18. no shutdown
DETAILED STEPS
PurposeCommand or Action
Enables privileged EXEC mode.enableStep 1
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
115
High-Density Analog (FXS, DID, FXO) and Digital (BRI) Extension Module for Voice-Fax (EVM-HD)
How to Configure High-Density Analog and Digital Extension Module for Voice Fax](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-127-2048.jpg)
![PurposeCommand or Action
For EVM-HD-8FXS/DID, adjacent ports 0/1, 2/3, 4/5, and 6/7 share
the same impedance coefficient settings within each pair. If you
change an impedance setting, a message alerts you to the change.
This behavior applies only to EVM-HD-8FXS/DID. It does not
apply to EM-HDA-8FXS.
Note
(Optional) Selects the ring frequency, in Hz, used on the FXS interface.ring frequency {25 | 50}Step 15
Example:
Router(config-voiceport)# ring
frequency 50
• The default is 25.
• This number must match the connected telephony equipment and may
be country-dependent.
• If not set properly, the attached telephony device may not ring or it
may buzz.
(Optional) Specifies an existing pattern for ring, or defines a new one.ring cadence {[pattern01 | pattern02|
pattern03 | pattern04 | pattern05 |
Step 16
• Each pattern specifies a ring-pulse time and a ring-interval time.
pattern06 | pattern07 | pattern08 |
pattern09 | pattern10 | pattern11 |
pattern12] | define pulse-interval}
• The keywords and arguments are as follows:
• pattern01 to pattern12--Preset ring cadence patterns. Enter ring
cadence ? to display ring pattern explanations.
Example:
Router(config-voiceport)# ring
cadence pattern04
• define pulse-interval--User-defined pattern: pulse is a number
(one or two digits, from 1 to 50) specifying ring pulse (on) time
in hundreds of milliseconds, and interval is a number (one or two
digits from 1 to 50) specifying ring interval (off) time in hundreds
of milliseconds.
• The default is the pattern specified by the cptone locale that has been
configured.
Attaches a text string to the configuration that describes the connection for
this voice port.
description string
Example:
Router(config-voiceport)# description
alpha central
Step 17
• string --Character string from 1 to 255 characters in length.
• The default is no text string (describing the voice port) attached to the
configuration.
Activates the voice port.no shutdownStep 18
Example:
Router(config-voiceport)# no shutdown
• If a voice port is not being used, shut the voice port down with the
shutdown command.
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
119
High-Density Analog (FXS, DID, FXO) and Digital (BRI) Extension Module for Voice-Fax (EVM-HD)
Configuring Analog FXS FXO and DID Voice Ports](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-131-2048.jpg)
![SUMMARY STEPS
1. enable
2. configure terminal
3. isdn switch-type switch-type
4. network-clock-participate slot slot-number
5. network-clock-select priority {bri | t1| e1} slot/port
6. Do one of the following:
• interface bri slot/port
•
•
•
• interface bri slot/subslot/port
7. isdn overlap-receiving
8. isdn twait-disable
9. isdn spid1 spid-number [ldn]
10. isdn spid2 spid-number [ldn]
11. isdn incoming-voice voice
12. shutdown
13. isdn layer1-emulate {user| network}
14. Do one of the following:
• line-power
•
•
• no line-power
15. no shutdown
16. isdn protocol-emulate {user| network}
17. isdn sending-complete
18. isdn static-tei tei-number
19. end
20. clear interface slot|port
DETAILED STEPS
PurposeCommand or Action
Enables privileged EXEC mode.enableStep 1
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
122
High-Density Analog (FXS, DID, FXO) and Digital (BRI) Extension Module for Voice-Fax (EVM-HD)
Configuring ISDN BRI Digital Interfaces](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-134-2048.jpg)
![PurposeCommand or Action
• port --Identifies the location of the BRI VIC in the voice network
module. Range is 0 to 7:
•
•
• • Port 0 to 3 for EM-4BRI installed in EM0.
• interface bri slot/subslot/port
• Port 4 to 7 for EM-4BRI installed in EM1.
Example:
Router(config)# interface bri 2/0
For the Cisco 2800 series, there are two kinds of port numbering:
slot / port and slot / subslot / port. The first example shows that the
network module is in slot 2. The second example shows that the
VIC2-2BRI is in HWIC slot 1. The first 0 means the module is on
the motherboard, the 1 means it is in HWIC slot 1, and the last 0
means it is the first BRI interface on VIC2-2BRI.
Note
Example:
Example:
Example:
Example:
Router(config)# interface bri 0/1/0
(Optional) Activates overlap signaling to send to the destination PBX.isdn overlap-receivingStep 7
Example:
Router(config-if)# isdn
overlap-receiving
• In this mode, the interface waits for possible additional call-control
information.
(Optional) Delays a National ISDN BRI switch a random time before
activating the Layer 2 interface when the switch starts up.
isdn twait-disable
Example:
Router(config-if)# isdn
twait-disable
Step 8
• Use this command when the ISDN switch type is basic-ni1.
(Optional) Specifies a SPID and optional local directory number for the B1
channel.
isdn spid1 spid-number [ldn]
Example:
Router(config-if)# isdn spid1 12
Step 9
This command applies to TE configuration
only.
Note
• The spid-number argument identifies the service to which you have
subscribed. This value is assigned by the ISDN service provider and
is usually a 10-digit telephone number with additional digits such as
40855501000101.
• (Optional) The ldnargument is a seven-digit number assigned by the
service provider. You can optionally specify a second and third LDN.
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
124
High-Density Analog (FXS, DID, FXO) and Digital (BRI) Extension Module for Voice-Fax (EVM-HD)
Configuring ISDN BRI Digital Interfaces](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-136-2048.jpg)
![PurposeCommand or Action
• Only the DMS-100 and NI-1 switch types require SPIDs.
• Although some switch types might support a SPID, Cisco recommends
that you set up ISDN service without SPIDs.
(Optional) Specifies a SPID and optional local directory number for the B2
channel.
isdn spid2 spid-number [ldn]
Example:
Router(config-if)# isdn spid2 13
Step 10
This command applies to TE configuration
only.
Note
• The spid-number argument identifies the service to which you have
subscribed. This value is assigned by the ISDN service provider and
is usually a ten-digit telephone number with additional digits such as
40855501000101.
• (Optional) The ldnargument is a seven-digit number assigned by the
service provider. You can optionally specify a second and third LDN.
Configures the port to treat incoming ISDN voice calls as voice calls that
are handled by either a modem or a voice DSP, as directed by the
call-switching module.
isdn incoming-voice voice
Example:
Router(config-if)# isdn
incoming-voice voice
Step 11
(Optional) Resets the interface.shutdownStep 12
Example:
Router(config-if)# shutdown
• Do this before setting the port emulation.
(Optional) Configures the Layer-1 port-mode emulation and clock settings.isdn layer1-emulate {user| network}Step 13
Example:
Router(config-if)# isdn
layer1-emulate network
• Enter userto configure the port as TE and to function as a clock slave.
This is the default.
• Enter network to configure the port as NT and to function as a clock
master.
Turns on or off the power supplied from an NT-configured port to a TE
device.
Do one of the following:Step 14
• line-power
•
•
• no line-power
Example:
Router(config-if)# line-power
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
125
High-Density Analog (FXS, DID, FXO) and Digital (BRI) Extension Module for Voice-Fax (EVM-HD)
Configuring ISDN BRI Digital Interfaces](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-137-2048.jpg)
![C H A P T E R 6
Integrated Data and Voice Services for ISDN PRI
Interfaces on Multiservice Access Routers
This chapter describes how to configure ISDN PRI interfaces to support the integration of data and voice
calls on multiservice access routers. This feature enables data (dial-in, dial-on-demand routing [DDR], and
DDR backup) and voice call traffic to occur simultaneously from the supported ISDN PRI interfaces. You
can also enable multilevel precedence and preemption (MLPP) for DDR calls over the active voice call when
no idle channel is available during the DDR call setup.
Feature History for Integrated Data and Voice Services for ISDN PRI Interfaces
ModificationRelease
This feature was introduced.12.4(4)XC
This feature was integrated into Cisco IOS Release
12.4(9)T.
12.4(9)T
• Finding Feature Information, page 134
• Prerequisites for Integrated Data and Voice Services for ISDN PRI Interfaces, page 134
• Restrictions for Integrated Data and Voice Services for ISDN PRI Interfaces, page 135
• Information About Integrated Data and Voice Services for ISDN PRI Interfaces, page 136
• How to Configure Integrated Data and Voice Services for ISDN PRI Interfaces, page 139
• Troubleshooting Tips for Integrated Data and Voice Services, page 154
• Configuration Examples for Integrated Data and Voice Services for ISDN PRI Interfaces, page 155
• Additional References, page 169
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
133](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-145-2048.jpg)
![The tone timer defines the expiry timer for the preemption tone for the outgoing voice call, which is being
preempted by a DDR backup call. When the tone timer expires, the call is disconnected.
During dial-on-demand routing (DDR) call setup, an idle B channel is selected from the trunk group. The
trunk group and preemption level are configured as part of a map class, which can be attached to a dialer map
or dialer string. By default, the preemption level of dialer calls is set to the lowest level (routine) to disable
the MLPP service for a DDR call.
The trunk group preemption level is configured as part of a map class, which can be attached to a dialer map
or dialer string.
• For legacy DDR, configure the dialer interface to associate the class parameter with the dialer in-band
and dialer map commands.
• For dialer profiles, configure the dialer interface to associate the class parameter with the dialer pool
and dialer string commands.
For TDM-only calls, or for calls that are hairpinned, the preemption tone is not heard as the DSPs are dropped.
For this reason, you must disable TDM hairpinning on the voice card to use the MLPP DDR backup call
preemption feature.
The preemption level of an outgoing voice call is defined from the outbound POTS dial peer. The preemption
level defines the preemption priority level of an outgoing voice call.
ISDN call failures are most commonly attributed to dial-on-demand routing (DDR), ISDN layers 1, 2, and 3,
and Point-to-Point Protocol (PPP), including link control protocol (LCP), Authentication, or IP Control
Protocol (IPCP)-related issues.
Integrated Services for Multiple Call Types
ISDN interfaces can support both data calls and voice calls. Typically, this is done using one interface for
data and another for voice. This feature enables data (dial-in, dial-on-demand routing [DDR], and DDR
backup) and voice call traffic to occur simultaneously from the supported ISDN PRI interfaces. To enable
integrated services, the interface used for incoming voice calls is configured to accept multiple voice call
types.
The figure below shows an ISDN network configured for integrated data and voice services.
Figure 5: Integrated Voice with DDR Interface for WAN Failure Backup
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
137
Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers
Integrated Services for Multiple Call Types](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-149-2048.jpg)
![PurposeCommand or Action
Enables the serial interface for integrated mode, which allows
data and voice call traffic to occur simultaneously.
isdn integrate calltype all
Example:
Router(config-if)# isdn integrate calltype
all
Step 5
This configuration disables the voice option for the
isdn incoming-voicecommand on the interface.
Note
Returns the interface to the active state.no shutdown
Example:
Router(config-if)# no shutdown
Step 6
Creating a Trunkgroup and Configuring Maximum Calls Based on Call Type
Use the following procedure to create a trunk group and configure maximum calls based on call type.
If trunk groups are not configured, data and voice calls are treated as first-come first-served.Note
SUMMARY STEPS
1. enable
2. configure terminal
3. trunk group name
4. max-calls {any | d at a| voice} number [direction [in | out]]
DETAILED STEPS
PurposeCommand or Action
Enables privileged EXEC mode.enableStep 1
Example:
Router> enable
• Enter your password if prompted.
Enters global configuration mode.configure terminal
Example:
Router# configure terminal
Step 2
Defines a trunk group and enters trunk group configuration mode.trunk group nameStep 3
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
144
Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers
Configuring the ISDN PRI Interface for Multiple Call Types](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-156-2048.jpg)
![PurposeCommand or Action
Example:
Router(config)# trunk group 20
• name --Name of the trunk group. Valid names contain a maximum of
63 alphanumeric characters.
Defines the maximum number of dial-in or DDR data calls, or voice calls
(incoming or outgoing) that can be accepted.
max-calls {any | d at a| voice} number
[direction [in | out]]
Step 4
Example:
Router(config-trunk-group)#
max-calls data 100 direction out
• any --Assigns the maximum number of calls that the trunk group can
handle, regardless of the call type.
• data --Assigns the maximum number of data calls to the trunk group.
• voice --Assigns the maximum number of voice calls to the trunk group.
• number --Specifies number of allowed calls. Range is from 0 to 1000.
• direction --(Optional) Specifies direction of calls.
• in --(Optional) Allows only incoming calls.
• out --(Optional) Allows only outgoing calls.
Examples
See the following sample configurations for the max-calls command:
• This example configuration for trunk group 1 accepts up to a maximum of 7 dial-in data or DDR calls
and places no restriction on voice calls:
trunk group 1
max-calls data 7
• This sample configuration for trunk group 2 accepts up to a maximum of 2 data dial-in, 3 DDR calls,
and 16 voice calls in any direction:
trunk group 2
max-calls data 2 direction in
max-calls data 3 direction out
max-calls voice 16
• This sample configuration for trunk group 3 accepts up to a maximum of 10 incoming voice and dial-in
data calls.
trunk group 3
max-calls any 10 direction in
Disabling Integrated Services
Use the following procedure to remove the integrated services option from the interface.
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
145
Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers
Configuring the ISDN PRI Interface for Multiple Call Types](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-157-2048.jpg)
![Associating the Class Parameter on the Dialer Interface
Use the following procedure to associate the class parameter on the dialer interface.
or
dialer string dial-string class class-name
SUMMARY STEPS
1. enable
2. configure terminal
3. interface dialer dialer-rotary-group-number
4. Do one of the following:
• dialer in-band [no-parity| odd-parity]
• dialer pool number
5. Do one of the following:
• dialer map protocol-keyword protocol-next-hop-address [name host-name] [speed 56| speed
64] [broadcast] class dialer-map-class-name [dial-string[: isdn-subaddress]]
•
•
•
• dialer string dial-string [ class class name]
DETAILED STEPS
PurposeCommand or Action
Enables privileged EXEC mode.enableStep 1
Example:
Router> enable
• Enter your password if prompted.
Enters global configuration mode.configure terminal
Example:
Router# configure terminal
Step 2
Defines a dialer rotary group.interface dialer
dialer-rotary-group-number
Step 3
• dialer-rotary-group-number-- Number of the dialer rotary group. The
range is 0 to 255.
Example:
Router(config)# interface dialer 10
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
150
Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers
Configuring MLPP Call Preemption over Outgoing Voice Calls](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-162-2048.jpg)
![PurposeCommand or Action
Specifies that dial-on-demand routing (DDR) is to be supported on this interface.Do one of the following:Step 4
• dialer in-band [no-parity|
odd-parity]
• no-parity --(Optional) No parity is to be applied to the dialer string that
is sent out to the modem on synchronous interfaces.
• odd-parity --(Optional) Dialed number has odd parity (7-bit ASCII
characters with the eighth bit as the parity bit) on synchronous interfaces.
• dialer pool number
Example:
Router(config-if)# dialer in-band
or
Specifies, for a dialer interface, which dialing pool to use to connect to a specific
destination subnetwork.
Example:
Router(config-if)# dialer pool 1
• number --The dialing pool number. The range is 1 to 255.
Configures an ISDN interface to place a call to multiple sites and to
authenticate calls from multiple sites.
Do one of the following:Step 5
• dialer map protocol-keyword
protocol-next-hop-address [name • protocol-keyword protocol-next-hop-address --For ISDN services, you
must use ip for the protocol-keyword.host-name] [speed 56| speed 64]
[broadcast] class
• name host-name --(Optional) The remote system with which the local
router or access server communicates. Used for authenticating the remote
dialer-map-class-name [dial-string[:
isdn-subaddress]]
system on incoming calls. The host-name argument is a case-sensitive
name or ID of the remote device. For routers with ISDN interfaces, if•
calling line identification--sometimes called CLID, but also known as•
caller ID and automatic number identification (ANI)--is provided, the•
host-name argument can contain the number that the calling line ID
provides.
• dialer string dial-string [ class
class name]
• speed 56 | speed 64--(Optional) Keyword and value indicating the line
speed in kbps to use. Used for ISDN only. The default speed is 64 kbps.
Example:
Router(config-if)# dialer map ip
• broadcast --(Optional) Forwards broadcasts to the address specified with
the protocol-next-hop-address argument.
172.22.82.2 name gw3845 class dial1
20009 • class dialer-map-class-name--Dialer map class name.
Example:
Router(config-if)# dialer string
4081234 class test
• dial-string : isdn-subaddress ] --(Optional) Dial string (telephone
number) sent to the dialing device when it recognizes packets with the
specified address that matches the configured access lists, and the optional
subaddress number used for ISDN multipoint connections. The colon is
required for separating numbers. The dial string and ISDN subaddress,
when used, must be the last item in the command line.
or
Specifies the string (telephone number) to be used when placing a call from an
interface.
• dial-string --Telephone number to be sent to a DCE device.
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
151
Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers
Configuring MLPP Call Preemption over Outgoing Voice Calls](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-163-2048.jpg)
![PurposeCommand or Action
Example:
Router> enable
• Enter your password if prompted.
Enters global configuration mode.configure terminal
Example:
Router# configure terminal
Step 2
Enters voice-card configuration mode to configure a voice card.voice-card slotStep 3
Example:
Router(config)# voice-card 1
• slot --Slot number for the card to be configured.
Valid entries vary by router platform; enter the show
voice port summary command for available values.
Note
Disables TDM hairpinning.no local-bypass
Example:
Router(config-voicecard)# no local-bypass
Step 4
Configuring the POTS Dial Peer for Outgoing Voice Calls
Use the following procedure to set the preemption level for outgoing voice calls on a POTS dial peer.
SUMMARY STEPS
1. enable
2. configure terminal
3. dial-peer voice tag pots
4. trunkgroup name [preference-number]
5. preemption level {flash-override | fla s h| immediate| priority| routine}
DETAILED STEPS
PurposeCommand or Action
Enables privileged EXEC mode.enableStep 1
Example:
Router> enable
• Enter your password if prompted.
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
153
Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers
Configuring MLPP Call Preemption over Outgoing Voice Calls](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-165-2048.jpg)
![PurposeCommand or Action
Enters global configuration mode.configure terminal
Example:
Router# configure terminal
Step 2
Defines a particular dial peer, specifies the method of voice encapsulation,
and enters dial-peer configuration mode.
dial-peer voice tag pots
Example:
Router(config)# dial-peer voice 25
pots
Step 3
• tag --Digits that define a particular dial peer. The range is from 1 to
2147483647.
• pots --Indicates that this is a POTS peer that uses VoIP encapsulation
on the IP backbone.
Defines the trunk group associated with this dial peer.trunkgroup name [preference-number]Step 4
Example:
Router(config-dial-peer)# trunkgroup
1
• name --Label of the trunk group to use for the call. Valid trunk group
names contain a maximum of 63 alphanumeric characters.
• preference-number --Preference or priority of the trunk group. Range
is from 1 (highest priority) to 64 (lowest priority).
Sets the preemption level of the selected outbound dial peer. Voice calls
can be preempted by a DDR call with a higher preemption level. The default
is routine.
preemption level {flash-override | fla s
h| immediate| priority| routine}
Example:
Router(config-dial-peer)# preemption
level flash
Step 5
• flash-override --Level 0 (highest)
• flash --Level 1
• immediate --Level 2
• priority --Level 3
• routine --Level 4 (lowest)
The preemption level flash-override setting can prevent the call
to be preempted by a DDR call.
Note
Troubleshooting Tips for Integrated Data and Voice Services
Use the following commands to troubleshoot integrated data and voice for ISDN interfaces:
• debug dialer events --Used to display debugging information about the packets received on a dialer
interface.
• debug isdn q931 --Used to check outgoing dial-peer matching for an ISDN incoming call. Enable this
command on both sides of the call. The output indicates whether the messages are generated by the
calling party router (indicated by TX ->) or by the called party router (indicated by RX <-).
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
154
Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers
Troubleshooting Tips for Integrated Data and Voice Services](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-166-2048.jpg)
![PeerIfIndex=161
LogicalIfIndex=160
DisconnectCause=8
DisconnectText=preemption (8)
ConnectTime=286160 ms
DisconnectTime=441190 ms
CallDuration=00:02:35 sec
CallOrigin=2
ReleaseSource=7
InternalErrorCode=1.1.8.11.35.0
ChargedUnits=0
InfoType=speech
TransmitPackets=0
TransmitBytes=0
ReceivePackets=6910
ReceiveBytes=1105600
TELE:
ConnectionId=[0x4E9D9EF1 0x23E411DA 0x8002A31F 0xB25BECEF]
IncomingConnectionId=[0x4E9D9EF1 0x23E411DA 0x8002A31F 0xB25BECEF]
CallID=1
TxDuration=0 ms
VoiceTxDuration=0 ms
FaxTxDuration=0 ms
CoderTypeRate=g711ulaw
NoiseLevel=0
ACOMLevel=0
SessionTarget=
ImgPages=0
CallerName=
CallerIDBlocked=False
OriginalCallingNumber=7002
OriginalCallingOctet=0x0
OriginalCalledNumber=
OriginalCalledOctet=0x80
OriginalRedirectCalledNumber=
OriginalRedirectCalledOctet=0x0
TranslatedCallingNumber=7002
TranslatedCallingOctet=0x0
TranslatedCalledNumber=
TranslatedCalledOctet=0x80
TranslatedRedirectCalledNumber=
TranslatedRedirectCalledOctet=0x0
GwCollectedCalledNumber=2000
GwReceivedCallingNumber=7002
GwReceivedCallingOctet3=0x0
GwReceivedCallingOctet3a=0x0 GENERIC:
SetupTime=282800 ms
Index=2
PeerAddress=2000
PeerSubAddress=
PeerId=2001
PeerIfIndex=144
LogicalIfIndex=42
DisconnectCause=8
DisconnectText=preemption (8)
ConnectTime=286160 ms
DisconnectTime=441210 ms
CallDuration=00:02:35 sec
CallOrigin=1
ReleaseSource=7
InternalErrorCode=1.1.8.11.35.0
ChargedUnits=0
InfoType=speech
TransmitPackets=6910
TransmitBytes=1160880
ReceivePackets=6917
ReceiveBytes=1106720
TELE:
ConnectionId=[0x4E9D9EF1 0x23E411DA 0x8002A31F 0xB25BECEF]
IncomingConnectionId=[0x4E9D9EF1 0x23E411DA 0x8002A31F 0xB25BECEF]
CallID=2
TxDuration=0 ms
VoiceTxDuration=0 ms
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
168
Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers
Disconnect Cause Example](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-180-2048.jpg)
![You must configure network clock source and participation to use the Integrated Voice and Data WAN
on T1/E1 Interfaces Using the AIM-ATM-VOICE-30 Module feature.
Note
Before You Begin
Configure the controller for PRI or DS0 groups and for ATM AIM or CAS before configuring network-clock
participation parameters.
SUMMARY STEPS
1. enable
2. configure terminal
3. controller {t1 | e1} slot/port
4. clock source {line [primary] | internal}
5. mode atm [aim aim-slot-number]
6. exit
7. network-clock-participate [slot slot-number | wic wic-slot | aim aim-slot-number]
8. exit
DETAILED STEPS
PurposeCommand or Action
Enters privileged EXEC mode. Enter your password when prompted.enable
Example:
Router> enable
Step 1
Enters configuration mode.configure terminal
Example:
Router# configure terminal
Step 2
Enters controller configuration mode on the T1 or E1 controller on the
selected slot/port.
controller {t1 | e1} slot/port
Example:
Router(config)# controller t1 1/0
Step 3
Specifies the source from which the phase-locked loop (PLL) on this port
derives its clocking and, if the source is line, whether this port is the
primary source. Arguments and keywords are as follows:
clock source {line [primary] | internal}
Example:
Router(config-controller)# clock
source internal
Step 4
• line --Clock recovered from the line’s receive data stream. This is
the default.
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
178
Integrated Voice and Data WAN on T1 E1 Interfaces
Configuring Network Clock Source and Participation](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-190-2048.jpg)
![PurposeCommand or Action
• primary --External source to which the port is connected. This
option also puts a second port, which is generally connected to the
PBX, into looped-time mode. Both ports are configured with line,
but only the port connected to the external source is configured with
primary.
• internal --T1 or E1 controller internal PLL.
With the default, the clock source does not appear in the show
running-config command output. Use the show controllers
command to display the current source for a port.
Note
Specifies that the configuration on this controller is for ATM, using the
AIM in the specified slot for ATM processing, and creates ATM interface
mode atm [aim aim-slot-number]
Example:
Router(config-controller)# mode atm
aim 0
Step 5
0. Use when you connect the T1 line to an ATM network. The argument
is as follows:
• aim-slot-number --AIM slot number on the router chassis:
• Cisco 2600 series: 0
• Cisco 3660 and Cisco 3700 series: 0 or 1
This command without the aim keyword uses software rather
than the AIM to perform ATM SAR. This is supported on Cisco
2600 series WIC slots only and not on network module slots.
Note
Exits the current mode.exit
Example:
Router(config-controller)# exit
Step 6
Allows the network module or VWIC in the specified slot to use the
network clock for its timing. Keywords depend on platform.
network-clock-participate [slot
slot-number | wic wic-slot | aim
aim-slot-number]
Step 7
Example:
Router(config)#
network-clock-participate slot 5
Example:
Router(config)#
network-clock-participate wic 0
Example:
Router(config)#
network-clock-participate aim 0
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
179
Integrated Voice and Data WAN on T1 E1 Interfaces
Configuring Network Clock Source and Participation](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-191-2048.jpg)
![PurposeCommand or Action
Exits the current mode.exit
Example:
Router(config)# exit
Step 8
Configuring the Clock-Source Line
To configure the clock-source line, perform the following steps.
SUMMARY STEPS
1. enable
2. configure terminal
3. controller {t1 | e1} slot/port
4. clock source {line [primary] | internal}
5. Do one of the following:
• mode atm [aim aim-slot]
•
•
• mode cas
•
•
• ds0-group group-number timeslots timeslot-range type type
•
•
• pri-group timeslots timeslot-range
6. exit
7. network-clock-participate [slot slot-number | wic wic-slot| aim aim-slot-number]
8. network-clock-select priority {t1 | e1} slot/port
9. exit
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
180
Integrated Voice and Data WAN on T1 E1 Interfaces
Configuring Network Clock Source and Participation](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-192-2048.jpg)
![DETAILED STEPS
PurposeCommand or Action
Enables privileged EXEC mode. Enter your password if prompted.enable
Example:
Router> enable
Step 1
Enters global configuration mode.configure terminal
Example:
Router# configure terminal
Step 2
Enters controller configuration mode on the T1 or E1 controller on the
specified slot/port.
controller {t1 | e1} slot/port
Example:
Router(config)# controller t1 1/0
Step 3
Specifies the source from which the phase-locked loop (PLL) on this port
derives its clocking and, if the source is line, whether this port is the primary
source. Keywords are as follows:
clock source {line [primary] | internal}
Example:
Router(config-controller)# clock source
line
Step 4
• line --Clock recovered from the line’s receive data stream. This is the
default.
• primary --External source to which the port is connected. This option
also puts a second port, which is generally connected to the PBX, into
looped-time mode. Both ports are configured with line, but only the
port connected to the external source is configured with primary.
• internal --T1 or E1 controller internal PLL.
With the default, the clock source does not appear in the show
running-config command output. Use the show controllers
command to display the current source for a port.
Note
(mode atm command) Sets the controller to ATM mode and creates ATM
interface ATM 0. Use for Cisco 2600 series, Cisco 3660, and Cisco 3700
Do one of the following:Step 5
• mode atm [aim aim-slot]
series that use an AIM for ATM processing. Do not use on routers that use
an AIM only for DSP resources.•
• This command without the aim keyword uses software (rather
than AIM) to perform ATM segmentation and reassembly. This
is supported on Cisco 2600 series WIC slots only and is not
supported on network module slots.
Note
or
• mode cas
•
•
• ds0-group group-number timeslots
timeslot-range type type
(mode cas command) Sets the controller to CAS mode (for software images
earlier than Cisco IOS Release 12.2(15)T). Use for Cisco 2600 series with
WIC slots.•
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
181
Integrated Voice and Data WAN on T1 E1 Interfaces
Configuring Network Clock Source and Participation](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-193-2048.jpg)
![PurposeCommand or Action
Exits the current mode.exit
Example:
Router(config-controller)#
exit
Step 6
Allows the network module or VWIC in the specified slot to use the network
clock for its timing. Keywords depend on platform.
network-clock-participate [slot
slot-number | wic wic-slot| aim
aim-slot-number]
Step 7
Example:
Router(config)#
network-clock-participate wic 0
Example:
Router(config)# network-clock-participate
slot 5
Specifies a slot/port to be used as a timing source for the network clock
and the priority level for that port. The source that is given the highest
network-clock-select priority {t1 | e1}
slot/port
Step 8
priority is designated the primary source and is used first; if it becomes
Example:
Router(config)# network-clock-select 1
e1 0/1
unavailable, the source with the second-highest priority is used, and so
forth. This command is required if the clock source is from the line. The
clocking is provided to the AIM, which then provides it to participating
slots in the router. Keywords and arguments are as follows:
• priority --Priority for the clock source (1 is highest priority)
• t1 or e1--T1 or E1 ports
• slot/port --Slot and port for the controller clock source. Slots are as
follows:
• Cisco 2600 series and Cisco 2600XM--0 (built-in WIC slot) or
1 (network module slot)
• Cisco 3660--1 to 6
• Cisco 3725 and Cisco 3745--1 to 4
Exits the current mode.exit
Example:
Router(config)# exit
Step 9
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
183
Integrated Voice and Data WAN on T1 E1 Interfaces
Configuring Network Clock Source and Participation](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-195-2048.jpg)
![Configuring Integrated Voice and Serial Data WAN
To configure integrated voice and serial data WAN, perform the following steps.
SUMMARY STEPS
1. enable
2. configure terminal
3. controller {t1 | e1} slot/port
4. clock source {line [primary] | internal}
5. channel-group channel-group-number timeslots timeslot-range [speed bit-rate] aim aim-slot-number
6. Do one of the following:
• ds0-group ds0-group-number timeslots timeslot-range type type
•
•
• pri-group timeslots timeslot-range | d-channel timeslot| rlm-timeslot timeslot number]
7. no shutdown
8. exit
DETAILED STEPS
PurposeCommand or Action
Enters privileged EXEC mode. Enter your password when prompted.enable
Example:
Router> enable
Step 1
Enters global configuration mode.configure terminal
Example:
Router# configure terminal
Step 2
Enters controller configuration mode on the T1 or E1 controller on the
specified slot/port. The example shows a VWIC E1 card installed in WIC
slot 0.
controller {t1 | e1} slot/port
Example:
Router(config)# controller e1 0/1
Step 3
Specifies the source from which the phase-locked loop (PLL) on this
port derives its clocking and, if the source is line, whether this port is the
primary source. Arguments and keywords are as follows:
clock source {line [primary] | internal}
Example:
Router(config-controller)# clock source
internal
Step 4
• line --Clock recovered from the line’s receive data stream. This is
the default.
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
186
Integrated Voice and Data WAN on T1 E1 Interfaces
Configuring Integrated Voice and Serial Data WAN](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-198-2048.jpg)
![PurposeCommand or Action
• primary --External source to which the port is connected. This
option also puts a second port, which is generally connected to the
PBX, into looped-time mode. Both ports are configured with line,
but only the port connected to the external source is configured
with primary.
• internal --T1 or E1 controller internal PLL.
With the default, the clock source does not appear in the show
running-config command output. To display the current source
for a port, use the show controllers command.
Note
Directs HDLC traffic from the T1/E1 interface to the
AIM-ATM-VOICE-30 digital signaling processor (DSP) card. Use to
channel-group channel-group-number
timeslots timeslot-range [speed bit-rate] aim
aim-slot-number
Step 5
specify T1/E1 timeslots to be used for HDLC/PPP/Frame-relay
encapsulated data.
Example:
Router(config-controller)# channel-group
1 timeslots 1-5 aim 0
(DS0 groups) Creates a DS0 group that makes up a logical voice port on
a T1/E1 controller. Keywords and arguments are as follows:
Do one of the following:Step 6
• ds0-group ds0-group-number
timeslots timeslot-range type
type
• timeslot timeslot-range --Number, range of numbers, or multiple
ranges of numbers separated by commas. T1 range: 1 to 24. E1
range: 1 to 31.
•
• type type -- Signaling type by which the router communicates
with the PBX or PSTN.
•
• pri-group timeslots timeslot-range
| d-channel timeslot| rlm-timeslot
timeslot number] High-complexity codecs with the AIM-ATM-VOICE-30 module
can process up to 16 voice channels.
Note
or
Example:
Router(config-controller)# ds0-group 2
timeslots 6-12 type e&m-immediate-start
(PRI groups) Creates a PRI group that makes up a logical voice port on
a channelized T1 or E1 controller. The keyword and argument are as
follows:
• timeslot timeslot-range --Range of numbers. T1 range: 1 to 23.
E1 range: 1 to 15.Example:
Only one PRI group can be configured on a
controller.
Note
Example:
Example:
Router(config-controller)# pri-group
timeslots 6-23
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
187
Integrated Voice and Data WAN on T1 E1 Interfaces
Configuring Integrated Voice and Serial Data WAN](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-199-2048.jpg)
![SUMMARY STEPS
1. enable
2. configure terminal
3. interface serial controller-number : timeslot
4. isdn service [dsl number | nfas_int number] b_channel number state{0 | 1 | 2}
5. isdn service [dsl number | nfas_int number] b_channel number state {0 | 1 | 2}
6. exit
DETAILED STEPS
PurposeCommand or Action
Enters privileged EXEC mode. Enter your password when
prompted.
enable
Example:
Router> enable
Step 1
Enters configuration mode.configure terminal
Example:
Router# configure terminal
Step 2
Enters interface configuration mode and specifies a serial
interface for ISDN PRI, channel-associated signaling, or
robbed-bit signaling.
interface serial controller-number : timeslot
Example:
Router(config)# interface serial 4/1:23
Step 3
Takes an individual B channel out of service or sets it to
a different state. State values are as follows:
isdn service [dsl number | nfas_int number] b_channel
number state{0 | 1 | 2}
Step 4
Example:
Router(config-if)# isdn service nfas_int 3
b_channel 1 state 1
• 0 --In service
• 1 --Maintenance
• 2 --Out of service
As above. Setting the b-channel number to 0 sets the entire
PRI interface to a specified state value.
isdn service [dsl number | nfas_int number] b_channel
number state {0 | 1 | 2}
Example:
Router(config-if)# isdn service nfas_int 3
b_channel 0 state 1
Step 5
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
227
NFAS with D-Channel Backup
Disabling a Channel or Interface](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-239-2048.jpg)
![SUMMARY STEPS
1. enable
2. configure terminal
3. iua
4. as as-name {local-ip1 [local-ip2]} [local-sctp-port]
5. asp asp-name as as-name remote-ip1 remote-ip2 ]}[remote-sctp-port
6. asp asp-name sctp-keepalives remote-ip keepalive-value
7. asp asp-name ip-precedence remote-ip ip-precedence-level
8. as as-name fail-over-timer time
9. exit
DETAILED STEPS
PurposeCommand or Action
Enters privileged EXEC mode. Enter your password if prompted.enable
Example:
Router> enable
Step 1
Enters global configuration mode.configure terminal
Example:
Router# configure terminal
Step 2
Enters IUA configuration mode and specifies backhaul using
SCTP.
iua
Example:
Router(config)# iua
Step 3
Defines an application server on a gateway.as as-name {local-ip1 [local-ip2]}
[local-sctp-port]
Step 4
You can specify up to three local IP addresses (note that SCTP
has built-in support for multihomed machines).
Example:
Router(config-iua)# as as5400-3 10.1.2.34
10.1.2.35 2577
Defines an ASP. Use this command to establish SCTP
associations.
asp asp-name as as-name remote-ip1
remote-ip2 ]}[remote-sctp-port
Step 5
Example:
Router(config-iua)# asp asp1 as as5400-3
10.4.8.68 10.4.9.68 2577
A maximum of three ASPs can be configured per
application server.
Note
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
245
PRI Backhaul and IUA Support Using SCTP
Configuring PRI Backhaul Using the SCTP and the ISDN Q.921 User Adaptation Layer](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-257-2048.jpg)
![Configuring Support for IUA with SCTP for Cisco Access Servers Feature
This section contains the following procedures:
Configuring IUA for Cisco Access Servers
To configure IUA for Cisco access servers, follow the steps for configuring IUA for PRI Q.921 backhaul, as
described in the Configuring IUA, on page 244.
Configuring the SCTP T1 Initiation Timer
To configure the SCTP T1 initiation timer, perform the following steps.
SUMMARY STEPS
1. enable
2. configure terminal
3. iua
4. as as-name {localip1 [localip2]} [local-sctp-port]
5. as as-name fail-over-timer time
6. as as-name sctp-startup-rtx number
7. as as-name sctp-streams number
8. as as-name sctp-t1init number
9. asp asp-name as as-name ip-address
10. asp asp-name ip-precedence remote-ip-address number
11. asp asp-name as as-name remote-ip remote-ip2 ]}[remote-sctp-port
12. asp asp-name sctp-keepalive remote-ip-address number
13. asp asp-name sctp-max-association ip-address number
14. asp asp-name sctp-path-retransmission ip-address number
15. asp asp-name sctp-t3-timeout ip-address number
16. exit
DETAILED STEPS
PurposeCommand or Action
Enters privileged EXEC mode. Enter your password if
prompted.
enable
Example:
Router> enable
Step 1
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
251
PRI Backhaul and IUA Support Using SCTP
Configuring Support for IUA with SCTP for Cisco Access Servers Feature](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-263-2048.jpg)
![PurposeCommand or Action
Enters global configuration mode.configure terminal
Example:
Router# configure terminal
Step 2
Enters IUA configuration mode and specifies backhaul
using SCTP.
iua
Example:
Router(config)# iua
Step 3
Defines an application server on a gateway.as as-name {localip1 [localip2]} [local-sctp-port]
Example:
Router(config-iua)# as as5400-3 10.1.2.34
10.1.2.35 2577
Step 4
(Optional) Sets the failover timer value, in ms.as as-name fail-over-timer timeStep 5
Example:
Router(config-iua)# as as5400-3 fail-over 10000
Find the failover timer value by examining the
show iua as all command output.
Note
Configures the SCTP startup retransmission interval.as as-name sctp-startup-rtx number
Example:
Router(config-iua)# as as5400-3 sctp-startup-rtx
8
Step 6
Configures the number of SCTP streams for this application
server.
as as-name sctp-streams number
Example:
Router(config-iua)# as as5400-3 sctp-streams 56
Step 7
Although the gateway help function displays a range of 2
to 57, the upper end of the range (also the default) is
determined by your hardware, and is equal to the number
of controllers on that gateway and NAS one plus. If you
enter a number higher than that, the system assumes the
default.
If you want to set this value to something other
than the default, add one to the number of D
channel interfaces that you want to use
concurrently.
Note
Sets the SCTP T1 initiation timer, in ms.as as-name sctp-t1init number
Example:
Router(config-iua)# as as1 sctp-t1init 1000
Step 8
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
252
PRI Backhaul and IUA Support Using SCTP
Configuring Support for IUA with SCTP for Cisco Access Servers Feature](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-264-2048.jpg)
![PurposeCommand or Action
Creates an ASP and specifies to which application server
it belongs.
asp asp-name as as-name ip-address
Example:
Router(config-iua)# asp asp1 as as1 10.4.8.68
10.4.9.68
Step 9
Specifies the IP precedence level for protocol data units
(PDUs) for a given IP address.
asp asp-name ip-precedence remote-ip-address
number
Step 10
Example:
Router(config-iua)# asp asp1 ip-precedence
10.1.2.345 7
Default for normal IP precedence handling is 0.
Defines an ASP. Use this command to establish SCTP
associations.
asp asp-name as as-name remote-ip remote-ip2
]}[remote-sctp-port
Example:
Router(config-iua)# asp asp1 as as5400-3
10.4.8.68 10.4.9.68 2577
Step 11
(Optional) Specifies the IP address to enable and disable
keepalives and control SCTP keepalives on destination IP
addresses.
asp asp-name sctp-keepalive remote-ip-address
number
Example:
Router(config-iua)# asp asp1 sctp-keepalive
10.1.2.234 1000
Step 12
Sets the maximum association retransmissions for this ASP.asp asp-name sctp-max-association ip-address
number
Step 13
Example:
Router(config-iua)# asp asp1
sctp-max-association 10.10.10.10 20
Sets the SCTP path retransmissions for this ASP.asp asp-name sctp-path-retransmission ip-address
number
Step 14
Example:
Router(config-iua)# asp asp1
sctp-path-retransmission 10.10.10.10 2
Enters IUA-SCTP configuration mode and sets the SCTP
T3 retransmission timeout for this ASP.
asp asp-name sctp-t3-timeout ip-address number
Example:
Router(config-iua)# asp asp1 sctp-t3-timeout
10.10.10.10 60000
Step 15
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
253
PRI Backhaul and IUA Support Using SCTP
Configuring Support for IUA with SCTP for Cisco Access Servers Feature](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-265-2048.jpg)
![• At the global level to support QSIGX, PRI 5ess, or another switch type such as VN3
• At the interface level to set a particular interface to support QSIG, to set a particular interface to a PRI
setting such as 5ess, or to set one particular interface to a PRI setting and another interface to support
QSIG.
SUMMARY STEPS
1. enable
2. configure terminal
3. isdn switch-type primary-qsig
4. controller {t1 | e1} controller-number
5. pri-group [timeslot range]
6. exit
7. interface serial 1: channel-number
8. isdn switch-type primary-qsig
9. isdn protocol-emulate {user| network}
10. isdn overlap-receiving [T302 value]
11. isdn incoming-voice modem
12. isdn network-failure-cause [value]
13. isdn bchan-number-order {ascending | descending}
14. exit
DETAILED STEPS
PurposeCommand or Action
Enters privileged EXEC mode. Enter your password when prompted.enable
Example:
Router> enable
Step 1
Enters global configuration mode.configure terminal
Example:
Router# configure terminal
Step 2
(Optional) Globally configures the ISDN switch type to support QSIG
signaling.
isdn switch-type primary-qsig
Example:
Router(config)# isdn switch-type
primary-qsig
Step 3
Depending on your configuration, you can configure the ISDN
switch type by using this command either in global configuration
mode or interface configuration mode (see Configuring VoIP QSIG).
Note
If the PBX in your configuration is an NEC PBX and you use Fusion Call
Control Signaling (FCCS), see the Configuring FCCS, on page 317.
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
315
Implementing FCCS (NEC Fusion)
Configuring VoIP QSIG](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-327-2048.jpg)
![PurposeCommand or Action
Enters controller configuration mode for the specified controller.controller {t1 | e1} controller-number
Example:
Router(config)# controller t1 3
Step 4
Configures the PRI group for either T1 or E1 to carry voice traffic. T1 time
slots are 1 to 23. E1 time slots are 1 to 31.
pri-group [timeslot range]
Example:
Router(config-controller)# pri-group
timeslot 1-23
Step 5
You can configure the PRI group to include either all available time slots or
just a select group. For example, if only time slots 1 to 10 are in the PRI
group, specify timeslot 1-10. If the PRI group includes all channels available
for T1, specify timeslot 1-23. If the PRI group includes all channels available
for E1, specify timeslot 1-31.
Exits the current mode.exit
Example:
Router(config-controller)# exit
Step 6
Enters interface configuration mode for the ISDN PRI interface. T1 channel
number is 23. E1 channel number is 15.
interface serial 1: channel-number
Example:
Router(config)# interface serial
1:23
Step 7
(Optional) Configures the ISDN switch type to support QSIG signaling for
the specified interface. Use this command if you did not configure the ISDN
switch type for QSIG support globally in Step 1.
isdn switch-type primary-qsig
Example:
Router(config-if)# isdn switch-type
primary-qsig
Step 8
The same conditions that apply to this command in global configuration
mode also apply to this command in interface configuration mode.
For the selected interface, this command in interface configuration
mode overrides the same command in global configuration mode.
Note
Configures the ISDN interface to serve as either the primary QSIG slave or
the primary QSIG master. Keywords are as follows:
isdn protocol-emulate {user| network}
Example:
Router(config-if)# isdn
protocol-emulate user
Step 9
• user --Slave
• network --Master
If the private integrated services network exchange (PINX) is the primary
QSIG master, configure the access server as the primary QSIG slave. If the
PINX is the primary QSIG slave, configure it as the primary QSIG master.
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
316
Implementing FCCS (NEC Fusion)
Configuring VoIP QSIG](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-328-2048.jpg)
![PurposeCommand or Action
(Optional) Activates overlap signaling to send to the destination PBX using
timer T302. The keyword are argument are as follows:
isdn overlap-receiving [T302 value]
Example:
Router(config-if)# isdn
overlap-receiving T302 500
Step 10
• T302 value --Value of timer T302, in ms.
Routes incoming voice calls to the modem and treats them as analog data.isdn incoming-voice modem
Example:
Router(config-if)# isdn
incoming-voice modem
Step 11
(Optional) Specifies the cause code to pass to the PBX when a call cannot
be placed or completed because of internal network failures. The argument
is as follows:
isdn network-failure-cause [value]
Example:
Router(config-if)# isdn
network-failure-cause 5
Step 12
• value --Cause code, from 1 to 127. All cause codes except Normal Call
Clearing (16), User Busy (17), No User Responding (18), and No
Answer from User (19) are changed to the specified cause code.
(Optional) Configures the ISDN PRI interface to make the outgoing call
selection in ascending or descending order. Keywords are as follows:
isdn bchan-number-order {ascending
| descending}
Step 13
Example:
Router(config-if)# isdn
bchan-number-order ascending
• ascending --Ascending order.
• descending --Descending order. This is the default.
For descending order, the first call from the access server uses (T1) channel
23 or (E1) channel 31. The second call then uses (T1) channel 22 or (E1)
channel 30, and so on, in descending order.
For ascending order, if the PRI group starts with 1, the first call uses channel
1, the second call uses channel 2, and so on, in ascending order. If the PRI
group starts with a different time slot, the ascending order starts with the
lowest time slot.
Exits the current mode.exit
Example:
Router(config-if)# exit
Step 14
Configuring FCCS
To configure FCCS, perform the following steps.
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
317
Implementing FCCS (NEC Fusion)
Configuring FCCS](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-329-2048.jpg)
![C H A P T E R 14
Digital J1 Voice Interface Card
This chapter describes how to implement the Digital J1 Voice Interface Card (VIC) feature. The digital J1
VIC provides the proper interface for directly connecting Cisco multiservice access routers to PBXs throughout
Japan that use a J1 (2.048-Mbps time-division-multiplexed [TDM]) interface.
Feature History for Digital J1 Voice Interface Card
ModificationRelease
This feature was introduced on the Cisco 2600 series
and Cisco 3600 series.
12.2(8)T
• Finding Feature Information, page 321
• Prerequisites for Configuring the Digital J1 VIC, page 322
• Restrictions for Configuring the Digital J1 VIC, page 322
• Information About the Digital J1 VIC, page 322
• How to Configure the Digital J1 VIC, page 324
• Configuration Examples for the Digital J1 VIC, page 334
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest caveats and
feature information, see Bug Search Tool and the release notes for your platform and software release. To
find information about the features documented in this module, and to see a list of the releases in which each
feature is supported, see the feature information table at the end of this module.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support.
To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
321](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-333-2048.jpg)
![Configuring T-CCS for a Clear-Channel Codec
To configure transparent common-channel signaling (T-CCS), perform the following steps.
SUMMARY STEPS
1. enable
2. configure terminal
3. controller j1 slot/port
4. ds0-group ds0-group-no timeslots timeslot-list type signaling-type
5. no shutdown
6. exit
7. dial-peer voice number pots
8. destination-pattern string [T]
9. port slot/port : ds0-group-no
10. exit
11. dial-peer voice number voip
12. codec clear-channel
13. vad
14. destination-pattern string [T]
15. session target {ipv4: destination-address | dns:[$s$.| $d$. | $e$. | $u$.] hostname}
16. exit
DETAILED STEPS
PurposeCommand or Action
Enters privileged EXEC mode. Enter your password when prompted.enable
Example:
Router> enable
Step 1
Enters global configuration mode.configure terminal
Example:
Router# configure terminal
Step 2
Enters controller configuration mode for the J1 controller in the specified
slot and port.
controller j1 slot/port
Example:
Router(config)# controller j1 1/0
Step 3
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
329
Digital J1 Voice Interface Card
Configuring T-CCS for a Clear-Channel Codec](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-341-2048.jpg)
![PurposeCommand or Action
Configures channelized J1 time slots for use by compressed voice calls
and the signaling method that the router uses to connect to the PBX. The
keywords and arguments are as described earlier.
ds0-group ds0-group-no timeslots
timeslot-list type signaling-type
Example:
Router(config-controller)# ds0-group
Step 4
1 timeslots 1-15,17-31 type
e&m-wink-start
Activates the controller.no shutdown
Example:
Router(config-controller)# no shutdown
Step 5
Exits the current mode.exit
Example:
Router(config-controller)# exit
Step 6
Enters dial-peer configuration mode for the specified POTS dial peer.dial-peer voice number pots
Example:
Router(config)# dial-peer voice 20
pots
Step 7
Configures the dial peer's destination pattern so that the system can
reconcile dialed digits with a telephone number. The keyword and
argument are as follows:
destination-pattern string [T]
Example:
Router(config-dialpeer)#
destination-pattern 3050 T
Step 8
• string --Series of digits that specify the E.164 or private-dialing-plan
phone number. Valid entries: digits 0 to 9 and letters A to D. The
plus symbol (+) is not valid. You can enter the following special
characters:
• Star character (*) that appears on standard touch-tone dial
pads--Can be in any dial string, but not as a leading character
(for example, *650).
• Period (.)--Acts as a wildcard character.
• Comma (,)--In prefixes, inserts a one-second pause.
• T --When included at the end of the destination pattern, causes the
system to collect dialed digits as they are entered until the interdigit
timer expires (default: 10 seconds) or the user dials the termination
of end-of-dialing key (default: #).
The timer character must be a capital
T.
Note
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
330
Digital J1 Voice Interface Card
Configuring T-CCS for a Clear-Channel Codec](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-342-2048.jpg)
![PurposeCommand or Action
Associates the dial peer with a specific logical interface. Arguments are
as follows:
port slot/port : ds0-group-no
Example:
Router(config-dialpeer)# port 1/0:1
Step 9
• slot -- Router location where the voice module is installed. Range:
0 to 3.
• port --Voice interface card location. Range: 0 to 1.
• ds0-group-no --DS0 group number. Each defined DS0 group number
is represented on a separate voice port, allowing you to define
individual DS0s.
Exits the current mode.exit
Example:
Router(config-dialpeer)# exit
Step 10
Enters dial-peer configuration mode for the specified VoIP dial peer.dial-peer voice number voip
Example:
Router(config)# dial-peer voice 20
voip
Step 11
Specifies use of the clear-channel codec.codec clear-channel
Example:
Router(config-dialpeer)# codec
clear-channel
Step 12
(Optional; enabled by default) Activates voice activity detection (VAD),
which allows the system to reduce unnecessary voice transmissions caused
by unfiltered background noise.
vad
Example:
Router(config-dialpeer)# vad
Step 13
Configures the dial peer's destination pattern so that the system can
reconcile dialed digits with a telephone number. The keyword are
argument are as described above.
destination-pattern string [T]
Example:
Router(config-dialpeer)#
destination-pattern 3050 T
Step 14
Configures the IP session target for the dial peer. Keywords and arguments
are as follows:
session target {ipv4: destination-address |
dns:[$s$.| $d$. | $e$. | $u$.] hostname}
Step 15
Example:
Router(config-dialpeer)# session
• ipv4: destination-address --IP address of the dial peer to receive
calls.
• dns: hostname --Domain-name server that resolves the name of
the IP address. You can use wildcards by using source, destination,
target {ipv4:10.168.1.1
serverA.mycompany.com}
and dialed information in the hostname. Use one of the following
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
331
Digital J1 Voice Interface Card
Configuring T-CCS for a Clear-Channel Codec](https://image.slidesharecdn.com/vi-15-mt-book-160912190710/75/Vi-15-mt-book-343-2048.jpg)
More Related Content
Vi 15-mt-book
- 1. ISDN Voice ConfigurationGuide, Cisco IOS Release 15M&T Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883
- 2. THE SPECIFICATIONS ANDINFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental. Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: http:// www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R) © 2014 Cisco Systems, Inc. All rights reserved.
- 3. C O NT E N T S C H A P T E R 1 Overview of ISDN Voice Interfaces 1 Finding Feature Information 1 Prerequisites for Configuring ISDN Voice Interfaces 2 Restrictions for Configuring ISDN Voice Interfaces 2 Information About ISDN Voice Interfaces 3 ISDN Media Types 3 Interface Cards and Network Modules 3 Typical ISDN Application 4 QSIG Protocol 4 QSIG Basics 4 ISDN Switch Types for Use with QSIG 6 Traceability of Diverted Calls 8 Additional References 8 C H A P T E R 2 Basic ISDN Voice-Interface Configuration 17 Finding Feature Information 17 Prerequisites for Configuring an ISDN Voice Interface 18 Restrictions for Configuring an ISDN Voice Interface 18 Information About ISDN Voice Interfaces 18 How to Configure an ISDN Voice Interface 18 Configuring a Router for ISDN BRI Voice-Interface Support 18 Configuring BRI NT and TE Interfaces 19 Verifying BRI Interfaces 24 Examples 25 Troubleshooting Tips 32 Configuring ISDN PRI Voice-Interface Support 32 Configuring PRI Interfaces 32 Configuring PRI Voice Ports 36 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T iii
- 4. Verifying PRI Interfaces36 Troubleshooting Tips 37 Configuring QSIG Support 38 Configure Global QSIG Support for BRI or PRI 38 Configure Controllers for QSIG over PRI 40 Configure PRI Interfaces for QSIG 41 Configure BRI Interfaces for QSIG 44 Verify the QSIG Configuration 49 Troubleshooting Tips 50 Examples 50 Configuring ISDN PRI Q.931 Support 54 Configuration Examples for ISDN Voice Interfaces 57 ISDN-to-PBX and ISDN-to-PSTN Examples 57 QSIG Support Examples 58 Q.931-Support Example 74 Additional References 77 C H A P T E R 3 Expanded Scope for Cause-Code-Initiated Call-Establishment Retries 79 Finding Feature Information 79 Prerequisites for Expanded Scope for Cause-Code-Initiated Call Establishment Retries 80 Restrictions for Expanded Scope for Cause-Code-Initiated Call Establishment Retries 80 Information About Expanded Scope for Cause-Code-Initiated Call-Establishment Retries 80 How to Configure Expanded Scope for Cause-Code-Initiated Call-Establishment Retries 81 Configuring Expanded Scope for Cause-Code-Initiated Call-Establishment Retries 81 Verifying Expanded Scope for Cause-Code-Initiated Call-Establishment Retries 82 Troubleshooting Tips 82 Configuration Examples for Expanded Scope for Cause-Code-Initiated Call Establishment Retries 83 ISDN Interface Example 83 Cause Codes Example 83 Additional References 83 C H A P T E R 4 Clear Channel T3 E3 with Integrated CSU DSU 85 Finding Feature Information 86 Prerequisites for Clear Channel T3 E3 with Integrated CSU DSU 86 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T iv Contents
- 5. Restrictions for ClearChannel T3 E3 with Integrated CSU DSU 86 Information About Clear Channel T3 E3 with Integrated CSU DSU 87 How to Configure Clear Channel T3 E3 with Integrated CSU DSU 87 Configuring Clear-Channel T3 87 Configuring the Card Type and Controller for T3 87 Configuring DSU Mode and Bandwidth for T3 89 Configuring Encryption Scrambling for T3 90 Configuring a Bit-Error-Rate Test Pattern for T3 91 Configuring Loopback for T3 93 Configuring the Maintenance Data Link for T3 94 Configuring Clear-Channel E3 96 Configuring the Card Type and Controller for E3 96 Configuring DSU Mode and Bandwidth for E3 97 Configuring Encryption Scrambling for E3 99 Configuring a Bit-Error-Rate Test Pattern for E3 100 Configuring Loopback for E3 101 Configuring the National Bit in the G.751 Frame for E3 102 Verifying Clear-Channel T3 E3 103 Troubleshooting Tips 104 Configuration Example for Clear Channel T3 E3 with Integrated CSU DSU 105 Additional References 107 C H A P T E R 5 High-Density Analog (FXS, DID, FXO) and Digital (BRI) Extension Module for Voice-Fax (EVM-HD) 109 Finding Feature Information 110 Prerequisites for High-Density Analog and Digital Extension Module for Voice Fax 110 Restrictions for High-Density Analog and Digital Extension Module for Voice Fax 111 Information About High-Density Analog and Digital Extension Module for Voice Fax 112 Key Features 112 FXS and FXO Interfaces 113 Network Clock Timing 113 How to Configure High-Density Analog and Digital Extension Module for Voice Fax 115 Configuring Analog FXS FXO and DID Voice Ports 115 Troubleshooting Tips 120 Examples 120 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T v Contents
- 6. Configuring ISDN BRIDigital Interfaces 121 Configuration Examples for High-Density Analog and Digital Extension Module for Voice Fax 127 show running-config Command Example 127 show running-config Command Example with Base Voice Module and Two 4BRI Expansion Modules 129 Additional References 131 C H A P T E R 6 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers 133 Finding Feature Information 134 Prerequisites for Integrated Data and Voice Services for ISDN PRI Interfaces 134 Restrictions for Integrated Data and Voice Services for ISDN PRI Interfaces 135 Information About Integrated Data and Voice Services for ISDN PRI Interfaces 136 Integrated Services for Multiple Call Types 137 Resource Allocation for Voice and Data Calls 138 MLPP Call Preemption over Voice Calls 138 Preemption of Outgoing Voice Calls 138 Preemption Tones 139 How to Configure Integrated Data and Voice Services for ISDN PRI Interfaces 139 Configuring the ISDN PRI Interface for Multiple Call Types 139 Prerequisites 139 Configuring the POTS Dial-Peer Incoming Called Number 141 Configuring the Data Dial Peer Lookup Preference 142 Enabling Integrated Services 143 Creating a Trunkgroup and Configuring Maximum Calls Based on Call Type 144 Disabling Integrated Services 145 Configuring MLPP Call Preemption over Outgoing Voice Calls 147 Enabling Preemption on the Trunk Group 147 Defining a Dialer Map Class and Setting the Preemption Level 148 Associating the Class Parameter on the Dialer Interface 150 Disabling TDM Hairpinning on the Voice Card 152 Configuring the POTS Dial Peer for Outgoing Voice Calls 153 Troubleshooting Tips for Integrated Data and Voice Services 154 Configuration Examples for Integrated Data and Voice Services for ISDN PRI Interfaces 155 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T vi Contents
- 7. MLPP DDR BackupCall Preemption over Voice Call Example 155 Legacy DDR (Dialer Map) Example 160 Dialer Profiles Example 162 Maximum Number of Data and Voice Calls on the Dial-Out Trunk Group Example 163 Dial-Peer Configuration Example 165 Disconnect Cause Example 167 Additional References 169 C H A P T E R 7 Integrated Voice and Data WAN on T1 E1 Interfaces 171 Finding Feature Information 172 Prerequisites for Configuring Integrated Voice and Data WAN on T1 E1 Interfaces Using the AIM-ATM-VOICE-30 Module 172 Restrictions for Configuring Integrated Voice and Data WAN on T1 E1 Interfaces Using the AIM-ATM-VOICE-30 Module 173 Information About Integrated Voice and Data WAN on T1 E1 Interfaces Using the AIM-ATM-VOICE-30 Module 174 AIM-ATM-VOICE-30 Module 174 Integrated Voice and Data WAN 174 High-Complexity Voice Compression 176 Network Clock Source and Participation 176 How to Configure Integrated Voice and Data WAN on T1 E1 Interfaces Using the AIM-ATM-VOICE-30 Module 177 Configuring Network Clock Source and Participation 177 Configuring Clock Source Internal 177 Configuring the Clock-Source Line 180 Configuring the AIM-ATM-VOICE-30 Card for High-Complexity Codecs and Time Slots 184 Configuring Integrated Voice and Serial Data WAN 186 Verifying Integrated Voice and Serial Data WAN 188 Configuration Examples for Integrated Voice and Data WAN on T1 E1 Interfaces Using the AIM-ATM-VOICE-30 Module 190 Single-Serial-Data WAN Example 190 Multiple-Serial-Data WAN Example 191 High-Complexity Codecs and Network Clock Example 193 Additional References 194 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T vii Contents
- 8. C H AP T E R 8 ISDN GTD for Setup Message 195 Finding Feature Information 196 Prerequisites for Configuring ISDN GTD for Setup Message 196 Restrictions for Configuring ISDN GTD for Setup Message 196 Information About ISDN GTD for Setup Message 196 Feature Design of ISDN GTD for Setup Messages 196 Mapping of ISDN Information Elements to GTD Parameters 197 Mapping for CPN CGN and RGN 198 Mapping for Calling Party Number (CGN) 199 Mapping for Redirection Information (RNI) 200 Mapping for Originating Line Information (OLI) 200 Mapping for Bearer Capability (USI and TMR) Parameters 202 How to Configure ISDN GTD for Setup Message 211 Configuring ISDN GTD for Setup Messages 211 Configuring the OLI IE to Interface with MCI Switches 212 Verifying ISDN GTD 213 Troubleshooting Tips 214 Examples 214 Configuration Examples for ISDN Generic Transparency Descriptor (GTD) for Setup Message 216 GTD Mapping Example 216 OLI IE Example 216 OLI IE and GTD Example 216 Additional References 219 C H A P T E R 9 NFAS with D-Channel Backup 221 Finding Feature Information 222 Prerequisites for Configuring NFAS with D-Channel Backup 222 Restrictions for Configuring NFAS with D-Channel Backup 222 Information about NFAS 223 How to Configure NFAS with D-Channel Backup 223 Configuring NFAS on PRI Groups 223 Configuring a VoIP Dial Peer for NFAS Voice 225 Disabling a Channel or Interface 226 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T viii Contents
- 9. Verifying NFAS Configuration228 Examples 229 Configuration Examples for NFAS with D-Channel Backup 230 NFAS Primary and Backup D Channels Example 230 POTS Dial-Peer Configuration Example 232 PRI Service State Example 232 Additional References 232 C H A P T E R 1 0 PRI Backhaul and IUA Support Using SCTP 233 Finding Feature Information 234 Prerequisites for Implementing SCTP Features 234 Restrictions for Implementing SCTP Features 234 Information About SCTP and SCTP Features 235 SCTP Topology 236 IUA 238 Multiple NFAS Groups 239 Features That Use SCTP 240 PRI Backhaul Using SCTP and the ISDN Q.921 User Adaptation Layer 241 Support for IUA with SCTP for Cisco Access Servers 243 How to Configure SCTP Features 244 Configuring PRI Backhaul Using the SCTP and the ISDN Q.921 User Adaptation Layer 244 Configuring IUA 244 Configuring ISDN Signaling (PRI) Backhaul 246 Verifying PRI Backhaul 248 Configuring Support for IUA with SCTP for Cisco Access Servers Feature 251 Configuring IUA for Cisco Access Servers 251 Configuring the SCTP T1 Initiation Timer 251 Creating NFAS Groups and Bind Them to the Application Server 254 Migrating from RLM to IUA with SCTP 256 Modifying a PRI Group on an MGC 258 Verifying Support for IUA with SCTP 259 Troubleshooting Tips 263 Examples 265 Configuration Examples for SCTP Options 275 Application-Server and Application-Server-Process Example 275 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T ix Contents
- 10. Application-Server and Application-Server-Processwith IUA Example 276 ISDN Signaling Backhaul Example 278 IUA Configuration Example 279 PRI Group on an MGC Example 285 SCTP Configuration Example 285 SCTP Migration from RLM to IUA Example 286 Trunk Group Bound to an Application Server Example 287 Additional References 287 C H A P T E R 1 1 QSIG Support for Tcl IVR 2.0 289 Finding Feature Information 289 Prerequisites for Configuring QSIG for Tcl IVR 2.0 290 Restrictions for Configuring QSIG for Tcl IVR 2.0 290 Information About QSIG for Tcl IVR 2.0 291 How to Configure QSIG for Tcl IVR 2.0 291 Configuring QSIG 291 Configuring Supplementary Service for a POTS Dial Peer 292 Configuring Supplementary Service for a VoIP Dial Peer 293 Verifying QSIG and Supplementary Service 295 Configuration Example for QSIG for Tcl IVR 2.0 295 Additional References 297 C H A P T E R 1 2 Implementing T1 CAS for VoIP 299 Finding Feature Information 299 Prerequisites for Configuring T1 CAS 300 Restrictions for Configuring T1 CAS 300 Information About T1 CAS for VoIP 301 CAS Basics 301 EandM and Ground Start Protocols 301 How to Configure T1 CAS for VoIP 302 Configuring T1 CAS for Use with VoIP 302 Verifying and Troubleshooting a T1 CAS Configuration 306 Configuration Example for T1 CAS for VoIP 309 Additional References 311 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T x Contents
- 11. C H AP T E R 1 3 Implementing FCCS (NEC Fusion) 313 Finding Feature Information 313 Prerequisites for Implementing FCCS 314 Restrictions for Implementing FCCS 314 Information About FCCS 314 How to Configure FCCS 314 Configuring VoIP QSIG 314 Configuring FCCS 317 Verifying FCCS 318 Additional References 319 C H A P T E R 1 4 Digital J1 Voice Interface Card 321 Finding Feature Information 321 Prerequisites for Configuring the Digital J1 VIC 322 Restrictions for Configuring the Digital J1 VIC 322 Information About the Digital J1 VIC 322 How to Configure the Digital J1 VIC 324 Configuring the J1 VIC 324 Configuring CAS 325 Configuring the Clock Source 326 Configuring Loopback 328 Configuring T-CCS for a Clear-Channel Codec 329 Verifying Digital J1 VIC Configuration 332 Monitoring and Maintaining the Digital J1 VIC 332 Troubleshooting Tips 332 Configuration Examples for the Digital J1 VIC 334 Controller (J1) Example 336 Channel-Associated Signaling Example 336 Clock Source Example 336 Loopback Example 336 Transparent Common-Channel Signaling for a Clear-Channel Codec Example 336 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T xi Contents
- 12. ISDN Voice ConfigurationGuide, Cisco IOS Release 15M&T xii Contents
- 13. C H AP T E R 1 Overview of ISDN Voice Interfaces This chapter provides an overview of ISDN Basic Rate Interface (BRI) and Primary Rate Interface (PRI) for support of voice traffic. With those ports so configured, you can do the following: • Bypass PSTN tariffed services such as trunking and administration. • Connect your PBXs directly to a Cisco router and route PBX station calls automatically to the WAN. • Configure a voice interface on a Cisco router to emulate either a terminal-equipment (TE) or network-termination (NT) interface. All types of PBXs can send calls through a router and deliver those calls across the customer network. • Configure Layer 2 operation as point-to-point (static terminal endpoint identifier [TEI]) or point-to-multipoint (automatic TEI). • Finding Feature Information, page 1 • Prerequisites for Configuring ISDN Voice Interfaces, page 2 • Restrictions for Configuring ISDN Voice Interfaces, page 2 • Information About ISDN Voice Interfaces, page 3 • Additional References, page 8 Finding Feature Information Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 1
- 14. Prerequisites for ConfiguringISDN Voice Interfaces • Obtain PRI or BRI service and T1 or E1 service from your service provider, as required. Ensure that the BRI lines are provisioned at the switch to support voice calls. • Establish a working IP, Frame Relay, or ATM network. Ensure that at least one network module or WAN interface card is installed in the router to provide connection to the LAN or WAN. • Complete your company’s dial plan. • Establish a working telephony network based on your company’s dial plan and configure the network for real-time voice traffic. This chapter describes only a portion of the process; for further information, see the chapter "Cisco Voice Telephony." • Cisco 2600 series and Cisco 3600 series routers--Install digital T1 or E1 packet-voice trunk network modules, BRI voice interface cards, and other voice interface cards as required on your network. • Cisco 7200 series routers--Install a single-port 30-channel T1/E1 high-density voice port adapter. • Cisco MC3810 multiservice concentrators--Install the required digital voice modules (DVMs), BRI voice module (BVM), and multiflex trunk modules. • Configure, for all platforms (as required), the following: • Voice card and controller settings • Serial and LAN interfaces • Voice ports • Voice dial peers Restrictions for Configuring ISDN Voice Interfaces ISDN Voice Interface Limitations • Basic-net3 and basic-qsig are the only ISDN switch types currently supported for an NT interface. • When the ISDN BRI port on the router is configured as an NT port, you must use a "rolled" cable (one with the transmit and receive leads swapped) to connect to a TE interface. • Layer 1 can be configured only as point-to-point (that is, with one TE connected to each NT). Automatic TEI support issues only one TEI. QSIG Support Limitations • Cisco 2600 series routers do not support VoATM. • The following restrictions apply to the Cisco MC3810 multiservice concentrator: • QSIG data calls are not supported. All calls with bearer capability indicating a nonvoice type (such as for video telephony) are rejected. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 2 Overview of ISDN Voice Interfaces Prerequisites for Configuring ISDN Voice Interfaces
- 15. • Cisco MC3810supports only one T1/E1 interface with direct connectivity to a private integrated services network exchange (PINX). • Cisco MC3810 supports a maximum of 24 B channels. • When QSIG is configured, serial port 1 does not support speeds higher than 192 kbps. This restriction assumes that the MFT is installed in slot 3 on the Cisco MC3810. If the MFT is not installed, then serial port 1 does not operate. • The following restrictions apply to Cisco 7200 series routers: • VoATM is not supported. • BRI is not supported. Information About ISDN Voice Interfaces ISDN Media Types Cisco routing devices support ISDN BRI and ISDN PRI. Both media types use bearer (B) channels and data (D) channels as follows: • ISDN BRI (referred to as "2 B + D") uses the following: • Two 64-kbps B channels that carry voice or data for a maximum transmission speed of 128 kbps • One 16-kbps D channel that carries signaling traffic--that is, instructions about how to handle each of the B channels. • ISDN PRI (referred to as "23 B + D" or "30 B + D") uses the following: • 23 B channels (in North America and Japan) or 30 B channels (in the rest of the world) that carry voice or data • One 64-kbps D channel that carries signaling traffic The D channel, in its role as signal carrier for the B channels, directs the central-office switch to send incoming calls to particular timeslots on the Cisco access server or router. It also identifies the call as a circuit-switched digital call or an analog modem call. Circuit-switched digital calls are relayed directly to the ISDN processor in the router; analog modem calls are decoded and then sent to the onboard modems. Interface Cards and Network Modules The VIC-2BRI-NT/TE voice interface card for the Cisco 2600 series and Cisco 3600 series routers and the BVM4-NT/TE voice module for the Cisco MC3810 multiservice concentrator enable Cisco IOS software to replicate the PSTN interface to a PBX that is compatible with European Telecommunications Standards Institute (ETSI) NET3 and QSIG switch types. Before these cards and modules became available, if your PBXs implemented only a BRI TE interface, you had to make substantial hardware and software changes on the PBX to provide an NT interface to the router. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 3 Overview of ISDN Voice Interfaces Information About ISDN Voice Interfaces
- 16. provide an NTinterface to the router. VIC-2BRI-NT/NE and BVN4-NT/NE allow you to connect ISDN PBXs and key systems to a multiservice network with minimal configuration changes on the PBX. Typical ISDN Application A typical application (see the figure below) allows an enterprise customer with a large installed base of legacy telephony equipment to bypass the PSTN. Figure 1: Typical Application Using BRI-NT/TE Voice Interface Cards or BVM4-NT/TE Voice Modules QSIG Protocol This section contains the following information: QSIG Basics QSIG is a variant of ISDN Q.921 and Q.931 ISDN D-channel signaling, for use in private integrated-services network-exchange (PINX) devices such as PBXs or key systems. Using QSIG signaling, a router can route incoming voice calls from a PINX across a WAN to a peer router, which can then transport the signaling and voice packets to another PINX. The QSIG protocol was originally specified by European Computer Manufacturers Association (ECMA), and then adopted by European Telecommunications Standards Institute (ETSI) and the International Organization for Standardization (ISO). It is becoming the standard for PBX interoperability in Europe and North America. The table below identifies the ECMA standards and the OSI layer of the QSIG protocol stack to which they relate. Table 1: QSIG Protocol Stack DescriptionStandardOSI Layer End-to-end protocols; network transparent Application mechanisms7 to 4 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 4 Overview of ISDN Voice Interfaces Typical ISDN Application
- 17. DescriptionStandardOSI Layer Standards forsupplementary services and advanced network features Multiple ECMA standards3 QSIG generic functional procedures ECMA-165 QSIG basic callECMA-142/143 Interface-dependent protocolsECMA-1412 PRI and BRII.430 / I.4311 QSIG enables Cisco networks to emulate the functionality of the PSTN. A Cisco device routes incoming voice calls from a PINX across a WAN to a peer device, which then transports the signaling and voice packets to a second PINX (see the figure below). Figure 2: QSIG Signaling The Cisco voice-packet network appears to the QSIG PBXs as a distributed transit PBX that can establish calls to any PBX, non-QSIG PBX, or other telephony endpoint served by a Cisco gateway, including non-QSIG endpoints. QSIG messages that originate and terminate on QSIG endpoints pass transparently across the network; the PBXs process and provision any supplementary services. When endpoints are a mix of QSIG and non-QSIG, only basic calls that do not require supplementary services are supported. QSIG signaling provides the following benefits: • It provides efficient and cost-effective telephony services on permanent (virtual) circuits or leased lines. • It allows enterprise networks that include PBX networks to replace leased voice lines with a Cisco WAN. • It eliminates the need to route connections through multiple tandem PBX hops to reach the desired destination, thereby saving bandwidth, PBX hardware, and switching power. • It improves voice quality through the single-hop routing provided by voice switching while allowing voice to be compressed more aggressively, resulting in additional bandwidth savings. • It supports PBX feature transparency across a WAN, permitting PBX networks to provide advanced features such as calling name and number display, camp-on/callback, network call forwarding, centralized attendant, and centralized message waiting. Usually these capabilities are available on only a single site where users are connected to the same PBX. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 5 Overview of ISDN Voice Interfaces QSIG Protocol
- 18. QSIG support enablesthe following: • Digit forwarding on POTS dial peers • On Cisco 2600 series, QSIG-switched calls over VoFR and VoIP for T1/E1 and BRI voice interface cards • On Cisco 3600 series, QSIG-switched calls over VoFR, VoIP, and VoATM for T1/E1 and BRI voice interface cards • On Cisco 7200 series, QSIG-switched calls over VoFR and VoIP on T1/E1 voice interface cards • On Cisco MC3810, T1 or E1 PRI and BRI QSIG-switched calls over VoFR, VoIP, and VoATM for Cisco MC3810 digital voice modules and BRI voice module. See the figure below shows an example of how QSIG support can enable toll bypass. Figure 3: QSIG Toll-Bypass Application ISDN Switch Types for Use with QSIG You can configure QSIG at either the global configuration level or the interface configuration level. To do so requires that you know your switch type. Available types are shown in the table below. Table 2: ISDN Central-Office Switch Types DescriptionISDN Switch TypeCountry Australian TS013 switchesbasic-ts013Australia ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 6 Overview of ISDN Voice Interfaces QSIG Protocol
- 19. DescriptionISDN Switch TypeCountry German1TR6 ISDN switchesbasic-1tr6Europe Norwegian NET3 ISDN switches (phase 1) basic-nwnet3 NET3 ISDN switches (United Kingdom and others) basic-net3 French VN2 ISDN switchesvn2 French VN3 ISDN switchesvn3 Japanese NTT ISDN switchesnttJapan New Zealand NET3 switchesbasic-nznet3New Zealand Lucent Technologies basic rate switches basic-5essNorth America NT DMS-100 basic rate switchesbasic-dms100 National ISDN-1 switchesbasic-ni1 The table below lists the ISDN service-provider BRI switch types. Table 3: ISDN Service-Provider BRI Switch Types DescriptionISDN Switch Type German 1TR6 ISDN switchesbasic-1tr6 Lucent Technologies basic rate switchesbasic-5ess NT DMS-100 basic rate switchesbasic-dms100 NET3 (TBR3) ISDN, Norway NET3, and New Zealand NET3 switches. (This switch type covers the Euro-ISDN E-DSS1 signaling system and is ETSI-compliant.) basic-net3 National ISDN-1 switchesbasic-ni1 Norwegian NET3 ISDN switches (phase 1)basic-nwnet3 New Zealand NET3 switchesbasic-nznet3 PINX (PBX) switches with QSIG signaling in compliance with Q.931 basic-qsig ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 7 Overview of ISDN Voice Interfaces QSIG Protocol
- 20. DescriptionISDN Switch Type AustralianTS013 switchesbasic-ts013 Japanese NTT ISDN switchesntt French VN2 ISDN switchesvn2 French VN3 ISDN switchesvn3 Cisco platforms that support Q.931 offer both user-side and network-side switch types for ISDN call processing, providing the following benefits: • User-side PRI enables the Cisco device to provide a standard ISDN PRI user-side interface to the PSTN. • Network-side PRI enables the Cisco device to provide a standard ISDN PRI network-side interface via digital T1/E1 packet voice trunk network modules on Cisco 2600 series and Cisco 3600 series routers. Traceability of Diverted Calls European Telecommunication Standard ETSI 300 207-1 specifies that calls must be traceable if diverted. This requires that a VoIP call, when diverted, must translate into divertingLegInformation2 instead of Redirection IE. Cisco’s ISDN implementation satisfies this requirement. Additional References The following sections provide references related to ISDN. In addition to the references listed below, each chapter provides additional references related to ISDN.Note • Some of the products and services mentioned in this guide may have reached end of life, end of sale, or both. Details are available at http://www.cisco.com/en/US/products/hw/tsd_products_support_ end-of-sale_and_end-of-life_products_list.html ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 8 Overview of ISDN Voice Interfaces Traceability of Diverted Calls
- 21. Related Documents Document TitleRelatedTopic • AIM-ATM, AIM-VOICE-30, and AIM-ATM-VOICE-30 on the Cisco 2600 Series and Cisco 3660 at http://www.cisco.com/ univercd/cc/td/doc/product/software/ios122/ 122newft/122t/122t8/ft_04gin.htm AIM, ATM, and IMA • ATM Software Segmentation and Reassembly (SAR) at http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122x/122xb/122xb_2/ft_t1atm.htm • Cisco IOS Wide-Area Networking Configuration Guide, c hapter on configuring ATM at http:// www.cisco.com/univercd/cc/td/doc/product/ software/ios122/122cgcr/fwan_c/wcfatm.htm • Installing the High Performance ATM Advanced Integration Module in Cisco 2600 Series Routers at http://www.cisco.com/en/US/ products/hw/routers/ps259/tsd_products_ support_reference_guides.html • Cisco 2600 series documentation at http:// www.cisco.com/en/US/products/hw/routers/ ps259/tsd_products_support_reference_ guides.html Basic router configuration • Cisco 3600 series documentation at http://www.cisco.com/en/US/products/hw/routers/ps274/tsd_products_support_reference_guides.html • Cisco 3700 series documentation at http:// www.cisco.com/univercd/cc/td/doc/product/ access/acs_mod/cis3700/index.htm • Cisco AS5300 documentation at http:// www.cisco.com/univercd/cc/td/doc/product/ access/acs_serv/5300/index.htm ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 9 Overview of ISDN Voice Interfaces Additional References
- 22. Document TitleRelated Topic •Cisco IOS Debug Command Reference, Release 12.3T at http://www.cisco.com/univercd/cc/td/ doc/product/software/ios123/123tcr/123dbr/ index.htm Cisco IOS command references • Cisco IOS Voice Command Reference, Release 12.3T at http://www.cisco.com/univercd/cc/td/ doc/product/software/ios123/123tcr/123tvr/ index.htm • Cisco IOS Configuration Fundamentals Configuration Guide at http://www.cisco.com/ univercd/cc/td/doc/product/software/ios122/ 122cgcr/ffun_c/ Cisco IOS configuration fundamentals and examples • Cisco IOS Interface Command Reference at http://www.cisco.com/univercd/cc/td/doc/ product/software/ios122/122cgcr/finter_r/ index.htm • Cisco IOS Interface Configuration Guide at http://www.cisco.com/univercd/cc/td/doc/ product/software/ios122/122cgcr/finter_c/ • Cisco Systems Technologies website at http:// cisco.com/en/US/tech/index.html From the website, select a technology category and subsequent hierarchy of subcategories, then click Technical Documentation > Configuration Examples. • Cisco IOS Voice Configuration Library at http://www.cisco.com/en/US/docs/ios/12_3/vvf_c/cisco_ios_voice_configuration_library_glossary/vcl.htm Cisco IOS Voice Configuration Library, including library preface and glossary • Cisco IOS Voice, Video, and Fax Configuration Guide chapter on configuring voice ports at http://www.cisco.com/univercd/cc/td/doc/ product/software/ios122/122cgcr/fvvfax_c/ vvfport.htm#18533 Clock sources ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 10 Overview of ISDN Voice Interfaces Additional References
- 23. Document TitleRelated Topic •Cisco IOS Release 12.2 Configuration Guides and Command References library at http:// www.cisco.com/univercd/cc/td/doc/product/ software/ios122/122cgcr/ ISDN basics • Cisco IOS Release 12.3 Configuration Guides and Command References library at http:// www.cisco.com/univercd/cc/td/doc/product/ software/ios123/123cgcr/index.htm • ISDN Switch Types, Codes, and Values at http:/ /www.cisco.com/univercd/cc/td/doc/product/ software/ios113ed/dbook/disdn.htm ISDN cause codes • Cisco IOS Voice, Video, and Fax Configuration Guide at http://www.cisco.com/univercd/cc/td/ doc/product/software/ios122/122cgcr/fvvfax_c/ vvfisdn.htm ISDN configuration • ISDN Basic Rate Service Setup Commands at http://www.cisco.com/univercd/cc/td/doc/ product/software/ios120/12cgcr/dial_r/drprt1/ drbri.htm • Cisco 7200 Series Port Adapter Hardware Configuration Guidelines at http:// www.cisco.com/univercd/cc/td/doc/product/ core/7206/port_adp/config/ ISDN interfaces for voice • Cisco MC3810 Multiservice Concentrator Hardware Installation at http://www.cisco.com/ univercd/cc/td/doc/product/access/multicon/ 3810hwig/ • Quick Start Guide: Cisco MC3810 Installation and Startup at http://www.cisco.com/univercd/ cc/td/doc/product/access/multicon/3810qsg.htm ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 11 Overview of ISDN Voice Interfaces Additional References
- 24. Document TitleRelated Topic •Cisco Network Modules Hardware Installation Guide at http://www.cisco.com/univercd/cc/td/ doc/product/access/acs_mod/cis2600/hw_inst/ nm_inst/nm-doc/ ISDN network modules and interface cards • Cisco WAN Interface Cards Hardware Installation Guide at http://www.cisco.com/ univercd/cc/td/doc/product/access/acs_mod/ cis3600/wan_mod/ • Installing and Configuring 1-Port J1 Voice Interface Cards at http://www.cisco.com/univercd/cc/td/doc/product/access/acs_mod/cis3600/hw_inst/hw_notes/j1vwic.htm • Update to Cisco WAN Interface Cards Hardware Installation Guide at http:// www.cisco.com/univercd/cc/td/doc/product/ access/acs_mod/cis2600/hw_inst/wic_inst/wan_ updt.htm • Voice Network Module and Voice Interface Card Configuration Note at http:// www.cisco.com/univercd/cc/td/doc/product/ access/acs_mod/cis3600/voice/4712voic.htm • Multiservice Interchange (MIX) for Cisco 2600 and 3600 Series Multiservice Platforms athttp:/ /www.cisco.com/univercd/cc/td/doc/product/ software/ios122/122newft/122t/122t4/ft_ 24mix.htm MIX module • RADIUS VSA Voice Implementation Guide at http://www.cisco.com/univercd/cc/td/doc/ product/access/acs_serv/vapp_dev/vsaig3.htm RADIUS VSA configuration • Stream Control Transfer Protocol (SCTP) at http://www.cisco.com/univercd/cc/td/doc/ product/software/ios122/122newft/122t/122t8/ ft_sctp2.htm SCTP ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 12 Overview of ISDN Voice Interfaces Additional References
- 25. Document TitleRelated Topic •Cisco IOS Security Configuration Guide at http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fsecur_c/index.htm Security • Configuring Media Gateways for the SS7 Interconnect for Voice Gateways Solution at http://www.cisco.com/univercd/cc/td/doc/ product/access/sc/rel7/soln/das22/gateway/ dascfg5.htm SS7 for voice gateways • Tcl IVR API Version 2.0 Programmer's Guide at http://www.cisco.com/univercd/cc/td/doc/ product/access/acs_serv/vapp_dev/tclivrv2/ index.htm Tcl IVR programming • Cisco IOS Debug Command Reference, Release 12.3T at http://www.cisco.com/univercd/cc/td/ doc/product/software/ios123/123tcr/123dbr/ index.htm Troubleshooting • Cisco IOS Voice Troubleshooting and Monitoring Guide at http://www.cisco.com/ univercd/cc/td/doc/product/software/ios123/ 123cgcr/vvfax_c/voipt_c/index.htm • Internetwork Troubleshooting Guide at http:// www.cisco.com/univercd/cc/td/doc/cisintwk/ itg_v1/index.htm • Voice over IP Troubleshooting and Monitoring at http://cisco.com/univercd/cc/td/doc/product/ software/ios123/123cgcr/vvfax_c/voipt_c/ index.htm • Configuring AAL2 and AAL5 for the High-Performance Advanced Integration Module on the Cisco 2600 Series athttp:// www.cisco.com/univercd/cc/td/doc/product/ software/ios122/122newft/122limit/122x/122xa/ 122xa_2/ft_ataim.htm VoATM configuration ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 13 Overview of ISDN Voice Interfaces Additional References
- 26. Document TitleRelated Topic •Voice over IP for the Cisco 2600/3600 Series at http://www.cisco.com/univercd/cc/td/doc/ product/access/nubuvoip/voip3600/index.htm VoIP configuration • Voice over IP for the Cisco AS5300 at http:// www.cisco.com/univercd/cc/td/doc/product/ access/nubuvoip/voip5300/index.htm • Voice over IP for the Cisco AS5800 at http:// www.cisco.com/univercd/cc/td/doc/product/ access/nubuvoip/voip5800/index.htm • Cisco IOS Wide-Area Networking Command Reference athttp://www.cisco.com/univercd/ cc/td/doc/product/software/ios122/122cgcr/ fwan_r/index.htm WAN configuration • Cisco IOS Wide-Area Networking Configuration Guide at http://www.cisco.com/univercd/cc/td/ doc/product/software/ios122/122cgcr/fwan_c/ wcfatm.htm Standards TitleStandards CPE Requirements for MCI ISDN Primary Rate Interface, revision 4.3D, February 10, 1998 014-0018-04.3D-ER Integrated Services Digital Network (ISDN): Diversion supplementary services; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 1: Protocol specification , December 1994 ETSI 300 207-1 AT&T Network ISDN Primary Rate Interface and Special Applications Specifications, User-Network Interface, 1999 TR-41459 PBXTTC JJ-20.10 to JJ-20.12 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 14 Overview of ISDN Voice Interfaces Additional References
- 27. MIBs MIBs LinkMIBs To locateand download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL: http:// www.cisco.com/go/mibs • CISCO-CAS-IF-MIB.my • CISCO-ICSUDSU-MIB • RFC 1407 MIB RFCs TitleRFCs Stream Control Transmission Protocol (SCTP), Release 2 SCTP Technical Assistance LinkDescription http://www.cisco.com/techsupportThe Cisco Technical Support website contains thousands of pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 15 Overview of ISDN Voice Interfaces Additional References
- 28. ISDN Voice ConfigurationGuide, Cisco IOS Release 15M&T 16 Overview of ISDN Voice Interfaces Additional References
- 29. C H AP T E R 2 Basic ISDN Voice-Interface Configuration This chapter describes how to configure ISDN BRI and PRI ports to support voice traffic. For more information about related Cisco IOS voice features, see the following: • "Overview of ISDN Voice Interfaces" • Entire Cisco IOS Voice Configuration Library--including library preface and glossary, other feature documents, and troubleshooting documentation--at http://www.cisco.com/en/US/docs/ios/12_3/vvf_c/cisco_ios_voice_configuration_library_glossary/vcl.htm For a list of references cited in this chapter, see the Additional References, on page 77. • Finding Feature Information, page 17 • Prerequisites for Configuring an ISDN Voice Interface, page 18 • Restrictions for Configuring an ISDN Voice Interface, page 18 • Information About ISDN Voice Interfaces, page 18 • How to Configure an ISDN Voice Interface, page 18 • Configuration Examples for ISDN Voice Interfaces, page 57 • Additional References, page 77 Finding Feature Information Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 17
- 30. Prerequisites for Configuringan ISDN Voice Interface • Perform the prerequisites that are listed in the "Prerequisites for Configuring ISDN Voice Interfaces" section. • Obtain PRI or BRI service and T1 or E1 service from your service provider, as required. Ensure that the BRI lines are provisioned at the switch to support voice calls. • Establish a working IP, Frame Relay, or ATM network. Ensure that at least one network module or WAN interface card is installed in the router to provide connection to the LAN or WAN. • Complete your company’s dial plan. • Establish a working telephony network based on your company’s dial plan and configure the network for real-time voice traffic. • Cisco 2600 series and Cisco 3600 series--Install digital T1 or E1 packet-voice trunk network modules, BRI voice interface cards, and other voice interface cards as required on your network. • Cisco 7200 series--Install a single-port 30-channel T1/E1 high-density voice port adapter. • Cisco MC3810--Install the required digital voice modules (DVMs), BRI voice module (BVM), and multiflex trunk modules. • Configure, for all platforms (as required), the following: • Voice card and controller settings • Serial and LAN interfaces • Voice ports • Voice dial peers Restrictions for Configuring an ISDN Voice Interface Restrictions are described in the "Restrictions for Configuring ISDN Voice Interfaces" section. Information About ISDN Voice Interfaces General information about ISDN voice interfaces is presented in the "Information About ISDN Voice Interfaces" section. How to Configure an ISDN Voice Interface Configuring a Router for ISDN BRI Voice-Interface Support This section contains the following procedures: ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 18 Basic ISDN Voice-Interface Configuration Prerequisites for Configuring an ISDN Voice Interface
- 31. Configuring BRI NTand TE Interfaces To configure BRI NT and TE interfaces, perform the following steps. Set up each channel for either user side or network side.Note SUMMARY STEPS 1. enable 2. configure terminal 3. isdn switch-type switch-type 4. Cisco MC3810 5. no ip address 6. isdn overlap-receiving 7. isdn twait-disable 8. isdn spid1 spid-number [ldn] 9. isdn spid2 spid-number [ldn] 10. isdn incoming-voice {voice | modem} 11. shutdown 12. Do one of the following: • isdn layer1-emulate user • • • isdn layer1-emulate network 13. no shutdown 14. network-clock-priority {low | high} 15. Cisco MC3810 Only 16. Do one of the following: • isdn protocol-emulate user • • • isdn protocol-emulate network 17. isdn sending-complete 18. isdn static-tei tei-number 19. isdn point-to-point-setup 20. exit 21. Cisco MC3810 22. Repeat the appropriate steps for the other BRI NT/TE interfaces. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 19 Basic ISDN Voice-Interface Configuration Configuring a Router for ISDN BRI Voice-Interface Support
- 32. DETAILED STEPS PurposeCommand orAction Enters privileged EXEC mode. Enter your password when prompted. enable Example: Router> enable Step 1 Enters configuration mode.configure terminal Example: Router# configure terminal Step 2 Configures the telephone-company ISDN switch type. Table 3 on page 9 shows a list of switch types. isdn switch-type switch-type Example: Router(config)# isdn switch-type basic-qsig Step 3 The only switch types currently supported for an NT interface are basic-net3 and basic-qsig. Note Enters interface configuration mode for the specified port, connector, or interface card number (location of voice module) Cisco MC3810 Example: Step 4 or slot/port (location of voice network module and voice interface card). interface bri number Example: Other Supported Routers Example: interface bri slot/port Example: Router(config)# interface bri 1/1 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 20 Basic ISDN Voice-Interface Configuration Configuring a Router for ISDN BRI Voice-Interface Support
- 33. PurposeCommand or Action Specifiesthat there is no IP address for this interface.no ip address Example: Router(config-if)# no ip address Step 5 (Optional) Activates overlap signaling to send to the destination PBX. In this mode, the interface waits for possible additional call-control information. isdn overlap-receiving Example: Router(config-if)# isdn overlap-receiving Step 6 (Optional) Delays a national ISDN BRI switch for a random length of time before activating the Layer 2 interface at switch isdn twait-disable Example: Router(config-if)# isdn twait-disable Step 7 startup. Use this command when the ISDN switch type is basic-ni1. Twait time is enabled by default. (Optional; TE only) Service-profile identifier (SPID) and optional local directory number for the B1 channel. Currently, only isdn spid1 spid-number [ldn] Example: Router(config-if)# isdn spid1 40855501220101 Step 8 DMS-100 and NI-1 switch types require SPIDs. Although some switch types might support a SPID, Cisco recommends that you set up ISDN service without SPIDs. (Optional; TE only) Specifies SPID and optional local directory number for the B2 channel. isdn spid2 spid-number [ldn] Example: Router(config-if)# isdn spid2 40855501220102 Step 9 Configures the port to treat incoming ISDN voice calls as voice calls that are handled by either a modem or a voice DSP, as directed by the call-switching module. isdn incoming-voice {voice | modem} Example: Router(config-if)# isdn incoming-voice voice Step 10 Turns off the port (before setting port emulation).shutdown Example: Router(config-if)# shutdown Step 11 (User side only) Configures Layer 1 port mode emulation and clock status for the user--that is, the TE (clock slave). Do one of the following:Step 12 • isdn layer1-emulate user or • (Network side only) Configures Layer 1 port mode emulation and clock status for the network--that is, the NT (clock master). • • isdn layer1-emulate network ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 21 Basic ISDN Voice-Interface Configuration Configuring a Router for ISDN BRI Voice-Interface Support
- 34. PurposeCommand or Action Example: Router(config-if)#isdn layer1-emulate user Example: Example: Example: Router(config-if)# isdn layer1-emulate network Turns on the port.no shutdown Example: Router(config-if)# no shutdown Step 13 (Optional; TE only) Sets priority for recovering clock signal from the network NT device for this BRI voice port. Keywords are as follows: network-clock-priority {low | high} Example: Router(config-if)# network-clock-priority low Step 14 • high --First priority (default for BRI voice interface cards) • low --Low priority (default for BRI voice modules) Do not use this command if the port is configured as NT in Configuring BRI NT and TE Interfaces. Note Turns on the power supplied from an NT-configured port to a TE device. Cisco MC3810 Only Example: Step 15 line-power Example: Router(config-if)# line-power (User side only) Configures Layer 2 and Layer 3 port mode emulation and clock status for the user--that is, the TE (clock master). Do one of the following:Step 16 • isdn protocol-emulate user • or ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 22 Basic ISDN Voice-Interface Configuration Configuring a Router for ISDN BRI Voice-Interface Support
- 35. PurposeCommand or Action (Networkside only) Configures Layer 2 and Layer 3 port mode emulation and clock status for the network--that is, the NT (clock slave). • • isdn protocol-emulate network Example: Router(config-if)# isdn protocol-emulate user Example: Example: Example: Router(config-if)# isdn protocol-emulate network (Optional) Configures the voice port to include the "Sending Complete" information element in the outgoing call-setup isdn sending-complete Example: Router(config-if)# isdn sending-complete Step 17 message. This command is used in some geographic locations, such as Hong Kong and Taiwan, where the "Sending Complete" information element is required in the outgoing call setup message. (Optional) Configures a static ISDN Layer 2 terminal endpoint identifier (TEI). isdn static-tei tei-number Example: Router(config-if)# isdn static-tei 0 Step 18 (Optional) Configures the ISDN port to send SETUP messages on the static TEI (point-to-point link). isdn point-to-point-setup Example: Router(config-if)# isdn point-to-point-setup Step 19 A static TEI must be configured in order for this command to be effective. Note Exits the current mode.exit Example: Router(config-if)# exit Step 20 (Optional) Resets the specified port, connector, or interface card number (location of voice module) or slot/port (location of voice Cisco MC3810 Example: clear interface bri number Step 21 network module and voice interface card). The interface needs to be reset if the static TEI number was configured in Configuring BRI NT and TE Interfaces. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 23 Basic ISDN Voice-Interface Configuration Configuring a Router for ISDN BRI Voice-Interface Support
- 36. PurposeCommand or Action Example: OtherSupported Routers Example: clear interface bri slot/port Example: Router# clear interface bri 1/1 --Repeat the appropriate steps for the other BRI NT/TE interfaces. Step 22 What to Do Next To complete voice configuration, set up your voice ports and dial peers.Note Verifying BRI Interfaces To verify BRI interfaces, perform the following steps (listed alphabetically). SUMMARY STEPS 1. show controllers bri number or show controllers bri slot/port 2. show interfaces bri 3. show isdn {active [serial-number] | history [serial-number]} 4. show isdn {memory | status | timers 5. show isdn status 6. show running-config 7. show voice port slot/port | summary ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 24 Basic ISDN Voice-Interface Configuration Configuring a Router for ISDN BRI Voice-Interface Support
- 37. DETAILED STEPS Step 1show controllers bri number or show controllers bri slot/port Use this command to display information about the specified BRI port, connector, or interface card number (location of voice module) or slot/port (location of voice network module and voice interface card). Step 2 show interfaces bri Use this command to display information about the physical attributes of the BRI B and D channels. In the output, look for the term spoofing , which indicates that the interface presents itself to the Cisco IOS software as operational. Step 3 show isdn {active [serial-number] | history [serial-number]} Use this command to display current (active keyword) or both historic and current (history keyword) call information for all ISDN interfaces or, optionally, a specific ISDN PRI interface (created and configured as a serial interface). Information displayed includes called number, remote node name, seconds of connect time, seconds of connect time remaining, seconds idle, and advice of charge (AOC) charging time units used during the call. Step 4 show isdn {memory | status | timers Use this command to display information about memory, status, and Layer 2 and Layer 3 timers. Step 5 show isdn status Use this command to display the status of all ISDN interfaces, including active layers, timer information, and switch-type settings. Step 6 show running-config Use this command to display basic router configuration. Step 7 show voice port slot/port | summary Use this command to display information about BRI voice ports. Examples This section provides the following output examples: Sample Output for the show running-config Command The following is sample output from a Cisco 2600 series system. Note that BRI1/0 and BRI1/1 are configured as ISDN user side and BRI2/0 and BRI2/1 are configured as ISDN network side. The table below describes significant fields shown in this output Router# show running-config Building configuration... Current configuration: ! version 12.2 ! no service udp-small-servers service tcp-small-servers ! hostname Router ! username xxxx password x 11x5xx07 no ip domain-lookup ip host Labhost 172.22.66.11 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 25 Basic ISDN Voice-Interface Configuration Configuring a Router for ISDN BRI Voice-Interface Support
- 38. ip host Labhost2172.22.66.12 ip name-server 172.22.66.21 ! . . . interface BRI1/0 no ip address no ip directed-broadcast isdn switch-type basic-net3 isdn overlap-receiving isdn T306 30000 isdn skipsend-idverify isdn incoming-voice voice ! interface BRI1/1 no ip address no ip directed-broadcast isdn switch-type basic-net3 isdn overlap-receiving isdn T306 30000 isdn skipsend-idverify isdn incoming-voice voice ! interface BRI2/0 no ip address isdn switch-type basic-net3 isdn overlap-receiving isdn protocol-emulate network isdn layer1-emulate network isdn T306 30000 isdn sending-complete isdn skipsend-idverify isdn incoming-voice voice ! interface BRI2/1 no ip address isdn switch-type basic-net3 isdn overlap-receiving isdn protocol-emulate network isdn layer1-emulate network isdn T306 30000 isdn sending-complete isdn skipsend-idverify isdn incoming-voice voice ! . . . The following is sample output from a Cisco MC3810 system. The table below describes significant fields shown in this output. Router# show running-config Building configuration... Current configuration: ! version 12.2 service timestamps debug uptime service timestamps log uptime no service password-encryption ! hostname Router ! no logging console ! network-clock base-rate 56k network-clock-select 2 T1 0 network-clock-select 3 system(SCB) network-clock-select 1 BVM ip subnet-zero ! ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 26 Basic ISDN Voice-Interface Configuration Configuring a Router for ISDN BRI Voice-Interface Support
- 39. isdn switch-type basic-net3 isdnvoice-call-failure 0 call rsvp-sync ! voice-card 0 ! controller T1 0 mode atm framing esf linecode b8zs ! interface BRI1 no ip address isdn switch-type basic-net3 isdn protocol-emulate network isdn layer1-emulate network isdn incoming-voice voice isdn T306 30000 isdn skipsend-idverify no cdp enable ! interface BRI2 no ip address isdn switch-type basic-net3 isdn protocol-emulate network isdn layer1-emulate network isdn incoming-voice voice isdn T306 30000 isdn skipsend-idverify no cdp enable ! interface BRI3 no ip address shutdown network-clock-priority low isdn switch-type basic-net3 isdn T306 30000 no cdp enable ! interface BRI4 no ip address shutdown network-clock-priority low isdn switch-type basic-net3 isdn T306 30000 no cdp enable ! . . . The table below describes significant fields shown in these outputs. Table 4: Significant Fields from the show running-config Command DescriptionField Value of the T306 timer, in ms. An ISDN timer is started when a Q.931 Disconnect message with progress indicator number 8 is sent. The timer is stopped when a ISDN Release/Disconnect message is received from the other end. The call clears on expiration of the T306 timer. isdn T306 timer-value ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 27 Basic ISDN Voice-Interface Configuration Configuring a Router for ISDN BRI Voice-Interface Support
- 40. DescriptionField Value of theT310 timer, in ms. An ISDN timer is started when a Q.931 Call Proceeding message is received. The timer is stopped when a Q.931 Alerting/Connect/Disconnect message is received from the other end. The call clears on expiration of the T310 timer. isdn T310 timer-value Sample Output for the show interfaces bri Command The following shows sample output for a Cisco 2610. The table below describes significant fields shown in this output. Router# show interfaces bri 1/0 BRI3/1 is up, line protocol is up (spoofing) Hardware is Voice NT or TE BRI MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation VOICE, loopback not set Last input 00:00:02, output never, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: weighted fair Output queue: 0/1000/64/0 (size/max total/threshold/drops) Conversations 0/0/16 (active/max active/max total) Reserved Conversations 0/0 (allocated/max allocated) 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 26110 packets input, 104781 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 0 packets output, 0 bytes, 0 underruns 0 output errors, 0 collisions, 5 interface resets 0 output buffer failures, 0 output buffers swapped out 9 carrier transitions The following shows sample output for a Cisco MC3810. The table below describes significant fields shown in this output. Router# show interfaces bri 1 BRI1 is up, line protocol is up (spoofing) Hardware is BVM MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation HDLC, loopback not set Last input 19:32:19, output 19:32:27, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: weighted fair Output queue: 0/1000/64/0 (size/max total/threshold/drops) Conversations 0/1/16 (active/max active/max total) Reserved Conversations 0/0 (allocated/max allocated) 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 13282 packets input, 53486 bytes, 0 no buffer Received 1 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 13292 packets output, 53515 bytes, 0 underruns 0 output errors, 0 collisions, 4 interface resets 0 output buffer failures, 0 output buffers swapped out 33 carrier transitions ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 28 Basic ISDN Voice-Interface Configuration Configuring a Router for ISDN BRI Voice-Interface Support
- 41. Table 5: SignificantFields from the show interfaces bri Command DescriptionField (in alpha order) Illegal sequence of one bits on a serial interface. This usually indicates a clocking problem between the serial interface and the data link equipment. abort Whether the interface hardware is currently active (whether line signal is present) and whether it has been taken down by an administrator. BRI... is {up | down | administratively down} Total number of broadcast or multicast packets received by the interface. broadcasts Bandwidth of the interface in kbps.BW Total number of bytes, including data and media access control (MAC) encapsulation, in the error-free packets sent or received by the system. bytes Number of times that the carrier detect signal of a serial interface has changed state. Check for modem or line problems if the carrier detect line is changing state often. carrier transitions Number of collisions. These can occur when you have several devices connected on a multiport line. collisions Cyclic redundancy checksum generated by the originating station or far-end device does not match the checksum calculated from the data received. On a serial link, CRCs usually indicate noise, gain hits, or other transmission problems on the data link. CRC Delay of the interface in microseconds.DLY Encapsulation method assigned to interface.encapsulation Average number of bits and packets transmitted per second in the last 5 minutes. five-minute input/output rate Number of packets that are received incorrectly having a CRC error and a noninteger number of octets. On a serial line, this is usually the result of noise or other transmission problems. frame Number of packets that are discarded because they exceed the medium's maximum packet size. giants Hardware type.Hardware is... ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 29 Basic ISDN Voice-Interface Configuration Configuring a Router for ISDN BRI Voice-Interface Support
- 42. DescriptionField (in alphaorder) Number of received packets that are ignored by the interface because the interface hardware ran low on internal buffers. Broadcast storms and bursts of noise can increase the ignored count. ignored Total number of no buffer, runts, giants, CRCs, frame, overrun, ignored, and abort counts. Other input-related errors can also increment the count, so this sum may not balance with the other counts. input errors Number of packets in output and input queues. Each number is followed by a slash (/), the maximum size of the queue, and the number of packets dropped due to a full queue. input/output queue, drops Number of times that an interface has been completely reset. This can happen if packets queued for transmission were not sent within several seconds. On a serial line, this can be caused by a malfunctioning modem that is not supplying the transmit clock signal or by a cable problem. If the system recognizes that the carrier detect line of a serial interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an interface is looped back or shut down. interface resets IP address and subnet mask, followed by packet size.Internet address is... Whether keepalives are set.keepalive Number of hours, minutes, and seconds since the last packet was successfully received by an interface. Useful for knowing when a nonfunctioning interface failed. last input Whether the software processes that handle the line protocol consider the line usable (that is, whether keepalives are successful). line protocol is {up | down | administratively down} Load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes. load Whether loopback is set.loopback Maximum transmission unit of the interface.MTU ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 30 Basic ISDN Voice-Interface Configuration Configuring a Router for ISDN BRI Voice-Interface Support
- 43. DescriptionField (in alphaorder) Number of received packets that are discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernets and bursts of noise on serial lines are often responsible for no input buffer events. no buffer Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface. output Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this may not balance with the sum of the enumerated output errors, because some datagrams may have more than one error, and others may have errors that do not fall into any of the specifically tabulated categories. output errors Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks (**) are printed. output hang Number of packets in output and input queues. Each number is followed by a slash (/), the maximum size of the queue, and the number of packets dropped due to a full queue. output/input queue, drops Number of times that the serial receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data. overrun Total number of error-free packets received or sent by the system. packets input/output Reliability of the interface as a fraction of 255 (255/255 is 100 percent reliability), calculated as an exponential average over 5 minutes. rely Number of times that the controller was restarted because of errors restarts Number of packets that are discarded because they are smaller than the medium’s minimum packet size. runts ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 31 Basic ISDN Voice-Interface Configuration Configuring a Router for ISDN BRI Voice-Interface Support
- 44. DescriptionField (in alphaorder) Number of times that the transmitter has been running faster than the router can handle. This may never be reported on some interfaces. underruns Troubleshooting Tips • Use the debug isdn q921command to display Layer 2 access procedures that are taking place at the router on the D channel (LAPD) of its ISDN interface. • Use the debug isdn q931command to display information about call setup and teardown of ISDN network connections (Layer 3) between the local router (user side) and the network. • For information on these and additional debug commands, see the following references: • Cisco IOS Debug Command Reference, Release 12.3T at http://www.cisco.com/univercd/cc/td/ doc/product/software/ios123/123tcr/123dbr/index.htm • Cisco IOS Voice Troubleshooting and Monitoring Guide at http://www.cisco.com/univercd/cc/td/ doc/product/software/ios123/123cgcr/vvfax_c/voipt_c/index.htm Configuring ISDN PRI Voice-Interface Support This section contains the following procedures: Configuring PRI Interfaces To configure PRI interfaces, perform the following steps. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 32 Basic ISDN Voice-Interface Configuration Configuring ISDN PRI Voice-Interface Support
- 45. SUMMARY STEPS 1. enable 2.configure terminal 3. isdn switch-type switch-type 4. Cisco AS5300 5. description string 6. framing esf 7. linecode {ami | b8zs | hdb3} 8. pri-group timeslots range 9. exit 10. Cisco AS5300 11. isdn incoming-voice modem 12. description string 13. isdn-bchan-number-order {ascending | descending} 14. exit DETAILED STEPS PurposeCommand or Action Enters privileged EXEC mode. Enter your password when prompted. enable Example: Router> enable Step 1 Enters configuration mode.configure terminal Example: Router# configure terminal Step 2 Configures the telephone company ISDN switch type. Table 3 on page 9 shows a list of switch types. isdn switch-type switch-type Example: Router(config)# isdn switch-type basic-qsig Step 3 The only switch types currently supported for an NT interface are basic-net3 and basic-qsig. Note Enters T1/E1 controller configuration mode for the specified (as appropriate) dial shelf, slot, port (or T3 port), and timeslot as follows: Cisco AS5300 Example: controller {t1 | e1} 0 Step 4 • Cisco AS5300: T1 0 or E1 0 controller • Cisco AS5800 (T1 card): T1 0 controller ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 33 Basic ISDN Voice-Interface Configuration Configuring ISDN PRI Voice-Interface Support
- 46. PurposeCommand or Action Example: •Cisco AS5800 (T3 card): T1 1 controller Cisco AS5800 (T1 card) Example: controller t1 1/0/0 Example: Cisco AS5800 (T3 card) Example: controller t1 1/0/0 : 1 Example: Router(config)# controller t1 1/0/0 Includes a specific description about the digital signal processor (DSP) interface. description string Example: Router(config-if)# description interface01 Step 5 Defines the framing characteristics.framing esf Example: Router(config-controller)# framing esf Step 6 Sets the line-encoding method to match that of your telephone-company service provider. Keywords are as follows: linecode {ami | b8zs | hdb3} Example: Router(config-controller)# linecode ami Step 7 • ami --Alternate mark inversion (AMI), valid for T1 or E1 controllers. Default for T1 lines. • b8zs --B8ZS, valid for T1 controllers only. • hdb3 --High-density bipolar 3 (hdb3), valid for E1 controllers only. Default for E1 lines. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 34 Basic ISDN Voice-Interface Configuration Configuring ISDN PRI Voice-Interface Support
- 47. PurposeCommand or Action SpecifiesPRI on the specified or timeslots that make up the PRI group. Maximum T1 range: 1 to 23. Maximum E1 range: 1 to 31. Separate low and high values with a hyphen. pri-group timeslots range Example: Router(config-controller)# pri-group timeslots 1-23 Step 8 You can configure the PRI group to include all available timeslots, or you can configure a select group of timeslots for the PRI group. Note Exits the current mode.exit Example: Router(config-controller)# exit Step 9 Enters interface configuration mode for the specified PRI slot/port and D-channel ISDN interface. D-channel ISDN interface is (for T1) 23 and (for E1) 15. Cisco AS5300 Example: Step 10 interface serial 0: channel-number Example: Cisco AS5800 Example: interface serial 1/0: channel-number Example: Router(config)# interface serial 0:23 Enables incoming ISDN voice calls.isdn incoming-voice modemStep 11 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 35 Basic ISDN Voice-Interface Configuration Configuring ISDN PRI Voice-Interface Support
- 48. PurposeCommand or Action Example: Router(config-if)#isdn incoming-voice modem The modem keyword specifies that incoming voice calls are passed over to digital modems, where they negotiate the appropriate modem connection with the far-end modem. Its use here is required. Includes a specific description about the digital signal processor (DSP) interface. description string Example: Router(config-if)# description interface02 Step 12 Configures an ISDN PRI interface to make outgoing call selection in ascending or descending order--that is, to select the lowest or isdn-bchan-number-order {ascending | descending} Step 13 highest available B channel starting at either channel B1 (ascending) Example: Router(config-if)# isdn-bchan-number-order descending or channel B23 for a T1 and channel B30 for an E1 (descending). Default: descending. Before configuring ISDN PRI on your router, check with your service vendor to determine if ISDN trunk call selection is configured for ascending or descending order. A mismatch between router and switch causes the switch to send an error message stating that the channel is not available. Note Exits the current mode.exit Example: Router(config-if)# exit Step 14 Configuring PRI Voice Ports Under most circumstances, default voice-port command values are adequate to configure voice ports to transport voice data over your existing IP network. However, because of the inherent complexities of PBX networks, you might need to configure specific voice-port values, depending on the specifications of the devices in your network. Verifying PRI Interfaces To verify PRI interfaces, perform the following steps (listed alphabetically). ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 36 Basic ISDN Voice-Interface Configuration Configuring ISDN PRI Voice-Interface Support
- 49. SUMMARY STEPS 1. showisdn {active [serial-number] | history [serial-number]} 2. show isdn status 3. show vfc slot version 4. show voice port slot/port | summary DETAILED STEPS Step 1 show isdn {active [serial-number] | history [serial-number]} Use this command to display current (active keyword) or both historic and current (history keyword) call information for all ISDN interfaces or, optionally, a specific ISDN PRI interface (created and configured as a serial interface). Information displayed includes called number, remote node name, seconds of connect time, seconds of connect time remaining, seconds idle, and advice of charge (AOC) charging time units used during the call. Step 2 show isdn status Use this command to display the status of all ISDN interfaces, including active layers, timer information, and switch-type settings. Step 3 show vfc slot version Use this command to display the version of software residing on the voice feature card in the specified slot. Step 4 show voice port slot/port | summary Use this command to display configuration information about a specific voice port. Troubleshooting Tips • Verify that you have dial tone and connectivity. • If you have not configured your device to support Direct Inward Dialing (DID), do the following: • Dial in to the router and verify that you have dial tone. • Enter a dual-tone multifrequency (DTMF) digit. If dial tone stops, you have verified two-way voice connectivity with the router. • If you have trouble connecting a call and suspect that the problem is associated with voice-port configuration, do the following: • Confirm connectivity by pinging the associated IP address. For more information, see the Cisco IOS IP Configuration Guide chapter on configuring IP.Note 1 Determine if the voice feature card (VFC) is installed correctly. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 37 Basic ISDN Voice-Interface Configuration Configuring ISDN PRI Voice-Interface Support
- 50. For more information,see the instructions that came with your voice network module.Note 1 Ensure that your (T1-line) a-law or (E1-line) mu-law setting is correct. 2 If dialing cannot occur, use the debug isdn q931 command to check the ISDN configuration. For T1 troubleshooting information, see http://www.cisco.com/en/US/tech/tk713/tk628/technologies_ tech_note09186a00800a5f40.shtml Note Configuring QSIG Support This section contains the following procedures: Configure Global QSIG Support for BRI or PRI To configure global QSIG support for BRI or PRI, perform the following steps. For additional guidance on switch-type configuration, see the "ISDN Switch Types for Use with QSIG" section on page 9 . Note SUMMARY STEPS 1. enable 2. configure terminal 3. BRI on Cisco MC3810, Cisco 2600 Series, and Cisco 3600 Series 4. BRI or PRI on Cisco 7200 Series 5. BRI or PRI on Cisco 7200 Series 6. exit DETAILED STEPS PurposeCommand or Action Enters privileged EXEC mode. Enter your password when prompted. enable Example: Router> enable Step 1 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 38 Basic ISDN Voice-Interface Configuration Configuring QSIG Support
- 51. PurposeCommand or Action Entersconfiguration mode.configure terminal Example: Router# configure terminal Step 2 (Optional) Configures the global ISDN switch type to support QSIG signaling. Table 2 on page 9 shows a list of switch types. BRI on Cisco MC3810, Cisco 2600 Series, and Cisco 3600 Series Example: Step 3 You can configure all interfaces at once by using this command in global configuration mode. Or you can configure one interface at a time by using this command in interface configuration mode. Note isdn switch-type basic-qsig Example: PRI on Any Supported Router Example: isdn switch-type primary-qsig Example: Router(config)# isdn switch-type basic-qsig Configures the digital signal processor (DSP) farm at the specified slot/port. BRI or PRI on Cisco 7200 Series Example: dspint dspfarm slot/port Step 4 Example: Router(config)# dspint dspfarm 1/1 Configures card type (T1 or E1) at the specified slot.BRI or PRI on Cisco 7200 Series Example: card type {t1 | e1} slot Step 5 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 39 Basic ISDN Voice-Interface Configuration Configuring QSIG Support
- 52. PurposeCommand or Action Example: Router(config)#card type t1 0 Exits the current mode.exit Example: Router(config)# exit Step 6 Configure Controllers for QSIG over PRI To configure controllers for QSIG over PRI, perform the following steps. Steps in this section apply to PRI only, and not to BRI.Note SUMMARY STEPS 1. enable 2. configure terminal 3. Cisco MC3810 4. pri-group timeslots range 5. exit DETAILED STEPS PurposeCommand or Action Enters privileged EXEC mode. Enter your password when prompted. enable Example: Router> enable Step 1 Enters configuration mode.configure terminal Example: Router# configure terminal Step 2 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 40 Basic ISDN Voice-Interface Configuration Configuring QSIG Support
- 53. PurposeCommand or Action EntersT1 or E1 controller configuration mode for the specified controller number o r slot/port. Cisco MC3810 Example: Step 3 Cisco MC3810 supports QSIG only on controller 1. Note controller {t1 | e1} controller-number Example: Other Supported Routers Example: controller {t1 | e1} slot/port Example: Router(config)# controller t1 1/1 Specifies PRI on the specified or timeslots that make up the PRI group. Maximum T1 range: 1-23. Maximum E1 range: 1-31. Separate low and high values with a hyphen. pri-group timeslots range Example: Router(config-controller)# pri-group timeslots 1-23 Step 4 You can configure the PRI group to include all available timeslots, or you can configure a select group of timeslots for the PRI group. Note Exits the current mode.exit Example: Router(config-controller)# exit Step 5 Configure PRI Interfaces for QSIG To configure PRI interfaces for QSIG, perform the following steps. Set up each channel for either user side or network side.Note ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 41 Basic ISDN Voice-Interface Configuration Configuring QSIG Support
- 54. SUMMARY STEPS 1. enable 2.configure terminal 3. Cisco MC3810 4. isdn switch-type primary-qsig 5. isdn contiguous-bchan 6. Do one of the following: • isdn protocol-emulate user • • • isdn protocol-emulate network 7. isdn overlap-receiving 8. isdn network-failure-cause value 9. exit DETAILED STEPS PurposeCommand or Action Enters privileged EXEC mode. Enter your password when prompted.enable Example: Router> enable Step 1 Enters configuration mode.configure terminal Example: Router# configure terminal Step 2 Enters interface configuration mode for the specified PRI slot/port and D-channel ISDN interface. D-channel ISDN interface is (for T1) 23 and (for E1) 15. Cisco MC3810 Example: Step 3 interface serial 1: channel-number ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 42 Basic ISDN Voice-Interface Configuration Configuring QSIG Support
- 55. PurposeCommand or Action Example: OtherSupported Routers Example: interface serial slot/port : channel-number Example: Router(config)# interface serial 1/1:23 If you did not configure the global PRI ISDN switch type for QSIG support in global configuration mode, configures the interface ISDN switch type to support QSIG signaling. isdn switch-type primary-qsig Example: Router(config-if)# isdn switch-type primary-qsig Step 4 Conditions that apply to this command in global configuration mode also apply in interface configuration mode. For more information, see the "ISDN Switch Types for Use with QSIG" section on page 9 . For this interface, this interface configuration command overrides the setting of the isdn switch-type command entered in global configuration mode. Note (E1 only) Sets contiguous bearer-channel handling, causing B channels 1 to 30 to map to timeslots 1 to 31, skipping timeslot 16. isdn contiguous-bchan Example: Router(config-if)# isdn contiguous-bchan Step 5 (User side only) Configures Layer 2 and Layer 3 port mode emulation and clock status for the user--that is, the TE (clock slave). This is the default. Do one of the following:Step 6 • isdn protocol-emulate user • or • (Network side only) Configures Layer 2 and Layer 3 port mode emulation and clock status for the network--that is, the NT (clock master). • isdn protocol-emulate network Example: Router(config-if)# isdn protocol-emulate user On the Cisco MC3810, the isdn protocol-emulate command replaces the isdn switch-type command. Note Example: ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 43 Basic ISDN Voice-Interface Configuration Configuring QSIG Support
- 56. PurposeCommand or Action Example: Example: Router(config-if)#isdn protocol-emulate network (Optional) Activates overlap signaling to send to the destination PBX. The interface waits for possible additional call-control information from the preceding PBX. isdn overlap-receiving Example: Router(config-if)# isdn overlap-receiving Step 7 You can leave the default mode of enbloc , in which all call-setup information is sent in the setup message without need for additional messages from the preceding PINX. Note (Optional) Specifies the cause code to pass to the PBX when a call cannot be placed or completed because of internal network failures. isdn network-failure-cause value Example: Router(config-if)# isdn network-failure-cause 1 Step 8 Exits the current mode.exit Example: Router(config-if)# exit Step 9 Configure BRI Interfaces for QSIG To configure BRI interfaces for QSIG, perform the following steps. Set up each interface for either user side or network side.Note ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 44 Basic ISDN Voice-Interface Configuration Configuring QSIG Support
- 57. SUMMARY STEPS 1. enable 2.configure terminal 3. Cisco MC3810 4. Cisco MC3810, Cisco 2600 Series, and Cisco 3600 Series Only 5. Cisco MC3810 Only 6. Cisco MC3810 Only 7. Cisco MC3810 Only 8. Cisco 2600 Series and Cisco 3600 Series Only 9. isdn sending-complete 10. Cisco MC3810, Cisco 2600, and Cisco 3600 Series Only 11. Do one of the following: • isdn protocol-emulate user • • • isdn protocol-emulate network 12. isdn overlap-receiving 13. isdn network-failure-cause value 14. exit DETAILED STEPS PurposeCommand or Action Enters privileged EXEC mode. Enter your password when prompted. enable Example: Router> enable Step 1 Enters configuration mode.configure terminal Example: Router# configure terminal Step 2 Enters interface configuration mode for the specified port, connector, or interface card number (location of voice module) or Cisco MC3810 Example: interface bri number Step 3 slot/port (location of voice network module and voice interface card). ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 45 Basic ISDN Voice-Interface Configuration Configuring QSIG Support
- 58. PurposeCommand or Action Example: Cisco2600 Series and Cisco 3600 Series Example: interface bri slot/port Example: Router(config)# interface bri 1/1 Enables use of the ISDN lines.Cisco MC3810, Cisco 2600 Series, and Cisco 3600 Series Only Step 4 This command is required. In previous releases, it was set automatically with use of the isdn switch-type basic-qsig command. Note Example: isdn static-tei tei-number Example: Router(config-if)# isdn static-tei 0 Configures Layer 1 port mode emulation and clock status for the user--that is, the TE (clock slave). Cisco MC3810 Only Example: Step 5 isdn layer1-emulate user Example: Router(config-if)# isdn layer1-emulate user Configures Layer 1 port mode emulation and clock status for the network--that is, the NT (clock master). Cisco MC3810 Only Example: Step 6 isdn layer1-emulate ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 46 Basic ISDN Voice-Interface Configuration Configuring QSIG Support
- 59. PurposeCommand or Action network Example: Router(config-if)#isdn layer1-emulate network (TE only) Sets priority for recovering clock signal from the network NT device for this BRI voice port. Keywords are as follows: Cisco MC3810 Only Example: Step 7 • high --First priority network-clock-priority • low --Low priority {low | high} Do not use this command if the port is configured as NT in Configure BRI Interfaces for QSIG. Note Example: Router(config-if)# network-clock-priority high Routes incoming voice calls. This is set for voice-capable BRI interfaces by default. The exception is for Cisco 2600 series and Cisco 2600 Series and Cisco 3600 Series Only Example: Step 8 Cisco 3600 series BRI S/T TE voice interface cards, where, in the absence of this command, the isdn incoming-voice modem configuration setting converts to isdn incoming-voice voice when it receives an incoming call. isdn incoming-voice voice Example: Router(config-if)# isdn incoming-voice voice (Optional) Configures the voice port to include the "Sending Complete" information element in the outgoing call-setup message. isdn sending-complete Example: Router(config-if)# isdn sending-complete Step 9 This command is used in some geographic locations, such as Hong Kong and Taiwan, where the "Sending Complete" information element is required in the outgoing call-setup message. (Optional) If the service-provider switch type for this BRI port differs from the global ISDN switch type, set the interface ISDN Cisco MC3810, Cisco 2600, and Cisco 3600 Series Only Step 10 switch type to match the service-provider switch type. The Example: interface ISDN switch type overrides the global ISDN switch type on this interface. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 47 Basic ISDN Voice-Interface Configuration Configuring QSIG Support
- 60. PurposeCommand or Action Formore information, see the "ISDN Switch Types for Use with QSIG" section on page 9 . isdn switch-type basic-qsig Example: Router(config-if)# isdn switch-type basic-qsig (User side only) Configures Layer 2 and Layer 3 port mode emulation and clock status for the user--that is, the TE (clock slave). Do one of the following:Step 11 • isdn protocol-emulate user • or • (Network side only) Configures Layer 2 and Layer 3 port mode emulation and clock status for the network--that is, the NT (clock master). • isdn protocol-emulate network Example: Router(config-if)# isdn protocol-emulate user On the Cisco MC3810, the isdn protocol-emulate command replaces the isdn switch-type command. Note Example: Example: Example: Router(config-if)# isdn protocol-emulate network (Optional) Activates overlap signaling to send to the destination PBX and causes the interface to wait for possible additional call-control information from the preceding PINX. isdn overlap-receiving Example: Router(config-if)# isdn overlap-receiving Step 12 You can leave the default mode of enbloc , in which all call-setup information is sent in the setup message without need for additional messages from the preceding PINX. Note (Optional) Specifies the cause code to pass to the PBX when a call cannot be placed or completed because of internal network failures. isdn network-failure-cause value Example: Router(config-if)# isdn network-failure-cause 1 Step 13 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 48 Basic ISDN Voice-Interface Configuration Configuring QSIG Support
- 61. PurposeCommand or Action Exitsthe current mode.exit Example: Router(config-if)# exit Step 14 Verify the QSIG Configuration To verify the QSIG configuration, perform the following steps (listed alphabetically). SUMMARY STEPS 1. show call history voice record 2. show cdapi 3. show controllers t1 or show controllers e1 4. show dial-peer voice 5. show isdn 6. show isdn {active [serial-number] | history [serial-number]} 7. show isdn service 8. show isdn status 9. show rawmsg 10. show running-config 11. show voice port slot/port | summary DETAILED STEPS Step 1 show call history voice record Use this command to display information about calls made to and from the router. Step 2 show cdapi Use this command to display Call Distributor Application Programming Interface (CDAPI) information. Step 3 show controllers t1 or show controllers e1 Use this command to display information about T1 and E1 controllers. Step 4 show dial-peer voice Use this command to display how voice dial peers are configured. Step 5 show isdn Use this command to display information about switch type, memory, status, and Layer 2 and Layer 3 timers. Step 6 show isdn {active [serial-number] | history [serial-number]} ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 49 Basic ISDN Voice-Interface Configuration Configuring QSIG Support
- 62. Use this commandto display current (active keyword) or both historic and current (history keyword) call information for all ISDN interfaces or, optionally, a specific ISDN PRI interface (created and configured as a serial interface). Information displayed includes called number, remote node name, seconds of connect time, seconds of connect time remaining, seconds idle, and advice of charge (AOC) charging time units used during the call. Step 7 show isdn service Use this command to display the state and the service status of each ISDN channel. Step 8 show isdn status Use this command to display the status of all ISDN interfaces, including active layers, timer information, and switch-type settings. Step 9 show rawmsg Use this command to display information about memory leaks. Step 10 show running-config Use this command to display basic router configuration. Step 11 show voice port slot/port | summary Use this command to display summary information about voice-port configuration. Troubleshooting Tips • Use the debug cdapi events | detail} command to display information about CDAPI application events, registration, messages, and more. • Use the debug isdn event command to display events occurring on the user side (on the router) of the ISDN interface. ISDN events that can be displayed are Q.931 events (call setup and teardown of ISDN network connections). • Use the debug tsp command to display information about the telephony-service provider (TSP). Examples This section provides the following output examples: Sample Output for the show cdapi Command The following shows sample output for a PRI voice port on a Cisco 3660 series. Router# show cdapi Registered CDAPI Applications/Stacks ==================================== Application: TSP CDAPI Application Voice Application Type(s) : Voice Facility Signaling Application Level : Tunnel Application Mode : Enbloc Signaling Stack: ISDN Interface: Se5/0:15 Signaling Stack: ISDN Interface: Se5/1:15 Signaling Stack: ISDN ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 50 Basic ISDN Voice-Interface Configuration Configuring QSIG Support
- 63. Interface: Se6/0:15 Signaling Stack:ISDN Interface: Se6/1:15 CDAPI Message Buffers ===================== Used Msg Buffers: 0, Free Msg Buffers: 9600 Used Raw Buffers: 0, Free Raw Buffers: 4800 Used Large-Raw Buffers: 0, Free Large-Raw Buffers: 480 The following shows sample output for a PRI voice port on a Cisco MC3810. Router# show cdapi Registered CDAPI Applications/Stacks ==================================== Application: TSP CDAPI Application Voice Application Type(s) : Voice Facility Signaling Application Level : Tunnel Application Mode : Enbloc Signaling Stack: ISDN Interface: Se1:15 CDAPI Message Buffers ===================== Used Msg Buffers: 2, Free Msg Buffers: 1198 Used Raw Buffers: 2, Free Raw Buffers: 598 Used Large-Raw Buffers: 0, Free Large-Raw Buffers: 60 Sample Output for the show controller Command The following shows sample output for a T1 line (not having problems). Router# show controller T1 T1 3/0 is up. Applique type is Channelized T1 Cablelength is long gain36 0db No alarms detected. alarm-trigger is not set Version info Firmware: 20020812, FPGA: 11 Framing is ESF, Line Code is B8ZS, Clock Source is Line. Data in current interval (425 seconds elapsed): 0 Line Code Violations, 0 Path Code Violations 0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins 0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs Total Data (last 24 hours) 0 Line Code Violations, 0 Path Code Violations, 0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins, 0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs The following shows sample output for a T1 line (having problems). Router# show controller T1 2 T1 2 is down. Applique type is Channelized T1 Cablelength is long gain36 0db Transmitter is sending remote alarm. Receiver has loss of signal. alarm-trigger is not set Version info of slot 0: HW: 4, PLD Rev: 0 Manufacture Cookie Info: EEPROM Type 0x0001, EEPROM Version 0x01, Board ID 0x42, Board Hardware Version 1.32, Item Number 800-2540-02, Board Revision A0, Serial Number 15264519, PLD/ISP Version 0.0, Manufacture Date 24-Sep-1999. Framing is SF, Line Code is AMI, Clock Source is Internal. Data in current interval (329 seconds elapsed): 1 Line Code Violations, 0 Path Code Violations 0 Slip Secs, 329 Fr Loss Secs, 1 Line Err Secs, 0 Degraded Mins 0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 329 Unavail Secs Total Data (last 24 hours) 543 Line Code Violations, 0 Path Code Violations, 3 Slip Secs, 86400 Fr Loss Secs, 364 Line Err Secs, 0 Degraded Mins, 0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 86400 Unavail Secs ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 51 Basic ISDN Voice-Interface Configuration Configuring QSIG Support
- 64. Sample Output forthe show isdn service Command The following shows sample output for a PRI on a T1 controller. Router# show isdn service PRI Channel Statistics: ISDN Se0:15, Channel (1-31) Activated dsl 8 State (0=Idle 1=Propose 2=Busy 3=Reserved 4=Restart 5=Maint) 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Channel (1-31) Service (0=Inservice 1=Maint 2=Outofservice) 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Sample Output for the show isdn status Command The following shows sample output for a BRI voice port on a Cisco 3600 series. Router# show isdn status Global ISDN Switchtype = primary-qsig ISDN Serial3/1:15 interface dsl 0, interface ISDN Switchtype = primary-qsig **** Master side configuration **** Layer 1 Status: ACTIVE Layer 2 Status: TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED Layer 3 Status: 29 Active Layer 3 Call(s) Activated dsl 0 CCBs = 29 CCB:callid=89BF, sapi=0, ces=0, B-chan=5, calltype=VOICE . . . CCB:callid=89C8, sapi=0, ces=0, B-chan=14, calltype=VOICE . . . CCB:callid=89D9, sapi=0, ces=0, B-chan=1, calltype=VOICE CCB:callid=89DA, sapi=0, ces=0, B-chan=2, calltype=VOICE CCB:callid=89DB, sapi=0, ces=0, B-chan=3, calltype=VOICE The Free Channel Mask: 0x80000018 ISDN Serial3/0:15 interface dsl 1, interface ISDN Switchtype = primary-qsig **** Master side configuration **** Layer 1 Status: ACTIVE Layer 2 Status: TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED TEI = 0, Ces = 9, SAPI = 16, State = TEI_ASSIGNED Layer 3 Status: 28 Active Layer 3 Call(s) Activated dsl 1 CCBs = 28 CCB:callid=BDF, sapi=0, ces=0, B-chan=2, calltype=VOICE CCB:callid=BE0, sapi=0, ces=0, B-chan=1, calltype=VOICE CCB:callid=BE1, sapi=0, ces=0, B-chan=3, calltype=VOICE . . . CCB:callid=BFA, sapi=0, ces=0, B-chan=31, calltype=VOICE The Free Channel Mask: 0xB0000000 Total Allocated ISDN CCBs = 54 Total Allocated ISDN CCBs = 0 . . . CCB:callid=89C8, sapi=0, ces=0, B-chan=14, calltype=VOICE . . . CCB:callid=89D9, sapi=0, ces=0, B-chan=1, calltype=VOICE ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 52 Basic ISDN Voice-Interface Configuration Configuring QSIG Support
- 65. CCB:callid=89DA, sapi=0, ces=0,B-chan=2, calltype=VOICE CCB:callid=89DB, sapi=0, ces=0, B-chan=3, calltype=VOICE The Free Channel Mask: 0x80000018 ISDN Serial3/0:15 interface dsl 1, interface ISDN Switchtype = primary-qsig **** Master side configuration **** Layer 1 Status: ACTIVE Layer 2 Status: TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED TEI = 0, Ces = 9, SAPI = 16, State = TEI_ASSIGNED Layer 3 Status: 28 Active Layer 3 Call(s) Activated dsl 1 CCBs = 28 CCB:callid=BDF, sapi=0, ces=0, B-chan=2, calltype=VOICE CCB:callid=BE0, sapi=0, ces=0, B-chan=1, calltype=VOICE CCB:callid=BE1, sapi=0, ces=0, B-chan=3, calltype=VOICE . . . CCB:callid=BFA, sapi=0, ces=0, B-chan=31, calltype=VOICE The Free Channel Mask: 0xB0000000 Total Allocated ISDN CCBs = 54 The following shows sample output for a BRI voice port and a PRI voice port on a Cisco MC3810. Router# show isdn status Global ISDN Switchtype = basic-qsig ISDN BRI1 interface dsl 1, interface ISDN Switchtype = basic-qsig **** Slave side configuration **** Layer 1 Status: DEACTIVATED Layer 2 Status: TEI = 0, Ces = 1, SAPI = 0, State = TEI_ASSIGNED Layer 3 Status: NLCB:callid=0x0, callref=0x0, state=31, ces=0 event=0x0 0 Active Layer 3 Call(s) Activated dsl 1 CCBs = 0 ISDN BRI2 interface . . . Router# show isdn status Global ISDN Switchtype = primary-qsig ISDN Serial1:23 interface dsl 0, interface ISDN Switchtype = primary-qsig **** Slave side configuration **** Layer 1 Status: DEACTIVATED Layer 2 Status: TEI = 0, Ces = 1, SAPI = 0, State = TEI_ASSIGNED Layer 3 Status: 0 Active Layer 3 Call(s) Activated dsl 0 CCBs = 0 The Free Channel Mask: 0x7FFFFF The following shows sample output for a PRI voice port on a Cisco 7200 series. Router# show isdn status Global ISDN Switchtype = primary-qsig ISDN Serial1/0:15 interface dsl 0, interface ISDN Switchtype = primary-qsig **** Slave side configuration **** Layer 1 Status: DEACTIVATED Layer 2 Status: TEI = 0, Ces = 1, SAPI = 0, State = TEI_ASSIGNED Layer 3 Status: 0 Active Layer 3 Call(s) Activated dsl 0 CCBs = 0 The Free Channel Mask: 0x7FFF7FFF ISDN Serial1/1:15 interface ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 53 Basic ISDN Voice-Interface Configuration Configuring QSIG Support
- 66. dsl 1, interfaceISDN Switchtype = primary-qsig **** Slave side configuration **** Layer 1 Status: DEACTIVATED Layer 2 Status: TEI = 0, Ces = 1, SAPI = 0, State = TEI_ASSIGNED Layer 3 Status: 0 Active Layer 3 Call(s) Activated dsl 1 CCBs = 0 The Free Channel Mask: 0x7FFF7FFF Total Allocated ISDN CCBs = 0 Configuring ISDN PRI Q.931 Support To configure ISDN PRI Q.931 support, perform the following steps. Use these commands on Cisco 2600 series and Cisco 3600 series only.Note • Set up each interface for either user side or network side. SUMMARY STEPS 1. enable 2. configure terminal 3. isdn switch-type primary-net5 4. controller {t1 | e1} slot/port 5. pri-group timeslots range 6. exit 7. interface serial 0/0: channel-number 8. Do one of the following: • isdn protocol-emulate user • • • isdn protocol-emulate network 9. line-power 10. isdn incoming-voice voice 11. exit ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 54 Basic ISDN Voice-Interface Configuration Configuring ISDN PRI Q.931 Support
- 67. DETAILED STEPS PurposeCommand orAction Enters privileged EXEC mode. Enter your password when prompted.enable Example: Router> enable Step 1 Enters configuration mode.configure terminal Example: Router# configure terminal Step 2 (Optional) Selects a service-provider switch type that accommodates PRI. isdn switch-type primary-net5 Example: Router(config)# isdn switch-type primary-net5 Step 3 You can set the ISDN switch type in either global configuration mode or interface configuration mode. • Global configuration mode (this step): specify the switch type for all PRI ports. • Interface configuration mode: specify the switch type for a single interface. The type specified in this mode for any individual interface overrides the type specified in global configuration mode. Enters T1 or E1 controller configuration mode for the specified slot/port. controller {t1 | e1} slot/port Example: Router(config)# controller t1 1/1 Step 4 Specifies PRI on the specified or timeslots that make up the PRI group. Maximum T1 range: 1-23. Maximum E1 range: 1-31. Separate low and high values with a hyphen. pri-group timeslots range Example: Router(config-controller)# pri-group timeslots 1-23 Step 5 You can configure the PRI group to include all available timeslots, or you can configure a select group of timeslots for the PRI group. Note Exits the current mode.exit Example: Router(config-controller)# exit Step 6 Enters interface configuration mode for the specified PRI slot/port and D-channel ISDN interface. D-channel ISDN interface is (for T1) 23 and (for E1) 15. interface serial 0/0: channel-number Example: Router(config)# interface serial 0/0:23 Step 7 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 55 Basic ISDN Voice-Interface Configuration Configuring ISDN PRI Q.931 Support
- 68. PurposeCommand or Action (Userside only) Configures Layer 2 and Layer 3 port mode emulation and clock status for the user--that is, the TE (clock slave). Do one of the following:Step 8 • isdn protocol-emulate user or • (Network side only) Configures Layer 2 and Layer 3 port mode emulation and clock status for the network--that is, the NT (clock master). • • isdn protocol-emulate network Example: Router(config-if)# isdn protocol-emulate user Example: Example: Example: Router(config-if)# isdn protocol-emulate network Turns on the power supplied from an NT-configured port to a TE device. line-power Example: Router(config-if)# line-power Step 9 Routes incoming ISDN voice calls to the voice module.isdn incoming-voice voice Example: Router(config-if)# isdn incoming-voice voice Step 10 Exits the current mode.exit Example: Router(config-if)# exit Step 11 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 56 Basic ISDN Voice-Interface Configuration Configuring ISDN PRI Q.931 Support
- 69. Configuration Examples forISDN Voice Interfaces ISDN-to-PBX and ISDN-to-PSTN Examples This section contains the following configuration examples: Configuration examples included in this section correspond to the topology shown in the figure below. The routers each include a BRI voice interface card and a two-slot voice network module, along with other voice interface cards and modules that are included for completeness. Router A is connected to a PBX through the BRI voice interface card and to Router B by a serial interface. Router B includes a BRI voice interface card for connection to the PSTN in order to process voice calls from off-premises terminal equipment. Router A is configured for ISDN BRI network-side emulation and Router B is configured for ISDN BRI user-side emulation. Figure 4: Configuration Example Topology ISDN Connection to a PBX Configuration (Network-Side Emulation) The following illustrates the configuration of the BRI interfaces on a Cisco 3640 (Router A in the figure above) connected to a PBX: interface BRI1/0 no ip address isdn switch-type basic-net3 isdn overlap-receiving isdn protocol-emulate network isdn layer1-emulate network isdn T306 30000 isdn sending-complete isdn skipsend-idverify isdn incoming-voice voice ! interface BRI1/1 no ip address isdn switch-type basic-net3 isdn overlap-receiving isdn protocol-emulate network isdn layer1-emulate network isdn T306 30000 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 57 Basic ISDN Voice-Interface Configuration Configuration Examples for ISDN Voice Interfaces
- 70. isdn sending-complete isdn skipsend-idverify isdnincoming-voice voice ! ip default-gateway 1.14.0.1 ip classless ip route 2.0.0.0 255.0.0.0 Ethernet0/1 ip route 2.0.0.0 255.0.0.0 Serial0/1 ip route 172.22.66.33 255.255.255.255 Ethernet0/0 ! ! line con 0 exec-timeout 0 0 transport input none line aux 0 line vty 0 4 login ISDN Connection to the PSTN Configuration (User-Side Emulation) The following illustrates the configuration of the BRI interfaces on a Cisco 2600 series (Router B in the figure above) connected to the public ISDN telephone network: interface BRI1/0 no ip address no ip directed-broadcast isdn switch-type basic-ni1 isdn twait-disable isdn spid1 14085552111 5552111 isdn spid2 14085552112 5552112 isdn incoming-voice voice interface BRI1/1 no ip address no ip directed-broadcast isdn switch-type basic-ni1 isdn twait-disable isdn spid1 14085552111 5552111 isdn spid2 14085552112 5552112 isdn incoming-voice voice ! ip classless ip route 3.0.0.0 255.0.0.0 Ethernet0/1 ip route 3.0.0.0 255.0.0.0 Serial0/1 ip route 172.21.66.0 255.255.255.0 Ethernet0/0 ! line con 0 exec-timeout 0 0 transport input none line aux 0 line vty 0 4 login QSIG Support Examples The following show QSIG configurations on a variety of supported routers: QSIG Support on Cisco 3600 Series Routers The following shows how a Cisco 3660 series can be configured for E1 and PRI with QSIG signaling support using VoIP and VoATM. Note that Serial5/0, Serial5/1, Serial6/0, and Serial6/1 are configured as ISDN E1 PRI (user side). . . . ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 58 Basic ISDN Voice-Interface Configuration QSIG Support Examples
- 71. hostname router3660 ! memory-size iomem20 voice-card 5 ! voice-card 6 ! ip subnet-zero ! isdn switch-type primary-qsig isdn voice-call-failure 0 ! controller E1 5/0 pri-group timeslots 1-5,16 ! controller E1 5/1 pri-group timeslots 1-31 ! controller E1 6/0 pri-group timeslots 1-31 ! controller E1 6/1 pri-group timeslots 1-31 ! interface FastEthernet0/0 ip address 10.7.72.9 255.255.255.0 speed auto half-duplex ! interface FastEthernet0/1 ip address 10.100.100.7 255.255.255.0 no keepalive duplex auto speed auto hold-queue 1000 in ! interface Serial2/0 no ip address shutdown ! interface Serial2/1 no ip address shutdown ! interface Serial2/2 no ip address shutdown ! interface Serial2/3 no ip address shutdown ! interface ATM3/0 no ip address atm clock INTERNAL no atm ilmi-keepalive pvc 10/40 vbr-rt 155000 50000 64000 encapsulation aal5mux voice ! interface Serial5/0:15 no ip address ip mroute-cache no logging event link-status isdn switch-type primary-qsig isdn overlap-receiving isdn incoming-voice voice no cdp enable ! interface Serial5/1:15 no ip address ip mroute-cache no logging event link-status ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 59 Basic ISDN Voice-Interface Configuration QSIG Support Examples
- 72. isdn switch-type primary-qsig isdnincoming-voice voice fair-queue 64 256 0 no cdp enable ! interface Serial6/0:15 no ip address ip mroute-cache no logging event link-status isdn switch-type primary-qsig isdn incoming-voice voice fair-queue 64 256 0 no cdp enable ! interface Serial6/1:15 no ip address ip mroute-cache no logging event link-status isdn switch-type primary-qsig isdn incoming-voice voice fair-queue 64 256 0 no cdp enable ! ip classless ip route 192.168.17.125 255.255.255.255 FastEthernet0/0 no ip http server ! map-class frame-relay frs0 frame-relay voice bandwidth 1260000 frame-relay fragment 200 no frame-relay adaptive-shaping frame-relay cir 1260000 frame-relay fair-queue ! voice-port 1/0/0 modem passthrough system timing hookflash-in 0 ! voice-port 1/0/1 modem passthrough system timing hookflash-in 0 ! voice-port 5/0:15 compand-type a-law ! voice-port 5/1:15 compand-type a-law cptone DE ! voice-port 6/0:15 compand-type a-law cptone DE ! voice-port 6/1:15 no echo-cancel enable compand-type a-law cptone DE ! dial-peer voice 1 pots shutdown destination-pattern 21... modem passthrough system direct-inward-dial ! dial-peer voice 51 voip shutdown destination-pattern 6504007 modem passthrough system session target ipv4:100.100.100.3 ! dial-peer voice 2 pots shutdown destination-pattern 21... ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 60 Basic ISDN Voice-Interface Configuration QSIG Support Examples
- 73. modem passthrough system direct-inward-dial port5/1:15 ! dial-peer voice 3 voip shutdown destination-pattern 22... modem passthrough system session target ipv4:100.100.100.6 ! dial-peer voice 5 pots shutdown destination-pattern 22... modem passthrough system direct-inward-dial prefix 4006 ! dial-peer voice 13 pots shutdown destination-pattern 21... modem passthrough system direct-inward-dial port 6/0:15 ! dial-peer voice 6 pots destination-pattern 21... modem passthrough system direct-inward-dial port 6/1:15 ! dial-peer voice 44 voatm destination-pattern 22... modem passthrough system session target ATM3/0 pvc 10/40 ! dial-peer voice 20 pots incoming called-number 4... destination-pattern 4007 modem passthrough system direct-inward-dial port 5/0:15 prefix 4007 ! dial-peer voice 21 pots destination-pattern 4006 modem passthrough system direct-inward-dial port 5/0:15 prefix 4006 ! line con 0 transport input none line aux 0 line vty 0 4 login ! end ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 61 Basic ISDN Voice-Interface Configuration QSIG Support Examples
- 74. QSIG Support onCisco 7200 Series Routers The following shows how QSIG protocol support is configured with VoFR on Router A (where calls originate) and Router B (where calls terminate). Note that Serial3/0:15, Serial3/1:15, Serial4/0:15, and Serial4/1:15 are configured as ISDN E1 PRI (user side). Router B: Terminating ConfigurationRouter A: Originating Configuration ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 62 Basic ISDN Voice-Interface Configuration QSIG Support Examples
- 75. Router B: TerminatingConfigurationRouter A: Originating Configuration .. .. .. hostname 7200_RouterBhostname 7200_RouterA !! card type e1 3card type e1 3 card type e1 4card type e1 4 !! dspint DSPfarm3/0dspint DSPfarm3/0 !! dspint DSPfarm4/0dspint DSPfarm4/0 !! ip subnet-zeroip subnet-zero ip cefno ip domain-lookup no ip domain-lookupip host routerC 192.168.17.125 ip host routerC 192.168.17.125ip host routerD 10.1.1.2 !! multilink virtual-template 1multilink virtual-template 1 isdn switch-type primary-qsigframe-relay switching isdn voice-call-failure 0isdn switch-type primary-qsig !isdn voice-call-failure 0 !! !voice class codec 1 !codec preference 1 g711ulaw !codec preference 3 g729br8 !! controller E1 3/0controller E1 3/0 pri-group timeslots 1-31pri-group timeslots 1-31 description qsig connected to PCG 5description qsig connected to PCG 1 !! controller E1 3/1controller E1 3/1 pri-group timeslots 1-31pri-group timeslots 1-31 description cas connected to PCG 6description cas connected to PCG 2 !! controller E1 4/0controller E1 4/0 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 63 Basic ISDN Voice-Interface Configuration QSIG Support Examples
- 76. Router B: TerminatingConfigurationRouter A: Originating Configuration pri-group timeslots 1-31 description qsig group connected PCG slot3 ! controller E1 4/1 pri-group timeslots 1-31 description qsig group connected PCG slot4 ! ! ! ! ! pri-group timeslots 1-31 description cas connected to PCG slot7 ! controller E1 4/1 pri-group timeslots 1-31 description cas connected to PCG slot8 ! interface Loopback0 no ip address no ip directed-broadcast ! ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 64 Basic ISDN Voice-Interface Configuration QSIG Support Examples
- 77. Router B: TerminatingConfigurationRouter A: Originating Configuration interface FastEthernet0/0interface FastEthernet0/0 description VOIP_10.0.0.1_maxstress to 7200_RouterAgate no ip address no ip directed-broadcast ip address 10.0.0.1 255.0.0.0 shutdown no ip directed-broadcast half-duplex no ip mroute-cache ! shutdown ! media-type MII ! full-duplex ! ! ! interface Serial1/0 interface Serial1/0 no ip address bandwidth 512 no ip directed-broadcast ip address 10.1.1.104 255.255.255.0 no ip mroute-cache no ip directed-broadcast shutdown encapsulation ppp ! no ip route-cache ! no ip mroute-cache ! load-interval 30 ! no keepalive ! shutdown ! no fair-queue ! clockrate 2015232 ! ppp multilink ! ! interface Serial1/1 interface Serial1/1 description vofr connection to 7200_RouterA description vofr connection to 7200_RouterB_s1/1 ip address 10.0.0.1 255.0.0.0 ip address 10.0.0.2 255.0.0.0 ip broadcast-address 10.0.0.0 ip broadcast-address 10.0.0.0 no ip directed-broadcast no ip directed-broadcast encapsulation frame-relay encapsulation frame-relay no keepalive no ip route-cache clockrate 8060928 no ip mroute-cache frame-relay traffic-shaping no keepalive frame-relay map ip 10.0.0.2 100 broadcast frame-relay traffic-shaping frame-relay interface-dlci 100 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 65 Basic ISDN Voice-Interface Configuration QSIG Support Examples
- 78. Router B: TerminatingConfigurationRouter A: Originating Configuration class vofr_class vofr data 4 call-control 5 ! ! interface Serial1/2 no ip address no ip directed-broadcast shutdown clockrate 2015232 ! ! interface Serial1/3 no ip address no ip directed-broadcast shutdown ! ! ! ! frame-relay map ip 10.0.0.1 100 broadcast frame-relay interface-dlci 100 class vofr_class vofr data 4 call-control 5 ! interface Serial1/2 no ip address no ip directed-broadcast no ip route-cache no ip mroute-cache shutdown ! interface Serial1/3 no ip address no ip directed-broadcast no ip route-cache no ip mroute-cache shutdown clockrate 2015232 ! ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 66 Basic ISDN Voice-Interface Configuration QSIG Support Examples
- 79. Router B: TerminatingConfigurationRouter A: Originating Configuration interface Ethernet2/0interface Ethernet2/0 ip address 10.5.192.123 255.255.0.0ip address 10.1.50.77 255.255.0.0 ip helper-address 192.168.17.125ip broadcast-address 10.1.0.0 no ip directed-broadcastno ip directed-broadcast no ip mroute-cacheno ip route-cache !no ip mroute-cache !! interface Ethernet2/1interface Ethernet2/1 ip address 10.0.0.1 255.255.0.0ip address 10.0.0.2 255.255.0.0 no ip directed-broadcastip broadcast-address 10.0.0.0 no ip mroute-cacheno ip directed-broadcast shutdownno ip route-cache !no ip mroute-cache !shutdown !! interface Ethernet2/2interface Ethernet2/2 no ip addressno ip address no ip directed-broadcastno ip directed-broadcast shutdownno ip route-cache !no ip mroute-cache !shutdown !! interface Ethernet2/3interface Ethernet2/3 no ip addressno ip address no ip directed-broadcastno ip directed-broadcast shutdownno ip route-cache !no ip mroute-cache !shutdown !! interface Serial3/0:15interface Serial3/0:15 no ip addressno ip address no ip directed-broadcastno ip directed-broadcast no ip route-cache cefno logging event link-status ip mroute-cacheisdn switch-type primary-qsig no logging event link-statusisdn overlap-receiving ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 67 Basic ISDN Voice-Interface Configuration QSIG Support Examples
- 80. Router B: TerminatingConfigurationRouter A: Originating Configuration isdn incoming-voice voice isdn bchan-number-order ascending no cdp enable ! ! ! interface Serial3/1:15 no ip address no ip directed-broadcast no logging event link-status isdn switch-type primary-qsig isdn overlap-receiving isdn incoming-voice voice isdn bchan-number-order ascending no cdp enable ! ! ! isdn switch-type primary-qsig isdn overlap-receiving isdn incoming-voice voice isdn bchan-number-order ascending no cdp enable ! interface Serial3/1:15 no ip address no ip directed-broadcast no ip route-cache cef ip mroute-cache no logging event link-status isdn switch-type primary-qsig isdn overlap-receiving isdn incoming-voice voice isdn bchan-number-order ascending no cdp enable ! ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 68 Basic ISDN Voice-Interface Configuration QSIG Support Examples
- 81. Router B: TerminatingConfigurationRouter A: Originating Configuration interface Serial4/0:15interface Serial4/0:15 no ip addressno ip address no ip directed-broadcastno ip directed-broadcast no ip route-cache cefno logging event link-status ip mroute-cacheisdn switch-type primary-qsig no logging event link-statusisdn overlap-receiving isdn switch-type primary-qsigisdn incoming-voice voice isdn overlap-receivingisdn bchan-number-order ascending isdn incoming-voice voiceno cdp enable isdn bchan-number-order ascending! no cdp enable! !! interface Serial4/1:15interface Serial4/1:15 no ip addressno ip address no ip directed-broadcastno ip directed-broadcast no ip route-cache cefno logging event link-status ip mroute-cacheisdn switch-type primary-qsig no logging event link-statusisdn overlap-receiving isdn switch-type primary-qsigisdn incoming-voice voice isdn overlap-receivingisdn bchan-number-order ascending isdn incoming-voice voiceno cdp enable isdn bchan-number-order ascending! no cdp enable! !! interface ATM5/0interface ATM5/0 no ip addressno ip address no ip directed-broadcastno ip directed-broadcast shutdownno ip route-cache no atm ilmi-keepaliveno ip mroute-cache !shutdown interface FastEthernet6/0no atm ilmi-keepalive no ip address! no ip directed-broadcast! shutdown! half-duplex! ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 69 Basic ISDN Voice-Interface Configuration QSIG Support Examples
- 82. Router B: TerminatingConfigurationRouter A: Originating Configuration ! interface Virtual-Template1 ip address 10.0.0.2 255.255.255.0 no ip directed-broadcast load-interval 30 fair-queue 64 256 1 ppp multilink ppp multilink fragment-delay 20 ppp multilink interleave ip rtp priority 16384 16383 92 ! router igrp 144 network 10.0.0.0 ! ip default-gateway 10.21.75.10 ip classless no ip http server ! ! interface Virtual-Template1 ip unnumbered Loopback0 no ip directed-broadcast no ip route-cache cef ip mroute-cache ppp multilink ppp multilink fragment-delay 20 ppp multilink interleave ! ! router igrp 144 network 10.0.0.0 ! ! ip classless no ip http server ! ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 70 Basic ISDN Voice-Interface Configuration QSIG Support Examples
- 83. Router B: TerminatingConfigurationRouter A: Originating Configuration map-class frame-relay vofr_classmap-class frame-relay vofr_class no frame-relay adaptive-shapingno frame-relay adaptive-shaping frame-relay cir 4400000frame-relay cir 4400000 frame-relay bc 1000frame-relay bc 1000 frame-relay fair-queueframe-relay fair-queue frame-relay voice bandwidth 4000000frame-relay voice bandwidth 4000000 frame-relay fragment 256frame-relay fragment 256 !! voice-port 3/0:15voice-port 3/0:15 compand-type a-lawcompand-type a-law !cptone DE !! voice-port 3/1:15voice-port 3/1:15 compand-type a-lawcompand-type a-law !cptone DE !! voice-port 4/0:15voice-port 4/0:15 compand-type a-lawcompand-type a-law !cptone DE !! voice-port 4/1:15voice-port 4/1:15 compand-type a-lawcompand-type a-law !cptone DE !! dial-peer voice 5552222 potsdial-peer voice 5552222 pots destination-pattern +6662...destination-pattern +5552... direct-inward-dialdirect-inward-dial port 3/1:15port 3/1:15 prefix 6662prefix 5552 !! dial-peer voice 5551111 vofrdial-peer voice 5551111 vofr destination-pattern +5......destination-pattern +6...... sequence-numberssequence-numbers session target Serial1/1 100session target Serial1/1 100 codec g729br8codec g729br8 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 71 Basic ISDN Voice-Interface Configuration QSIG Support Examples
- 84. Router B: TerminatingConfigurationRouter A: Originating Configuration ! dial-peer voice 5554 pots destination-pattern 5554... direct-inward-dial port 4/1:15 prefix 5554 ! dial-peer voice 5553 pots destination-pattern 5553... direct-inward-dial port 4/0:15 prefix 5553 ! dial-peer voice 5551 pots destination-pattern +5551... direct-inward-dial port 3/0:15 prefix 5551 . . . ! dial-peer voice 6661 pots destination-pattern +6661... direct-inward-dial port 3/0:15 prefix 6661 ! dial-peer voice 6663 pots destination-pattern +6663... direct-inward-dial port 4/0:15 prefix 6663 ! dial-peer voice 6664 pots destination-pattern +6664... direct-inward-dial port 4/1:15 prefix 6664 . . . QSIG Support on Cisco MC3810 Multiservice Concentrators The following shows how a Cisco MC3810 can be configured for E1 and PRI with QSIG signaling support and VoIP and VoFR. Note that Serial1:15 is configured as ISDN E1 PRI (user side). . . . hostname Router3810 ! network-clock base-rate 56k ip subnet-zero ! isdn switch-type primary-qsig isdn voice-call-failure 0 ! controller T1 0 mode atm framing esf clock source internal linecode b8zs ! ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 72 Basic ISDN Voice-Interface Configuration QSIG Support Examples
- 85. controller E1 1 pri-grouptimeslots 1-7,16 ! interface Ethernet0 ip address 100.100.100.6 255.255.255.0 no ip directed-broadcast ! interface Serial0 bandwidth 2000 ip address 10.168.14.1 255.255.255.0 no ip directed-broadcast encapsulation frame-relay no ip mroute-cache no keepalive clockrate 2000000 cdp enable frame-relay traffic-shaping frame-relay interface-dlci 100 class frs0 vofr cisco ! interface Serial1 no ip address no ip directed-broadcast shutdown ! interface Serial1:15 no ip address no ip directed-broadcast ip mroute-cache no logging event link-status isdn switch-type primary-qsig isdn overlap-receiving isdn incoming-voice voice fair-queue 64 256 0 no cdp enable ! interface ATM0 no ip address no ip directed-broadcast ip mroute-cache no atm ilmi-keepalive pvc 10/42 encapsulation aal5mux voice ! ! interface FR-ATM20 no ip address no ip directed-broadcast shutdown ! no ip http server ip classless ip route 223.255.254.0 255.255.255.0 Ethernet0 ! map-class frame-relay frs0 frame-relay voice bandwidth 1260000 frame-relay fragment 200 no frame-relay adaptive-shaping frame-relay cir 1260000 frame-relay fair-queue ! map-class frame-relay frsisco ! voice-port 1:15 compand-type a-law ! dial-peer voice 100 voatm shutdown destination-pattern 4... session target ATM0 pvc 10/42 codec g729ar8 no vad ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 73 Basic ISDN Voice-Interface Configuration QSIG Support Examples
- 86. ! dial-peer voice 1pots shutdown destination-pattern 3001 ! dial-peer voice 42 vofr destination-pattern 4006 session target Serial0 100 signal-type ext-signal ! dial-peer voice 21 pots destination-pattern 4007 direct-inward-dial port 1:15 prefix 4007 ! dial-peer voice 12 voip shutdown destination-pattern 4006 session target ipv4:100.100.100.7 . . . Q.931-Support Example The following shows how a Cisco 3660 can be configured for E1 and PRI with network-side support using VoIP. Note that Serial5/0:15 and Serial6/0:15 are configured as ISDN E1 PRI (network side) and that Serial5/1:15 and Serial6/1:15 are configured as ISDN E1 PRI (user side). . . . hostname router3660 ! memory-size iomem 20 voice-card 5 ! voice-card 6 ! ip subnet-zero ! isdn switch-type primary-net5 isdn voice-call-failure 0 ! controller E1 3/0 pri-group timeslots 1-5,16 ! controller E1 3/1 pri-group timeslots 1-31 ! controller E1 4/0 pri-group timeslots 1-31 ! controller E1 4/1 pri-group timeslots 1-31 ! interface FastEthernet0/0 ip address 10.7.72.9 255.255.255.0 speed auto half-duplex ! interface FastEthernet0/1 ip address 10.100.100.7 255.255.255.0 no keepalive duplex auto speed auto hold-queue 1000 in ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 74 Basic ISDN Voice-Interface Configuration Q.931-Support Example
- 87. ! interface Serial2/0 no ipaddress shutdown ! interface Serial2/1 no ip address shutdown ! interface Serial2/2 no ip address shutdown ! interface Serial2/3 no ip address shutdown ! interface Serial5/0:15 no ip address ip mroute-cache no logging event link-status isdn switch-type primary-qsig isdn overlap-receiving isdn incoming-voice voice isdn protocol-emulate network no cdp enable ! interface Serial5/1:15 no ip address ip mroute-cache no logging event link-status isdn switch-type primary-qsig isdn incoming-voice voice fair-queue 64 256 0 no cdp enable ! interface Serial6/0:15 no ip address ip mroute-cache no logging event link-status isdn switch-type primary-qsig isdn incoming-voice voice fair-queue 64 256 0 isdn protocol-emulate network no cdp enable ! interface Serial6/1:15 no ip address ip mroute-cache no logging event link-status isdn switch-type primary-qsig isdn incoming-voice voice fair-queue 64 256 0 no cdp enable ! ip classless ip route 223.255.254.254 255.255.255.255 FastEthernet0/0 no ip http server ! voice-port 1/0/0 timing hookflash-in 0 ! voice-port 1/0/1 timing hookflash-in 0 ! voice-port 5/0:15 compand-type a-law ! voice-port 5/1:15 compand-type a-law cptone DE ! voice-port 6/0:15 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 75 Basic ISDN Voice-Interface Configuration Q.931-Support Example
- 88. compand-type a-law cptone DE ! voice-port6/1:15 no echo-cancel enable compand-type a-law cptone DE ! dial-peer voice 1 pots shutdown destination-pattern 21... direct-inward-dial ! dial-peer voice 51 voip shutdown destination-pattern 6504007 session target ipv4:100.100.100.3 ! dial-peer voice 2 pots shutdown destination-pattern 21... direct-inward-dial port 5/1:15 ! dial-peer voice 3 voip shutdown destination-pattern 22... session target ipv4:100.100.100.6 ! dial-peer voice 5 pots shutdown destination-pattern 22... modem passthrough system direct-inward-dial prefix 4006 ! dial-peer voice 13 pots shutdown destination-pattern 21... direct-inward-dial port 6/0:15 ! dial-peer voice 6 pots destination-pattern 21... direct-inward-dial port 6/1:15 ! dial-peer voice 20 pots incoming called-number 4... destination-pattern 4007 direct-inward-dial port 5/0:15 prefix 4007 ! dial-peer voice 21 pots destination-pattern 4006 direct-inward-dial port 5/0:15 prefix 4006 ! line con 0 transport input none line aux 0 line vty 0 4 login ! end ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 76 Basic ISDN Voice-Interface Configuration Q.931-Support Example
- 89. Additional References General ISDNReferences • "Overview of ISDN Voice Interfaces" on page 3 --Describes relevant underlying technology; lists related documents, standards, MIBs, and RFCs; and describes how to obtain technical assistance • Additional References, on page 77--Lists additional ISDN references References Mentioned in This Chapter • Cisco IOS Debug Command Reference, Release 12.3T at http://www.cisco.com/univercd/cc/td/doc/ product/software/ios123/123tcr/123dbr/index.htm • Cisco IOS IP Configuration Guide at http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/ 122cgcr/ • Cisco IOS Voice Troubleshooting and Monitoring Guide at http://www.cisco.com/univercd/cc/td/doc/ product/software/ios123/123cgcr/vvfax_c/voipt_c/index.htm • Cisco IOS Voice, Video, and Fax Command Reference at http://www.cisco.com/univercd/cc/td/doc/ product/software/ios122/122cgcr/ • E1 PRI Troubleshooting at http://www.cisco.com/warp/public/116/E1_pri.html • Installing VoIP Cards at http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/5300/hw_inst/ 6271voip.htm • T1 PRI Troubleshooting at http://www.cisco.com/warp/public/116/T1_pri.html • T1 troubleshooting information at http://www.cisco.com/en/US/tech/tk713/tk628/technologies_tech_ note09186a00800a5f40.shtml • Using the show isdn status Command for BRI Troubleshooting at http://www.cisco.com/warp/public/ 129/bri_sh_isdn_stat.html • Troubleshooting ISDN at http://www.cisco.com/cisco/web/solutions/small_business/ index.html?Referring_site=PrintTv&Country_Site=us&Campaign=SAMBA&Position=Vanity&Creative=go/ smb&Where=go/smb ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 77 Basic ISDN Voice-Interface Configuration Additional References
- 90. ISDN Voice ConfigurationGuide, Cisco IOS Release 15M&T 78 Basic ISDN Voice-Interface Configuration Additional References
- 91. C H AP T E R 3 Expanded Scope for Cause-Code-Initiated Call-Establishment Retries This chapter describes how to implement the Expanded Scope for Cause-Code-Initiated Call Establishment Retries feature. This feature enables a gateway to reattempt calls when a disconnect message is received from the PSTN without maintaining extra dial peers. Feature History for Expanded Scope for Cause-Code-Initiated Call Establishment Retries ModificationRelease This feature was introduced.12.2(15)T • Finding Feature Information, page 79 • Prerequisites for Expanded Scope for Cause-Code-Initiated Call Establishment Retries, page 80 • Restrictions for Expanded Scope for Cause-Code-Initiated Call Establishment Retries, page 80 • Information About Expanded Scope for Cause-Code-Initiated Call-Establishment Retries, page 80 • How to Configure Expanded Scope for Cause-Code-Initiated Call-Establishment Retries, page 81 • Configuration Examples for Expanded Scope for Cause-Code-Initiated Call Establishment Retries, page 83 • Additional References, page 83 Finding Feature Information Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 79
- 92. PrerequisitesforExpandedScopeforCause-Code-InitiatedCall Establishment Retries • Performthe prerequisites that are listed in the "Prerequisites for Configuring ISDN Voice Interfaces" section. • Configure ISDN (trunks) or the Cisco Signaling System 7 (SS7) on the gateway. Restrictions for Expanded Scope for Cause-Code-Initiated Call Establishment Retries Restrictions are described in the "Restrictions for Configuring ISDN Voice Interfaces" section. In addition, the following applies: • This feature must be used with ISDN Net5 PRI or NI2 PRI switch types. Information About Expanded Scope for Cause-Code-Initiated Call-Establishment Retries Before this feature was available, there was no easy way to reattempt most calls when a disconnect was received from the PSTN. Only cause code 44 reattempted a call--and only if multiple dial peers to the same destination were configured. General information about ISDN voice interfaces is presented in the "Information About ISDN Voice Interfaces" section. Note This feature enables you to configure a gateway to reattempt a call when a disconnect message is received from the PSTN. You can configure up to 16 arguments (specifying values from 1 to 127 in each argument) for cause codes. For a list of cause codes, see ISDN Switch Types, Codes, and Values.Note ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 80 Expanded Scope for Cause-Code-Initiated Call-Establishment Retries Prerequisites for Expanded Scope for Cause-Code-Initiated Call Establishment Retries
- 93. How to ConfigureExpanded Scope for Cause-Code-Initiated Call-Establishment Retries Configuring Expanded Scope for Cause-Code-Initiated Call-Establishment Retries To configure expanded scope for cause-code-initiated call-establishment retries, perform the following steps. SUMMARY STEPS 1. enable 2. configure terminal 3. interface type slot/port 4. isdn negotiate-bchan [resend-setup] [cause-codes {cause-code1 [cause-code2...cause-code16]}] 5. exit DETAILED STEPS PurposeCommand or Action Enters privileged EXEC mode. Enter your password when prompted. enable Example: Router> enable Step 1 Enters global configuration mode.configure terminal Example: Router# configure terminal Step 2 Configures an interface type and enters interface configuration mode for the specified slot/port. interface type slot/port Example: Router(config)# interface serial 0/4 Step 3 Enables the router to accept a B channel that is different from the B channel requested in the outgoing call-setup message and specifies the cause codes for which the call is reattempted. isdn negotiate-bchan [resend-setup] [cause-codes {cause-code1 [cause-code2...cause-code16]}] Example: Router(interface)# isdn negotiate-bchan resend-setup cause-codes 34 44 63 Step 4 You must have ISDN trunks configured on your router before you can configure the cause codes. Note ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 81 Expanded Scope for Cause-Code-Initiated Call-Establishment Retries How to Configure Expanded Scope for Cause-Code-Initiated Call-Establishment Retries
- 94. PurposeCommand or Action Exitsthe current mode.exit Example: Router(interface)# exit Step 5 VerifyingExpandedScopeforCause-Code-InitiatedCall-EstablishmentRetries To verify expanded scope for cause-code-initiated call-establishment retries, perform the following steps (listed alphabetically). SUMMARY STEPS 1. show isdn status 2. show running-config DETAILED STEPS Step 1 show isdn status Use this command to display the status of all ISDN interfaces, including active layers, timer information, and switch-type settings. Step 2 show running-config Use this command to display basic router configuration, including cause codes and values entered to verify that the gateway can reattempt disconnect calls received form the PSTN. Troubleshooting Tips • Use the debug isdn q931 command to display calls that the router has attempted or reattempted. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 82 Expanded Scope for Cause-Code-Initiated Call-Establishment Retries Verifying Expanded Scope for Cause-Code-Initiated Call-Establishment Retries
- 95. Configuration Examples forExpanded Scope for Cause-Code-Initiated Call Establishment Retries ISDN Interface Example The following output shows that the ISDN interface is configured on the gateway and that the gateway is configured to reattempt disconnect calls received from the PSTN when the disconnect cause code is 18. Router# show running-config ! interface Serial7/0:0 no ip address isdn switch-type primary-ni isdn incoming-voice modem isdn T306 30000 isdn rlm-group 0 no isdn send-status-inquiry isdn negotiate-bchan resend-setup cause-code 18 ==> Cause-code 18 is configured. no cdp enable ! end Cause Codes Example The following sample configuration shows that cause codes 34, 44, and 63 are set on serial slot 0 and port 23: Router# show running-config ! interface serial0:23 isdn negotiate-bchan resend-setup cause-codes 34 44 63 end Additional References General ISDN References • "Overview of ISDN Voice Interfaces" --Describes relevant underlying technology; lists related documents, standards, MIBs, and RFCs; and describes how to obtain technical assistance • "Additional References" section --Lists additional ISDN references References Mentioned in This Chapter • ISDN Switch Types, Codes, and Values at http://www.cisco.com/univercd/cc/td/doc/product/software/ ios123/123sup/123debug/dbg_ap2g.htm ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 83 Expanded Scope for Cause-Code-Initiated Call-Establishment Retries Configuration Examples for Expanded Scope for Cause-Code-Initiated Call Establishment Retries
- 96. ISDN Voice ConfigurationGuide, Cisco IOS Release 15M&T 84 Expanded Scope for Cause-Code-Initiated Call-Establishment Retries Additional References
- 97. C H AP T E R 4 Clear Channel T3 E3 with Integrated CSU DSU This chapter describes how to implement the Clear Channel T3/E3 with Integrated CSU/DSU feature. The feature delivers Clear Channel service as a T3/E3 pipe with bandwidth of 28x24x64k for T3 or 16x32x64 for E3. The software-configurable T3/E3 network module allows you to switch between T3 and E3 applications with a single Cisco IOS command. The T3/E3 NM-1 network module supports a single-port T3 or E3 with an integrated channel service unit (CSU) and a data service unit (DSU). It supports High-Level Data Link Control (HDLC), PPP, and frame relay. It includes the following features: • Single port--universal T3/E3 version • Clear and subrate support on both T3 and E3 modes • Online insertion and removal (OIR) support on Cisco 3660 series and Cisco 3745 routers • Onboard processing of Cisco Message Definition Language (MDL) and performance monitoring • Support for scrambling and subrate can be independently or simultaneously enabled in each DSU mode • Support for full T3 and E3 line rates The T3/E3 NM-1 network module provides high-speed performance for advanced, fully converged networks supporting a wide array of applications and services such as security and advanced QoS for voice and video. T3/E3 and subrate T3/E3 connectivity optimizes WAN bandwidth for deploying the new applications and service delivery. Feature History for Clear Channel T3/E3 with Integrated CSU/DSU ModificationRelease This feature was introduced.12.2(11)YT This feature was integrated into this release.12.2(15)T • Finding Feature Information, page 86 • Prerequisites for Clear Channel T3 E3 with Integrated CSU DSU, page 86 • Restrictions for Clear Channel T3 E3 with Integrated CSU DSU, page 86 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 85
- 98. • Information AboutClear Channel T3 E3 with Integrated CSU DSU, page 87 • How to Configure Clear Channel T3 E3 with Integrated CSU DSU, page 87 • Configuration Example for Clear Channel T3 E3 with Integrated CSU DSU, page 105 • Additional References, page 107 Finding Feature Information Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required. Prerequisites for Clear Channel T3 E3 with Integrated CSU DSU • Perform the prerequisites that are listed in the "Prerequisites for Configuring an ISDN Voice Interface" section. • Ensure that you have sufficient system memory (see the table below). Table 6: Minimum Memory Requirements DRAM MemoryFlash MemoryPlatform 32 MB8 MBCisco 2650 Cisco 2651XM 64 MB32 MBCisco 2691 64 MB8 MBCisco 3660 series 128 MB32 MBCisco 3725 128 MB32 MBCisco 3745 Restrictions for Clear Channel T3 E3 with Integrated CSU DSU Restrictions are described in the "Restrictions for Configuring ISDN Voice Interfaces" section. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 86 Clear Channel T3 E3 with Integrated CSU DSU Finding Feature Information
- 99. Information About ClearChannel T3 E3 with Integrated CSU DSU All supported platforms are capable of supporting line-rate performance, but impose varying levels of CPU overhead and therefore affect overall platform performance. The table below shows recommended branch-office positioning. Table 7: T3/E3 NM-1 Branch Office Positioning and Support Comparison Supported T3/E3 ModesRecommended Positioning Platform Branch Office SizeType of Service 1Small to medium officesSubrate T3/E3Cisco 2650 Cisco 2651XM 1Small to medium officesSubrate T3/E3Cisco 2691 1Large and regional offices Subrate and full-rate T3/E3 Cisco 3660 series 1Medium and large offices Subrate and full-rate T3/E3 Cisco 3725 2Medium, large, and regional offices Subrate and full-rate T3/E3 Cisco 3745 General information about ISDN voice interfaces is presented in the "Information About ISDN Voice Interfaces" section on page 4 . Note HowtoConfigureClearChannelT3E3withIntegratedCSUDSU Configuring Clear-Channel T3 This section contains the following procedures: Configuring the Card Type and Controller for T3 To configure the card type and controller for T3, perform the following steps. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 87 Clear Channel T3 E3 with Integrated CSU DSU Information About Clear Channel T3 E3 with Integrated CSU DSU
- 100. When the clear-channelT3/E3 network module is used for the first time, the running configuration does not show the T3/E3 controller and its associated serial interface. Use the show version command to learn if the router recognized the T3/E3 card and was able to initialize the card properly. After the card type is configured for the slot, the respective controller and serial interfaces appear in the running configuration. See the Additional References, on page 107. Note • The autoconfig/setup utility does not support configuring the card type for the T3/E3 network module. SUMMARY STEPS 1. enable 2. configure terminal 3. card type t3 slot 4. controller t3 slot/port 5. framing {c-bit| m23} 6. cablelength feet 7. clock source {internal| line} 8. exit DETAILED STEPS PurposeCommand or Action Enables privileged EXEC mode. Enter your password if prompted. enable Example: Router> enable Step 1 Enters global configuration mode.configure terminal Example: Router# configure terminal Step 2 Configures the card type on the T3 controller for the designated slot. card type t3 slot Example: Router(config)# card type t3 1 Step 3 By default, the T3 controller does not show up in the show running-config output. Note Specifies the T3 controller and enters controller configuration mode for the specified slot/port. controller t3 slot/port Example: Router(config)# controller t3 1 Step 4 Specifies the T3 framing type. Keywords are as follows:framing {c-bit| m23}Step 5 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 88 Clear Channel T3 E3 with Integrated CSU DSU Configuring Clear-Channel T3
- 101. PurposeCommand or Action Example: Router(config-controller)#framing c-bit • c-bit --C-bit framing • m23 --M23 framing Specifies the distance from the routers to the network equipment. cablelength feet Example: Router(config-controller)# cablelength 250 Step 6 Selects the clock source. Keywords are as follows:clock source {internal| line}Step 7 Example: Router(config-controller)# clock source line • internal --Internal clock source (T3 default) • line --Network clock source (E3 default) Exits the current mode.exit Example: Router(config-controller)# exit Step 8 Configuring DSU Mode and Bandwidth for T3 To configure DSU mode and bandwidth for T3, perform the following steps. SUMMARY STEPS 1. enable 2. configure terminal 3. interface serial slot/port 4. dsu mode {0 | 1| 2| 3| 4} 5. dsu bandwidth kbps 6. exit DETAILED STEPS PurposeCommand or Action Enables privileged EXEC mode. Enter your password if prompted.enable Example: Router> enable Step 1 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 89 Clear Channel T3 E3 with Integrated CSU DSU Configuring Clear-Channel T3
- 102. PurposeCommand or Action Entersglobal configuration mode.configure terminal Example: Router# configure terminal Step 2 Enters interface configuration mode for the specified slot/port.interface serial slot/port Example: Router(config)# interface serial 1/1 Step 3 Specifies the interoperability mode used by a T3 controller--that is, to what the T3 controller connects. Keywords are as follows: dsu mode {0 | 1| 2| 3| 4} Example: Router(config-if)# dsu mode 0 Step 4 • 0 --Another T3 controller or a Digital Link DSU (DL3100) (default) • 1 --Kentrox DSU • 2 --Larscom DSU • 3 --Adtran T3SU 300 • 4 --Verilink HDM 2182 Specifies the maximum allowable bandwidth, in kbps. Range: 1 to 44210. dsu bandwidth kbps Example: Router(config-if)# dsu bandwidth 44210 Step 5 The real (actual) vendor-supported bandwidth range is 75 to 44210 kbps. See Configuring DSU Mode and Bandwidth for T3, on page 89. Note Exits the current mode.exit Example: Router(config-if)# exit Step 6 Configuring Encryption Scrambling for T3 To configure encryption scrambling for T3, perform the following steps. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 90 Clear Channel T3 E3 with Integrated CSU DSU Configuring Clear-Channel T3
- 103. SUMMARY STEPS 1. enable 2.configure terminal 3. interface serial slot/port 4. scramble 5. exit DETAILED STEPS PurposeCommand or Action Enables privileged EXEC mode. Enter your password if prompted. enable Example: Router> enable Step 1 Enters global configuration mode.configure terminal Example: Router# configure terminal Step 2 Enters interface configuration mode for the specified slot/port. interface serial slot/port Example: Router(config)# interface serial 1/1 Step 3 Enables the scrambling of the payload. Default: off.scramble Example: Router(config-if)# scramble Step 4 Exits the current mode.exit Example: Router(config-if)# exit Step 5 Configuring a Bit-Error-Rate Test Pattern for T3 To configure a bit-error-rate test pattern for T3, perform the following steps. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 91 Clear Channel T3 E3 with Integrated CSU DSU Configuring Clear-Channel T3
- 104. SUMMARY STEPS 1. enable 2.configure terminal 3. controller t3 slot/port 4. bert pattern {2^23 | 2^20 | 2^15 | 1s | 0s | alt-0-1} interval time 5. no bert 6. exit DETAILED STEPS PurposeCommand or Action Enables privileged EXEC mode. Enter your password if prompted.enable Example: Router> enable Step 1 Enters global configuration mode.configure terminal Example: Router# configure terminal Step 2 Enters controller configuration mode for the specified slot/port.controller t3 slot/port Example: Router(config)# controller t3 1/1 Step 3 Configures a bit-error-rate test pattern. Keywords and arguments are as follows: bert pattern {2^23 | 2^20 | 2^15 | 1s | 0s | alt-0-1} interval time Step 4 Example: Router(config-controller)# bert pattern 2^20 interval 10000 • 2^23 --Pseudorandom 0.151 test pattern, 8,388,607 bits long • 2^20 --Pseudorandom 0.153 test pattern, 1,048,575 bits long • 2^15 --Pseudorandom 0.151 test pattern, 32,768 bits long • 1s --Repeating pattern of ones (...111...) • 0s --Repeating pattern of zeros (...000...) • alt-0-1 --Repeating pattern of alternating zeros and ones (...01010...) • interval time --Duration of the BER test, in minutes. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 92 Clear Channel T3 E3 with Integrated CSU DSU Configuring Clear-Channel T3
- 105. PurposeCommand or Action Disablesthe BERT test pattern.no bert Example: Router(config-controller)# no bert Step 5 Exits the current mode.exit Example: Router(config-controller)# exit Step 6 Configuring Loopback for T3 To configure loopback for T3, perform the following steps. SUMMARY STEPS 1. enable 2. configure terminal 3. controller t3 slot/port 4. loopback {local | network {line| p ayload}| remote} 5. no loopback 6. exit DETAILED STEPS PurposeCommand or Action Enables privileged EXEC mode. Enter your password if prompted.enable Example: Router> enable Step 1 Enters global configuration mode.configure terminal Example: Router# configure terminal Step 2 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 93 Clear Channel T3 E3 with Integrated CSU DSU Configuring Clear-Channel T3
- 106. PurposeCommand or Action Enterscontroller configuration mode for the specified slot/port.controller t3 slot/port Example: Router(config)# controller t3 1/1 Step 3 Loops the T3 line toward the line and back toward the router. Keywords are as follows: loopback {local | network {line| p ayload}| remote} Step 4 Example: Router(config-controller)# loopback local • local-- Loops the data back toward the router and sends an alarm-indication signal (AIS) out toward the network. On a dual port card, it is possible to run channelized on one port and primary rate on the other port. • network line | payload} --Sets loopback toward the network before going through the framer (line) or after going through the framer (payload). • remote --Sends a far-end alarm control (FEAC) request to the remote end requesting that it enter into a network line loopback. FEAC requests (and therefore remote loopbacks) are possible only when the T3 is configured for C-bit framing. M23 format does not support remote loopbacks. Removes the loop.no loopback Example: Router(config-controller)# no loopback Step 5 Exits the current mode.exit Example: Router(config-controller)# exit Step 6 Configuring the Maintenance Data Link for T3 To configure the maintenance date link for T3, perform the following steps. This configuration information is applicable only to C-bit parity T3.Note ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 94 Clear Channel T3 E3 with Integrated CSU DSU Configuring Clear-Channel T3
- 107. SUMMARY STEPS 1. enable 2.configure terminal 3. controller t3 slot/port 4. mdl {transmit{path| idle-signal | test-signal} | string{eic | lic | fic | unit | pfi | port | generator} string} 5. exit DETAILED STEPS PurposeCommand or Action Enables privileged EXEC mode. Enter your password if prompted.enable Example: Router> enable Step 1 Enters global configuration mode.configure terminal Example: Router# configure terminal Step 2 Enters controller configuration mode for the specified slot/port.controller t3 slot/port Example: Router(config)# controller t3 1/1 Step 3 Configures the MDL message. Keywords and arguments are as follows:mdl {transmit{path| idle-signal | test-signal} | string{eic | lic | fic | unit | pfi | port | generator} string} Step 4 • transmit path-- Enables transmission of the MDL path message. Example: Router(config-controller)# mdl transmit path • transmit idle-signal-- Enables transmission of the MDL idle signal message. • transmit test-signal-- Enables transmission of the MDL test signal message. • string eic string -- Equipment identification code (EIC); can be up to 10 characters. • string lic string --Location identification code (LIC); can be up to 11 characters. • string fic string --Frame identification code (FIC); can be up to 10 characters. • string unit string --Unit identification code (UIC); can be up to 6 characters. • string pfi string --Facility identification code (PFI) sent in the MDL path message; can be up to 38 characters. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 95 Clear Channel T3 E3 with Integrated CSU DSU Configuring Clear-Channel T3
- 108. PurposeCommand or Action •string port string --Port number string sent in the MDL idle signal message; can be up to 38 characters. • string generator string-- Generator number string sent in the MDL test signal message; can be up to 38 characters. Exits the current mode.exit Example: Router(config-controller)# exit Step 5 Configuring Clear-Channel E3 This section contains the following procedures: Configuring the Card Type and Controller for E3 To configure the card type and controller for E3, perform the following steps. The autoconfig/setup utility does not support configuring the card type for the T3/E3 network module.Note SUMMARY STEPS 1. enable 2. configure terminal 3. card type e3 slot 4. controller e3 slot/port 5. framing {bypass| g751} 6. clock source { internal | line } 7. exit DETAILED STEPS PurposeCommand or Action Enables privileged EXEC mode. Enter your password if prompted. enable Example: Router> enable Step 1 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 96 Clear Channel T3 E3 with Integrated CSU DSU Configuring Clear-Channel E3
- 109. PurposeCommand or Action Entersglobal configuration mode.configure terminal Example: Router# configure terminal Step 2 Configures the card type on the E3 controller for the designated slot. card type e3 slot Example: Router(config)# card type e3 1 Step 3 By default, the E3 controller does not show up in the show running-config output. Note Enters controller configuration mode for the specified slot/port.controller e3 slot/port Example: Router(config)# controller e3 1 Step 4 Specifies the framing type. Keywords are as follows:framing {bypass| g751}Step 5 Example: Router(config-controller)# framing bypass • bypass --G.751 framing is bypassed • g751 --G.751 is the E3 framing type (default) Selects the clock source. Keywords are as follows:clock source { internal | line }Step 6 Example: Router(config-controller)# clock source line • internal --Internal clock source (T3 default) • line --Network clock source (E3 default) Exits the current mode.exit Example: Router(config-controller)# exit Step 7 Configuring DSU Mode and Bandwidth for E3 To configure DSU mode and bandwidth for E3, perform the following steps. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 97 Clear Channel T3 E3 with Integrated CSU DSU Configuring Clear-Channel E3
- 110. SUMMARY STEPS 1. enable 2.configure terminal 3. interface serial slot/port 4. dsu mode {0 | 1} 5. dsu bandwidth kbps 6. exit DETAILED STEPS PurposeCommand or Action Enables privileged EXEC mode. Enter your password if prompted.enable Example: Router> enable Step 1 Enters global configuration mode.configure terminal Example: Router# configure terminal Step 2 Enters interface configuration mode for the specified slot/port.interface serial slot/port Example: Router(config)# interface serial 1/1 Step 3 Specifies the interoperability mode used by an E3 controller--that is, to what the E3 controller connects. Keywords are as follows: dsu mode {0 | 1} Example: Router(config-if)# dsu mode 0 Step 4 • 0-- (default) Another E3 controller or a digital link DSU (DL3100) • 1-- Kentrox DSU Specifies the maximum allowable bandwidth, in kbps. Range: 22 to 34010. dsu bandwidth kbps Example: Router(config-if)# dsu bandwidth 34010 Step 5 The real (actual) vendor-supported bandwidth range is 358 to 34010 kbps. See Configuring DSU Mode and Bandwidth for E3, on page 97. Note Exits the current mode.exit Example: Router(config-if)# exit Step 6 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 98 Clear Channel T3 E3 with Integrated CSU DSU Configuring Clear-Channel E3
- 111. Configuring Encryption Scramblingfor E3 To configure encryption scrambling for E3, perform the following steps. SUMMARY STEPS 1. enable 2. configure terminal 3. interface serial slot/port 4. scramble 5. exit DETAILED STEPS PurposeCommand or Action Enables privileged EXEC mode. Enter your password if prompted. enable Example: Router> enable Step 1 Enters global configuration mode.configure terminal Example: Router# configure terminal Step 2 Enters interface configuration mode for the specified slot/port. interface serial slot/port Example: Router(config)# interface serial 1/1 Step 3 Enables the scrambling of the payload. Default: off.scramble Example: Router(config-if)# scramble Step 4 Exits the current mode.exit Example: Router(config-if)# exit Step 5 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 99 Clear Channel T3 E3 with Integrated CSU DSU Configuring Clear-Channel E3
- 112. Configuring a Bit-Error-RateTest Pattern for E3 To configure a bit-error-rate test pattern for E3, perform the following steps. SUMMARY STEPS 1. enable 2. configure terminal 3. controller e3 slot/port 4. bert pattern {2^23 | 2^20 | 2^15 | 1s | 0s | alt-0-1} interval time 5. no bert 6. exit DETAILED STEPS PurposeCommand or Action Enables privileged EXEC mode. Enter your password if prompted.enable Example: Router> enable Step 1 Enters global configuration mode.configure terminal Example: Router# configure terminal Step 2 Enters controller configuration mode for the specified slot/port.controller e3 slot/port Example: Router(config)# controller e3 1/0 Step 3 Enables a bit-error-rate (BER) test pattern on a T1 or E1 line, and sets the length of the test pattern and duration of the test. Keywords and arguments are as follows: bert pattern {2^23 | 2^20 | 2^15 | 1s | 0s | alt-0-1} interval time Example: Router(config-controller)# bert pattern 2^20 interval 1440 Step 4 • 2^23 --Pseudorandom 0.151 test pattern, 8,388,607 bits long • 2^20 --Pseudorandom 0.153 test pattern, 1,048,575 bits long • 2^15 --Pseudorandom 0.151 test pattern, 32,768 bits long • 1s --Repeating pattern of ones (...111...) • 0s --Repeating pattern of zeros (...000...) • alt-0-1 --Repeating pattern of alternating zeros and ones (...01010...) • interval time --Duration of the BER test, in minutes ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 100 Clear Channel T3 E3 with Integrated CSU DSU Configuring Clear-Channel E3
- 113. PurposeCommand or Action Disablesthe BER test pattern.no bert Example: Router(config-controller)# no bert Step 5 Exits the current mode.exit Example: Router(config-controller)# exit Step 6 Configuring Loopback for E3 To configure loopback for E3, perform the following steps. SUMMARY STEPS 1. enable 2. configure terminal 3. controller e3 slot/port 4. loopback {local | network {line | payload} } 5. no loopback 6. exit DETAILED STEPS PurposeCommand or Action Enables privileged EXEC mode. Enter your password if prompted. enable Example: Router> enable Step 1 Enters global configuration mode.configure terminal Example: Router# configure terminal Step 2 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 101 Clear Channel T3 E3 with Integrated CSU DSU Configuring Clear-Channel E3
- 114. PurposeCommand or Action Enterscontroller configuration mode for the specified slot/port.controller e3 slot/port Example: Router(config)# controller e3 1/1 Step 3 Loops the E3 line toward the line and back toward the router. Keywords are as follows: loopback {local | network {line | payload} } Example: Router(config-controller)# loopback local Step 4 • local-- Loops the data back toward the router and sends an AIS signal out toward the network. • network line payload -- Sets loopback toward the network before going through the framer (line) or after going through the framer (payload). Removes the loop.no loopback Example: Router(config-controller)# no loopback Step 5 Exits the current mode.exit Example: Router(config-controller)# exit Step 6 Configuring the National Bit in the G.751 Frame for E3 To configure the national bit in the G.751 frame for E3, perform the following steps. SUMMARY STEPS 1. enable 2. configure terminal 3. controller e3 slot/port 4. national bit { 1 | 0 } 5. exit ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 102 Clear Channel T3 E3 with Integrated CSU DSU Configuring Clear-Channel E3
- 115. DETAILED STEPS PurposeCommand orAction Enables privileged EXEC mode. Enter your password if prompted. enable Example: Router> enable Step 1 Enters global configuration mode.configure terminal Example: Router# configure terminal Step 2 Enters controller configuration mode for the specified slot/port. controller e3 slot/port Example: Router(config)# controller e3 1/1 Step 3 Sets the E3 national bit in the G.751 frame used by the E3 controller. Valid values: 0 and 1. Default: 1. national bit { 1 | 0 } Example: Router(config-controller)# national bit 1 Step 4 Exits the current mode.exit Example: Router(config-controller)# exit Step 5 Verifying Clear-Channel T3 E3 To verify clear-channel T3/E3, perform the following steps (listed alphabetically). SUMMARY STEPS 1. show controllers 2. show interfaces serial 3. show isdn status 4. show running-config 5. show version ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 103 Clear Channel T3 E3 with Integrated CSU DSU Verifying Clear-Channel T3 E3
- 116. DETAILED STEPS Step 1show controllers Use this command to display information about the specified port, connector, or interface card number (location of voice module) or slot/port (location of voice network module and VIC). Step 2 show interfaces serial Use this command to display information about a serial interface. Step 3 show isdn status Use this command to display the status of all ISDN interfaces, including active layers, timer information, and switch-type settings. Step 4 show running-config Use this command to display basic router configuration. Step 5 show version Use this command to display whether the router recognized the T3/E3 card and was able to initialize the card properly. Lists the hardware interfaces and controllers present in the router. You should find "1 Subrate T3/E3 port(s)". Example: Router# show version . . . Router uptime is 2 hours, 6 minutes System returned to ROM by power-on System image file is "flash:c3725-i-mz" cisco 3725 (R7000) processor (revision 0.4) with 111616K/19456K bytes of memory. Processor board ID 12345678901 R7000 CPU at 240Mhz, Implementation 39, Rev 3.3, 256KB L2 Cache Bridging software. X.25 software, Version 3.0.0 Primary Rate ISDN software, Version 1.1 2 FastEthernet/IEEE 802.3 interface(s) 1 Serial network interface(s) 2 Channelized T1/PRI port(s) 1 Subrate T3/E3 port(s) DRAM configuration is 64 bits wide with parity disabled. 55K bytes of non-volatile configuration memory. 15680K bytes of ATA System CompactFlas (Read/Write) Configuration register is 0x0 Troubleshooting Tips Set Loopbacks • Use T3/E3 local loopback to ensure that the router and the T3/E3 network module are working properly. The controller clock source should be configured to "internal." • Use T3/E3 network loopback and remote loopback to diagnose problems with cables between the T3/E3 controller and the central switching office at the link level. For this diagnostic setup to work, if the ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 104 Clear Channel T3 E3 with Integrated CSU DSU Verifying Clear-Channel T3 E3
- 117. network module islooped toward the network, the network module must be configured with the clock source as "line." Run Bit Error Rate Test • The network module contains onboard BERT circuitry. With this circuitry present, the software can send and detect a programmable pattern that is compliant with CCITT/ITU pseudorandom and repetitive test patterns. BERT allows you to test cables and signal problems in the field. • When a BERT is running, your system expects to receive the same pattern that it is sending. To help ensure this, two common options are available. • Use a loopback somewhere in the link or network. • Configure remote testing equipment to send the same BERT pattern at the same time. Configuration Example for Clear Channel T3 E3 with Integrated CSU DSU This example shows the running configuration of a router whose E3 (slot1/0) interface is configured to use G.751 framing and a network (line, or network, is the E3 default) clock source. Note that the bandwidth of the interface is configured to 34010 kbps. Router# show running-config Building configuration... %AIM slot 0 doesn't exist Current configuration :1509 bytes ! version 12.2 service timestamps debug uptime service timestamps log uptime no service password-encryption ! hostname Router1 ! card type e3 1 no logging console ! ip subnet-zero no ip routing ! voice call carrier capacity active ! mta receive maximum-recipients 0 ! controller E3 1/0 clock source line framing g751 linecode <line code> dsu bandwidth 34010 ! interface Loopback0 no ip address no ip route-cache shutdown no keepalive ! interface FastEthernet0/0 ip address 10.0.145.34 255.255.255.0 no ip route-cache ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 105 Clear Channel T3 E3 with Integrated CSU DSU Configuration Example for Clear Channel T3 E3 with Integrated CSU DSU
- 118. no ip mroute-cache duplexauto speed auto no cdp enable ! interface Serial0/0 no ip address encapsulation ppp no ip route-cache no ip mroute-cache shutdown clockrate 2000000 no fair-queue ! interface FastEthernet0/1 no ip address no ip route-cache no ip mroute-cache shutdown duplex auto speed auto no keepalive no cdp enable ! interface Serial0/1 no ip address encapsulation ppp no ip route-cache no ip mroute-cache shutdown clockrate 2000000 ! interface Serial0/2:0 ip address 172.27.27.2 255.255.255.0 no ip route-cache no keepalive ! interface Serial1/0 no ip address no ip route-cache no keepalive dsu bandwidth 34010 ! ip classless no ip http server ! ip pim bidir-enable ! call rsvp-sync ! mgcp profile default ! dial-peer cor custom ! line con 0 exec-timeout 0 0 line aux 0 line vty 0 4 login ! end ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 106 Clear Channel T3 E3 with Integrated CSU DSU Configuration Example for Clear Channel T3 E3 with Integrated CSU DSU
- 119. Additional References General ISDNReferences • "Overview of ISDN Voice Interfaces" --Describes relevant underlying technology; lists related documents, standards, MIBs, and RFCs; and describes how to obtain technical assistance • "Additional References" section --Lists additional ISDN references ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 107 Clear Channel T3 E3 with Integrated CSU DSU Additional References
- 120. ISDN Voice ConfigurationGuide, Cisco IOS Release 15M&T 108 Clear Channel T3 E3 with Integrated CSU DSU Additional References
- 121. C H AP T E R 5 High-Density Analog (FXS, DID, FXO) and Digital (BRI) Extension Module for Voice-Fax (EVM-HD) This chapter describes the High-Density Analog (FXS/DID/FXO) and Digital (BRI) Extension Module for Voice/Fax (EVM-HD) feature, which delivers a higher-density integrated analog/digital voice interface. The EVM-HD-8FXS/DID baseboard network module provides eight Foreign Exchange Station (FXS) or direct inward dialing (DID) ports. This network module accesses digital signal processor (DSP) modules on the motherboard, instead of using onboard DSPs. You can increase the port density by plugging in up to two optional expansion modules in any combination: • EM-HDA-8FXS--8-port FXS voice/fax expansion module • EM-HDA-3FXS/4FXO--3-port FXS and 4-port FXO voice/fax expansion module • EM-HDA-6FXO--6-port FXO voice/fax expansion module • EM-4BRI-NT/TE--4-port ISDN BRI expansion module PVDM2 DSP modules are used in combination with the EVM-HD-8FXS/DID baseboard and its expansion modules. PVDM2 modules are available separately and installed in the DSP module slots located inside the router chassis. Feature History for the High-Density Analog (FXO/FXS/ DID) and Digital (BRI) Extension Module for Voice/Fax (EVM-HD) ModificationRelease This feature was introduced on the Cisco 2800 series routers. 12.3(8)T4 This feature was integrated into Cisco IOS Release 12.3(11)T. Support was added for the Cisco 3800 series routers and the EM-HDA-3FXS/4FXO and EM-HDA-6FXO expansion modules to provide FXO capability. 12.3(11)T ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 109
- 122. ModificationRelease The groundstart auto-tipcommand was added to the command-line interface and the feature was integrated into Cisco IOS Release 12.3(11)T2. This new command is not supported on the Cisco 1700 series platform. 12.3(11)T2 • Finding Feature Information, page 110 • Prerequisites for High-Density Analog and Digital Extension Module for Voice Fax, page 110 • Restrictions for High-Density Analog and Digital Extension Module for Voice Fax, page 111 • Information About High-Density Analog and Digital Extension Module for Voice Fax, page 112 • How to Configure High-Density Analog and Digital Extension Module for Voice Fax, page 115 • Configuration Examples for High-Density Analog and Digital Extension Module for Voice Fax, page 127 • Additional References, page 131 Finding Feature Information Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required. Prerequisites for High-Density Analog and Digital Extension Module for Voice Fax • Insert the network modules in the correct slots of the router at your installation. For instructions on hardware installation for this feature, refer to the Cisco Network Modules Hardware Installation Guide . • Install DSPs on the baseboard and configure the DSPs with a voice-enabled image of Cisco IOS Release 12.3(8)T4 or 12.3(11)T or a later release. • The minimum Cisco IOS Release for this feature is Release 12.3(8)T4. For optimum results, use Cisco IOS Release 12.3(11)T2. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 110 High-Density Analog (FXS, DID, FXO) and Digital (BRI) Extension Module for Voice-Fax (EVM-HD) Finding Feature Information
- 123. Restrictions for High-DensityAnalog and Digital Extension Module for Voice Fax Patch Panel Installation For the BRI interface port, you must install an appropriate patch panel. Patch panels are generally available from multiple cable and network adapter vendors: • If you are using the digital voice module EM-4BRI-NT/TE, you may, at your sole discretion, consider using the JPM2194A patch panel from the Black Box Corporation. • The EVM-HD-8FXS/DID baseboard has an RJ-21 connector. The Black Box JPM2194A patch panel accommodates RJ-11 and RJ-45 combinations possible on Cisco high-density expansion modules, and offers flexibility for expansion module upgrades (either analog or digital). Mention of non-Cisco products or services is for information purposes only and constitutes neither an endorsement nor a recommendation. Note For more information about the patch panel, see the Cisco Network Modules Hardware Installation Guide . Impedance Coefficient Settings For EVM-HD-8FXS/DID, adjacent ports 0/1, 2/3, 4/5, and 6/7 share the same impedance-coefficient settings within each pair. This pairing is especially important when you are configuring some ports for DID mode and others for FXS mode. DID installations may require different impedance selections resulting from off-premises loop characteristics. If you change an impedance setting, a message alerts you to the change. These impedance settings apply to the baseboard (EVM-HD-8FXS/DID) only--not to EM-HDA-8FXS. Setting the impedance on the EM-HDA-8FXS changes only the impedance for the port being configured. Cisco CallManager Support Before you can run the High-Density Analog (FXS/DID/FXO) and Digital (BRI) Extension Module for Voice/Fax (EVM-HD) feature, you must install a voice-enabled image of Cisco IOS Release 12.3(8)T4, Release 12.3(11)T, or a later release. When the High-Density Analog (FXS/DID/FXO) and Digital (BRI) Extension Module for Voice/Fax (EVM-HD) feature is used in a Cisco CallManager network, Release 4.1.2, Release 4.0.2a SR1, or Release 3.3.5 of Cisco CallManager must be installed. If this feature is used in a Cisco CallManager Express network, Release 3.1 of Cisco CallManager Express must be installed. EM-HDA-8FXS Ring Signal Has a Maximum of 46 Vrms for 1 REN FXS ports on the EM-HDA-8FXS have a ring signal of about 46 Vrms with a 1-REN load. If you increase the voltage by reprogramming the PCM codec filters, a false ring-trip occurs. The SLIC ring-trip detection point is determined by the amount of current flowing into the loop, so an increase in voltage increases the current for a given load. This increase in current causes an undesirable false ring trip at a REN of 1 or 2. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 111 High-Density Analog (FXS, DID, FXO) and Digital (BRI) Extension Module for Voice-Fax (EVM-HD) Restrictions for High-Density Analog and Digital Extension Module for Voice Fax
- 124. Port Numbering onthe EM-HDA-3FXS/4FXO Expansion Module If your installation includes EM-HDA-3FXS/4FXO expansion modules, note that the port numbering on these modules is not consecutive. One port number is "skipped" in the numbering between the FXO and FXS interfaces. This is important when you are defining the port numbers. The table below provides an example port-numbering scheme for FXS and FXO ports on EM-HDA-3FXS/4FXO modules installed in slots EM0 and EM1. Table 8: Example Port-Numbering Scheme for EM-HDA-3FXS/4FXO EM1EM0 FXS2/0/16FXS2/0/8 FXS2/0/17FXS2/0/9 FXS2/0/18FXS2/0/10 FXO2/0/20FXO2/0/12 FXO2/0/21FXO2/0/13 FXO2/0/22FXO2/0/14 FXO2/0/23FXO2/0/15 Information About High-Density Analog and Digital Extension Module for Voice Fax Key Features The High-Density Analog and Digital Extension Module for Voice/Fax supports the following: • Analog FXS, analog Foreign Exchange Office (FXO), DID, and digital BRI S/T NT/TE • Generic DSPware feature support: silent suppression, tone detection, voice codec • The following new expansion modules: • EM-HDA-3FXS/4FXO--3-port FXS and 4-port FXO voice/fax expansion module • EM-HDA-6FXO--6-port FXO voice/fax expansion module • EM-4BRI-NT/TE--4-port ISDN BRI expansion module • The existing EM-HDA-8FXS expansion module • G.168 ECAN echo-cancellation support • Signaling types: ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 112 High-Density Analog (FXS, DID, FXO) and Digital (BRI) Extension Module for Voice-Fax (EVM-HD) Information About High-Density Analog and Digital Extension Module for Voice Fax
- 125. FXO and FXS:Ground-start and loop-start• • DID: Wink-start, immediate-start, and delay-start • VoX (Voice over Packet) protocol support: • VoIP for H.323, Media Gateway Control Protocol (MGCP), Session Initiation Protocol (SIP) as supported by Cisco IOS software • VoFR or VoATM as supported by Cisco IOS software • Channel-bank emulation and cross connect • Hairpinning: • Digital to digital (same card) • Analog to digital (same card) • BRI ports with inline power support • BRI S/T NT/TE support, clock distribution, synchronization • REN support: five RENs per port FXS and FXO Interfaces An FXS interface connects the router or access server to end-user equipment such as telephones, fax machines, or modems. The FXS interface supplies ring, voltage, and dial tone to the station. An FXO interface is used for trunk, or tie line, connections to a PSTN CO or to a PBX. This interface is of value for off-premises station applications. FXO and FXS interfaces indicate on-hook or off-hook status and the seizure of telephone lines by one of two access signaling methods: loop-start or ground-start. The type of access signaling is determined by the type of service from the CO; standard home telephone lines use loop-start, but business telephones can use ground-start lines instead. Loop-start is the more common of the access signaling techniques. When a handset is picked up (the telephone goes off-hook), this action closes the circuit that draws current from the telephone company CO and indicates a change in status, which signals the CO to provide dial tone. An incoming call is signaled from the CO to the handset by a standard on/off pattern signal, which causes the telephone to ring. For information related to the hardware connections, refer to the hardware documents listed in the FXS and FXO Interfaces, on page 113. Network Clock Timing Voice systems that pass digitized pulse-code modulation (PCM) speech have always relied on the clocking signal being embedded in the received bit stream. This technique allows connected devices to recover the clock signal from the bit stream, and then use this recovered clock signal to ensure that data on different channels keeps the same timing relationship with other channels. If a common clock source is not used between devices, the binary values in the bit streams may be misinterpreted because the device samples the signal at the wrong moment. As an example, if the local timing of a receiving ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 113 High-Density Analog (FXS, DID, FXO) and Digital (BRI) Extension Module for Voice-Fax (EVM-HD) FXS and FXO Interfaces
- 126. device is usinga slightly shorter time period than the timing of the sending device, a string of eight continuous binary 1s may be interpreted as nine continuous 1s. If this data is then resent to further downstream devices that use varying timing references, the error can be compounded. When you make sure that each device in the network uses the same clocking signal, the integrity of the traffic can be trusted. If timing between devices is not maintained, a condition known as clock slip can occur. Clock slip is the repetition or deletion of a block of bits in a synchronous bit stream due to a discrepancy in the read and write rates at a buffer. Slips are caused by the inability of an equipment buffer store (or other mechanisms) to accommodate differences between the phases or frequencies of the incoming and outgoing signals in cases where the timing of the outgoing signal is not derived from that of the incoming signal. A BRI interface sends traffic inside repeating bit patterns called frames. Each frame is a fixed number of bits. This means that the receiving device knows exactly when to expect the end of a frame simply by counting the bits as they arrive. Therefore, if the timing between the sending and receiving device is not the same, the receiving device may sample the bit stream at the wrong moment, resulting in an incorrect value being returned. Even though you can configure Cisco IOS software to control the clocking on these devices, the default clocking mode is effectively free running, meaning that the received clock signal from an interface is not connected to the backplane of the router and used for internal synchronization between the rest of the router and its interfaces. The router uses its internal clock source to pass traffic across the backplane and other interfaces. For data applications, this internal clock sourcing generally does not present a problem because a packet is buffered in internal memory and is then copied to the transmit buffer of the destination interface. The reading and writing of packets to memory effectively removes the need for any clock synchronization between ports. Digital voice ports have a different issue. Unless otherwise configured, Cisco IOS software uses the backplane (or internal) clocking to control the reading and writing of data to the DSPs. If a PCM stream comes in on a digital voice port, it uses the external clocking for the received bit stream. However, this bit stream is not necessarily using the same reference as the router backplane, meaning the DSPs can misinterpret the data that is coming in from the controller. This clocking mismatch is seen on the router’s BRI controller as a clock slip--the router is using its internal clock source to send the traffic out the interface but the traffic coming in to the interface is using a completely different clock reference. Eventually, the difference in the timing relationship between the transmit and receive signal becomes so great that the controller registers a slip in the received frame. To eliminate the problem, you must change the default clocking behavior through Cisco IOS configuration commands. It is absolutely critical to set up the clocking commands properly. Even though the following commands are optional, we strongly recommend that you enter them as part of your configuration that you ensure proper network clock synchronization: network-clock-participate slot slot-number network-clock-select priority bri t1 e1 } slot/port The network-clock-participate command allows the router to use the clock from the line via the specified slot and synchronize the onboard clock to the same reference. If multiple VWICS are installed, you must repeat the commands for each installed card. The system clocking can be confirmed using the show network clocks command. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 114 High-Density Analog (FXS, DID, FXO) and Digital (BRI) Extension Module for Voice-Fax (EVM-HD) Network Clock Timing
- 127. How to ConfigureHigh-Density Analog and Digital Extension Module for Voice Fax Configuring Analog FXS FXO and DID Voice Ports Perform this task to configure analog FXS/FXO and DID voice ports. SUMMARY STEPS 1. enable 2. configure terminal 3. voice-port slot/subunit/port 4. shutdown 5. Do one of the following: • signal {loopStart | groundStart} • • • • signal did (immediate-start| wink-start | delay-start} 6. cptone locale 7. compand-type {u-law| a-law} 8. input gain decibels 9. output attenuation decibels 10. echo-cancel enable 11. echo-cancel coverage {24| 32 | 48| 64} 12. timeouts initial seconds 13. timeouts interdigit seconds 14. impedance {600c | 600r | 900c | 900r | complex1 | complex2} 15. ring frequency {25 | 50} 16. ring cadence {[pattern01 | pattern02| pattern03 | pattern04 | pattern05 | pattern06 | pattern07 | pattern08 | pattern09 | pattern10 | pattern11 | pattern12] | define pulse-interval} 17. description string 18. no shutdown DETAILED STEPS PurposeCommand or Action Enables privileged EXEC mode.enableStep 1 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 115 High-Density Analog (FXS, DID, FXO) and Digital (BRI) Extension Module for Voice-Fax (EVM-HD) How to Configure High-Density Analog and Digital Extension Module for Voice Fax
- 128. PurposeCommand or Action Example: Router>enable • Enter your password if prompted. Enters global configuration mode.configure terminal Example: Router# configure terminal Step 2 Enters voice-port configuration mode.voice-port slot/subunit/portStep 3 Example: Router(config)# voice-port 2/0/0 • The arguments are as follows: • slot--Specifies the number of the router slot where the voice network module is installed. • subunit--Specifies the location of the Cisco High-Density Analog Voice/Fax Network Module (EVM-HD). For this feature, the only valid entry is 0. • port--Indicates the voice port. A slash must be entered between arguments. Note • Valid entries vary by router platform; enter the show voice port summarycommand for available values. Shuts down the specified port so that it is offline when the configuration commands are entered. shutdown Example: Router(config-voiceport)# shutdown Step 4 Selects the access signaling type to match that of the telephony connection you are making. Do one of the following:Step 5 • signal {loopStart | groundStart} • FXS voice ports: • • loopStart--(default) Uses a closed circuit to indicate off-hook status; used for residential loops. • • • signal did (immediate-start| wink-start | delay-start} • groundStart--Uses ground and current detectors; preferred for PBXs and trunks. Example: Router(config-voiceport)# signal groundStart or • DID support (applies only to the base voice module). • immediate-start--Enables immediate-start signaling on the DID voice port. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 116 High-Density Analog (FXS, DID, FXO) and Digital (BRI) Extension Module for Voice-Fax (EVM-HD) Configuring Analog FXS FXO and DID Voice Ports
- 129. PurposeCommand or Action Example: •wink-start--Enables wink-start signaling on the DID voice port. • delay-start--Enables delay-start signaling on the DID voice port. Example: • To disable DID and reset to loop-start signaling, use the no signal didcommand. Example: Example: Router(config-voiceport)# signal did immediate-start Specifies the two-letter locale for the voice-call progress tones and other locale-specific parameters to be used on this voice port. cptone locale Example: Router(config-voiceport)# cptone au Step 6 • Cisco routers comply with the ISO 3166 locale name standards. To see valid choices, enter a question mark (?) following the cptone command. • The default is us. Specifies the companding standard used.compand-type {u-law| a-law}Step 7 Example: Router(config-voiceport)# compand type u-law • This command is used in cases when the DSP is not used, such as local cross-connects, and overwrites the compand-type value set by the cptone command. • The default for E1 is a-law. • The default for T1 is u-law. If you have a Cisco 3660 router, the compand-type a-law command must be configured on the analog ports only. The Cisco 2660, 3620, and 3640 routers do not require the compand-type a-law command to be configured; however, if you request a list of commands, the compand-type a-law command displays. Note Configures a specific input gain, in decibels, to be inserted at the receiver side of the interface. input gain decibels Example: Router(config-voiceport)# input gain 0 Step 8 • Range is integers from -14 to +6. • The default is 0. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 117 High-Density Analog (FXS, DID, FXO) and Digital (BRI) Extension Module for Voice-Fax (EVM-HD) Configuring Analog FXS FXO and DID Voice Ports
- 130. PurposeCommand or Action Configuresa specific output attenuation, in decibels, at the transmit side of the interface. output attenuation decibels Example: Router(config-voiceport)# output attenuation 0 Step 9 • Range is integers from -6 to +14. • The default is 0. Enables the cancellation of voice that is sent out the interface and received on the same interface. echo-cancel enable Example: Router(config-voiceport)# echo-cancel enable Step 10 Adjusts the echo canceller by the specified number of ms.echo-cancel coverage {24| 32 | 48| 64}Step 11 Example: Router(config-voiceport)# echo-cancel coverage 48 • The default is 64. Specifies the number of seconds for which the system waits for the caller to input the first digit of the dialed digits. timeouts initial seconds Example: Router(config-voiceport)# timeouts initial 5 Step 12 • Range is from 0 to 120. • The default is 10. Specifies the number of seconds for which the system will wait (after the caller has input the initial digit) for the caller to input a subsequent digit of the dialed digits. timeouts interdigit seconds Example: Router(config-voiceport)# timeouts interdigit 5 Step 13 • Range is from 0 to 120. • The default is 10. Specifies the terminating impedance of a voice-port interface for FXS only. Keywords are as follows: impedance {600c | 600r | 900c | 900r | complex1 | complex2} Step 14 Example: Router(config-voiceport)# impedance complex1 • 600c --600 ohms (complex) • 600r --600 ohms (real) • 900c --900 ohms (complex) • 900r --900 ohms (real) • complex1 --Complex 1 • complex2 --Complex 2 The default is 600r. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 118 High-Density Analog (FXS, DID, FXO) and Digital (BRI) Extension Module for Voice-Fax (EVM-HD) Configuring Analog FXS FXO and DID Voice Ports
- 131. PurposeCommand or Action ForEVM-HD-8FXS/DID, adjacent ports 0/1, 2/3, 4/5, and 6/7 share the same impedance coefficient settings within each pair. If you change an impedance setting, a message alerts you to the change. This behavior applies only to EVM-HD-8FXS/DID. It does not apply to EM-HDA-8FXS. Note (Optional) Selects the ring frequency, in Hz, used on the FXS interface.ring frequency {25 | 50}Step 15 Example: Router(config-voiceport)# ring frequency 50 • The default is 25. • This number must match the connected telephony equipment and may be country-dependent. • If not set properly, the attached telephony device may not ring or it may buzz. (Optional) Specifies an existing pattern for ring, or defines a new one.ring cadence {[pattern01 | pattern02| pattern03 | pattern04 | pattern05 | Step 16 • Each pattern specifies a ring-pulse time and a ring-interval time. pattern06 | pattern07 | pattern08 | pattern09 | pattern10 | pattern11 | pattern12] | define pulse-interval} • The keywords and arguments are as follows: • pattern01 to pattern12--Preset ring cadence patterns. Enter ring cadence ? to display ring pattern explanations. Example: Router(config-voiceport)# ring cadence pattern04 • define pulse-interval--User-defined pattern: pulse is a number (one or two digits, from 1 to 50) specifying ring pulse (on) time in hundreds of milliseconds, and interval is a number (one or two digits from 1 to 50) specifying ring interval (off) time in hundreds of milliseconds. • The default is the pattern specified by the cptone locale that has been configured. Attaches a text string to the configuration that describes the connection for this voice port. description string Example: Router(config-voiceport)# description alpha central Step 17 • string --Character string from 1 to 255 characters in length. • The default is no text string (describing the voice port) attached to the configuration. Activates the voice port.no shutdownStep 18 Example: Router(config-voiceport)# no shutdown • If a voice port is not being used, shut the voice port down with the shutdown command. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 119 High-Density Analog (FXS, DID, FXO) and Digital (BRI) Extension Module for Voice-Fax (EVM-HD) Configuring Analog FXS FXO and DID Voice Ports
- 132. Troubleshooting Tips In somerare instances, if you have installed the EM-HDA-3FXS/4FXO or the EM-HDA-6FXO and configured the voice port for groundstart signaling, you may have difficulty connecting some outgoing calls. The problem relates to the FXO groundstart voice port failing to detect a tip-ground acknowledgment, resulting in an unsuccessful call setup. If you encounter this problem, upgrade your Cisco IOS software image to the latest version (for example, if you have Release 12.3(11)T installed, upgrade to Release 12.3(11)T2). This should fix the problem. If this problem still occurs, you must enable the groundstart auto-tip command in the configuration of the FXO voice port. When you are placing outgoing calls, this ensures that the circuit detects a tip-ground acknowledgment from the far end and completes the connection within the time-out parameter. For more information about this problem, see the document Troubleshoot Analog FXO GroundStart Outbound Call Failures . This document is available on Cisco.com. Examples This section shows a sample topology (see the figure below) and configuration for the EVM-HD-8FXS/DID used as an analog DID voice gateway connecting to the PSTN. The following sample shows the configuration commands used for DID signaling: ! ! voice-port 2/0/0 signal did immediate ! voice-port 2/0/1 ! signal did wink-start timing wait-wink 550 <-- sets max time to wait for wink signaling after outgoing seizure is sent. Default is 550 ms. timing wink-wait 200 <-- sets the maximum time to wait before sending wink signal after an incoming seizure is detected. Default is 200 ms. timing wink-duration 200 <-- sets duration of wink-start signal. Default is 200 ms. ! voice-port 2/0/2 ! signal did delay-dial timing delay-duration 200 <-- sets duration of the delay signal. Default is 200 ms. timing delay-start 300 <-- sets delay interval after incoming seizure is detected. Default is 300 ms. ! ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 120 High-Density Analog (FXS, DID, FXO) and Digital (BRI) Extension Module for Voice-Fax (EVM-HD) Configuring Analog FXS FXO and DID Voice Ports
- 133. Output of theshow voice port Command: Example The following output is based on the sample configuration: Router# show voice port 2/0/1 Foreign Exchange Station with Direct Inward Dialing (FXS-DID) 2/0/0 Slot is 2, Sub-unit is 0, Port is 0 Type of VoicePort is DID-IN Operation State is DORMANT Administrative State is UP No Interface Down Failure Description is not set Noise Regeneration is enabled Non Linear Processing is enabled Music On Hold Threshold is Set to -38 dBm In Gain is Set to 0 dB Out Attenuation is Set to 0 dB Echo Cancellation is enabled Echo Cancel Coverage is set to 8 ms Playout-delay Mode is set to default Playout-delay Nominal is set to 60 ms Playout-delay Maximum is set to 200 ms Connection Mode is normal Connection Number is not set Initial Time Out is set to 10 s Interdigit Time Out is set to 10 s Ringing Time Out is set to 180 s Companding Type is u-law Region Tone is set for US Analog Info Follows: Currently processing none Maintenance Mode Set to None (not in mtc mode) Number of signaling protocol errors are 0 Impedance is set to 600r Ohm Wait Release Time Out is 30 s Station name None, Station number None Voice card specific Info Follows: Signal Type is wink-start Dial Type is dtmf In Seizure is inactive Out Seizure is inactive Digit Duration Timing is set to 100 ms InterDigit Duration Timing is set to 100 ms Pulse Rate Timing is set to 10 pulses/second InterDigit Pulse Duration Timing is set to 750 ms Clear Wait Duration Timing is set to 400 ms Wink Wait Duration Timing is set to 200 ms Wait Wink Duration Timing is set to 550 ms Wink Duration Timing is set to 200 ms Delay Start Timing is set to 300 ms Delay Duration Timing is set to 2000 ms Dial Pulse Min. Delay is set to 140 ms Percent Break of Pulse is 60 percent Auto Cut-through is disabled Dialout Delay for immediate start is 300 ms Configuring ISDN BRI Digital Interfaces To configure the ISDN BRI digital interfaces, perform this task. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 121 High-Density Analog (FXS, DID, FXO) and Digital (BRI) Extension Module for Voice-Fax (EVM-HD) Configuring ISDN BRI Digital Interfaces
- 134. SUMMARY STEPS 1. enable 2.configure terminal 3. isdn switch-type switch-type 4. network-clock-participate slot slot-number 5. network-clock-select priority {bri | t1| e1} slot/port 6. Do one of the following: • interface bri slot/port • • • • interface bri slot/subslot/port 7. isdn overlap-receiving 8. isdn twait-disable 9. isdn spid1 spid-number [ldn] 10. isdn spid2 spid-number [ldn] 11. isdn incoming-voice voice 12. shutdown 13. isdn layer1-emulate {user| network} 14. Do one of the following: • line-power • • • no line-power 15. no shutdown 16. isdn protocol-emulate {user| network} 17. isdn sending-complete 18. isdn static-tei tei-number 19. end 20. clear interface slot|port DETAILED STEPS PurposeCommand or Action Enables privileged EXEC mode.enableStep 1 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 122 High-Density Analog (FXS, DID, FXO) and Digital (BRI) Extension Module for Voice-Fax (EVM-HD) Configuring ISDN BRI Digital Interfaces
- 135. PurposeCommand or Action Example: Router>enable • Enter your password if prompted. Enters global configuration mode.configure terminal Example: Router# configure terminal Step 2 Configures the global ISDN switch type.isdn switch-type switch-typeStep 3 Example: Router(config)# isdn switch-type basic-qsig • Switch types for an NT interface are basic-net3 and basic-qsig. Allows the ports on a specified network module or VWIC to use the network clock for timing. network-clock-participate slot slot-number Step 4 Example: Router(config)# network-clock-participate slot 2 • slot-number --the network module slot number on the router chassis. (Optional) Allows backplane TDM PLL circuitry to select recovered timing references from operating digital links according to a defined priority. network-clock-select priority {bri | t1| e1} slot/port Step 5 Example: Router(config)# network-clock-select 1 bri 2/0 • The priorityargument specifies selection priority for the clock sources (1 is the highest priority). • When the higher-priority clock source fails, the next-higher-priority clock source is selected. • The bri keyword specifies that the slot is configured as BRI. • The t1 keyword specifies that the slot is configured as T1. • The e1 keyword specifies that the slot is configured as E1. • The slotargument is the slot number identifying the controller that is the clock source. • The portargument is the port number identifying the controller that is the clock source. • The range is from 0 to 7. Enters interface configuration mode for the specified interface.Do one of the following:Step 6 • interface bri slot/port • slot --Identifies the location of the voice network module in the router. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 123 High-Density Analog (FXS, DID, FXO) and Digital (BRI) Extension Module for Voice-Fax (EVM-HD) Configuring ISDN BRI Digital Interfaces
- 136. PurposeCommand or Action •port --Identifies the location of the BRI VIC in the voice network module. Range is 0 to 7: • • • • Port 0 to 3 for EM-4BRI installed in EM0. • interface bri slot/subslot/port • Port 4 to 7 for EM-4BRI installed in EM1. Example: Router(config)# interface bri 2/0 For the Cisco 2800 series, there are two kinds of port numbering: slot / port and slot / subslot / port. The first example shows that the network module is in slot 2. The second example shows that the VIC2-2BRI is in HWIC slot 1. The first 0 means the module is on the motherboard, the 1 means it is in HWIC slot 1, and the last 0 means it is the first BRI interface on VIC2-2BRI. Note Example: Example: Example: Example: Router(config)# interface bri 0/1/0 (Optional) Activates overlap signaling to send to the destination PBX.isdn overlap-receivingStep 7 Example: Router(config-if)# isdn overlap-receiving • In this mode, the interface waits for possible additional call-control information. (Optional) Delays a National ISDN BRI switch a random time before activating the Layer 2 interface when the switch starts up. isdn twait-disable Example: Router(config-if)# isdn twait-disable Step 8 • Use this command when the ISDN switch type is basic-ni1. (Optional) Specifies a SPID and optional local directory number for the B1 channel. isdn spid1 spid-number [ldn] Example: Router(config-if)# isdn spid1 12 Step 9 This command applies to TE configuration only. Note • The spid-number argument identifies the service to which you have subscribed. This value is assigned by the ISDN service provider and is usually a 10-digit telephone number with additional digits such as 40855501000101. • (Optional) The ldnargument is a seven-digit number assigned by the service provider. You can optionally specify a second and third LDN. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 124 High-Density Analog (FXS, DID, FXO) and Digital (BRI) Extension Module for Voice-Fax (EVM-HD) Configuring ISDN BRI Digital Interfaces
- 137. PurposeCommand or Action •Only the DMS-100 and NI-1 switch types require SPIDs. • Although some switch types might support a SPID, Cisco recommends that you set up ISDN service without SPIDs. (Optional) Specifies a SPID and optional local directory number for the B2 channel. isdn spid2 spid-number [ldn] Example: Router(config-if)# isdn spid2 13 Step 10 This command applies to TE configuration only. Note • The spid-number argument identifies the service to which you have subscribed. This value is assigned by the ISDN service provider and is usually a ten-digit telephone number with additional digits such as 40855501000101. • (Optional) The ldnargument is a seven-digit number assigned by the service provider. You can optionally specify a second and third LDN. Configures the port to treat incoming ISDN voice calls as voice calls that are handled by either a modem or a voice DSP, as directed by the call-switching module. isdn incoming-voice voice Example: Router(config-if)# isdn incoming-voice voice Step 11 (Optional) Resets the interface.shutdownStep 12 Example: Router(config-if)# shutdown • Do this before setting the port emulation. (Optional) Configures the Layer-1 port-mode emulation and clock settings.isdn layer1-emulate {user| network}Step 13 Example: Router(config-if)# isdn layer1-emulate network • Enter userto configure the port as TE and to function as a clock slave. This is the default. • Enter network to configure the port as NT and to function as a clock master. Turns on or off the power supplied from an NT-configured port to a TE device. Do one of the following:Step 14 • line-power • • • no line-power Example: Router(config-if)# line-power ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 125 High-Density Analog (FXS, DID, FXO) and Digital (BRI) Extension Module for Voice-Fax (EVM-HD) Configuring ISDN BRI Digital Interfaces
- 138. PurposeCommand or Action Example: Example: or Example: Example: Router(config-if)#no line-power Activates the interface.no shutdown Example: Router(config-if)# no shutdown Step 15 Configures the Layer 2 and Layer 3 port protocol emulation. Keywords are as follows: isdn protocol-emulate {user| network} Example: Router(config-if)# isdn protocol-emulate network Step 16 • user --Configures the port as TE; the PBX is the master. This is the default. • network --Configures the port as NT; the PBX is the slave. (Optional) Configures the voice port to include the Sending Complete information element in the outgoing call setup message. isdn sending-complete Example: Router(config-if)# isdn sending-complete Step 17 • This command is used in some geographic locations, such as Hong Kong and Taiwan, where the sending complete information element is required in the outgoing call setup message. (Optional) Configures a static ISDN Layer 2 terminal-endpoint identifier (TEI). The argument is as follows: isdn static-tei tei-number Example: Router(config-if)# isdn static-tei 33 Step 18 • tei-number --Range is 0 to 64. Exits interface configuration mode.end Example: Router(config-if)# end Step 19 (Optional) Resets the interface.clear interface slot|portStep 20 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 126 High-Density Analog (FXS, DID, FXO) and Digital (BRI) Extension Module for Voice-Fax (EVM-HD) Configuring ISDN BRI Digital Interfaces
- 139. PurposeCommand or Action Example: Router#clear interface 2/0 • The interface needs to be reset if the static TEI number has been configured in Configuring ISDN BRI Digital Interfaces. Arguments are as follows: • slot--Location of the voice network module in the router. • port--Location of the BRI VIC in the voice network module. Range is from 0 to 7. Configuration Examples for High-Density Analog and Digital Extension Module for Voice Fax show running-config Command Example This example shows the result of a show running-config command used with a base voice module (8FXS/DID) and one 4BRI expansion module: Router1# show running-config isdn switch-type basic-dms100 ! voice-card 0 no dspfarm ! interface GigabitEthernet0/0 ip address 10.0.0.0 255.255.0.0 duplex auto speed auto ! interface GigabitEthernet0/1 no ip address shutdown duplex auto speed auto ! interface BRI2/0 no ip address isdn switch-type basic-dms100 isdn incoming-voice voice ! interface BRI2/1 no ip address ! interface BRI2/2 no ip address ! interface BRI2/3 no ip address ! voice-port 2/0/0 signal did wink-start ! voice-port 2/0/1 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 127 High-Density Analog (FXS, DID, FXO) and Digital (BRI) Extension Module for Voice-Fax (EVM-HD) Configuration Examples for High-Density Analog and Digital Extension Module for Voice Fax
- 140. signal did wink-start ! voice-port2/0/2 caller-id enable ! voice-port 2/0/3 caller-id enable ! voice-port 2/0/4 caller-id enable ! voice-port 2/0/5 caller-id enable ! voice-port 2/0/6 caller-id enable ! voice-port 2/0/7 caller-id enable ! voice-port 2/0/8 ! voice-port 2/0/9 ! voice-port 2/0/10 ! voice-port 2/0/11 ! voice-port 2/0/17 caller-id enable signal groundStart ! voice-port 2/0/18 caller-id enable ! voice-port 2/0/19 caller-id enable ! dial-peer voice 1 pots destination-pattern 202 port 2/0/2 ! dial-peer voice 2 pots destination-pattern 203 port 2/0/3 ! dial-peer voice 3 pots destination-pattern 204 port 2/0/4 ! dial-peer voice 4 pots destination-pattern 205 port 2/0/5 ! dial-peer voice 5 pots destination-pattern 206 port 2/0/6 ! dial-peer voice 6 pots destination-pattern 207 port 2/0/7 ! end ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 128 High-Density Analog (FXS, DID, FXO) and Digital (BRI) Extension Module for Voice-Fax (EVM-HD) show running-config Command Example
- 141. show running-config CommandExample with Base Voice Module and Two 4BRI Expansion Modules This example shows the result of a show running-config command used with base voice module (8FXS/DID) and two 4BRI expansion modules. Note that the BRI interfaces are from BRI 2/0 to BRI 2/7, but that the voice ports for those BRIs are from 2/0/8 to 2/0/11 and 2/0/16 to 2/0/19. version 12.3 network-clock-participate slot 2 network-clock-select 1 BRI2/2 network-clock-select 2 BRI2/3 network-clock-select 3 BRI2/4 network-clock-select 4 BRI2/5 network-clock-select 5 BRI2/6 network-clock-select 6 BRI2/7 ! isdn switch-type basic-net3 voice-card 0 no dspfarm ! interface BRI2/0 no ip address isdn switch-type basic-net3 isdn protocol-emulate network isdn layer1-emulate network isdn incoming-voice voice isdn skipsend-idverify ! interface BRI2/1 no ip address isdn switch-type basic-net3 isdn protocol-emulate network isdn layer1-emulate network isdn incoming-voice voice isdn skipsend-idverify ! interface BRI2/2 no ip address isdn switch-type basic-net3 isdn incoming-voice voice ! interface BRI2/3 no ip address isdn switch-type basic-net3 isdn incoming-voice voice ! interface BRI2/4 no ip address isdn switch-type basic-net3 isdn incoming-voice voice ! interface BRI2/5 no ip address isdn switch-type basic-net3 isdn incoming-voice voice ! interface BRI2/6 no ip address isdn switch-type basic-net3 isdn incoming-voice voice ! interface BRI2/7 no ip address isdn switch-type basic-net3 isdn incoming-voice voice ! voice-port 2/0/0 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 129 High-Density Analog (FXS, DID, FXO) and Digital (BRI) Extension Module for Voice-Fax (EVM-HD) show running-config Command Example with Base Voice Module and Two 4BRI Expansion Modules
- 142. cptone IT ! voice-port 2/0/1 cptoneIT ! voice-port 2/0/2 cptone IT ! voice-port 2/0/3 cptone IT ! voice-port 2/0/4 cptone IT ! voice-port 2/0/5 cptone IT ! voice-port 2/0/6 cptone IT ! voice-port 2/0/7 cptone IT ! voice-port 2/0/8 cptone IT ! voice-port 2/0/9 cptone IT ! voice-port 2/0/10 cptone IT ! voice-port 2/0/11 cptone IT ! voice-port 2/0/16 cptone IT ! voice-port 2/0/17 cptone IT ! voice-port 2/0/18 cptone IT ! voice-port 2/0/19 cptone IT ! dial-peer voice 200 pots destination-pattern 200 port 2/0/0 ! dial-peer voice 201 pots destination-pattern 201 port 2/0/1 ! dial-peer voice 202 pots destination-pattern 202 port 2/0/2 ! dial-peer voice 203 pots destination-pattern 203 port 2/0/3 ! dial-peer voice 204 pots destination-pattern 204 port 2/0/4 ! dial-peer voice 205 pots destination-pattern 205 port 2/0/5 ! dial-peer voice 206 pots destination-pattern 206 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 130 High-Density Analog (FXS, DID, FXO) and Digital (BRI) Extension Module for Voice-Fax (EVM-HD) show running-config Command Example with Base Voice Module and Two 4BRI Expansion Modules
- 143. port 2/0/6 ! dial-peer voice207 pots destination-pattern 207 port 2/0/7 ! end Additional References The following sections provide references related to the High-Density Analog (FXS/DID/FXO) and Digital (BRI) Extension Module for Voice/Fax feature. Related Documents Document TitleRelated Topic Cisco Network Modules Hardware Installation GuideHardware installation instructions for network modules Cisco IOS Voice Command Reference, Release 12.3TGeneral information about voice configuration and command Voice Network Module and Voice Interface Card Configuration Note Update to information about voice configuration cards Standards TitleStandards --No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature. RFCs TitleRFCs --No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 131 High-Density Analog (FXS, DID, FXO) and Digital (BRI) Extension Module for Voice-Fax (EVM-HD) Additional References
- 144. MIBs MIBs LinkMIBs To locateand download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL: http://www.cisco.com/go/mibs • CISCO-ENTITY-VENDORTYPE-OID-MIB • OLD-CISCO-CHASSIS-MIB Technical Assistance LinkDescription http://www.cisco.com/public/support/tac/home.shtmlTechnical Assistance Center (TAC) home page, containing 30,000 pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 132 High-Density Analog (FXS, DID, FXO) and Digital (BRI) Extension Module for Voice-Fax (EVM-HD) Additional References
- 145. C H AP T E R 6 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers This chapter describes how to configure ISDN PRI interfaces to support the integration of data and voice calls on multiservice access routers. This feature enables data (dial-in, dial-on-demand routing [DDR], and DDR backup) and voice call traffic to occur simultaneously from the supported ISDN PRI interfaces. You can also enable multilevel precedence and preemption (MLPP) for DDR calls over the active voice call when no idle channel is available during the DDR call setup. Feature History for Integrated Data and Voice Services for ISDN PRI Interfaces ModificationRelease This feature was introduced.12.4(4)XC This feature was integrated into Cisco IOS Release 12.4(9)T. 12.4(9)T • Finding Feature Information, page 134 • Prerequisites for Integrated Data and Voice Services for ISDN PRI Interfaces, page 134 • Restrictions for Integrated Data and Voice Services for ISDN PRI Interfaces, page 135 • Information About Integrated Data and Voice Services for ISDN PRI Interfaces, page 136 • How to Configure Integrated Data and Voice Services for ISDN PRI Interfaces, page 139 • Troubleshooting Tips for Integrated Data and Voice Services, page 154 • Configuration Examples for Integrated Data and Voice Services for ISDN PRI Interfaces, page 155 • Additional References, page 169 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 133
- 146. Finding Feature Information Yoursoftware release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required. Prerequisites for Integrated Data and Voice Services for ISDN PRI Interfaces • Establish a working H.323 or SIP network for voice calls. • Ensure that you have a Cisco IOS image that supports this feature. Access Cisco Feature Navigator at http://www.cisco.com/go/cfn . • Perform basic ISDN PRI voice configuration, including dial-on demand routing (DDR) configuration for data calls. For more information, see Configuring ISDN PRI Voice-Interface Support. • To support PRI data calls, a VWIC-1MFT-E1 voice cards must have a packet voice data module (PVDM). Supported Modules • This feature supports the following modules: • NM-HD • NM-HDV2 • Onboard DSPs • This feature supports the following voice cards: • VWIC-XMFT-X interface modules • VWIC2-XMFT-X interface modules Data calls are supported only on the NM-HDV2-2T1/E1 and NM-HD-2V-E network modules, and the VWIC-2MFT-E1, VWIC-2MFT-T1 and VWIC2-T1/E1 voice cards. Note Use the isdn switch-type ? command in interface configuration mode or global configuration mode to view the list of supported ISDN switch types. See the following example: Router(config)# isdn switch-type ? primary-4ess Lucent 4ESS switch type for the U.S. primary-5ess Lucent 5ESS switch type for the U.S. primary-dms100 Northern Telecom DMS-100 switch type for the U.S. primary-dpnss DPNSS switch type for Europe ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 134 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers Finding Feature Information
- 147. primary-net5 NET5 switchtype for UK, Europe, Asia and Australia primary-ni National ISDN Switch type for the U.S. primary-ntt NTT switch type for Japan primary-qsig QSIG switch type primary-ts014 TS014 switch type for Australia (obsolete) Restrictions for Integrated Data and Voice Services for ISDN PRI Interfaces • This feature is supported only on C5510 DSP-based platforms. • ISDN backhaul is not supported. • This feature does not support modem calls. • For platforms that support HDLC resources on the motherboard, the available on board HDLC resources are limited to 31 if all resources are not enabled. • The Cisco 2801 platform does not support full channelized data or full integrated data and voice over T1/E1 PRI interfaces. However, data back up through one PRI channel, or one group of PRI channels for data backup, is supported on this platform. • Only PPP with multilink is supported for multiple channels. HDLC is not supported for multiple channels. • You can either configure ds0-groups or pri-groups on one controller, but not both. You receive a message, as in the following example: Router(config-controller)#ds0-group 19 timeslots 20 type e&m-imme$9 timeslots 20 type e&m-immediate-start %A pri-group was configured already. Please remove it to configure a ds0-group • The following calls are not preempted by a DDR call: • Calls from a T.37 store-and-forward off-ramp gateway • Incoming ISDN calls • This feature is not supported from a BRI interface. • The following dialer commands are not supported with the integrated data and voice feature: • dialer aaa • dialer callback-secure • dialer callback-server • dialer dns • dialer order • dialer persistent • dialer redial • dialer vpdn • dialer watch-disable ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 135 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers Restrictions for Integrated Data and Voice Services for ISDN PRI Interfaces
- 148. • dialer watch-group •dialer watch-list • dialer watch-list delay Information About Integrated Data and Voice Services for ISDN PRI Interfaces An ISDN serial interface configured for integrated mode supports data and voice calls using incoming call type checking to accept incoming voice and data calls when an inbound voice dial peer is matched. The call type of an incoming call is determined using the incoming dial-peer. For data dial peer matching, the called number of an incoming call is used to match the incoming called-number of POTS dial peers. Enabling integrated services allows data and voice call traffic to occur from ISDN PRI interfaces simultaneously. When an interface is in integrated service mode: • ISDN performs calltype checking for the incoming call. The call is rejected by ISDN if no voice or data dial peer is matched for an incoming call. • The voice option for the isdn incoming-voice command, which treats incoming calls as voice calls, is not available. By default, the integrated service option is disabled from the supported interfaces. After an ISDN interface is assigned to a trunk group, you can configure maximum incoming and outgoing calls based on the call type (voice or data) or direction (inbound or outbound) through the trunk group. When the isdn integrate calltype allcommand is removed from the interface, the isdn incoming-voice voicesetting is restored and the interface returns to voice mode. This feature adds support for multilevel precedence and preemption (MLPP) for dial-on-demand routing (DDR) backup calls over outgoing voice calls. Precedence designates the priority level that is associated with a call. Preemption designates the process of terminating lower-precedence calls so that a call of higher precedence can be extended. DDR backup is used to provide backup to a WAN link using any DDR or a dial-capable interface, like ISDN PRI interfaces. From the gateway, voice and DDR backup calls are controlled by different entities. • The preemption level of an outgoing voice call is determined using the selected outbound POTS dial peer. • The preemption level of a DDR backup call is determined using the dialer map class. A DDR backup call with higher precedence preempts the active outgoing voice call with a lower precedence if the idle B channel is not available from a trunk group during the DDR backup call setup. If MLPP is not configured, data calls wait for a free channel. A trunk group is used as a common channel resource pool for idle channel allocation for outgoing voice calls and DDR backup calls. Multiple ISDN PRI interfaces that have been configured for integrated services are assigned to this trunk group to build up a channel resource pool for both voice and data calls. Enabling preemption on the trunk group allows DDR call preemption over a voice call per trunk group. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 136 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers Information About Integrated Data and Voice Services for ISDN PRI Interfaces
- 149. The tone timerdefines the expiry timer for the preemption tone for the outgoing voice call, which is being preempted by a DDR backup call. When the tone timer expires, the call is disconnected. During dial-on-demand routing (DDR) call setup, an idle B channel is selected from the trunk group. The trunk group and preemption level are configured as part of a map class, which can be attached to a dialer map or dialer string. By default, the preemption level of dialer calls is set to the lowest level (routine) to disable the MLPP service for a DDR call. The trunk group preemption level is configured as part of a map class, which can be attached to a dialer map or dialer string. • For legacy DDR, configure the dialer interface to associate the class parameter with the dialer in-band and dialer map commands. • For dialer profiles, configure the dialer interface to associate the class parameter with the dialer pool and dialer string commands. For TDM-only calls, or for calls that are hairpinned, the preemption tone is not heard as the DSPs are dropped. For this reason, you must disable TDM hairpinning on the voice card to use the MLPP DDR backup call preemption feature. The preemption level of an outgoing voice call is defined from the outbound POTS dial peer. The preemption level defines the preemption priority level of an outgoing voice call. ISDN call failures are most commonly attributed to dial-on-demand routing (DDR), ISDN layers 1, 2, and 3, and Point-to-Point Protocol (PPP), including link control protocol (LCP), Authentication, or IP Control Protocol (IPCP)-related issues. Integrated Services for Multiple Call Types ISDN interfaces can support both data calls and voice calls. Typically, this is done using one interface for data and another for voice. This feature enables data (dial-in, dial-on-demand routing [DDR], and DDR backup) and voice call traffic to occur simultaneously from the supported ISDN PRI interfaces. To enable integrated services, the interface used for incoming voice calls is configured to accept multiple voice call types. The figure below shows an ISDN network configured for integrated data and voice services. Figure 5: Integrated Voice with DDR Interface for WAN Failure Backup ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 137 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers Integrated Services for Multiple Call Types
- 150. Resource Allocation forVoice and Data Calls Voice calls use DSP resources and data calls use HDLC resources for transmission. When an interface is configured for integrated services, the gateway allocates the HDLC resources dynamically during call setup and frees them back to the HDLC resource pools when the call terminates. This allows spare HDLC resources to support ISDN PRI data calls and DSP resources to support voice calls. MLPP Call Preemption over Voice Calls Multilevel precedence and preemption (MLPP) is the placement of priority calls through the network. Precedence designates the priority level that is associated with a call. Preemption designates the process of terminating lower-priority calls so that a call of higher precedence can be extended. Preemption levels are assigned to outgoing voice calls and DDR backup calls. DDR backup is used to provide backup to a WAN link. From the gateway, voice and DDR backup calls are controlled by different entities: • The preemption level of an outgoing voice call is determined using the selected outbound POTS dial peer. • The preemption level of a DDR backup call is determined using the dialer map class. A trunk group is used as the common channel resource pool for outgoing voice call and DDR backup calls. Calls with a higher precedence preempt an active outgoing voice call, of a lower precedence, if an idle B channel is not available. An ISDN interface that is configured for integrated mode is assigned to this trunk group to allow dialer resources and voice resources to request an idle B channel from the same resource pool. Preemption of Outgoing Voice Calls The trunk group and preemption level are configured as part of a map class, which can be attached to a dialer map. The dialer map class supplies configuration parameters to dialer interfaces and can be referenced from multiple dialer interfaces. During dial-on-demand routing (DDR) backup call setup, an idle B channel is selected from the trunk group. When no idle channel is found, the trunk group resource manager (TGRM) selects a B channel on the basis of the following: • The B channel currently active with a connected outgoing voice call • The preemption level of the connected voice call being lower than the preemption level of a DDR call A guard timer, configured for the trunk group, is used to delay the idle channel notification and defer the DDR setup to allow the remote channel time to become ready and accept the incoming call with the higher precedence. By default, the preemption level of dialer calls is set to the lowest level (routine) to disable the MLPP service for a DDR call. The preemption level of an outgoing voice call is defined from the selected outbound POTS dial peer. During the voice call setup, the trunk group resource manager (TGRM) selects an idle B channel from a trunk group on the basis of the following: • The call ID of an outgoing voice call ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 138 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers Resource Allocation for Voice and Data Calls
- 151. • The preemptionlevel of an outgoing call as defined by the POTS dial peer • The voice interface B channel information of an outgoing voice call When the preemption call notification is received, the TGRM saves the outgoing voice call to the preemption level link list based on FIFO. Preemption Tones When an outgoing voice call is preempted by a DDR backup call, the preemption call treatment starts by providing a preemption tone and starting the tone timer. An MLPP preemption tone is a special tone played to the voice call announcing that the line is about to be seized by a call with a higher precedence. A steady tone, 1060 ms in duration, is played on all legs of the call until the user hangs up or the preemption tone times out. • For the telephony leg of the call, the preemption tone is played using the DSP. • For the IP leg (across the VoIP network) of the call, the preemption tone is played as media. • For the ephone leg on Cisco CME, a reorder tone is played for the local user and a preemption tone is played for the remote user. Preemption Cause Codes When the preemption tone timer is expired and the call is still in a connected state, both call legs are disconnected by the gateway with the following cause code: Preemption - Circuit Reserved 0x8 If you release the call before the preemption tone timer expires, the following cause code is used: Normal Call Clear 0x10 In both cases, the following internal cause code is used for the release calls: Preemption Circuit Reserved 0x8 How to Configure Integrated Data and Voice Services for ISDN PRI Interfaces Configuring the ISDN PRI Interface for Multiple Call Types Perform the following tasks to configure integrated services: Prerequisites Unlike voice calls, which use DSP resources, data calls use HDLC resources for transmission. To use the integrated services feature, the gateway must allocate HDLC resources dynamically during call setup and free them back to the HDLC resource pools when the call terminates. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 139 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers How to Configure Integrated Data and Voice Services for ISDN PRI Interfaces
- 152. Use the followingshow commands to view the availability of HDLC resources: • show tdm connections The following example shows HDLC resources on the TDM side. Router# show tdm connections slot 0 Active TDM connections for slot 0 ================================= (Key: GT=FLEX TDM, V0=VWIC0, V1=VWIC1, V2=VWIC2, V3=VWIC3 IC=EXPANSION, P0=PVDM0, P1=PVDM1, P2=PVDM2, P3=PVDM3 HD=HDLC, BP=Backplane(AIM/NM)) V0:04/04-->HD:31/18, V0:04/06-->HD:31/06, V0:04/08-->HD:31/12 V0:04/10-->HD:31/36, V0:04/12-->HD:31/16, V0:04/14-->HD:31/10 V0:04/16-->HD:31/04, V0:04/18-->HD:31/14, V0:04/20-->HD:31/22 V0:04/22-->HD:31/20, V0:04/24-->HD:31/24, V0:04/26-->HD:31/30 V0:04/28-->HD:31/26, V0:04/30-->HD:31/32, V0:04/32-->HD:31/08 V0:04/34-->HD:31/34, V0:04/36-->HD:31/28, V0:04/38-->HD:31/38 V0:04/64-->HD:31/00, V0:04/66-->HD:31/02, HD:31/00-->V0:04/64 HD:31/02-->V0:04/66, HD:31/04-->V0:04/16, HD:31/06-->V0:04/06 HD:31/08-->V0:04/32, HD:31/10-->V0:04/14, HD:31/12-->V0:04/08 HD:31/14-->V0:04/18, HD:31/16-->V0:04/12, HD:31/18-->V0:04/04 HD:31/20-->V0:04/22, HD:31/22-->V0:04/20, HD:31/24-->V0:04/24 HD:31/26-->V0:04/28, HD:31/28-->V0:04/36, HD:31/30-->V0:04/26 HD:31/32-->V0:04/30, HD:31/34-->V0:04/34, HD:31/36-->V0:04/10 HD:31/38-->V0:04/38, • show controllers serial [slot/port In the following example, the -1 listings under the hdlc_chan column show the free HDLC channels. Router# show controllers Serial 1/1:0 Interface Serial1/1:0 Hardware is HDLC32 HDLC32 resource allocated to this interface: Slot 1, Vic_slot 1, Port 1 CRC on 1, idle flags 1, frame inverted 0, clocking 0 Channel-group number 0, hdlc32 channel number 2 Channel-group bitfield 0x80000000, hdlc32 quad used 0x4 Channel HW state: 2 TX Ring: data_ptr: 0x0, descriptor: 0x102 data_ptr: 0x0, descriptor: 0x102 data_ptr: 0x0, descriptor: 0x102 data_ptr: 0x0, descriptor: 0x102 data_ptr: 0x0, descriptor: 0x102 data_ptr: 0x0, descriptor: 0x102 data_ptr: 0x0, descriptor: 0x102 data_ptr: 0x0, descriptor: 0x102 data_ptr: 0x0, descriptor: 0x102 data_ptr: 0x0, descriptor: 0x102 data_ptr: 0x0, descriptor: 0x102 data_ptr: 0x0, descriptor: 0x102 data_ptr: 0x0, descriptor: 0x102 data_ptr: 0x0, descriptor: 0x102 data_ptr: 0x2DD1918C, descriptor: 0xB8830102 data_ptr: 0x0, descriptor: 0x102 RX Ring: data_ptr: 0x2EE83E04, descriptor: 0x88800102 data_ptr: 0x2EE84064, descriptor: 0x88800102 data_ptr: 0x2EE842C4, descriptor: 0x88800102 data_ptr: 0x2EE84524, descriptor: 0x88800102 hdlc_chan hdlc_quad owner_idb chan chan_bitfield vic_slot port ========= ========= ========= ==== ============= ======== ==== 0 1 65C03D5C 15 10000 1 0 1 2 65CB80F8 15 10000 1 1 2 4 67B862B0 0 80000000 1 1 3 8 65C7B1E4 1 40000000 1 1 4 10 67B8EDFC 2 20000000 1 1 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 140 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers Configuring the ISDN PRI Interface for Multiple Call Types
- 153. 5 20 65C83D303 10000000 1 1 6 40 67B97948 4 8000000 1 1 7 80 65C8C87C 5 4000000 1 1 8 100 67BA0494 6 2000000 1 1 9 200 65C953C8 7 1000000 1 1 -1 0 0 8 800000 1 1 -1 0 0 28 8 1 1 -1 0 0 0 0 0 0 -1 0 0 0 0 0 0 -1 0 0 0 0 0 0 -1 0 0 0 0 0 0 -1 0 0 0 0 0 0 -1 0 0 0 0 0 0 -1 0 0 0 0 0 0 -1 0 0 0 0 0 0 -1 0 0 0 0 0 0 -1 0 0 0 0 0 0 -1 0 0 0 0 0 0 -1 0 0 0 0 0 0 -1 0 0 0 0 0 0 -1 0 0 0 0 0 0 -1 0 0 0 0 0 0 -1 0 0 0 0 0 0 -1 0 0 0 0 0 0 -1 0 0 0 0 0 0 -1 0 0 0 0 0 0 -1 0 0 0 0 0 0 Configuring the POTS Dial-Peer Incoming Called Number Use the following procedure to configure the POTS dial peer and incoming called number. SUMMARY STEPS 1. enable 2. configure terminal 3. dial-peer data tag pots 4. incoming called number string DETAILED STEPS PurposeCommand or Action Enables privileged EXEC mode.enableStep 1 Example: Router> enable • Enter your password if prompted. Enters global configuration mode.configure terminal Example: Router# configure terminal Step 2 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 141 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers Configuring the ISDN PRI Interface for Multiple Call Types
- 154. PurposeCommand or Action Createsa data dial peer and enters data dial-peer configuration mode. dial-peer data tag pots Example: Router(config)# dial-peer data 100 pots Step 3 For data dial-peer matching, only the called number of an incoming call is used to match the incoming called number of POTS dial peers. Wild cards are accepted. incoming called number string Example: Router(config-dial-peer)# incoming called number 4085550110 Step 4 The string must match the dialer string on the remote gateway. Note Configuring the Data Dial Peer Lookup Preference To optimize data or voice dial-peer searches for incoming ISDN calls, configure the preference of dial-peer lookup during the call type checking. Use the following procedure to configure a search for dial peers by type. SUMMARY STEPS 1. enable 2. configure terminal 3. dial-peer search type {data| none| voice} {data | voice} DETAILED STEPS PurposeCommand or Action Enables privileged EXEC mode.enableStep 1 Example: Router> enable • Enter your password if prompted. Enters global configuration mode.configure terminal Example: Router# configure terminal Step 2 Configures the preference of voice or data dial-peer lookup during the calltype checking for incoming ISDN calls. dial-peer search type {data| none| voice} {data | voice} Step 3 Example: Router(config)# dial-peer search type data voice • data --Search dial peers with type data first. • none --Search dial peers with any type at the same preference. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 142 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers Configuring the ISDN PRI Interface for Multiple Call Types
- 155. PurposeCommand or Action •voice --Search dial peers with type voice first. By default, the data dial peer is searched first before voice dial peers. Enabling Integrated Services Use the following procedure to enable integrated mode on a serial interface. SUMMARY STEPS 1. enable 2. configure terminal 3. interface serial slot/port : timeslot 4. shutdown 5. isdn integrate calltype all 6. no shutdown DETAILED STEPS PurposeCommand or Action Enables privileged EXEC mode.enableStep 1 Example: Router> enable • Enter your password if prompted. Enters global configuration mode.configure terminal Example: Router# configure terminal Step 2 Specifies a serial interface for ISDN PRI channel-associated signaling and enters interface configuration mode. interface serial slot/port : timeslot Example: Router(config)# interface serial 0/1:15 Step 3 Shuts down the interface.shutdown Example: Router(config-if)# shutdown Step 4 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 143 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers Configuring the ISDN PRI Interface for Multiple Call Types
- 156. PurposeCommand or Action Enablesthe serial interface for integrated mode, which allows data and voice call traffic to occur simultaneously. isdn integrate calltype all Example: Router(config-if)# isdn integrate calltype all Step 5 This configuration disables the voice option for the isdn incoming-voicecommand on the interface. Note Returns the interface to the active state.no shutdown Example: Router(config-if)# no shutdown Step 6 Creating a Trunkgroup and Configuring Maximum Calls Based on Call Type Use the following procedure to create a trunk group and configure maximum calls based on call type. If trunk groups are not configured, data and voice calls are treated as first-come first-served.Note SUMMARY STEPS 1. enable 2. configure terminal 3. trunk group name 4. max-calls {any | d at a| voice} number [direction [in | out]] DETAILED STEPS PurposeCommand or Action Enables privileged EXEC mode.enableStep 1 Example: Router> enable • Enter your password if prompted. Enters global configuration mode.configure terminal Example: Router# configure terminal Step 2 Defines a trunk group and enters trunk group configuration mode.trunk group nameStep 3 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 144 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers Configuring the ISDN PRI Interface for Multiple Call Types
- 157. PurposeCommand or Action Example: Router(config)#trunk group 20 • name --Name of the trunk group. Valid names contain a maximum of 63 alphanumeric characters. Defines the maximum number of dial-in or DDR data calls, or voice calls (incoming or outgoing) that can be accepted. max-calls {any | d at a| voice} number [direction [in | out]] Step 4 Example: Router(config-trunk-group)# max-calls data 100 direction out • any --Assigns the maximum number of calls that the trunk group can handle, regardless of the call type. • data --Assigns the maximum number of data calls to the trunk group. • voice --Assigns the maximum number of voice calls to the trunk group. • number --Specifies number of allowed calls. Range is from 0 to 1000. • direction --(Optional) Specifies direction of calls. • in --(Optional) Allows only incoming calls. • out --(Optional) Allows only outgoing calls. Examples See the following sample configurations for the max-calls command: • This example configuration for trunk group 1 accepts up to a maximum of 7 dial-in data or DDR calls and places no restriction on voice calls: trunk group 1 max-calls data 7 • This sample configuration for trunk group 2 accepts up to a maximum of 2 data dial-in, 3 DDR calls, and 16 voice calls in any direction: trunk group 2 max-calls data 2 direction in max-calls data 3 direction out max-calls voice 16 • This sample configuration for trunk group 3 accepts up to a maximum of 10 incoming voice and dial-in data calls. trunk group 3 max-calls any 10 direction in Disabling Integrated Services Use the following procedure to remove the integrated services option from the interface. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 145 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers Configuring the ISDN PRI Interface for Multiple Call Types
- 158. 1 enable 2 configureterminal 3 interface serial slot/port : timeslot 4 shutdown 5 no isdn integrate calltype all 6 no shutdown SUMMARY STEPS 1. enable 2. configure terminal 3. interface serial slot/port : timeslot 4. shutdown 5. no isdn integrate calltype all 6. no shutdown DETAILED STEPS PurposeCommand or Action Enables privileged EXEC mode.enableStep 1 Example: Router> enable • Enter your password if prompted. Enters global configuration mode.configure terminal Example: Router# configure terminal Step 2 Specifies a serial interface for ISDN PRI channel-associated signalling and enters interface configuration mode. interface serial slot/port : timeslot Example: Router(config)# interface serial 0/1:15 Step 3 Shuts down the interface.shutdown Example: Router(config-if)# shutdown Step 4 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 146 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers Configuring the ISDN PRI Interface for Multiple Call Types
- 159. PurposeCommand or Action Disablesthe serial interface from being in integrated mode. You are prompted to confirm this command. no isdn integrate calltype all Example: Router(config-if)# no isdn integrate calltype all Step 5 This configuration restores the voice option for the isdn incoming-voicecommand on the interface. Note Returns the interface to the active state.no shutdown Example: Router(config-if)# no shutdown Step 6 Configuring MLPP Call Preemption over Outgoing Voice Calls Perform the following tasks to configure call preemption: Enabling Preemption on the Trunk Group Use the following procedure to create a trunk group resource pool and enable preemption on the trunk group. If the trunk group channel resource pool is not shared between voice and DDR calls, you should not enable preemption on the trunk group. Note SUMMARY STEPS 1. enable 2. configure terminal 3. trunk group name 4. preemption enable 5. preemption tone timer seconds 6. preemption guard timer value DETAILED STEPS PurposeCommand or Action Enables privileged EXEC mode.enableStep 1 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 147 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers Configuring MLPP Call Preemption over Outgoing Voice Calls
- 160. PurposeCommand or Action Example: Router>enable • Enter your password if prompted. Enters global configuration mode.configure terminal Example: Router# configure terminal Step 2 Defines a trunk group and enters trunk group configuration mode.trunk group nameStep 3 Example: Router(config)# trunk group 20 • name --Name of the trunk group. Valid names contain a maximum of 63 alphanumeric characters. Enables preemption capabilities on a trunk group.preemption enable Example: Router(config-trunk-group)# preemption enable Step 4 Defines the expiry time for the preemption tone for the outgoing call being preempted by a DDR backup call. preemption tone timer seconds Example: Router(config-trunk-group)# preemption tone timer 20 Step 5 • seconds --Expiry time, in seconds. The range is 4 to 30. The default value is 10. Use the default preemption tone timer command to change back to the default value and no preemption tone timer to disable the tone timer. Note Defines the guard timer for the DDR call to allow time to clear the last call from the channel. preemption guard timer value Example: Router(config-trunk-group)# preemption guard timer 60 Step 6 • value --Guard timer, in milliseconds. The range is 60 to 500. When preemption is enabled on the trunk group, the default value is 60. Defining a Dialer Map Class and Setting the Preemption Level Use the following procedure to define a map class for the dialer interface. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 148 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers Configuring MLPP Call Preemption over Outgoing Voice Calls
- 161. SUMMARY STEPS 1. enable 2.configure terminal 3. map-class dialer class-name 4. dialer trunkgroup label 5. dialer preemption level {flash-override | flash | immediate | priority | routine} DETAILED STEPS PurposeCommand or Action Enables privileged EXEC mode.enableStep 1 Example: Router> enable • Enter your password if prompted. Enters global configuration mode.configure terminal Example: Router# configure terminal Step 2 Defines a class of shared configuration parameters associated with the dialer map command for outgoing calls from an ISDN interface. The class name is a unique class identifier. map-class dialer class-name Example: Router(config)# map-class dialer dial1 Step 3 • class-name --Unique class identifier. Defines the dial-on-demand trunk group label.dialer trunkgroup labelStep 4 Example: Router(config-map-class)# dialer trunkgroup 20 • label --Unique name for the dialer interface trunk group. Valid names contain a maximum of 63 alphanumeric characters. Defines the preemption level of the DDR call on the dialer interface. The default is routine. dialer preemption level {flash-override | flash | immediate | priority | routine} Step 5 Example: Router(config-map-class)# dialer preemption level flash • flash-override --Level 0 (highest) • flash --Level 1 • immediate --Level 2 • priority --Level 3 • routine --Level 4 (lowest) ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 149 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers Configuring MLPP Call Preemption over Outgoing Voice Calls
- 162. Associating the ClassParameter on the Dialer Interface Use the following procedure to associate the class parameter on the dialer interface. or dialer string dial-string class class-name SUMMARY STEPS 1. enable 2. configure terminal 3. interface dialer dialer-rotary-group-number 4. Do one of the following: • dialer in-band [no-parity| odd-parity] • dialer pool number 5. Do one of the following: • dialer map protocol-keyword protocol-next-hop-address [name host-name] [speed 56| speed 64] [broadcast] class dialer-map-class-name [dial-string[: isdn-subaddress]] • • • • dialer string dial-string [ class class name] DETAILED STEPS PurposeCommand or Action Enables privileged EXEC mode.enableStep 1 Example: Router> enable • Enter your password if prompted. Enters global configuration mode.configure terminal Example: Router# configure terminal Step 2 Defines a dialer rotary group.interface dialer dialer-rotary-group-number Step 3 • dialer-rotary-group-number-- Number of the dialer rotary group. The range is 0 to 255. Example: Router(config)# interface dialer 10 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 150 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers Configuring MLPP Call Preemption over Outgoing Voice Calls
- 163. PurposeCommand or Action Specifiesthat dial-on-demand routing (DDR) is to be supported on this interface.Do one of the following:Step 4 • dialer in-band [no-parity| odd-parity] • no-parity --(Optional) No parity is to be applied to the dialer string that is sent out to the modem on synchronous interfaces. • odd-parity --(Optional) Dialed number has odd parity (7-bit ASCII characters with the eighth bit as the parity bit) on synchronous interfaces. • dialer pool number Example: Router(config-if)# dialer in-band or Specifies, for a dialer interface, which dialing pool to use to connect to a specific destination subnetwork. Example: Router(config-if)# dialer pool 1 • number --The dialing pool number. The range is 1 to 255. Configures an ISDN interface to place a call to multiple sites and to authenticate calls from multiple sites. Do one of the following:Step 5 • dialer map protocol-keyword protocol-next-hop-address [name • protocol-keyword protocol-next-hop-address --For ISDN services, you must use ip for the protocol-keyword.host-name] [speed 56| speed 64] [broadcast] class • name host-name --(Optional) The remote system with which the local router or access server communicates. Used for authenticating the remote dialer-map-class-name [dial-string[: isdn-subaddress]] system on incoming calls. The host-name argument is a case-sensitive name or ID of the remote device. For routers with ISDN interfaces, if• calling line identification--sometimes called CLID, but also known as• caller ID and automatic number identification (ANI)--is provided, the• host-name argument can contain the number that the calling line ID provides. • dialer string dial-string [ class class name] • speed 56 | speed 64--(Optional) Keyword and value indicating the line speed in kbps to use. Used for ISDN only. The default speed is 64 kbps. Example: Router(config-if)# dialer map ip • broadcast --(Optional) Forwards broadcasts to the address specified with the protocol-next-hop-address argument. 172.22.82.2 name gw3845 class dial1 20009 • class dialer-map-class-name--Dialer map class name. Example: Router(config-if)# dialer string 4081234 class test • dial-string : isdn-subaddress ] --(Optional) Dial string (telephone number) sent to the dialing device when it recognizes packets with the specified address that matches the configured access lists, and the optional subaddress number used for ISDN multipoint connections. The colon is required for separating numbers. The dial string and ISDN subaddress, when used, must be the last item in the command line. or Specifies the string (telephone number) to be used when placing a call from an interface. • dial-string --Telephone number to be sent to a DCE device. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 151 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers Configuring MLPP Call Preemption over Outgoing Voice Calls
- 164. PurposeCommand or Action •class class name --(Optional) Dialer map class associated with this telephone number. Examples Legacy DDR Example interface Dialer11 ip address 172.22.82.1 255.255.255.0 encapsulation ppp dialer in-band dialer map ip 172.22.82.2 name gw3845 class dial1 20009 dialer load-threshold 1 outbound dialer-group 1 ppp callback accept ppp authentication chap ppp multilink map-class dialer dial1 dialer trunkgroup 1 dialer preemption level flash-override Dialer Profiles Example interface Dialer10 ip address 192.168.254.1 255.255.255.0 dialer pool 1 dialer remote-name is2811 dialer string 4081234 class test dialer-group 1 map-class dialer test dialer trunkgroup 1 dialer preemption level flash-override Disabling TDM Hairpinning on the Voice Card Use the following procedure to disable TDM hairpinning on the voice card. SUMMARY STEPS 1. enable 2. configure terminal 3. voice-card slot 4. no local-bypass DETAILED STEPS PurposeCommand or Action Enables privileged EXEC mode.enableStep 1 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 152 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers Configuring MLPP Call Preemption over Outgoing Voice Calls
- 165. PurposeCommand or Action Example: Router>enable • Enter your password if prompted. Enters global configuration mode.configure terminal Example: Router# configure terminal Step 2 Enters voice-card configuration mode to configure a voice card.voice-card slotStep 3 Example: Router(config)# voice-card 1 • slot --Slot number for the card to be configured. Valid entries vary by router platform; enter the show voice port summary command for available values. Note Disables TDM hairpinning.no local-bypass Example: Router(config-voicecard)# no local-bypass Step 4 Configuring the POTS Dial Peer for Outgoing Voice Calls Use the following procedure to set the preemption level for outgoing voice calls on a POTS dial peer. SUMMARY STEPS 1. enable 2. configure terminal 3. dial-peer voice tag pots 4. trunkgroup name [preference-number] 5. preemption level {flash-override | fla s h| immediate| priority| routine} DETAILED STEPS PurposeCommand or Action Enables privileged EXEC mode.enableStep 1 Example: Router> enable • Enter your password if prompted. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 153 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers Configuring MLPP Call Preemption over Outgoing Voice Calls
- 166. PurposeCommand or Action Entersglobal configuration mode.configure terminal Example: Router# configure terminal Step 2 Defines a particular dial peer, specifies the method of voice encapsulation, and enters dial-peer configuration mode. dial-peer voice tag pots Example: Router(config)# dial-peer voice 25 pots Step 3 • tag --Digits that define a particular dial peer. The range is from 1 to 2147483647. • pots --Indicates that this is a POTS peer that uses VoIP encapsulation on the IP backbone. Defines the trunk group associated with this dial peer.trunkgroup name [preference-number]Step 4 Example: Router(config-dial-peer)# trunkgroup 1 • name --Label of the trunk group to use for the call. Valid trunk group names contain a maximum of 63 alphanumeric characters. • preference-number --Preference or priority of the trunk group. Range is from 1 (highest priority) to 64 (lowest priority). Sets the preemption level of the selected outbound dial peer. Voice calls can be preempted by a DDR call with a higher preemption level. The default is routine. preemption level {flash-override | fla s h| immediate| priority| routine} Example: Router(config-dial-peer)# preemption level flash Step 5 • flash-override --Level 0 (highest) • flash --Level 1 • immediate --Level 2 • priority --Level 3 • routine --Level 4 (lowest) The preemption level flash-override setting can prevent the call to be preempted by a DDR call. Note Troubleshooting Tips for Integrated Data and Voice Services Use the following commands to troubleshoot integrated data and voice for ISDN interfaces: • debug dialer events --Used to display debugging information about the packets received on a dialer interface. • debug isdn q931 --Used to check outgoing dial-peer matching for an ISDN incoming call. Enable this command on both sides of the call. The output indicates whether the messages are generated by the calling party router (indicated by TX ->) or by the called party router (indicated by RX <-). ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 154 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers Troubleshooting Tips for Integrated Data and Voice Services
- 167. • debug tgrminout --Used to check voice or DDR channel selection request and return status. From the output, you can determine what type of call enabled the preemption and which timeslot is selected from which trunkgroup. • debug voip ccapi individual 146 --Used to troubleshoot the call control application programming interface (CCAPI) contents. The individual 146 command option is used to log call preemption indication information. • debug voip ccapi inout --Used to show how a call flows through the system. From the output, you can see the call setup and teardown operations performed on both the telephony and network call legs. • show call history voice | i Cause --Used to gather DisconnectCause information from the show call history voice command line display. • show isdn active and show isdn status--Used to show the active data and voice calls. • show trunk group --Used to check the preemption active or pending calls counter for MLPP preemption calls. The output shows the number of active channels from the trunkgroup and the current preemption levels. If a data call with a higher priority initiates the preemption of voice call, it is shown as pending against the higher priority preemption level. ConfigurationExamplesforIntegratedDataandVoiceServices for ISDN PRI Interfaces MLPP DDR Backup Call Preemption over Voice Call Example The following example shows that preemption is enabled on the trunk group, the trunk group is associated with a map class, and the preemption level is set on the dialer interface. Router# show running-config Building configuration... Current configuration : 5984 bytes ! version 12.3 service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption ! hostname Router ! boot-start-marker boot-end-marker ! card type e1 0 3 no logging buffered ! no aaa new-model ! resource manager ! network-clock-participate slot 1 network-clock-participate wic 3 ip subnet-zero ! ! ip cef no ip dhcp use vrf connected ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 155 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers Configuration Examples for Integrated Data and Voice Services for ISDN PRI Interfaces
- 168. ! ip dhcp poolITS network 10.0.0.0 255.255.0.0 option 150 ip 10.0.0.1 default-router 10.0.0.1 ! ! no ip domain lookup ip name-server 192.168.2.87 ftp-server enable no ftp-server write-enable ftp-server topdir flash:/ isdn switch-type primary-ntt ! ! trunk group 1 max-calls data 10 direction out preemption enable preemption tone 4! voice-card 0 dspfarm no local-bypass ! voice-card 1 dspfarm no local-bypass ! ! voice call send-alert ! ! ! controller E1 0/3/0 clock source internal pri-group timeslots 1-5,16 trunk-group 1 timeslots 1-5 ! controller E1 0/3/1 clock source internal pri-group timeslots 1-2,16 trunk-group 1 timeslots 1-2 ! controller E1 1/0/0 clock source internal pri-group timeslots 1-31 trunk-group 1 timeslots 1-31 ! controller E1 1/0/1 clock source internal pri-group timeslots 1-10,16 trunk-group 1 timeslots 1-10 ! ! ! interface Loopback0 ip address 10.10.1.1 255.255.255.255 ! interface GigabitEthernet0/0 ip address 10.3.202.87 255.255.0.0 no ip proxy-arp duplex auto speed auto ! interface GigabitEthernet0/1 ip address 10.0.0.2 255.255.0.0 shutdown duplex auto speed auto ! interface FastEthernet0/1/0 switchport access vlan 2 no ip address load-interval 30 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 156 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers MLPP DDR Backup Call Preemption over Voice Call Example
- 169. duplex full speed 100 ! interfaceFastEthernet0/1/1 no ip address ! interface FastEthernet0/1/2 no ip address ! interface FastEthernet0/1/3 no ip address ! interface FastEthernet0/1/4 no ip address ! interface FastEthernet0/1/5 no ip address ! interface FastEthernet0/1/6 no ip address ! interface FastEthernet0/1/7 no ip address ! interface FastEthernet0/1/8 no ip address ! interface Serial0/2/0 no ip address encapsulation frame-relay load-interval 30 shutdown no keepalive clockrate 2000000 ! interface Serial0/2/0.1 point-to-point ip address 10.3.3.1 255.255.255.0 frame-relay interface-dlci 100 ! interface Serial0/2/1 no ip address shutdown clockrate 2000000 ! interface Serial0/3/0:15 no ip address dialer pool-member 1 isdn switch-type primary-ntt isdn protocol-emulate network isdn T310 15000 isdn bchan-number-order descending isdn integrate calltype all no cdp enable ! interface Serial0/3/1:15 no ip address dialer pool-member 1 isdn switch-type primary-ntt isdn protocol-emulate network isdn T310 15000 isdn bchan-number-order descending isdn integrate calltype all no cdp enable ! interface Serial1/0/0:15 no ip address dialer pool-member 1 isdn switch-type primary-dms100 isdn protocol-emulate network isdn T310 15000 isdn bchan-number-order descending isdn integrate calltype all no cdp enable ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 157 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers MLPP DDR Backup Call Preemption over Voice Call Example
- 170. ! interface Serial1/0/1:15 no ipaddress encapsulation ppp dialer pool-member 1 isdn switch-type primary-ntt isdn protocol-emulate network isdn T310 15000 isdn bchan-number-order descending isdn integrate calltype all ppp multilink ! interface Vlan1 ip address 10.0.0.1 255.255.0.0 load-interval 30 ! interface Vlan2 ip address 10.7.7.7 255.255.0.0 ! interface Dialer0 ip address 10.5.5.5 255.0.0.0 encapsulation ppp load-interval 30 dialer pool 1 dialer remote-name Router dialer string 4081234 class test dialer load-threshold 10 outbound dialer-group 1 ppp multilink ppp multilink load-threshold 5 outbound ! interface Dialer1 ip address 192.168.253.1 255.255.255.0 dialer pool 1 dialer string 4085678 class test dialer-group 1 ! interface Dialer2 ip address 192.168.252.1 255.255.255.0 dialer pool 1 dialer string 4087777 class test dialer-group 1 ! ip default-gateway 5.5.5.6 ip classless ip route 172.16.254.254 255.255.255.255 10.3.0.1 ! ip http server ! ! map-class dialer test dialer trunkgroup 1 dialer preemption level flash dialer-list 1 protocol ip permit snmp-server community public RO snmp-server enable traps tty ! ! ! control-plane ! ! ! voice-port 0/3/0:15 echo-cancel enable type hardware ! voice-port 0/3/1:15 echo-cancel enable type hardware ! voice-port 1/0/0:15 compand-type u-law ! voice-port 1/0/1:15 ! voice-port 2/0/0 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 158 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers MLPP DDR Backup Call Preemption over Voice Call Example
- 171. shutdown ! voice-port 2/0/1 ! voice-port 2/0/2 ! voice-port2/0/3 ! voice-port 2/0/4 ! voice-port 2/0/5 ! voice-port 2/0/6 ! voice-port 2/0/7 ! ! ! ! ! ! dial-peer voice 100 pots destination-pattern 1... port 2/0/1 forward-digits all ! dial-peer voice 2001 pots trunkgroup 1 destination-pattern 2... forward-digits all ! dial-peer voice 3001 pots trunkgroup 1 destination-pattern 3... forward-digits all ! dial-peer voice 300 pots destination-pattern 4... port 2/0/2 forward-digits all ! dial-peer voice 10 pots incoming called-number . direct-inward-dial forward-digits 0 ! dial-peer voice 5001 pots trunkgroup 1 destination-pattern 5... forward-digits all ! dial-peer voice 500 pots destination-pattern 6... port 2/0/3 forward-digits all ! dial-peer voice 800 pots trunkgroup 1 destination-pattern 8... forward-digits all ! dial-peer data 50 pots incoming called-number 650T ! ! ! telephony-service load 7960-7940 P00303020214 max-ephones 5 max-dn 5 ip source-address 10.0.0.1 port 2000 create cnf-files version-stamp Jan 01 2002 00:00:00 max-conferences 8 gain -6 transfer-system full-consult transfer-pattern .T ! ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 159 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers MLPP DDR Backup Call Preemption over Voice Call Example
- 172. ! ephone-dn 1 dual-line number7000 ! ! ephone-dn 2 number 7002 ! ! ephone-dn 3 number 1003 ! ! ephone-dn 4 number 1004 ! ! ephone 1 mac-address 0030.94C2.6073 type 7960 button 1:1 ! ! ! ephone 2 mac-address 000C.851C.ED81 type 7960 button 1:2 ! ! ! ephone 3 ! ! ! ephone 4 ! ! alias exec c conf t alias exec s sh run ! line con 0 exec-timeout 0 0 privilege level 15 line aux 0 line vty 0 4 login ! scheduler allocate 20000 1000 ! end Legacy DDR (Dialer Map) Example The following example shows how to associate the class parameter for legacy DDR. Router# show running-config Building configuration... Current configuration : 1358 bytes ! version 12.3 service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption ! hostname host2 ! boot-start-marker boot-end-marker ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 160 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers Legacy DDR (Dialer Map) Example
- 173. ! card type t11 ! username client password 0 lab memory-size iomem 10 no network-clock-participate aim 0 no network-clock-participate aim 1 no aaa new-model ip subnet-zero ! ip cef ! ip ips po max-events 100 no ftp-server write-enable isdn switch-type primary-ni ! controller T1 1/0 framing esf linecode b8zs cablelength long 0db pri-group timeslots 1-24 ! controller T1 1/1 framing sf linecode ami cablelength long 0db ! interface FastEthernet0/0 ip address 10.10.193.77 255.255.0.0 duplex auto speed auto ! interface FastEthernet0/1 ip address 192.168.10.1 255.255.255.0 shutdown duplex auto speed auto ! interface Serial1/0:23 ip address 192.168.254.2 255.255.255.0 encapsulation ppp dialer map ip 172.22.82.2 name gw3845 class dial1 20009 dialer-group 2 isdn switch-type primary-ni ppp authentication chap ! no ip classless ip route 10.10.1.0 255.255.255.0 192.168.254.1 ip route 172.16.254.0 255.255.255.0 10.10.0.1 ! ip http server no ip http secure-server ! dialer-list 2 protocol ip permit ! control-plane ! line con 0 line aux 0 line vty 0 4 login ! scheduler allocate 20000 1000 ! end ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 161 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers Legacy DDR (Dialer Map) Example
- 174. Dialer Profiles Example Thefollowing example shows how to associate the class parameter for dialer profiles. Router# show running-config Building configuration... Current configuration : 1689 bytes ! version 12.3 service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption ! hostname host3 ! boot-start-marker boot-end-marker ! card type t1 1 no logging console ! username uut password 0 lab no network-clock-participate aim 0 no network-clock-participate aim 1 no aaa new-model ip subnet-zero ! ip cef ! ip ips po max-events 100 no ftp-server write-enable isdn switch-type primary-ni ! controller T1 1/0 framing esf linecode b8zs cablelength long 0db pri-group timeslots 1-24 ! controller T1 1/1 framing sf linecode ami cablelength long 0db ! no crypto isakmp enable ! interface FastEthernet0/0 ip address 10.10.193.88 255.255.0.0 duplex auto speed auto ! interface FastEthernet0/1 ip address 10.10.1.1 255.255.255.0 duplex auto speed auto ! interface Serial0/3/0 no ip address clockrate 2000000 ! interface Serial0/3/1 no ip address clockrate 2000000 ! interface Serial1/0:23 no ip address encapsulation ppp dialer pool-member 1 isdn switch-type primary-ni ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 162 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers Dialer Profiles Example
- 175. isdn protocol-emulate network isdnT310 30000 isdn bchan-number-order descending ppp authentication chap ! i interface Dialer2 ip address 192.168.252.1 255.255.255.0 dialer pool 1 dialer string 4087777 class test dialer-group 1 ! ip default-gateway 5.5.5.6 ip classless ip route 172.16.254.254 255.255.255.255 10.3.0.1 ! ip http server ! ! map-class dialer test dialer trunkgroup 1 dialer preemption level flash dialer-list 1 protocol ip permit snmp-server community public RO snmp-server enable traps tty ! dialer-list 1 protocol ip permit ! control-plane ! line con 0 exec-timeout 0 0 line aux 0 line vty 0 4 login ! scheduler allocate 20000 8000 end Maximum Number of Data and Voice Calls on the Dial-Out Trunk Group Example The following sample configuration shows a maximum number of 500 data and voice calls configured on the trunk group, includes all B channels in the trunk group, and associates dialer test with the trunk group. Router# show running-config Building configuration... Current configuration : 2283 bytes ! version 12.3 service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption ! hostname host4 ! boot-start-marker boot-end-marker ! card type t1 1 1 no logging console ! no aaa new-model ! resource manager ! no network-clock-participate slot 1 ip subnet-zero ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 163 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers Maximum Number of Data and Voice Calls on the Dial-Out Trunk Group Example
- 176. ! ip cef ! no ftp-serverwrite-enable isdn switch-type primary-ni ! trunk group 1 max-calls any 500 ! voice-card 0 dspfarm ! voice-card 1 dspfarm ! controller T1 1/0 framing esf linecode b8zs ! controller T1 1/0/0 framing esf linecode b8zs pri-group timeslots 1-12,24 ! controller T1 1/0/1 framing esf linecode b8zs ! interface GigabitEthernet0/0 ip address 10.10.212.212 255.255.0.0 duplex auto speed auto ! interface GigabitEthernet0/1 no ip address duplex auto speed auto ! interface Serial1/0/0:23 no ip address dialer pool-member 1 isdn switch-type primary-ni isdn protocol-emulate network isdn T310 30000 isdn bchan-number-order descending isdn integrate calltype all trunk-group 1 1 no cdp enable ! interface Dialer0 ip address 192.168.254.1 255.255.255.0 dialer pool 1 dialer string 4081234 class test dialer-group 1 ! interface Dialer1 ip address 192.168.253.1 255.255.255.0 dialer pool 1 dialer string 4085678 class test dialer-group 1 ! interface Dialer2 ip address 192.168.252.1 255.255.255.0 dialer pool 1 dialer string 4087777 class test dialer-group 1 ! ip classless ip route 192.168.10.0 255.255.255.0 Dialer0 ip route 192.168.11.0 255.255.255.0 Dialer1 ip route 192.168.12.0 255.255.255.0 Dialer2 ip route 172.16.254.254 255.255.255.255 GigabitEthernet0/0 ! ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 164 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers Maximum Number of Data and Voice Calls on the Dial-Out Trunk Group Example
- 177. ip http server ! map-classdialer test dialer trunkgroup 1 dialer-list 1 protocol ip permit ! control-plane ! voice-port 1/0/0:23 ! voice-port 2/0/0 ! voice-port 2/0/1 ! voice-port 2/0/2 ! voice-port 2/0/3 ! voice-port 2/0/4 ! voice-port 2/0/5 ! voice-port 2/0/6 ! voice-port 2/0/7 ! dial-peer voice 100 pots destination-pattern 1001 port 2/0/0 forward-digits all ! dial-peer voice 2001 pots destination-pattern 200. port 1/0/0:23 forward-digits all ! dial-peer voice 101 pots destination-pattern 1002 port 2/0/1 ! line con 0 exec-timeout 0 0 line aux 0 line vty 0 4 login ! scheduler allocate 20000 1000 ! end Dial-Peer Configuration Example Data dial peers enable the configuration and order assignment of dial peers so that the gateway can identify incoming calls as voice or data. The incoming called number specifies the number associated with the data dial peer. The following example shows a configuration for the voice and data dial-peers and incoming called number. Router# show running-config Building configuration... Current configuration : 1978 bytes ! version 12.3 service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption ! hostname host6 ! ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 165 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers Dial-Peer Configuration Example
- 178. boot-start-marker boot-end-marker ! no aaa new-model ! resourcemanager ! no network-clock-participate slot 1 ip subnet-zero ! ip cef ! no ftp-server write-enable isdn switch-type primary-ni ! trunk group 1 max-calls any 2 ! voice-card 0 dspfarm ! voice-card 1 dspfarm ! controller T1 1/1/0 framing esf linecode b8zs pri-group timeslots 1-12,24 trunk-group 1 timeslots 2 ! controller T1 1/1/1 framing esf linecode b8zs ! interface FastEthernet0/0 ip address 10.10.193.90 255.255.0.0 duplex half speed 10 ! interface FastEthernet0/1 no ip address shutdown duplex auto speed auto ! interface FastEthernet0/1/0 no ip address shutdown ! interface FastEthernet0/1/1 no ip address shutdown ! interface FastEthernet0/1/2 no ip address shutdown ! interface FastEthernet0/1/3 no ip address shutdown ! interface Serial1/1/0:23 no ip address dialer pool-member 2 isdn switch-type primary-ni isdn integrate calltype all no cdp enable ! interface Vlan1 no ip address ! interface Dialer0 ip address 192.168.254.2 255.255.255.0 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 166 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers Dial-Peer Configuration Example
- 179. dialer pool 2 dialerstring 6501234 dialer-group 2 ! ip classless ip route 10.10.1.0 255.255.255.0 Dialer0 ip route 172.16.254.0 255.255.255.0 10.10.0.1 ! ip http server ! dialer-list 2 protocol ip permit ! control-plane ! voice-port 0/2/0 ! voice-port 0/2/1 ! voice-port 0/2/2 ! voice-port 0/2/3 ! voice-port 1/1/0:23 ! dial-peer voice 100 pots destination-pattern 2001 port 0/2/0 forward-digits all ! dial-peer voice 10 pots incoming called-number . direct-inward-dial port 1/1/0:23 ! dial-peer data 50 pots incoming called-number 408T ! dial-peer voice 101 pots destination-pattern 2002 port 0/2/1 forward-digits all ! line con 0 exec-timeout 0 0 line aux 0 line vty 0 4 login ! scheduler allocate 20000 1000 ! end Disconnect Cause Example This example shows the DisconnectCause information for a preemption call. Router# show call history voice Telephony call-legs: 2 SIP call-legs: 0 H323 call-legs: 0 Call agent controlled call-legs: 0 Total call-legs: 2 GENERIC: SetupTime=281680 ms Index=1 PeerAddress=7002 PeerSubAddress= PeerId=20002 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 167 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers Disconnect Cause Example
- 180. PeerIfIndex=161 LogicalIfIndex=160 DisconnectCause=8 DisconnectText=preemption (8) ConnectTime=286160 ms DisconnectTime=441190ms CallDuration=00:02:35 sec CallOrigin=2 ReleaseSource=7 InternalErrorCode=1.1.8.11.35.0 ChargedUnits=0 InfoType=speech TransmitPackets=0 TransmitBytes=0 ReceivePackets=6910 ReceiveBytes=1105600 TELE: ConnectionId=[0x4E9D9EF1 0x23E411DA 0x8002A31F 0xB25BECEF] IncomingConnectionId=[0x4E9D9EF1 0x23E411DA 0x8002A31F 0xB25BECEF] CallID=1 TxDuration=0 ms VoiceTxDuration=0 ms FaxTxDuration=0 ms CoderTypeRate=g711ulaw NoiseLevel=0 ACOMLevel=0 SessionTarget= ImgPages=0 CallerName= CallerIDBlocked=False OriginalCallingNumber=7002 OriginalCallingOctet=0x0 OriginalCalledNumber= OriginalCalledOctet=0x80 OriginalRedirectCalledNumber= OriginalRedirectCalledOctet=0x0 TranslatedCallingNumber=7002 TranslatedCallingOctet=0x0 TranslatedCalledNumber= TranslatedCalledOctet=0x80 TranslatedRedirectCalledNumber= TranslatedRedirectCalledOctet=0x0 GwCollectedCalledNumber=2000 GwReceivedCallingNumber=7002 GwReceivedCallingOctet3=0x0 GwReceivedCallingOctet3a=0x0 GENERIC: SetupTime=282800 ms Index=2 PeerAddress=2000 PeerSubAddress= PeerId=2001 PeerIfIndex=144 LogicalIfIndex=42 DisconnectCause=8 DisconnectText=preemption (8) ConnectTime=286160 ms DisconnectTime=441210 ms CallDuration=00:02:35 sec CallOrigin=1 ReleaseSource=7 InternalErrorCode=1.1.8.11.35.0 ChargedUnits=0 InfoType=speech TransmitPackets=6910 TransmitBytes=1160880 ReceivePackets=6917 ReceiveBytes=1106720 TELE: ConnectionId=[0x4E9D9EF1 0x23E411DA 0x8002A31F 0xB25BECEF] IncomingConnectionId=[0x4E9D9EF1 0x23E411DA 0x8002A31F 0xB25BECEF] CallID=2 TxDuration=0 ms VoiceTxDuration=0 ms ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 168 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers Disconnect Cause Example
- 181. FaxTxDuration=0 ms CoderTypeRate=g711ulaw NoiseLevel=-41 ACOMLevel=26 SessionTarget= ImgPages=0 CallerName= CallerIDBlocked=False AlertTimepoint=282820 ms Targettg label=1 OriginalCallingNumber=7002 OriginalCallingOctet=0x0 OriginalCalledNumber= OriginalCalledOctet=0x80 OriginalRedirectCalledNumber= OriginalRedirectCalledOctet=0x0 TranslatedCallingNumber=7002 TranslatedCallingOctet=0x0 TranslatedCalledNumber=2000 TranslatedCalledOctet=0x80 TranslatedRedirectCalledNumber= TranslatedRedirectCalledOctet=0x0 GwCollectedCalledNumber=2000 GwOutpulsedCalledNumber=2000 GwOutpulsedCalledOctet3=0x80 GwReceivedCallingNumber=7002 GwReceivedCallingOctet3=0x0 GwReceivedCallingOctet3a=0x0 GwOutpulsedCallingNumber=7002 GwOutpulsedCallingOctet3=0x0 GwOutpulsedCallingOctet3a=0x0 DSPIdentifier=0/1:1 Additional References The following sections provide references related to configuring integrated data and voice for ISDN interfaces. Related Documents Document TitleRelated Topic Cisco IOS Voice Configuration LibraryCisco IOS Voice Configuration Library, including library preface and glossary, other feature documents, and troubleshooting documentation. Cisco IOS Voice Command ReferenceVoice command reference Cisco IOS ISDN Voice Configuration GuideCisco IOS ISDN voice technologies • Cisco IOS Dial Configuration Guide • Cisco IOS Dial Technologies Command Reference Cisco dial technologies Configuring Network Side ISDN PRI Signaling, Trunking, and Switching ISDN PRI configuration information Multilevel Precedence and PreemptionMultilevel precedence and preemption (MLPP) information ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 169 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers Additional References
- 182. Document TitleRelated Topic ConfiguringISDN PRI Voice-Interface SupportISDN voice interface information. Standards TitleStandard No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature. MIBs MIBs LinkMIB To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL: http://www.cisco.com/go/mibs • CISCO-VOICE-COMMON-DIAL-CONTROL-MIB • CISCO-VOICE-DIAL-CONTROL-MIB RFCs TitleRFC --No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature. Technical Assistance LinkDescription http://www.cisco.com/techsupportThe Cisco Technical Support website contains thousands of pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 170 Integrated Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers Additional References
- 183. C H AP T E R 7 Integrated Voice and Data WAN on T1 E1 Interfaces This chapter describes how to implement the Integrated Voice and Data WAN on T1/E1 Interfaces with the AIM-ATM-VOICE-30 Module feature. This card provides a voice-processing termination solution at a density of 30 VoIP or VoFR voice or fax channels, while not consuming a network-module slot. It provides the following benefits: • Integrated voice and serial data WAN functionality on the same T1/E1 interface or on the second port of the voice/WAN interface cards (VWIC) • Support for high-complexity codecs The serial interface supports the following features: • Point-to-Point Protocol (PPP), Frame Relay (FR), and high-level data link control (HDLC) encapsulations--Up to 120 channels • FR, HDLC, and PPP encapsulation and voice on the same T1/E1 voice interface available in the following two options: • Channel associated signaling (CAS) or Primary Rate Interface (PRI) group, plus the channel group are defined on the same T1/E1 interface in the Cisco 2600 WIC slot. • The DS0 or PRI, plus the channel groups are configured across two ports of the same T1/E1 VWIC. For example, you can configure a DS0 group or a PRI group on port 0, and a channel group on the same port or another port. • HDLC data inversion--Meets the density requirement for T1 links • Compression support--Software and hardware compression is supported on the Cisco 3660, Cisco 3725, and Cisco 3745 There is only one advanced integration module (AIM) slot on Cisco 2600 platforms, so hardware compression is not applicable to the Cisco 2600 series. Note • Multilink PPP ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 171
- 184. • G.703 (E1unframed mode) Feature History for Integrated Voice and Data WAN on T1/E1 Interfaces with the AIM-ATM-VOICE-30 Module ModificationRelease This feature was introduced.12.2(15)T • Finding Feature Information, page 172 • Prerequisites for Configuring Integrated Voice and Data WAN on T1 E1 Interfaces Using the AIM-ATM-VOICE-30 Module, page 172 • Restrictions for Configuring Integrated Voice and Data WAN on T1 E1 Interfaces Using the AIM-ATM-VOICE-30 Module, page 173 • Information About Integrated Voice and Data WAN on T1 E1 Interfaces Using the AIM-ATM-VOICE-30 Module, page 174 • How to Configure Integrated Voice and Data WAN on T1 E1 Interfaces Using the AIM-ATM-VOICE-30 Module, page 177 • Configuration Examples for Integrated Voice and Data WAN on T1 E1 Interfaces Using the AIM-ATM-VOICE-30 Module, page 190 • Additional References, page 194 Finding Feature Information Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required. Prerequisites for Configuring Integrated Voice and Data WAN on T1 E1 Interfaces Using the AIM-ATM-VOICE-30 Module • Perform the prerequisites that are listed in the "Prerequisites for Configuring an ISDN Voice Interface" section. Cisco 2600 series and Cisco 2600XM • Ensure that you have the following: • 64-MB RAM and 32-MB flash memory ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 172 Integrated Voice and Data WAN on T1 E1 Interfaces Finding Feature Information
- 185. • Appropriate voice-interfacehardware, as listed in AIM-ATM, AIM-VOICE-30, and AIM-ATM-VOICE-30 on the Cisco 2600 Series and Cisco 3660 Cisco 3660, Cisco 3725, and Cisco 3745 • Ensure that you have the following: • Cisco IOS Release 12.2(15)T IP Plus or a later release • 128-MB RAM and 32-MB flash memory • Multiservice interchange (MIX) module (MIX-3660-64) installed in the time-division multiplexing (TDM) slot on the motherboard on the Cisco 3660 only • Appropriate voice-interface hardware, as listed in AIM-ATM, AIM-VOICE-30, and AIM-ATM-VOICE-30 on the Cisco 2600 Series and Cisco 3660 Restrictions for Configuring Integrated Voice and Data WAN on T1 E1 Interfaces Using the AIM-ATM-VOICE-30 Module Restrictions are described in the Restrictions for Configuring ISDN Voice Interfaces section. In addition, the following apply. Cisco 2600 Series Restrictions • This feature does not support Drop and Insert. • Voice channels can appear only on a single port of the two T1/E1 interfaces on the VWIC. Data channels can appear on both. Other Platform Restrictions • This feature is not supported on the following platforms: Cisco 1700 series, Cisco MC3810, and Cisco AS5x00. Hardware Restrictions • This feature is not supported on the AIM-VOICE-30 card or the AIM-ATM card. • Modem relay is not supported on AIM-ATM-VOICE-30 DSPs. • Codec GSM-EFR is not supported. • With a high-complexity image set, an AIM-ATM-VOICE-30 DSP card can process up to only 16 voice channels. The 16 associated time slots must be within a contiguous range. Applications and voice interfaces that can be used with the three types of AIM are listed in AIM-ATM, AIM-VOICE-30, and AIM-ATM-VOICE-30 on the Cisco 2600 Series and Cisco 3660. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 173 Integrated Voice and Data WAN on T1 E1 Interfaces Restrictions for Configuring Integrated Voice and Data WAN on T1 E1 Interfaces Using the AIM-ATM-VOICE-30 Module
- 186. Information About IntegratedVoice and Data WAN on T1 E1 Interfaces Using the AIM-ATM-VOICE-30 Module General information about ISDN voice interfaces is presented in the "Information About ISDN Voice Interfaces" section. Note AIM-ATM-VOICE-30 Module The AIM-ATM-VOICE-30 module is an advanced integration module capable of supporting up to 30 voice or fax channels when used in a supported platform with one of the T1/E1 voice/WAN interface cards (such as VWIC-1T1). The module includes DSPs that are used for a number of voice-processing tasks such as voice compression and decompression, voice-activity detection or silence suppression, and PBX or PSTN signaling protocols. The module supports VoIP, VoFR, and VoIP over ATM (VoATM) while leaving the router network-module slot open for other functions such as asynchronous or synchronous serial concentration. For additional information, see AIM-ATM, AIM-VOICE-30, and AIM-ATM-VOICE-30 on the Cisco 2600 Series and Cisco 3660 . Integrated Voice and Data WAN This feature adds integrated voice and serial-data WAN service on the same T1 or E1 interface or VWIC on AIM-ATM-VOICE-30 DSP cards. This enhancement enables you to use some DS0 channels for serial-data Frame Relay, high-level data link control (HDLC), and Point-to-Point Protocol (PPP), for example, while the remaining T1 or E1channels can be used for voice channel-associated signaling (CAS) or PRI. The figure below shows a typical application scenario in which 16 channels of a T1 line are used for voice and 4 channels are used for Frame relay data. Integrating voice and serial data on the same T1 or E1 line ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 174 Integrated Voice and Data WAN on T1 E1 Interfaces Information About Integrated Voice and Data WAN on T1 E1 Interfaces Using the AIM-ATM-VOICE-30 Module
- 187. minimizes the recurringcost of providing PSTN and data WAN access. In particular, integrated access provides a number of voice DS0s (for PSTN access) and a Frame Relay link on the same T1. Figure 6: Typical Application Scenario The figure below shows a typical deployment scenario in which port 0 of the VWIC-MFT module is connected to an integrated voice and data service provider with 20 channels. These 20 channels are used for voice (running CAS or PRI); the remaining four channels are used for serial data (running Frame Relay). Using this type of configuration, you can take advantage of the integrated service offered by a service provider and minimize the cost of leasing and supporting T1 or E1 lines. Figure 7: Typical Feature Deployment ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 175 Integrated Voice and Data WAN on T1 E1 Interfaces Integrated Voice and Data WAN
- 188. High-Complexity Voice Compression Thisfeature adds high-complexity G.723, G.728, and GSM-FR codec support to the AIM-ATM-VOICE-30 module so that the DSP can support both medium- and high-complexity codecs running separately. Each DSP core can process up to two voice channels, so each module can support up to 16 voice channels when running a high-complexity DSP firmware image. The following high-complexity codecs are supported: • G.723.1 5.3K • G.723.1 6.3K • G.723 1A 5.3K • G.723 1A 6.3K • G.728 • G.729 • G.729B • GSM-FR The following medium-complexity codecs are supported in high-complexity mode: • G.711 mu-law • G.711 a-law • G.726 • G.729A • G.729 AB • Clear-channel codec • Fax relay Neither modem-relay nor GSM-EFR is supported.Note Network Clock Source and Participation Packet voice and video are sensitive to time delays. To prevent mismatches and data slips, you must synchronize data flows to a single clock source, known as the network clock . When a network clock is configured on a gateway, the router is externally clocked by one T1 or E1 port and passes that clock signal across the backplane to another T1 or E1 port on another WIC or network module slot. Use of a network clock on a gateway is configured by naming the network modules and interface cards that are participating in network clocking, and then selecting a port to act as the source of timing for the network clock. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 176 Integrated Voice and Data WAN on T1 E1 Interfaces High-Complexity Voice Compression
- 189. You must configurenetwork clock source and participation to use the Integrated Voice and Data WAN on T1/E1 Interfaces Using the AIM-ATM-VOICE-30 Module feature. Note The network clock provides timing from the source, through the port to the AIM, and then out to all participating router slots. The number of supported AIM slots is as follows: • The Cisco 2600 series and Cisco 2600XM support one internal AIM slot. • The Cisco 3660, Cisco 3725, and Cisco 3745 support two internal AIM slots. The network clock source must be derived from an external source--for example, PSTN, PBX, or ATM network. For digital voice ports, the clock source command in configures the type of timing (internal or from the line) for each port that you designate as a primary source or backup for the network clock. This command allows maximum flexibility. For example, on a router with a multiflex trunk VWIC connected to an ATM network and a digital T1/E1 packet voice trunk network module connected to a PBX, you can set up network clocking in any of three ways: • The multiflex trunk VWIC provides clocking to the AIM, which provides it to the digital T1/E1 packet voice trunk network module (that is, to the PBX). • The digital T1/E1 packet voice trunk network module provides clocking to the AIM, which provides it to the multiflex trunk VWIC. • The ATM network and the PBX run their own clocks, which are not necessarily synchronized. However, this scenario could result in poor voice quality. For a detailed discussion of clock sources on individual ports, see the information about clock sources on digital T1/E1 voice ports in the chapter on configuring voice ports in the Cisco IOS Voice, Video, and Fax Configuration Guide. Note How to Configure Integrated Voice and Data WAN on T1 E1 Interfaces Using the AIM-ATM-VOICE-30 Module For detailed configuration tasks for the AIM-ATM, AIM-VOICE-30, see AIM-ATM, AIM-VOICE-30, and AIM-ATM-VOICE-30 on the Cisco 2600 Series and Cisco 3660 . Note Configuring Network Clock Source and Participation Configuring Clock Source Internal To configure a clock with an internal source, perform the following steps. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 177 Integrated Voice and Data WAN on T1 E1 Interfaces How to Configure Integrated Voice and Data WAN on T1 E1 Interfaces Using the AIM-ATM-VOICE-30 Module
- 190. You must configurenetwork clock source and participation to use the Integrated Voice and Data WAN on T1/E1 Interfaces Using the AIM-ATM-VOICE-30 Module feature. Note Before You Begin Configure the controller for PRI or DS0 groups and for ATM AIM or CAS before configuring network-clock participation parameters. SUMMARY STEPS 1. enable 2. configure terminal 3. controller {t1 | e1} slot/port 4. clock source {line [primary] | internal} 5. mode atm [aim aim-slot-number] 6. exit 7. network-clock-participate [slot slot-number | wic wic-slot | aim aim-slot-number] 8. exit DETAILED STEPS PurposeCommand or Action Enters privileged EXEC mode. Enter your password when prompted.enable Example: Router> enable Step 1 Enters configuration mode.configure terminal Example: Router# configure terminal Step 2 Enters controller configuration mode on the T1 or E1 controller on the selected slot/port. controller {t1 | e1} slot/port Example: Router(config)# controller t1 1/0 Step 3 Specifies the source from which the phase-locked loop (PLL) on this port derives its clocking and, if the source is line, whether this port is the primary source. Arguments and keywords are as follows: clock source {line [primary] | internal} Example: Router(config-controller)# clock source internal Step 4 • line --Clock recovered from the line’s receive data stream. This is the default. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 178 Integrated Voice and Data WAN on T1 E1 Interfaces Configuring Network Clock Source and Participation
- 191. PurposeCommand or Action •primary --External source to which the port is connected. This option also puts a second port, which is generally connected to the PBX, into looped-time mode. Both ports are configured with line, but only the port connected to the external source is configured with primary. • internal --T1 or E1 controller internal PLL. With the default, the clock source does not appear in the show running-config command output. Use the show controllers command to display the current source for a port. Note Specifies that the configuration on this controller is for ATM, using the AIM in the specified slot for ATM processing, and creates ATM interface mode atm [aim aim-slot-number] Example: Router(config-controller)# mode atm aim 0 Step 5 0. Use when you connect the T1 line to an ATM network. The argument is as follows: • aim-slot-number --AIM slot number on the router chassis: • Cisco 2600 series: 0 • Cisco 3660 and Cisco 3700 series: 0 or 1 This command without the aim keyword uses software rather than the AIM to perform ATM SAR. This is supported on Cisco 2600 series WIC slots only and not on network module slots. Note Exits the current mode.exit Example: Router(config-controller)# exit Step 6 Allows the network module or VWIC in the specified slot to use the network clock for its timing. Keywords depend on platform. network-clock-participate [slot slot-number | wic wic-slot | aim aim-slot-number] Step 7 Example: Router(config)# network-clock-participate slot 5 Example: Router(config)# network-clock-participate wic 0 Example: Router(config)# network-clock-participate aim 0 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 179 Integrated Voice and Data WAN on T1 E1 Interfaces Configuring Network Clock Source and Participation
- 192. PurposeCommand or Action Exitsthe current mode.exit Example: Router(config)# exit Step 8 Configuring the Clock-Source Line To configure the clock-source line, perform the following steps. SUMMARY STEPS 1. enable 2. configure terminal 3. controller {t1 | e1} slot/port 4. clock source {line [primary] | internal} 5. Do one of the following: • mode atm [aim aim-slot] • • • mode cas • • • ds0-group group-number timeslots timeslot-range type type • • • pri-group timeslots timeslot-range 6. exit 7. network-clock-participate [slot slot-number | wic wic-slot| aim aim-slot-number] 8. network-clock-select priority {t1 | e1} slot/port 9. exit ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 180 Integrated Voice and Data WAN on T1 E1 Interfaces Configuring Network Clock Source and Participation
- 193. DETAILED STEPS PurposeCommand orAction Enables privileged EXEC mode. Enter your password if prompted.enable Example: Router> enable Step 1 Enters global configuration mode.configure terminal Example: Router# configure terminal Step 2 Enters controller configuration mode on the T1 or E1 controller on the specified slot/port. controller {t1 | e1} slot/port Example: Router(config)# controller t1 1/0 Step 3 Specifies the source from which the phase-locked loop (PLL) on this port derives its clocking and, if the source is line, whether this port is the primary source. Keywords are as follows: clock source {line [primary] | internal} Example: Router(config-controller)# clock source line Step 4 • line --Clock recovered from the line’s receive data stream. This is the default. • primary --External source to which the port is connected. This option also puts a second port, which is generally connected to the PBX, into looped-time mode. Both ports are configured with line, but only the port connected to the external source is configured with primary. • internal --T1 or E1 controller internal PLL. With the default, the clock source does not appear in the show running-config command output. Use the show controllers command to display the current source for a port. Note (mode atm command) Sets the controller to ATM mode and creates ATM interface ATM 0. Use for Cisco 2600 series, Cisco 3660, and Cisco 3700 Do one of the following:Step 5 • mode atm [aim aim-slot] series that use an AIM for ATM processing. Do not use on routers that use an AIM only for DSP resources.• • This command without the aim keyword uses software (rather than AIM) to perform ATM segmentation and reassembly. This is supported on Cisco 2600 series WIC slots only and is not supported on network module slots. Note or • mode cas • • • ds0-group group-number timeslots timeslot-range type type (mode cas command) Sets the controller to CAS mode (for software images earlier than Cisco IOS Release 12.2(15)T). Use for Cisco 2600 series with WIC slots.• ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 181 Integrated Voice and Data WAN on T1 E1 Interfaces Configuring Network Clock Source and Participation
- 194. PurposeCommand or Action or• •pri-group timeslots timeslot-range (ds0-group timeslots command) Creates a DS0 group that makes up a logical voice port on a T1/E1 controller and specifies the signaling type by which the router connects to the PBX or CO. Example: Router(config-controller)# mode atm aim 0 or (pri-group timeslotscommand) Creates a PRI group that makes up a logical voice port on a channelized T1 or E1 controller. Example: Example: Example: Router(config-controller)# mode cas Example: Example: Example: Router(config-controller)# ds0-group 0 timeslots 1-4,8-23 type fxs-loop-start Example: Example: Example: Router(config-controller)# pri-group timeslots 1-4,8-23 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 182 Integrated Voice and Data WAN on T1 E1 Interfaces Configuring Network Clock Source and Participation
- 195. PurposeCommand or Action Exitsthe current mode.exit Example: Router(config-controller)# exit Step 6 Allows the network module or VWIC in the specified slot to use the network clock for its timing. Keywords depend on platform. network-clock-participate [slot slot-number | wic wic-slot| aim aim-slot-number] Step 7 Example: Router(config)# network-clock-participate wic 0 Example: Router(config)# network-clock-participate slot 5 Specifies a slot/port to be used as a timing source for the network clock and the priority level for that port. The source that is given the highest network-clock-select priority {t1 | e1} slot/port Step 8 priority is designated the primary source and is used first; if it becomes Example: Router(config)# network-clock-select 1 e1 0/1 unavailable, the source with the second-highest priority is used, and so forth. This command is required if the clock source is from the line. The clocking is provided to the AIM, which then provides it to participating slots in the router. Keywords and arguments are as follows: • priority --Priority for the clock source (1 is highest priority) • t1 or e1--T1 or E1 ports • slot/port --Slot and port for the controller clock source. Slots are as follows: • Cisco 2600 series and Cisco 2600XM--0 (built-in WIC slot) or 1 (network module slot) • Cisco 3660--1 to 6 • Cisco 3725 and Cisco 3745--1 to 4 Exits the current mode.exit Example: Router(config)# exit Step 9 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 183 Integrated Voice and Data WAN on T1 E1 Interfaces Configuring Network Clock Source and Participation
- 196. Configuring the AIM-ATM-VOICE-30Card for High-Complexity Codecs and Time Slots To configure the AIM-ATM-VOICE-30 card for high-complexity codecs and time slots, perform the following steps. SUMMARY STEPS 1. enable 2. configure terminal 3. voice-card slot 4. codec complexity {high | medium} 5. dspfarm 6. exit 7. controller {t1 | e1} slot/port 8. ds0-group group-number timeslots timeslot-range type type 9. exit DETAILED STEPS PurposeCommand or Action Enters privileged EXEC mode. Enter your password when prompted.enable Example: Router> enable Step 1 Enters global configuration mode.configure terminal Example: Router# configure terminal Step 2 Enters voice-card configuration mode to configure DSP resources on the specified card. The argument is as follows: voice-card slot Example: Router(config)# voice-card 0 Step 3 • slot --AIM slot number on the router chassis: • Cisco 2600 series and Cisco 2600XM--0 • Cisco 3660--7 is AIM slot 0; 8 is AIM slot 1 • Cisco 3725--3 is AIM slot 0; 4 is AIM slot 1 • Cisco 3745--5 is AIM slot 0; 6 is AIM slot 1 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 184 Integrated Voice and Data WAN on T1 E1 Interfaces Configuring the AIM-ATM-VOICE-30 Card for High-Complexity Codecs and Time Slots
- 197. PurposeCommand or Action Changesthe codec complexity to high or medium and matches the DSP complexity packaging to the supported codecs. codec complexity {high | medium} Example: Router(config-voice-card)# Step 4 When codec complexity changes, the system prompts you to remove all existing DS0 or PRI groups. Then all DSPs are reset, loaded with the specified firmware image, and released.codec complexity high For switched calls, you can configure a high-complexity codec even when the DSPs are loaded with medium-complexity firmware. However, an error message displays during call setup when a high-complexity codec is detected. This command affects all DSPs on this voice card. You cannot specify the DSP firmware type based on the DSP chip type. (Optional) Enters the DSP resources on the AIM specified in the voice-card command into the DSP resource pool. dspfarm Example: Router(config-voicecard)# dspfarm Step 5 Exits the current mode.exit Example: Router(config-voicecard)# exit Step 6 Enters controller configuration mode on the T1 or E1 controller on the selected slot/port. controller {t1 | e1} slot/port Example: Router(config)# controller e1 1/0 Step 7 Creates a DS0 group that makes up a logical voice port on a T1/E1 controller. The keyword and argument are as follows: ds0-group group-number timeslots timeslot-range type type Step 8 Example: Router(config-controller)# ds0-group 0 timeslots 1-16 • timeslots timeslot-range --Number, range of numbers, or multiple ranges of numbers separated by commas. T1 range: 1 to 24. E1 range: 1 to 31. • type type -- Signaling type by which the router communicates with the PBX or PSTN. High-complexity codecs with the AIM-ATM-VOICE-30 module can process up to 16 voice channels. Note Exits the current mode.exit Example: Router(config-controller)# exit Step 9 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 185 Integrated Voice and Data WAN on T1 E1 Interfaces Configuring the AIM-ATM-VOICE-30 Card for High-Complexity Codecs and Time Slots
- 198. Configuring Integrated Voiceand Serial Data WAN To configure integrated voice and serial data WAN, perform the following steps. SUMMARY STEPS 1. enable 2. configure terminal 3. controller {t1 | e1} slot/port 4. clock source {line [primary] | internal} 5. channel-group channel-group-number timeslots timeslot-range [speed bit-rate] aim aim-slot-number 6. Do one of the following: • ds0-group ds0-group-number timeslots timeslot-range type type • • • pri-group timeslots timeslot-range | d-channel timeslot| rlm-timeslot timeslot number] 7. no shutdown 8. exit DETAILED STEPS PurposeCommand or Action Enters privileged EXEC mode. Enter your password when prompted.enable Example: Router> enable Step 1 Enters global configuration mode.configure terminal Example: Router# configure terminal Step 2 Enters controller configuration mode on the T1 or E1 controller on the specified slot/port. The example shows a VWIC E1 card installed in WIC slot 0. controller {t1 | e1} slot/port Example: Router(config)# controller e1 0/1 Step 3 Specifies the source from which the phase-locked loop (PLL) on this port derives its clocking and, if the source is line, whether this port is the primary source. Arguments and keywords are as follows: clock source {line [primary] | internal} Example: Router(config-controller)# clock source internal Step 4 • line --Clock recovered from the line’s receive data stream. This is the default. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 186 Integrated Voice and Data WAN on T1 E1 Interfaces Configuring Integrated Voice and Serial Data WAN
- 199. PurposeCommand or Action •primary --External source to which the port is connected. This option also puts a second port, which is generally connected to the PBX, into looped-time mode. Both ports are configured with line, but only the port connected to the external source is configured with primary. • internal --T1 or E1 controller internal PLL. With the default, the clock source does not appear in the show running-config command output. To display the current source for a port, use the show controllers command. Note Directs HDLC traffic from the T1/E1 interface to the AIM-ATM-VOICE-30 digital signaling processor (DSP) card. Use to channel-group channel-group-number timeslots timeslot-range [speed bit-rate] aim aim-slot-number Step 5 specify T1/E1 timeslots to be used for HDLC/PPP/Frame-relay encapsulated data. Example: Router(config-controller)# channel-group 1 timeslots 1-5 aim 0 (DS0 groups) Creates a DS0 group that makes up a logical voice port on a T1/E1 controller. Keywords and arguments are as follows: Do one of the following:Step 6 • ds0-group ds0-group-number timeslots timeslot-range type type • timeslot timeslot-range --Number, range of numbers, or multiple ranges of numbers separated by commas. T1 range: 1 to 24. E1 range: 1 to 31. • • type type -- Signaling type by which the router communicates with the PBX or PSTN. • • pri-group timeslots timeslot-range | d-channel timeslot| rlm-timeslot timeslot number] High-complexity codecs with the AIM-ATM-VOICE-30 module can process up to 16 voice channels. Note or Example: Router(config-controller)# ds0-group 2 timeslots 6-12 type e&m-immediate-start (PRI groups) Creates a PRI group that makes up a logical voice port on a channelized T1 or E1 controller. The keyword and argument are as follows: • timeslot timeslot-range --Range of numbers. T1 range: 1 to 23. E1 range: 1 to 15.Example: Only one PRI group can be configured on a controller. Note Example: Example: Router(config-controller)# pri-group timeslots 6-23 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 187 Integrated Voice and Data WAN on T1 E1 Interfaces Configuring Integrated Voice and Serial Data WAN
- 200. PurposeCommand or Action Reinstatesthe controller.no shutdown Example: Router(config-controller)# no shutdown Step 7 Exits the current mode.exit Example: Router(config-controller)# Step 8 exit Verifying Integrated Voice and Serial Data WAN To verify integrated voice and serial data WAN, perform the following steps (listed alphabetically). SUMMARY STEPS 1. show controllers serial 2. show interface serial 3. show isdn status 4. show network-clocks 5. show running-config 6. show voice dsp DETAILED STEPS Step 1 show controllers serial Use this command to display the configuration on the serial interface Example: Router# show controllers serial 0/0:3 Interface Serial0/0:3 is up Hardware is ATM AIM SERIAL hwidb=0x82C1B768, sardb=0x826404A4 slot 0, unit 0, subunit 0 Current (mxt5100_t)sardb: Ind_Q(0x3D53580), Ind_Q_idx(695), Ind_Q_size(30000) Cmd_Q(0x3D4E720), Cmd_Q_idx(359), Cmd_Q_size(20000) Inpool(0x3B9E1A0), Inpool_size(4096) Outpool(0x3D1B080), Outpool_size(4096) Localpool(0x3D20000), Localpool_size(256) StorBlk(0x3BA7000), host_blk(0x3BA4840), em_blk(0x3BA4900) tx_buf_desc(0x3D476A0), tx_free_desc_idx (1023) ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 188 Integrated Voice and Data WAN on T1 E1 Interfaces Verifying Integrated Voice and Serial Data WAN
- 201. num_fallback(0) MXT5100 Port Info: PortNumber (4), Port ID (0xE05) Interface Number (0), Interface ID (0xF5E0) Port Type 2, Port Open Status SUCCESS HDLC channels opened(1) Port counters:Tx Packets:50686, Rx Packets:42864 Tx Bytes:0, Rx Bytes:0 Discards:No Resource:0, Protocol Errors 4 MXT5100 Channel Info: HDLC Channel Info (0): Chan_ID (0xF25), Open Status SUCCESS tx_limited=0(8) Step 2 show interface serial Use this command to display the configuration on the serial interface. Example: Router# show interface serial 0/0:3 Serial0/0:3 is up, line protocol is up Hardware is ATM AIM SERIAL Internet address is 20.0.0.1/16 MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation PPP, loopback not set LCP Open Open:IPCP, CDPCP Last input 00:00:09, output 00:00:09, output hang never Last clearing of "show interface" counters 18:36:25 Input queue:0/75/0/0 (size/max/drops/flushes); Total output drops:0 Queueing strategy:weighted fair Output queue:0/1000/64/0 (size/max total/threshold/drops) Conversations 0/1/256 (active/max active/max total) Reserved Conversations 0/0 (allocated/max allocated) Available Bandwidth 48 kilobits/sec 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 6696 packets input, 446400 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 6697 packets output, 460924 bytes, 0 underruns 0 output errors, 0 collisions, 0 interface resets 0 output buffer failures, 0 output buffers swapped out 0 carrier transitions Timeslot(s) Used:4, Transmitter delay is 0 flags Step 3 show isdn status Use this command to display the status of all ISDN interfaces, including active layers, timer information, and switch-type settings. Step 4 show network-clocks Use this command to display the current chosen clock and the list of all sources of network clocks according to their priority. Example: Router# show network-clocks Network Clock Configuration --------------------------- Priority Clock Source Clock State Clock Type 3 E1 6/2 GOOD E1 5 T1 2/0 GOOD T1 9 Backplane Good PLL ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 189 Integrated Voice and Data WAN on T1 E1 Interfaces Verifying Integrated Voice and Serial Data WAN
- 202. Current Primary ClockSource --------------------------- Priority Clock Source Clock State Clock Type 3 E1 6/2 GOOD E1 Step 5 show running-config Use this command to display the basic router configuration. Step 6 show voice dsp Use this command to display the voice DSP configuration. Example: Router# show voice dsp DSP DSP DSPWARE CURR BOOT PAK TX/RX TYPE NUM CH CODEC VERSION STATE STATE RST AI VOICEPORT TS ABORT PACK COUNT ==== === == ======== ======= ===== ======= === == ========= == ===== ============ C5421000 00 {high} 3.6.14 IDLE idle 0 0 0/0:0 01 0 5313/1516 Configuration Examples for Integrated Voice and Data WAN on T1 E1 Interfaces Using the AIM-ATM-VOICE-30 Module Single-Serial-Data WAN Example This example shows the configuration of a router whose E1 (0/0) controller is used for integrated voice and serial data. Note that E1 timeslots 1 to 11 are configured for serial data and E1 timeslots 12 to 31 are configured for PRI voice. Also note that interface Serial0/0:1 is the logical interface for E1 timeslots 1 to 11 and interface Serial0/0:15 is the logical interface for E1 timeslots 12 to 31. Router# show running-config Building configuration... Current configuration : 1356 bytes ! version 12.2 service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption ! hostname "buick-hc" ! network-clock-participate wic 0 network-clock-participate aim 0 network-clock-select 1 E1 0/0 voice-card 5 dspfarm ! ip subnet-zero !! isdn switch-type primary-qsig no voice hpi capture buffer no voice hpi capture destination ! mta receive maximum-recipients 0 ! ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 190 Integrated Voice and Data WAN on T1 E1 Interfaces Configuration Examples for Integrated Voice and Data WAN on T1 E1 Interfaces Using the AIM-ATM-VOICE-30 Module
- 203. controller E1 0/0 channel-group1 timeslots 1-11 aim 0 pri-group timeslots 12-31 ! controller E1 0/1 ! controller E1 0/3 controller E1 0/2 ! interface FastEthernet0/0 no ip address shutdown duplex auto speed auto ! interface Serial0/0:1 ip address 175.0.0.1 255.0.0.0 encapsulation ppp ! interface Serial0/0:15 no ip address no logging event link-status isdn switch-type primary-qsig isdn incoming-voice voice no cdp enable ! interface FastEthernet0/1 ip address 1.10.10.1 255.0.0.0 speed 100 full-duplex ! ip http server ip classless ! call rsvp-sync ! voice-port 0/0:15 ! mgcp profile default ! dial-peer cor custom ! dial-peer voice 40 pots destination-pattern 427.... direct-inward-dial port 0/0:15 prefix 427 ! dial-peer voice 400 voip destination-pattern 525.... session target ipv4:1.10.10.2 ! line con 0 exec-timeout 0 0 line aux 0 line vty 0 4 login ! end Multiple-Serial-Data WAN Example This example shows the configuration of a router whose E1 (0/0) controller is used voice and serial data traffic and whose E1 (0/1) controller is used completely for data traffic. Router# show running-config Building configuration... Current configuration : 1492 bytes ! ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 191 Integrated Voice and Data WAN on T1 E1 Interfaces Multiple-Serial-Data WAN Example
- 204. version 12.2 service timestampsdebug datetime msec service timestamps log datetime msec no service password-encryption ! hostname "buick-hc" ! network-clock-participate wic 0 network-clock-participate aim 0 network-clock-select 1 E1 0/0 voice-card 5 dspfarm ! ip subnet-zero ! isdn switch-type primary-qsig ! no voice hpi capture buffer no voice hpi capture destination ! mta receive maximum-recipients 0 ! controller E1 0/0 channel-group 1 timeslots 1-11 aim 0 pri-group timeslots 12-31 ! controller E1 0/1 channel-group 1 timeslots 1-31 aim 0 ! controller E1 0/3 ! controller E1 0/2 ! interface FastEthernet0/0 no ip address shutdown duplex auto speed auto ! interface Serial0/0:1 ip address 172.0.0.1 255.0.0.0 encapsulation ppp ! interface Serial0/0:15 no ip address no logging event link-status isdn switch-type primary-qsig isdn incoming-voice voice no cdp enable ! interface FastEthernet0/1 ip address 10.10.10.1 255.0.0.0 speed 100 full-duplex ! interface Serial0/1:1 ip address 175.5.0.1 255.0.0.0 encapsulation frame-relay ! ip http server ip classless ! call rsvp-sync ! voice-port 0/0:15 ! mgcp profile default ! dial-peer cor custom ! dial-peer voice 40 pots destination-pattern 427.... direct-inward-dial ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 192 Integrated Voice and Data WAN on T1 E1 Interfaces Multiple-Serial-Data WAN Example
- 205. port 0/0:15 prefix 427 ! dial-peervoice 400 voip destination-pattern 525.... session target ipv4:10.10.10.2 ! line con 0 exec-timeout 0 0 line aux 0 line vty 0 4 login ! end High-Complexity Codecs and Network Clock Example This example shows the configuration of a router in which the WIC at slot 0 and AIM at slot 0 are configured to received clock from the network (see the lines network-clock-participate). Also note that E1 0/0 controller is the source of the network clock (see the line network-clock-select). This example also shows that the voice card in slot 5 uses a high-complexity codec. Router# show running-config Building configuration... Current configuration : 1276 bytes ! version 12.2 service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption ! hostname "router-hc" ! network-clock-participate wic 0 network-clock-participate aim 0 network-clock-select 1 E1 0/0 voice-card 5 codec complexity high dspfarm ! ip subnet-zero ! isdn switch-type primary-qsig no voice hpi capture buffer no voice hpi capture destination ! mta receive maximum-recipients 0 ! controller E1 0/0 pri-group timeslots 1-16 ! controller E1 0/1 ! controller E1 0/3 ! controller E1 0/2 ! interface FastEthernet0/0 no ip address shutdown duplex auto speed auto ! interface Serial0/0:15 no ip address no logging event link-status isdn switch-type primary-qsig isdn incoming-voice voice ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 193 Integrated Voice and Data WAN on T1 E1 Interfaces High-Complexity Codecs and Network Clock Example
- 206. no cdp enable ! interfaceFastEthernet0/1 ip address 1.10.10.1 255.0.0.0 speed 100 full-duplex ! ip http server ip classless ! call rsvp-sync ! voice-port 0/0:15 ! mgcp profile default ! dial-peer cor custom ! dial-peer voice 40 pots destination-pattern 427.... direct-inward-dial port 0/0:15 prefix 427 ! dial-peer voice 400 voip destination-pattern 525.... session target ipv4:0.10.10.2 ! line con 0 exec-timeout 0 0 line aux 0 line vty 0 4 login ! end Additional References General ISDN References • "Overview of ISDN Voice Interfaces" on page 3 --Describes relevant underlying technology; lists related documents, standards, MIBs, and RFCs; and describes how to obtain technical assistance • "Additional References" section on page 64 --Lists additional ISDN references References Mentioned in This Chapter • AIM-ATM, AIM-VOICE-30, and AIM-ATM-VOICE-30 on the Cisco 2600 Series and Cisco 3660 at http:/ /www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t8/ft_04gin.htm • Cisco IOS Voice Command Reference at http://www.cisco.com/en/US/docs/ios/voice/command/reference/vr_book.html ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 194 Integrated Voice and Data WAN on T1 E1 Interfaces Additional References
- 207. C H AP T E R 8 ISDN GTD for Setup Message This chapter describes how to implement the ISDN Generic Transparency Descriptor (GTD) for Setup Message feature. The feature provides support for mapping ISDN information elements (IEs) to corresponding GTD parameters. The following IEs and parameters are supported: • Originating line information (OLI) • Bearer capability (USI and TMR) called-party number (CPN) • Calling-party number (CGN) • Redirecting number (RGN, OCN and RNI) This feature allows VoIP service providers to develop custom call treatments and enhanced service offerings based on call origination and to correctly identify the source of a call, bill appropriately, and settle accurately with other network providers. Feature History for ISDN GTD for Setup Message ModificationRelease This feature was introduced.12.2(15)T • Finding Feature Information, page 196 • Prerequisites for Configuring ISDN GTD for Setup Message, page 196 • Restrictions for Configuring ISDN GTD for Setup Message, page 196 • Information About ISDN GTD for Setup Message, page 196 • How to Configure ISDN GTD for Setup Message, page 211 • Configuration Examples for ISDN Generic Transparency Descriptor (GTD) for Setup Message, page 216 • Additional References, page 219 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 195
- 208. Finding Feature Information Yoursoftware release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required. Prerequisites for Configuring ISDN GTD for Setup Message • Perform the prerequisites that are listed in the "Prerequisites for Configuring an ISDN Voice Interface" section. • Configure your VoIP network and Cisco IOS gateways to allow sending and processing of ISDN Q.931 setup messages. Restrictions for Configuring ISDN GTD for Setup Message Restrictions are described in the Restrictions for Configuring ISDN Voice Interfaces section. In addition, the following applies: • This feature does not support ISDN BRI calls. Information About ISDN GTD for Setup Message General information about ISDN voice interfaces is presented in the "Information About ISDN Voice Interfaces" section. Note Feature Design of ISDN GTD for Setup Messages The ISDN GTD for Setup Messages feature allows the delivery of information elements present in ISDN setup messages to Tool Command Language (Tcl) scripts, RADIUS accounting servers, and routing servers in VoIP networks. This allows Tcl scripts and routing servers to access ISDN signaling information to provide enhanced features and routing services. In particular, the OLI IE present in AT&T (TR-41459 ISDN PRI UNI Specification) and MCI setup messages can be passed to the originating-line-info VSA in RADIUS start-accounting messages to identify the originating caller. FCC regulations mandate that pay-telephone operators be compensated by network operators for 1-800 calls made from their pay telephones. Before implementation of this feature, network operators had no way to identify calls made from their pay telephones. As a result, network operators had to compensate pay-telephone operators directly from their own revenues. In addition, network operators had no billing records to validate ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 196 ISDN GTD for Setup Message Finding Feature Information
- 209. pay-telephone operators’ settlementrequests to prevent fraud. This feature provides Cisco network operators with the ability to correctly identify the source of a call. It allows networks to do the following: • Extract originating-line information (OLI) to identify pay telephone calls and pass on applicable charges • Generate billing records that can be used to validate pay telephone operator settlement requests. For information on accounting records and RADIUS billing, see the RADIUS VSA Voice Implementation Guide. Note This feature provides the flexibility to identify other types of originated calls (from prisons, hotels, and so forth) and allows you to use the Tcl interface to define custom services for these types of calls. For more information on Tcl application programming, see the Tcl IVR API Version 2.0 Programmer's Guide. Note In addition to passing OLI, this feature supports GTD mapping for Bearer Capability, Called Party Number, Calling Party Number, and Redirecting Number IEs. Cisco implements this feature on Cisco IOS gateways by providing a mechanism to allow creating and passing the Q931 setup message and its parameters in a GTD format. The setup message, received by the gateway to initiate call establishment, is mapped to the GTD initial address message (IAM). Generic transparency descriptors represent parameters within signaling messages and enable transport of signaling data in a standard format across network components and applications. The GTD mechanism allows them to share signaling data and achieve interworking between different signaling types. This feature supports only ISDN PRI and non-facility associated signaling (NFAS) calls. Mapping of ISDN Information Elements to GTD Parameters ISDN messages, used to signal call control, are composed of information elements and follow the format specified in ITU-T Q.931. This feature supports only the mapping of Q931 setup messages to GTD IAM messages. This section defines the mapping of ISDN information elements to GTD parameters. Parameters are referred to by both parameter name and three-character GTD code. The table below defines the mapping of ISDN IEs to GTD parameters. The GTD mechanism also passes the following parameters for which there are no corresponding ISDN IEs: • Calling-party category (CPC) • Forward-call indicators (FCI) • Protocol name (PRN) Table 9: ISDN IEs Mapped to GTD Parameters GTD ParameterISDN Information Element USI (user-service information), TMR (transmission-medium requirements) Bearer Capability ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 197 ISDN GTD for Setup Message Mapping of ISDN Information Elements to GTD Parameters
- 210. GTD ParameterISDN InformationElement CPN (called party number)Called Party Number CGN (calling-party number)Calling Party Number OLI (originating-line information)Originating Line Info RGN (redirecting number), OCN (original called number), RNI (redirection information) Redirecting Number GTD mapping allows up to two redirecting number (original called number) IEs per call as follows: • If only one IE is present in the incoming setup message, then both RGN and OCN parameters are built by the ISDN stack and the RGN and OCN parameters contain the same values. Both the redirection reason (rr) field and original redirection reason (orr) field in the GTD RNI parameter contain the redirection reason indicated in the IE. • If two IEs are present, then OCN contains information specified in the first IE and RGN contains information for the second IE. RNI contains redirection reasons. The GTD orr field indicates the redirection reason of the first IE and the GTD rr field indicates that of the second IE. Mapping for CPN CGN and RGN This section defines mapping for fields and values common to the called party number (CPN), calling party number (CGN), and redirecting information (RGN) GTD parameters carried in the GTD IAM message. The table below defines mapping for ISDN type of number fields to GTD nature of address (noa) fields. Table 10: Type of Number to Nature of Address Mapping GTD Nature of Address (noa)ISDN Type of Number 00--Unknown (number present)0--Unknown 06--Unique international number1-- International number 04--Unique national (significant) number2--National number 08--Network specific number3--Network specific number 02--Unique subscriber number4--Subscriber number 34--Abbreviated number6--Abbreviated number The table below defines mapping for ISDN numbering plan identification fields to GTD numbering plan indicator (npi) fields. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 198 ISDN GTD for Setup Message Mapping of ISDN Information Elements to GTD Parameters
- 211. Table 11: NumberingPlan Identification to Numbering Plan Indicator Mapping GTD Numbering Plan Indicator (npi)ISDN Numbering Plan Identification u--Unknown0--Unknown 1--ISDN numbering plan1--ISDN telephony numbering plan 1--ISDN numbering plan (best fit)2--Telephony numbering plan 2--Data numbering plan3--Data numbering plan 3--Telex numbering plan4--Telex numbering plan 5--National numbering plan8--National standard numbering plan 4--Private numbering plan9--Private numbering plan The table below defines mapping for ISDN and GTD presentation indicator (pi) fields. Table 12: Presentation Indicator Mapping GTD Presentation Indicator (pi)ISDN Presentation Indicator u--Unknown-- y--Presentation allowed0-- Presentation allowed n--Presentation not allowed1--Presentation restricted 0--Address not available2--Number not available due to interworking Mapping for Calling Party Number (CGN) The table below defines mapping for ISDN and GTD screening indicator (si) fields. Table 13: Screening Indicator Mapping GTD Screening Indicator (si)ISDN Screening Indicator u--Unknown-- 1--User-provided, not screened0-- User-provided, not screened 2--User-provided screening passed1--User-provided, verified and passed 3--User-provided screening failed2--User-provided, verified and failed ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 199 ISDN GTD for Setup Message Mapping of ISDN Information Elements to GTD Parameters
- 212. Mapping for RedirectionInformation (RNI) The table below defines mapping for the ISDN reason for redirection fields to GTD original redirection reason (orr) and redirection reason (rr) fields in the GTD RNI parameter. Table 14: Reason for Redirection to Original Redirection Reason and Redirection Reason Mapping GTD Original Redirection Reason (orr) and Redirection Reason (rr) ISDN Reason for Redirection u--Unknown0--Unknown 1--User busy1--Call forwarding busy or called DTE busy 2--No reply2--Call forwarding no reply 4--Deflection during alerting4--Call deflection 5--Call deflection immediate response5--Call deflection immediate response 2--No reply (best fit)9--Called DTE out of order 5--Call deflection immediate response (best fit)10--Call forwarding by the called DTE 5--Call deflection immediate response (best fit)13--Call transfer 5--Call deflection immediate response (best fit)14--Call pickup 3--Unconditional15--Call forwarding unconditional Mapping for Originating Line Information (OLI) The table below defines mapping for OLI fields. Table 15: Originating Line Information Mapping GTD Originating-Line Information (oli)ISDN Originating-Line Information 0--POTS0-- POTS 1--Multiparty line1--Multiparty line 2--ANI failure2--ANI failure 6--Station-level rating6--Station-level rating 7--Special operator handling required7--Special operator handling required 8-- Inter-LATA restricted8--Inter-LATA restricted ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 200 ISDN GTD for Setup Message Mapping of ISDN Information Elements to GTD Parameters
- 213. GTD Originating-Line Information(oli)ISDN Originating-Line Information 10--Test call10--Test call 20--AIOD-listed DN sent20--AIOD-listed DN sent 23--Coin or noncoin on calls using database access23--Coin or noncoin on calls using database access 24--800 service call24--800 service call 25--800 service call from a pay station25-- 800 service call from a pay station 27--Payphone using coin control signaling27--Payphone using coin control signaling 29--Prison or inmate service29-- Prison or inmate service 30--Intercept (blank)30-- Intercept (blank) 31--Intercept (trouble)31--Intercept (trouble) 32--Intercept (regular)32--Intercept (regular) 34--Telco operator-handled call34--Telco operator-handled call 36--CPE36--CPE 52--OUTWATS52--OUTWATS 60--TRS call from unrestricted line60--TRS call from unrestricted line 61--Wireless or cellular PCS (type 1)61--Wireless or cellular PCS (type 1) 62--Wireless or cellular PCS (type 2)62--Wireless or cellular PCS (type 2) 63--Wireless or cellular PCS (roaming)63-- Wireless or cellular PCS (roaming) 66--TRS call from hotel66--TRS call from hotel 67--TRS call from restricted line67--TRS call from restricted line 68--Inter-LATA restricted hotel68-- Inter-LATA restricted hotel 78--Inter-LATA restricted coinless78--Inter-LATA restricted coinless 70--Private paystations70--Private paystations 93--Private virtual network93--Private virtual network ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 201 ISDN GTD for Setup Message Mapping of ISDN Information Elements to GTD Parameters
- 214. Mapping for BearerCapability (USI and TMR) Parameters The ISDN Bearer Capability IE is mapped to the GTD User Service Information (USI) and Transmission Medium Requirements (TMR) parameters. The table below defines mapping for coding standard fields and values. Table 16: ISDN to GTD Coding Standard Mapping GTD Coding Standard (cs)ISDN Coding Standard c--CCITT/ITU standardized coding0--CCITT standardized coding i--ISO/IEC standard1--Reserved for other international standard n--National standard2--National standard p--Standard defined for the network3--Standard defined for the network The table below defines ISDN to GTD mapping for information transfer capability fields and values. Table 17: Information Transfer Capability Mapping GTD Information Transfer Capability (cap)ISDN Information Transfer Capability s--Speech0--Speech d--Unrestricted digital information8--Unrestricted digital information r--Restricted digital information9--Restricted digital information 3--3.1-kbps audio16--3.1-kHz audio 7--7-kbps audio17--7-kHz audio v-- Video24--Video The table below defines mapping for transfer mode fields and values. Table 18: Transfer Mode Mapping GTD Transfer Mode (mode)ISDN Transfer Mode c--Circuit mode0--Circuit mode p--Packet mode2--Packet mode The table below defines mapping for information transfer rate fields and values. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 202 ISDN GTD for Setup Message Mapping of ISDN Information Elements to GTD Parameters
- 215. Table 19: InformationTransfer Rate Mapping GTD Information Transfer Rate (rate)ISDN Information Transfer Rate 0--Not applicable (used for packet call)0--Packet mode 1--64 kbps16--64 kbps 7--2x64 kbps17--2x64 kbps 2--384 kbps19--384 kbps 4--1536 kbps21--1536 kbps 5--1920 kbps23--1920 kbps The table below defines mapping for transmission medium requirements. Table 20: Transmission Medium Requirements Mapping GTD Transmission Medium Requirements ISDN Information Transfer RateISDN Information Transfer Capability 00--0--Speech 0116--64 kbps8--Unrestricted digital information 0417--2x64 kbps8--Unrestricted digital information 0519--384 kbps8--Unrestricted digital information 0621--1536 kbps8--Unrestricted digital information 0723--1920 kbps8--Unrestricted digital information 02--16--3.1-kHz audio 08--17--7-kHz audio 08--24--Video The table below defines mapping for structure fields and values. Table 21: Structure Mappings Structure (str)Structure 0--Default or unknown0--Default ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 203 ISDN GTD for Setup Message Mapping of ISDN Information Elements to GTD Parameters
- 216. Structure (str)Structure 1--8-kHz integrity1--8-kHzintegrity 2--Service data unit integrity4--Service data unit integrity 3--Unstructured7--Unstructured The table below defines mapping for configuration fields and values. Table 22: Configuration Field Mapping GTD Configuration (conf)ISDN Configuration 0--Point to point0--Point to point The table below defines mapping for establishment fields and values. Table 23: Establishment Field Mapping GTD Establishment (estab)ISDN Establishment d--Demand0--Demand The table below defines mapping for symmetry fields and values. Table 24: Symmetry Field Mapping GTD Symmetry (sym)ISDN Symmetry sb--Symmetric bidirectional0--Bidirectional symmetric The table below defines mapping for Layer 1 protocol fields and values. Table 25: Layer 1 Protocol Mapping GTD Layer 1 Protocol (lay1)ISDN Information Layer 1 Protocol v110--CCITT standardized V.110/X.301--CCITT standardized V110 ulaw--G711 mu-law2--G.711mu-law alaw--G711 A-law3--G.711A-law g721--G721 32 kbps4--G.721 32 kbps g722--G.722 and G.725/G.724 7-kHz audio5--G.722 and G.725 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 204 ISDN GTD for Setup Message Mapping of ISDN Information Elements to GTD Parameters
- 217. GTD Layer 1Protocol (lay1)ISDN Information Layer 1 Protocol g735--G.735 for 384 kbps video6--G.7xx 384 video nonc--Non-CCITT rate adaptation7--Non-CCITT standardized v120--CCITT standardized V.1208--CCITT standardized V.120 hdlc--CCITT standardized X.319--CCITT standardized X.31 The table below defines mapping for synchronization fields and values. Table 26: Synchronization Mapping GTD Synchronization (sync)ISDN Synchronous/Asynchronous y--Synchronous0--Synchronous n--Asynchronous1--Asynchronous The table below defines mapping for negotiation fields and values. Table 27: Negotiation Mapping GTD Negotiation (neg)ISDN Negotiation 0--In-band negotiation not possible0--In-band negotiation not possible 1--In-band negotiation possible1--In-band negotiation possible The table below defines mapping for user rate fields and values. Table 28: User-Rate Mapping ISDN User Rate (subrate)ISDN User Rate 0--rate is indicated by E-bits0--rate is indicated by E-bits 1--0.6 kbps1--0.6 kbps 2--1.2 kbps2--1.2 kbps 3--2.4 kbps3--2.4 kbps 4--3.6 kbps4--3.6 kbps 5--4.8 kbps5--4.8 kbps ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 205 ISDN GTD for Setup Message Mapping of ISDN Information Elements to GTD Parameters
- 218. ISDN User Rate(subrate)ISDN User Rate 6--7.2 kbps6--7.2 kbps 7--8.0 kbps7--8.0 kbps 8--9.6 kbps8--9.6 kbps 9--14.4 kbps9--14.4 kbps 10--16.0 kbps10--16.0 kbps 11--19.2 kbps11--19.2 kbps 12--32.0 kbps12--32.0 kbps 13--48.0 kbps14--48.0 kbps 14--56.0 kbps15--56.0 kbps 14--56.0 kbps (best fit)16--64.0 kbps 15--0.1345 kbps21--0.1345 kbps 16--0.1000 kbps22--0.100 kbps 17--0.075/1.2 kbps23--0.075/1.2 kbps 18--1.2/0.075 kbps24--1.2/0.075 kbps 19--0.050 kbps25--0.050 kbps 20--0.075 kbps26--0.075 kbps 21--0.110 kbps27--0.110 kbps 22--0.150 kbps28--0.150 kbps 23--0.200 kbps29--0.200 kbps 24--0.300 kbps30-- 0.300 kbps 25--12 kbps31--12 kbps The table below defines mapping for intermediate rate fields and values. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 206 ISDN GTD for Setup Message Mapping of ISDN Information Elements to GTD Parameters
- 219. Table 29: IntermediateRate Mapping GTD Intermediate Rate (int)ISDN Intermediate Rate 08--8 kbps1--8 kbps 16--16 kbps2--16 kbps 32--32 kbps3--32 kbps The table below defines mapping for network independent clock on transmission fields and values. Table 30: Mapping for Network Independent Clock on Transmission ISDN Network Independent Clock on TX (txnic)ISDN Network Independent Clock on TX n--Not required to send data0--Not required to send data y--Required to send data1--Required to send data The table below defines mapping for network independent clock on reception fields and values. Table 31: Mapping for Network Independent Clock on Reception GTD Network Independent Clock on RX (rxnic)ISDN Network Independent Clock on RX n--Cannot accept data0--Cannot accept data y--Can accept data1--Can accept data The table below defines mapping for flow control on transmission fields and values. Table 32: Mapping for Flow Control on Transmission GTD Flow Control on TX (txfl)ISDN Flow Control on TX n--Not required to send data0--Not required to send data y--Required to send data1--Required to send data The table below defines mapping for flow control on reception fields and values. Table 33: Mapping for Flow Control on Reception GTD Flow Control on RX (rxfl)ISDN Flow Control on RX n--Cannot accept data0--Cannot accept data ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 207 ISDN GTD for Setup Message Mapping of ISDN Information Elements to GTD Parameters
- 220. GTD Flow Controlon RX (rxfl)ISDN Flow Control on RX y--Can accept data1--Can accept data The table below defines mapping for rate adaptation header fields and values. Table 34: Mapping for Rate Adaptation Header GTD Rate Adaptation Header (hdr)ISDN Rate Adaptation Header/No Header n--Rate adaptation header not included0--Rate adaptation header not included y--Rate adaptation header included1--Rate adaptation header included The table below defines mapping for multiframe establishment support for data link fields and values. Table 35: Mapping for Multiframe Establishment (MFE) Support GTD MFE Support in Data Link (mf)ISDN MFE Support in Data Link n--MFE not supported0--MFE not supported y--MFE supported1--MFE supported The table below defines mapping for mode of operation fields and values. Table 36: Mode of Operation Mapping GTD Mode of Operation (mode)ISDN Mode of Operation 0--Bit-transparent mode of operation0--Bit-transparent mode of operation 1--Protocol-sensitive mode of operation1--Protocol-sensitive mode of operation The table below defines mapping for logical link identifier negotiation fields and values. Table 37: Logical Link Identifier (LLI) Mapping GTD LLI Negotiation (lli)ISDN LLI Negotiation 0--Default0--Default 1--Full-protocol negotiation1--Full protocol negotiation The table below defines mapping for assignor and assignee fields and values. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 208 ISDN GTD for Setup Message Mapping of ISDN Information Elements to GTD Parameters
- 221. Table 38: Mappingfor Assignor and Assignee GTD Assignor and Assignee (asgn)ISDN Assignor and Assignee 0--Message originator is default assignee0--Message originator is default assignee 1--Message originator is assignor only1--Message originator is assignor only The table below defines mapping for in-band and out-of-band negotiation fields and values. Table 39: Mapping for Inband and Out-of-Band Negotiation GTD In-band and Out-of-Band Negotiation (inbnd)ISDN In-band and Out-of-Band Negotiation 0-- Not applicable to this protocol0--Negotiation done with USER INFO 1-- Negotiation done in-band1--Negotiation done in-band The table below defines mapping for fields and values for number of stop bits. Table 40: Mapping for Number of Stop Bits GTD Number of Stop Bits (stp)ISDN Number of Stop Bits 1--1 bit1--1 bit 3--1.5 bit2--1.5 bit 2--2 bits3--2 bits The table below defines mapping for fields and values for number of data bits. Table 41: Mapping for Number of Data Bits GTD Number of Data Bits (dat)ISDN Number of Data Bits 5--5 bits1--5 bits 7--7 bits2--7 bits 8--8 bits3--8 bits The table below defines mapping for parity information fields and values. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 209 ISDN GTD for Setup Message Mapping of ISDN Information Elements to GTD Parameters
- 222. Table 42: ParityMapping GTD Parity (par)ISDN Parity Information o--Odd0--Odd e--Even2--Even n--None3--None 0--Forced to 04--Forced to 0 1-- Forced to 15--Forced to 1 The table below defines mapping for duplex mode fields and values. Table 43: Duplex Mode Mapping GTD Duplex (dup1)ISDN Duplex Mode h--Half duplex0--Half duplex f--Full duplex1--Full duplex The table below defines mapping for modem type fields and values. Table 44: Modem Type Mapping Modem Type (modm)Modem Type 11--V.211--V.21 00--V.222--V.22 01--V.22 bis3--V.22 bis 02--V.234--V.23 03--V.265--V.26 04--V.26 bis6--V.26 bis 05--V.26 ter7--V.26 ter 06--V.278 --V.27 07--V.27 bis9--V.27 bis 08--V.27 ter10--V.27 ter ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 210 ISDN GTD for Setup Message Mapping of ISDN Information Elements to GTD Parameters
- 223. Modem Type (modm)ModemType 09--V.2911--V.29 10--V.3212--V.32 12--V.34 (best fit)13--V.35 The table below defines mapping for Layer 2 protocol fields and values. Table 45: Layer 2 Protocol Mapping GTD Layer 2 Protocol (lay2)ISDN User Information Layer 2 Protocol 2--Q.9212--Q.921 1--X.256--X.25 The table below defines mapping for Layer 3 protocol fields and values. Table 46: Layer 3 Protocol Mapping GTD Layer 3 Protocol (lay3)ISDN User Information Layer 3 Protocol 2--Q.9312--Q.931 1--X.256--X.25 How to Configure ISDN GTD for Setup Message Configuring ISDN GTD for Setup Messages This feature is enabled by default; no configuration tasks are required to enable this feature. To reenable the feature if it was disabled by use of the no isdn gtd command, perform the following steps. SUMMARY STEPS 1. enable 2. configure terminal 3. interface 4. isdn gtd 5. exit ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 211 ISDN GTD for Setup Message How to Configure ISDN GTD for Setup Message
- 224. DETAILED STEPS PurposeCommand orAction Enables privileged EXEC mode. Enter your password if prompted. enable Example: Router> enable Step 1 Enters global configuration mode.configure terminal Example: Router# configure terminal Step 2 Enters interface configuration mode.interface Example: Router(config)# interface Step 3 Enables GTD parameter mapping for ISDN IEs.isdn gtd Example: Router(config-if)# isdn gtd Step 4 Exits the current mode.exit Example: Router(config-if)# exit Step 5 Configuring the OLI IE to Interface with MCI Switches To configure OLI IE to interface with MCI switches, perform the following steps. You must configure the Cisco IOS gateway to support the switch variant from which the gateway receives ISDN signaling. For a gateway that interfaces to an MCI switch or PBX, the OLI IE identifier for the MCI ISDN variant, as defined in CPE Requirements for MCI ISDN Primary Rate Interface, (014-0018-04.3D-ER, revision 4.3D), is configurable. Select the IE value that indicates OLI information to configure gateway support for the MCI ISDN variant. Note ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 212 ISDN GTD for Setup Message Configuring the OLI IE to Interface with MCI Switches
- 225. SUMMARY STEPS 1. enable 2.configure terminal 3. interface 4. isdn ie oli value 5. exit DETAILED STEPS PurposeCommand or Action Enables privileged EXEC mode. Enter your password if prompted. enable Example: Router> enable Step 1 Enters global configuration mode.configure terminal Example: Router# configure terminal Step 2 Enters interface configuration mode.interface Example: Router(config)# interface Step 3 Configures the OLI IE identifier to allow the gateway to interface with an MCI switch. isdn ie oli value Example: Router(config-if)# isdn ie oli 7F Step 4 OLI IE identifier values are in hexadecimal format. Values range from 00 to 7F. Exits the current mode.exit Example: Router(config-if)# exit Step 5 Verifying ISDN GTD To verify the interface, perform the following steps (listed alphabetically). ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 213 ISDN GTD for Setup Message Verifying ISDN GTD
- 226. SUMMARY STEPS 1. showisdn status 2. show running-config DETAILED STEPS Step 1 show isdn status Use this command to display the status of all ISDN interfaces, including active layers, timer information, and switch-type settings. Step 2 show running-config Use this command to display the configuration for the ISDN GTD for Setup Messages feature. If GTD mapping is enabled (default), command output does not display the isdn gtd command. Troubleshooting Tips • Use the debug gtd detailscommand to display GTD details. • Use the debug gtd error command to display GTD errors. • Use the debug gtd eventscommand to display GTD events. Examples This section provides the following output example: Sample Output for the debug gtd events Command Router# debug gtd events 00:05:19:%SYS-5-CONFIG_I:Configured from console by console *Aug 8 06:32:20.915:ISDN Se3:23 Q931:RX <- SETUP pd = 8 callref = 0x0002 Bearer Capability i = 0x8890 Standard = CCITT Transer Capability = Unrestricted Digital Transfer Mode = Circuit Transfer Rate = 64 kbit/s Channel ID i = 0xA98397 Exclusive, Channel 23 Called Party Number i = 0x81, '9999' Plan:ISDN, Type:Unknown *Aug 8 06:32:20.919:ISDN Se3:23:Built a GTD of size 86 octets for ISDN message type 0x5 *Aug 8 06:32:20.919:tsp_ccrawmsg_encap:calling cdapi_find_tsm *Aug 8 06:32:20.919:cdapi_find_tsm:Found Tunnelled Signaling Msg with GTD:PROT_PTYPE_GTD *Aug 8 06:32:20.919:cdapi_find_tsm:Found a gtd msg of length 86: *Aug 8 06:32:20.919:gtd msg = "IAM, PRN,isdn*,,, USI,rate,c,d,c,1 TMR,01 CPN,00,,1,9999 CPC,09 FCI,,,,,,,y," ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 214 ISDN GTD for Setup Message Troubleshooting Tips
- 227. *Aug 8 06:32:20.923:ccGTDExtractParm:Starting *Aug8 06:32:20.923: tunnelledPtype = 2 *Aug 8 06:32:20.923: gtdInstance = 0 *Aug 8 06:32:20.923: gtdBitMap = 0xFFFFFFFF *Aug 8 06:32:20.923:ccGTDExtractParm:TunnelledContent has GTD message *Aug 8 06:32:20.923:gtd msg = "IAM, PRN,isdn*,,, USI,rate,c,d,c,1 TMR,01 CPN,00,,1,9999 CPC,09 FCI,,,,,,,y," *Aug 8 06:32:20.927:ccGTDExtractParm:GTD Parm CPC obtained *Aug 8 06:32:20.927:ccGTDExtractParm:GTD Parm TMR obtained *Aug 8 06:32:20.927:ccGTDExtractParm:GTD Parm PRN obtained *Aug 8 06:32:21.547:ccMapGCItoGUID:GTD Parm GCI not present *Aug 8 06:32:21.547:ccMapGUIDtoGCI:Modified GTD string to include GCI *Aug 8 06:32:21.547:ccMapGUIDtoGCI:Calling update_gtd_in_raw_msg_buffer *Aug 8 06:32:21.547:update_gtd_in_raw_msg_buffer:Inserting 124 byte GTD string into rawmsg buffer. The new gtd string is: *Aug 8 06:32:21.547:gtd msg = "IAM, PRN,isdn*,,, USI,rate,c,d,c,1 TMR,01 CPN,00,,1,9999 CPC,09 FCI,,,,,,,y, GCI,7ba32c886c2c11d48005b0f6ff40a2c1" *Aug 8 06:32:21.547:update_gtd_in_raw_msg_buffer:Original rawmsg buf length is 115 the original gtd length was 86 the new gtd length is = 124 *Aug 8 06:32:21.547:update_gtd_in_raw_msg_buffer:New data and IE inserted in rawmsg buff, rawmsg buf length is now 153 *Aug 8 06:32:21.551:Have gtd msg, length=124: *Aug 8 06:32:21.551:gtd msg = "IAM, PRN,isdn*,,, USI,rate,c,d,c,1 TMR,01 CPN,00,,1,9999 CPC,09 FCI,,,,,,,y, GCI,7ba32c886c2c11d48005b0f6ff40a2c1" *Aug 8 06:32:21.555:Have gtd msg, length=124: *Aug 8 06:32:21.555:gtd msg = "IAM, PRN,isdn*,,, USI,rate,c,d,c,1 TMR,01 CPN,00,,1,9999 CPC,09 FCI,,,,,,,y, GCI,7ba32c886c2c11d48005b0f6ff40a2c1" *Aug 8 06:32:21.559:ccMapGUIDtoGCI:GTD Parm GCI is present:7ba32c886c2c11d48005b0f6ff40a2c1, just returning *Aug 8 06:32:21.559:ccGTDExtractParm:Starting *Aug 8 06:32:21.559: tunnelledPtype = 2 *Aug 8 06:32:21.559: gtdInstance = 0 *Aug 8 06:32:21.559: gtdBitMap = 0xFFFBFFFF *Aug 8 06:32:21.559:ccGTDExtractParm:TunnelledContent has GTD message *Aug 8 06:32:21.559:gtd msg = "IAM, PRN,isdn*,,, USI,rate,c,d,c,1 TMR,01 CPN,00,,1,9999 CPC,09 FCI,,,,,,,y, GCI,7ba32c886c2c11d48005b0f6ff40a2c1" *Aug 8 06:32:21.559:ccGTDExtractParm:GTD Parm CPC obtained *Aug 8 06:32:21.559:ccGTDExtractParm:GTD Parm TMR obtained *Aug 8 06:32:21.563:ccGTDExtractParm:GTD Parm PRN obtained *Aug 8 06:32:21.563:ISDN Se3:23 Q931:TX -> CALL_PROC pd = 8 callref = 0x8002 Channel ID i = 0xA98397 Exclusive, Channel 23 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 215 ISDN GTD for Setup Message Troubleshooting Tips
- 228. Configuration Examples forISDN Generic Transparency Descriptor (GTD) for Setup Message GTD Mapping Example The following example shows that GTD mapping is enabled: enable configure terminal interface isdn gtd The GTD feature is different from the isdn mapcommand.Note OLI IE Example The following example shows that the OLI IE identifier for interfacing to an MCI switch is set to 7F: enable configure terminal interface isdn ie oli 7F OLI IE and GTD Example The following example shows that the isdn gtd command is disabled and that the OLI IE identifier is set to 1F in the D channel of the T1 line in slot 3 (serial3:23): Router# show running-config Building configuration... Current configuration :4112 bytes ! version 12.2 no parser cache service timestamps debug datetime msec service timestamps log uptime no service password-encryption ! hostname Router ! boot system flash:c5300-i-mz.122-4.2 no logging buffered enable secret enable password ! username guam password username user1 password username user2 password spe 2/0 2/7 firmware location system:/ucode/mica_port_firmware ! resource-pool disable ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 216 ISDN GTD for Setup Message Configuration Examples for ISDN Generic Transparency Descriptor (GTD) for Setup Message
- 229. ! ip subnet-zero no ipdomain lookup ip domain name cisco.com ip host nlab-boot 172.21.200.2 ip host dirt 172.69.1.129 ip host dsbu-web.cisco.com 172.19.192.254 172.71.162.82 ip host lab 172.19.192.254 ! isdn switch-type primary-ni isdn gateway-max-interworking ! trunk group 1 carrier-id cd1 max-retry 2 hunt-scheme random ! trunk group 2 max-retry 2 hunt-scheme random ! voice service voip ! no voice hpi capture buffer no voice hpi capture destination ! fax interface-type modem mta receive maximum-recipients 0 ! controller T1 0 framing esf clock source line primary linecode b8zs pri-group timeslots 1-24 nfas_d primary nfas_int 0 nfas_group 0 no yellow generation no yellow detection ! controller T1 1 framing esf clock source line secondary 1 linecode b8zs pri-group timeslots 1-24 nfas_d backup nfas_int 1 nfas_group 0 no yellow generation no yellow detection ! controller T1 2 framing esf linecode b8zs pri-group timeslots 1-24 nfas_d none nfas_int 2 nfas_group 0 no yellow generation no yellow detection ! controller T1 3 framing esf linecode b8zs pri-group timeslots 1-24 no yellow generation no yellow detection ! interface Ethernet0 ip address 10.0.44.29 255.255.255.0 no ip route-cache no ip mroute-cache no cdp enable ! interface Serial0:23 ip address 10.1.1.2 255.255.255.0 dialer map ip 10.1.1.1 name host 1111 dialer-group 1 isdn switch-type primary-ni isdn protocol-emulate network isdn T310 30000 isdn negotiate-bchan ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 217 ISDN GTD for Setup Message OLI IE and GTD Example
- 230. isdn bchan-number-order descending nocdp enable ! interface Serial3:23 ip address 10.9.9.9 255.255.255.0 dialer map ip 10.8.8.8 name host 8888 dialer map ip 10.8.8.8 255.255.255.0 dialer-group 1 isdn switch-type primary-net5 isdn protocol-emulate network isdn incoming-voice modem isdn disconnect-cause 126 no isdn outgoing display-ie isdn ie oli 1F no isdn gtd no cdp enable ! interface FastEthernet0 no ip address no ip route-cache no ip mroute-cache shutdown duplex auto speed auto no cdp enable ! interface Group-Async1 no ip address encapsulation ppp dialer in-band dialer-group 1 no keepalive group-range 1 96 ! interface Dialer1 ip address 10.2.2.2 255.255.255.0 encapsulation ppp no ip route-cache no ip mroute-cache dialer remote-name host dialer-group 1 no fair-queue ! interface Dialer2 no ip address no cdp enable ! interface Dialer5 ip address 10.1.1.1 255.0.0.0 encapsulation ppp no ip route-cache no ip mroute-cache dialer in-band dialer map ip 10.1.1.2 name host 1234567 dialer-group 1 ppp authentication chap ! ip default-gateway 10.0.44.1 ip classless ip route 0.0.0.0 0.0.0.0 10.0.44.1 ip route 0.0.0.0 0.0.0.0 Ethernet0 no ip http server ! access-list 101 permit ip any any dialer-list 1 protocol ip permit no cdp run ! snmp-server enable traps tty snmp-server enable traps isdn layer2 snmp-server host 10.1.1.1 public ! call rsvp-sync ! ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 218 ISDN GTD for Setup Message OLI IE and GTD Example
- 231. voice-port 0:D ! voice-port 3:D ! mgcpprofile default ! dial-peer cor custom ! dial-peer voice 2 voip destination-pattern 111 session target ipv4:10.0.45.87 ! dial-peer voice 10 pots destination-pattern 9999 direct-inward-dial port 3:D prefix 9999 ! dial-peer voice 20 voip destination-pattern 000000002. session target ipv4:10.0.44.28 ! dial-peer voice 50 pots destination-pattern 2222 direct-inward-dial port 0:D prefix 2222 ! alias exec c conf t ! line con 0 exec-timeout 0 0 logging synchronous line 1 96 no flush-at-activation modem InOut transport input all transport output lat pad telnet rlogin udptn v120 lapb-ta line aux 0 line vty 0 4 password login ! end Additional References General ISDN References • "Overview of ISDN Voice Interfaces" --Describes relevant underlying technology; lists related documents, standards, MIBs, and RFCs; and describes how to obtain technical assistance • "Additional References" section --Lists additional ISDN references References Mentioned in This Chapter • RADIUS VSA Voice Implementation Guide at http://www.cisco.com/univercd/cc/td/doc/product/access/ acs_serv/vapp_dev/vsaig3.htm • Tcl IVR API Version 2.0 Programmer's Guide at http://www.cisco.com/univercd/cc/td/doc/product/ access/acs_serv/vapp_dev/tclivrv2/index.htm ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 219 ISDN GTD for Setup Message Additional References
- 232. ISDN Voice ConfigurationGuide, Cisco IOS Release 15M&T 220 ISDN GTD for Setup Message Additional References
- 233. C H AP T E R 9 NFAS with D-Channel Backup This chapter describes how to implement the Non-Facility Associated Signaling (NFAS) with D-Channel Backup feature with two new switch types: DMS100 and NI2. ISDN NFAS allows a single D channel to control multiple ISDN PRI interfaces. You can configure a backup D channel for use when the primary NFAS D channel fails. After you configure channelized T1 controllers for ISDN PRI, you only need to configure the NFAS primary D channel; its configuration is distributed to all the members of the associated NFAS group. A controller configured with backup D channel loses one B channel.Note Use of a single D channel to control up to 10 PRI interfaces can free one B channel on each interface to carry other traffic. Any hard failure causes a switchover to the backup D channel and currently connected calls remain connected. The backup D channel cannot be used for data transfer. On the Nortel dms100 switch, when a single D channel is shared, multiple PRI interfaces may be configured in a single trunk group. The additional use of alternate route indexing, which is a feature of the dms100 switch, provides a rotary from one trunk group to another. This enables the capability of building large trunk groups in a public switched network. Note Feature History for NFAS with D-Channel Backup ModificationRelease This feature was introduced.12.1(5)XM This feature was implemented on the Cisco AS5850 platform. 12.2(11)T NFAS network-side support was added.12.4(24)T ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 221
- 234. • Finding FeatureInformation, page 222 • Prerequisites for Configuring NFAS with D-Channel Backup, page 222 • Restrictions for Configuring NFAS with D-Channel Backup, page 222 • Information about NFAS, page 223 • How to Configure NFAS with D-Channel Backup, page 223 • Configuration Examples for NFAS with D-Channel Backup, page 230 • Additional References, page 232 Finding Feature Information Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required. Prerequisites for Configuring NFAS with D-Channel Backup • Perform the prerequisites that are listed in the "Prerequisites for Configuring an ISDN Voice Interface" section. • Configure your router’s channelized T1 controllers for ISDN, as described in the "Configuring ISDN PRI" section of the "Configuring Channelized E1 and Channelized T1" chapter in the Dial Solutions Quick Configuration Guide. Restrictions for Configuring NFAS with D-Channel Backup Restrictions are described in "Restrictions for Configuring ISDN Voice Interfaces". In addition, the following apply: • NFAS is supported with only a channelized T1 controller and, as a result, is ISDN PRI capable. • NFAS is supported across multiple T1 controllers installed on different slots only if the DSPs of those slots are of the same type. For example, if T1 controllers on slot 1 and slot 2 are combined to form an NFAS group with the T1 in slot 1 being primary, both slots must have the same type of DSP. If these two slots have different DSP types, only those calls using T1 on slot 1 will connect --all calls through T1 on slot 2 will fail with a disconnect cause of "Resource Unavailable/Unspecified (47)." • The router must connect to either a 4ess, dms250, dms100, or National ISDN switch type. The table below shows applicable ISDN switch types and supported NFAS types. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 222 NFAS with D-Channel Backup Finding Feature Information
- 235. Table 47: ISDNSwitch Types and Supported NFAS Types NFAS TypeISDN Switch Type Custom NFASLucent 4ESS Custom NFASNortel DMS250 Custom NFASNortel DMS100 Custom; does not support NFASLucent 5ESS NI-2 NFASLucent 5ESS NI-2 NFASAGCS GTD5 NI-2 NFASOther switch types Network-side emulationNetwork-side Information about NFAS Non-Facility Associated Signaling is a classification of signalling protocols that provide the signalling channel in a separate physical line from the bearer channels. General information about ISDN voice interfaces is presented in the "Information About ISDN Voice Interfaces" section. Note How to Configure NFAS with D-Channel Backup Configuring NFAS on PRI Groups To configure NFAS on PRI groups, perform the following steps. When a backup NFAS D channel is configured and the primary NFAS D channel fails, rollover to the backup D channel is automatic and all connected calls stay connected. If the primary NFAS D channel recovers, the backup NFAS D channel remains active and does not switch over again unless the backup NFAS D channel fails. Note ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 223 NFAS with D-Channel Backup Information about NFAS
- 236. SUMMARY STEPS 1. enable 2.configure terminal 3. controller {t1 | e1} controller-number 4. pri-group timeslots range nfas_d primary nfas_interface number nfas_group number 5. pri-group timeslots range nfas_d backup nfas_interface number nfas_group number 6. pri-group timeslots range nfas_d none nfas_int number nfas_group number 7. exit DETAILED STEPS PurposeCommand or Action Enters privileged EXEC mode. Enter your password when prompted. enable Example: Router> enable Step 1 Enters configuration mode.configure terminal Example: Router# configure terminal Step 2 Enters controller configuration mode for the specified controller number. controller {t1 | e1} controller-number Example: Router(config)# controller t1 3 Step 3 Configures, on one channelized T1 controller, the NFAS primary D channel. Keywords are as follows: pri-group timeslots range nfas_d primary nfas_interface number nfas_group number Step 4 Example: Router(config-controller)# pri-group timeslots • nfas_interface number --Value assigned by the service provider to ensure unique identification of a PRI interface. • nfas_group number --Group identifier unique on the router. Multiple NFAS groups can exist on the router. 1-24 nfas_d primary nfas_interface 1 nfas_group 1 The interface number is the number of the interface assigned to an interface that is part of an nfas group. All interfaces that are part of an nfas group have the same group number and each is identified uniquely within the group by the interface number. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 224 NFAS with D-Channel Backup Configuring NFAS on PRI Groups
- 237. PurposeCommand or Action Configures,on a different channelized T1 controller, the NFAS backup D channel to be used if the primary D channel fails. Keywords are as above. pri-group timeslots range nfas_d backup nfas_interface number nfas_group number Example: Router(config-controller)# pri-group timeslots Step 5 Repeat this step on other channelized T1 controllers, as appropriate. 1-24 nfas_d backup nfas_interface 2 nfas_group 1 (Optional) Configures, on other channelized T1 controllers, a 24 B channel interface, if desired. pri-group timeslots range nfas_d none nfas_int number nfas_group number Example: Router(config-controller)# pri-group timeslots 1-24 nfas_d none nfas_int 3 nfas_group 1 Step 6 Exits the current mode.exit Example: Router(config-controller)# exit Step 7 Configuring a VoIP Dial Peer for NFAS Voice To configure a VoIP dial peer for NFAS voice, perform the following steps. Dial peers are used by the Cisco IOS voice stack for handling calls going from the PSTN to the VoIP side or vice versa. The dial-peer configuration for each NFAS controller should contain the primary of the NFAS group. Note SUMMARY STEPS 1. enable 2. configure terminal 3. dial-peer voice tag voip 4. port controller :D 5. exit ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 225 NFAS with D-Channel Backup Configuring a VoIP Dial Peer for NFAS Voice
- 238. DETAILED STEPS PurposeCommand orAction Enters privileged EXEC mode. Enter your password when prompted. enable Example: Router> enable Step 1 Enters configuration mode.configure terminal Example: Router# configure terminal Step 2 Enters dial-peer configuration mode for the specified VoIP dial peer. dial-peer voice tag voip Example: Router(config)# dial-peer voice 99 voip Step 3 Associates the dial peer with a specific voice port--in this case, the D channel associated with ISDN PRI for the NFAS primary. port controller :D Example: Router(config-dial-peer)# port 4:D Step 4 Exits the current mode.exit Example: Router(config-dial-peer)# exit Step 5 Disabling a Channel or Interface To disable a channel or interface, perform the following steps. You can disable a specified channel or an entire PRI, thus taking it out of service or put it into one of the other states that is passed in to the switch. Note ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 226 NFAS with D-Channel Backup Disabling a Channel or Interface
- 239. SUMMARY STEPS 1. enable 2.configure terminal 3. interface serial controller-number : timeslot 4. isdn service [dsl number | nfas_int number] b_channel number state{0 | 1 | 2} 5. isdn service [dsl number | nfas_int number] b_channel number state {0 | 1 | 2} 6. exit DETAILED STEPS PurposeCommand or Action Enters privileged EXEC mode. Enter your password when prompted. enable Example: Router> enable Step 1 Enters configuration mode.configure terminal Example: Router# configure terminal Step 2 Enters interface configuration mode and specifies a serial interface for ISDN PRI, channel-associated signaling, or robbed-bit signaling. interface serial controller-number : timeslot Example: Router(config)# interface serial 4/1:23 Step 3 Takes an individual B channel out of service or sets it to a different state. State values are as follows: isdn service [dsl number | nfas_int number] b_channel number state{0 | 1 | 2} Step 4 Example: Router(config-if)# isdn service nfas_int 3 b_channel 1 state 1 • 0 --In service • 1 --Maintenance • 2 --Out of service As above. Setting the b-channel number to 0 sets the entire PRI interface to a specified state value. isdn service [dsl number | nfas_int number] b_channel number state {0 | 1 | 2} Example: Router(config-if)# isdn service nfas_int 3 b_channel 0 state 1 Step 5 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 227 NFAS with D-Channel Backup Disabling a Channel or Interface
- 240. PurposeCommand or Action Exitsthe current mode.exit Example: Router(config-if)# exit Step 6 Verifying NFAS Configuration To verify NFAS configuration, perform the following steps (listed alphabetically). SUMMARY STEPS 1. show dial-peer voice 2. show isdn nfas group 3. show isdn service 4. show isdn status 5. show running-config DETAILED STEPS Step 1 show dial-peer voice Use this command to display the configuration information for dial peers. Example: Router# show dial-peer voice VoiceOverIpPeer1 information type = voice, tag = 1, destination-pattern = `', answer-address = `', preference=0, numbering Type = `unknown' group = 1, Admin state is up, Operation state is down, incoming called-number = `', connections/maximum = 0/unlimited, DTMF Relay = disabled, modem passthrough = system, huntstop = disabled, in bound application associated: DEFAULT out bound application associated: permission :both incoming COR list:maximum capability outgoing COR list:minimum requirement type = voip, session-target = `', technology prefix: settle-call = disabled ip precedence = 0, UDP checksum = disabled, session-protocol = cisco, session-transport = udp, req-qos = best-effor acc-qos = best-effort, fax rate = voice, payload size = 20 bytes fax protocol = system fax NSF = 0xAD0051 (default) ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 228 NFAS with D-Channel Backup Verifying NFAS Configuration
- 241. codec = g729r8,payload size = 20 bytes, Expect factor = 0, Icpif = 20, Playout: Mode adaptive, Expect factor = 0, Max Redirects = 1, Icpif = 20,signaling-type = cas, CLID Restrict = disabled VAD = enabled, Poor QOV Trap = disabled, voice class perm tag = `' Connect Time = 0, Charged Units = 0, Successful Calls = 0, Failed Calls = 0, Accepted Calls = 0, Refused Calls = 0, Last Disconnect Cause is "", Last Disconnect Text is "", Last Setup Time = 0. Step 2 show isdn nfas group Use this command to display information about members of an NFAS group. Example: Router# show isdn nfas group 1 ISDN NFAS GROUP 1 ENTRIES: The primary D is Serial1/0:23. The backup D is Serial1/1:23. The NFAS member is Serial2/0:23. There are 3 total nfas members. There are 93 total available B channels. The primary D-channel is DSL 0 in state INITIALIZED. The backup D-channel is DSL 1 in state INITIALIZED. The current active layer 2 DSL is 1. Step 3 show isdn service Use this command to display information about ISDN channels and the service states. Step 4 show isdn status Use this command to display the status of all ISDN interfaces, including active layers, timer information, and switch-type settings. Step 5 show running-config Use this command to display the basic router configuration. Examples This section provides the following output examples: Sample Output for the show isdn nfas group Command The following three examples show D channel state changes when rollover occurs from the primary NFAS D channel to the backup D channel. The first example shows the output with the primary D channel in service and the backup D channel in standby. Router# show isdn nfas group 0 ISDN NFAS GROUP 0 ENTRIES: The primary D is Serial1/0:23. The backup D is Serial1/1:23. The NFAS member is Serial2/0:23. There are 3 total nfas members. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 229 NFAS with D-Channel Backup Verifying NFAS Configuration
- 242. There are 70total available B channels. The primary D-channel is DSL 0 in state IN SERVICE. The backup D-channel is DSL 1 in state STANDBY. The current active layer 2 DSL is 0. The following example shows output during rollover. The configured primary D channel is in maintenance busy state and the backup D channel is waiting. Router# show isdn nfas group 0 ISDN NFAS GROUP 0 ENTRIES: The primary D is Serial1/0:23. The backup D is Serial1/1:23. The NFAS member is Serial2/0:23. There are 3 total nfas members. There are 70 total available B channels. The primary D-channel is DSL 0 in state MAINTENANCE BUSY. The backup D-channel is DSL 1 in state WAIT. The current active layer 2 DSL is 1. The following example shows output when rollover is complete. The configured primary D channel is now in standby and the backup D channel is in service. Router# show isdn nfas group 0 ISDN NFAS GROUP 0 ENTRIES: The primary D is Serial1/0:23. The backup D is Serial1/1:23. The NFAS member is Serial2/0:23. There are 3 total nfas members. There are 70 total available B channels. The primary D-channel is DSL 0 in state STANDBY. The backup D-channel is DSL 1 in state IN SERVICE. The current active layer 2 DSL is 1. Configuration Examples for NFAS with D-Channel Backup NFAS Primary and Backup D Channels Example The following example configures ISDN PRI and NFAS on multiple T1 controllers of a Cisco 7500 series router. The D-channel of T1 1/0/0 is configured as primary D-channel and T1 1/0/1 is configured as backup D-channel. Once you configure the NFAS primary D channel, that channel is the only interface you see and have to configure. version 12.x service timestamps debug datetime msec localtime show-timezone service timestamps log datetime msec localtime show-timezone service password-encryption ! hostname travis-nas-01 ! aaa new-model aaa authentication login default local aaa authentication login NO_AUTHENT none aaa authorization exec default local if-authenticated aaa authorization exec NO_AUTHOR none aaa authorization commands 15 default local if-authenticated aaa authorization commands 15 NO_AUTHOR none aaa accounting exec default start-stop group tacacs+ aaa accounting exec NO_ACCOUNT none aaa accounting commands 15 default stop-only group tacacs+ aaa accounting commands 15 NO_ACCOUNT none enable secret 5 $1$LsoW$K/qBH9Ih2WstUxvazDgmY/ ! username admin privilege 15 password 7 06455E365E471D1C17 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 230 NFAS with D-Channel Backup Configuration Examples for NFAS with D-Channel Backup
- 243. username gmcmilla password7 071824404D06140044 username krist privilege 15 password 7 0832454D01181118 ! call rsvp-sync shelf-id 0 router-shelf shelf-id 1 dial-shelf ! resource-pool disable ! modem-pool Default pool-range 1/2/0-1/2/143,1/3/0-1/3/143 ! clock timezone CST -6 clock summer-time CST recurring ! ip subnet-zero ip domain-name cisco.com ip name-server 172.22.53.210 ip name-server 171.69.2.133 ip name-server 171.69.2.132 ip name-server 171.69.11.48 ! isdn switch-type primary-5ess isdn voice-call-failure 0 ! controller T1 1/0/0 framing esf linecode b8zs pri-group timeslots 1-24 nfas_d primary nfas_interface 1 nfas_group 1 description PacBell 3241933 ! controller T1 1/0/1 framing esf linecode b8zs pri-group timeslots 1-24 nfas_d backup nfas_interface 2 nfas_group 1 description PacBell 3241933 ! interface Loopback0 ip address 172.21.10.1 255.255.255.255 ! interface FastEthernet0/0/0 ip address 172.21.101.20 255.255.255.0 half-duplex ! interface Serial1/0/0:23 no ip address ip mroute-cache isdn switch-type primary-5ess isdn incoming-voice modem no cdp enable ! interface Group-Async0 no ip address group-range 1/2/00 1/3/143 ! router eigrp 1 network 172.21.0.0 no eigrp log-neighbor-changes ! ip classless ip route 0.0.0.0 0.0.0.0 172.21.101.1 ip http server ip http authentication aaa ! snmp-server engineID local 0000000902000030F2F51400 snmp-server community 5urf5h0p RO snmp-server community 5crapmeta1 RW snmp-server community SNMPv1 view v1default RO ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 231 NFAS with D-Channel Backup NFAS Primary and Backup D Channels Example
- 244. POTS Dial-Peer ConfigurationExample The following example shows configuration of a POTS dial peer with the primary controller of an NFAS group: dial-peer voice 35 pots incoming called-number 45... destination-pattern 35... direct-inward-dial port 1/0/0:D prefix 35 PRI Service State Example The following example reenables the entire PRI after it was disabled: isdn service dsl 0 b-channel 0 state 0 Additional References General ISDN References • "Overview of ISDN Voice Interfaces" --Describes relevant underlying technology; lists related documents, standards, MIBs, and RFCs; and describes how to obtain technical assistance • "Additional References" section --Lists additional ISDN references ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 232 NFAS with D-Channel Backup POTS Dial-Peer Configuration Example
- 245. C H AP T E R 10 PRI Backhaul and IUA Support Using SCTP This chapter describes how to implement Stream Control Transmission Protocol (SCTP) features. SCTP is not explicitly configured on routers, but it underlies several Cisco applications. This chapter describes how to configure several features that use SCTP and how to troubleshoot SCTP problems. SCTP is used with the following Cisco IOS software features: • PRI Backhaul Using SCTP and the ISDN Q.921 User Adaptation Layer • Support for IUA with SCTP for Cisco Access Servers Feature History for PRI Backhaul Using SCTP and the ISDN Q.921 User Adaptation Layer ModificationRelease This feature was introduced on the Cisco AS5300.12.1(1)T This feature was introduced on the Cisco 2600 series, Cisco 3600 series, and Cisco MC3810 series. 12.2(4)T This feature was implemented on the Cisco AS5850.12.2(2)XB1 Feature History for Support for IUA with SCTP for Cisco Access Servers ModificationRelease This feature was introduced.12.2(15)T • Finding Feature Information, page 234 • Prerequisites for Implementing SCTP Features, page 234 • Restrictions for Implementing SCTP Features, page 234 • Information About SCTP and SCTP Features, page 235 • How to Configure SCTP Features, page 244 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 233
- 246. • Configuration Examplesfor SCTP Options, page 275 • Additional References, page 287 Finding Feature Information Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required. Prerequisites for Implementing SCTP Features • Perform the prerequisites that are listed in the "Prerequisites for Configuring an ISDN Voice Interface" section. PRI Backhaul Using SCTP and the ISDN Q.921 User Adaptation Layer Feature • Configure ISDN to backhaul Q.921 signaling to the media gateway controller • For Cisco AS5850, install or implement the following: • MGCP 1.0 • IUA 0.4 • ISDN network-side support to terminate multiple voice PRIs Restrictions for Implementing SCTP Features Restrictions are described in the "Restrictions for Configuring ISDN Voice Interfaces" section. In addition, the following apply. PRI Backhaul Using SCTP and the ISDN Q.921 User Adaptation Layer Feature • Backhaul: Does not support backhauling for Basic Rate Interface (BRI). • Capacity: Supports only two application-server processes (ASPs) per application server. Supports only three explicit IP addresses per SCTP association endpoint. • IUA messages: Does not support new-traffic failover. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 234 PRI Backhaul and IUA Support Using SCTP Finding Feature Information
- 247. The IUA specificationdescribes an optional feature known as New Traffic Failover. In this process, all messages for calls pending completion during failover are sent to the inactive media-gateway controller, and messages for new calls are sent to the newly active controller. These IUA messages for new calls are not supported. Note • Load balancing: Does not support load balancing between ASPs on a per-call basis. • Platforms: Is not supported on the Cisco 2600XM series, Cisco 2691, Cisco 2800 series, Cisco 3700 series, and Cisco 3800 series. • Signaling: Supports Facility Associated Signaling (FAS) and Non-Facility Associated Signaling (NFAS) PRI D-channel signaling only; does not support any other signaling protocols, including NFAS with backup D-channel signaling. Support for IUA with SCTP for Cisco Access Servers Feature • Backhaul: Does not support Q.931 PRI backhaul on the Cisco PGW 2200. • Platforms: Is not supported on the Cisco 2600XM series or Cisco 2691. • Transport: Does not support concurrent Redundant Link Manager (RLM) and SCTP transport on the access-server gateway. You can configure one or the other but not both at the same time. For more information about the Cisco PGW 2200, see Support for IUA with SCTP.Note • For more information about IUA with SCTP, see Support for IUA with SCTP for Cisco Access Servers. Information About SCTP and SCTP Features The following is an example of an application-server configuration on a gateway: AS as1 10.4.8.69 10.4.9.69 2577 Application server as1 is configured to use two local IP addresses and port 2577. IP address values that are set apply to all IP addresses of the application-server process. An application-server process can be viewed as a local representation of an SCTP association since it specifies a remote endpoint that communicates with an application-server local endpoint. An application-server process is defined for a given application server. For example, the following configuration defines remote signaling controller asp1 at two IP addresses for application server as1. The remote SCTP port number is 2577: AS as1 10.4.8.69 10.4.9.69 2477 ASP asp1 AS as1 10.4.8.68 10.4.9.68 2577 Multiple application-server processes can be defined for a single application server for the purpose of redundancy, but only one process can be active. The other process is inactive and becomes active at failover. In the Cisco media-gateway-controller solution, a signaling controller is always the client that initiates association with a gateway. During initiation, you can request outbound and inbound stream numbers, but the ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 235 PRI Backhaul and IUA Support Using SCTP Information About SCTP and SCTP Features
- 248. gateway allows onlya number that is at least one digit higher than the number of interfaces (T1/E1) allowed for the platform. The number of streams to assign to a given association is implementation dependent. During initialization of the IUA association, you need to specify the total number of streams that can be used. Each D channel is associated with a specific stream within the association. With multiple-trunk-group support, every interface can potentially be a separate D channel. At startup, the IUA code checks for all the possible T1, E1, or T3 interfaces and sets the total number of inbound and outbound streams supported accordingly. In most cases, there is only a need for one association between the GW and the media gateway controller. For the rare case that you are configuring multiple application server associations to various media gateway controllers, the overhead from the unused streams would have minimal impact. The NFAS D channels are configured for one or more interfaces, where each interface is assigned a unique stream ID. The total number of streams for the association needs to include an additional stream for the SCTP management messages. So during startup the IUA code adds one to the total number of interfaces (streams) found. You can manually configure the number of streams per association. In the backhaul scenario, if the number of D-channel links is limited to one, allowing the number of streams to be configurable avoids the unnecessary allocation of streams in an association that will never be used. For multiple associations between a GW and multiple media gateway controllers, the configuration utility is useful in providing only the necessary number of streams per association. Overhead from the streams allocated but not used in the association is negligible. If you manually configure the number of streams through the CLI, the IUA code cannot distinguish between a startup event, which automatically sets the streams to the number of interfaces, or if the value is set manually during runtime. If you configure the number of SCTP streams manually, you must add one plus the number of interfaces using the sctp-streams keyword. Otherwise, IUA needs always to add one for the management stream, and the total number of streams increments by one after every reload. When you set the SCTP stream with the command-line interface, you cannot change the inbound and outbound stream support once the association is established with SCTP. The value takes effect when you first remove the IUA application server configuration and then configure it back as the same application server or a new one. The other option is to reload the router. General information about ISDN voice interfaces is presented in the "Information About ISDN Voice Interfaces" section on page 4 . Note SCTP Topology SCTP is a reliable datagram-oriented IP transport protocol specified by RFC 2960. It provides the layer between an SCTP user application and an unreliable end-to-end datagram service such as IP. The basic service offered by SCTP is the reliable transfer of user datagrams between peer SCTP users, within the context of an association between two SCTP hosts. SCTP is connection-oriented, but SCTP association is a broader concept than, for example, TCP connection. SCTP provides the means for each SCTP endpoint to provide its peer with a list of transport addresses during association startup (address and UDP port combinations, for example) through which that endpoint can be reached and from which messages originate. The association spans transfer over all of the possible source and destination combinations that might be generated from the two endpoint lists (also known as multihoming). SCTP provides the following services and features: ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 236 PRI Backhaul and IUA Support Using SCTP SCTP Topology
- 249. • Acknowledged reliablenonduplicated transfer of user data • Application-level segmentation to conform to the maximum transmission unit (MTU) size • Sequenced delivery of user datagrams within multiple streams • Optional multiplexing of user datagrams into SCTP datagrams • Enhanced reliability through support of multihoming at either end or both ends of the association • Congestion avoidance and resistance to flooding and masquerade attacks • Interoperability with third-party call agents SCTP allows you to terminate multiple switches and trunk groups on a gateway to add scalability. Adding trunk groups does not require more memory or processing resources because SCTP supports multiple streams in a single SCTP association. SCTP is a reliable transport protocol for message-oriented communications; SCTP is specifically designed to support PSTN signaling messages over IP networks. SCTP allows you to configure at least one trunk group per T1 or E1 interface available on a given platform. A gateway platform with four T1 or E1 interfaces, for example, can control four unique trunk groups per device. Certain platforms, such as the Cisco AS5800 and Cisco AS5850, can deliver the individual T1 or E1 trunk groups over a high-speed interface, such as T3, which operates at 45 Mbps. The table below shows the number of trunk groups supported per gateway platform. Table 48: SS7 Interconnect for Voice-Gateway Trunk Groups per Gateway CommentsSupported Trunk GroupsPlatform Verify both T1 and E1 cards.4Cisco AS5300 Verify both T1 and E1 cards. Verify with Integrated SLT option. For more information, see Integrated Signaling Link Terminal , Cisco IOS Release 12.2(11)T. Note 8Cisco AS5350 Verify CT3 DS-3 card. Verify with Integrated SLT option. 28Cisco AS5350 CT3 Verify both T1 and E1 cards. Verify with Integrated SLT option. 16Cisco AS5400 Verify CT3 DS-3 card. Verify with Integrated SLT option. 28Cisco AS5400 CT3 Verify E1 cards and CT3 DS-3 cards. T1 ports and the 112 supported trunk groups are available only with CT3 cards. Note 112Cisco AS5850 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 237 PRI Backhaul and IUA Support Using SCTP SCTP Topology
- 250. In a typicalnetwork topology, only one SCTP association is configured between a signaling controller and a gateway. Multiple IP addresses on either side can be designated to the same association to achieve link redundancy. On a gateway, signaling messages for all trunk groups are carried over on the same SCTP association to the same signaling controller. Trunk groups on a gateway can also be controlled through different signaling controllers. In such cases, you can configure multiple associations on a gateway and direct them to different signaling controllers. IUA IUA is the adaptation layer that makes SCTP services available to Q.921 services users, such as Q.931, Q Signaling (QSIG), and National ISDN-2 with Cisco extensions (Cisco NI2+). IUA supports the standard interlayer primitives provided by Q.921. As a result, an upper-layer protocol (ULP) that typically used Q.921 services can easily migrate to IUA. IUA service points are represented to the upper-layer protocol as application servers. Each application server is bound to an SCTP local endpoint managed by an SCTP instance. A remote signaling controller is known as an ASP. An ASP is connected to the local endpoint through a single SCTP association. The IUA module creates associations between the signaling gateway and the MGC based on configuration requests. It also manages multiple ASPs as defined in the IETF IUA specification. IUA performs the following functions: • Requests SCTP associations based on configuration information. • Manages the destination address list and requests a new primary destination in the event of a failure. • Manages the ASP state machine for each association. • Manages the application-server state machine across all ASPs associated with a single application. • Provides service for multiple applications simultaneously to handle different Layer 3 signaling protocols (Q.931 and Q.SIG, for example), or to communicate with different sets of call agents. The figure below shows IUA with SCTP transport stack. Figure 8: IUA with SCTP Transport Stack ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 238 PRI Backhaul and IUA Support Using SCTP IUA
- 251. To use IUAservices, you must make the application server and ASP available and bind a trunk group to an application server for its Layer 2 server. For configuration information, see the Configuring IUA, on page 244. Multiple NFAS Groups On a gateway, trunk groups are defined as Non-Facility Associated Signaling (NFAS) groups. An NFAS group is a group of ISDN PRI trunks with a single dedicated D channel. In a voice-gateway solution, the D channel in a trunk group is symbolic because SS7 is used as the signaling mechanism. The D channels defined for each NFAS group are actually DS0 bearer channels for voice or modem calls. Therefore, each NFAS has a corresponding D channel for which it is allocated. A symbolic D-channel interface is dedicated to a trunk group. Each D-channel interface is bound to an application server and a dedicated stream is associated with this interface. Thus, the NFAS group identification can be recovered on each side of the SCTP association through this two-stage mapping as long as both sides share the same configuration information. Multiplexing of multiple trunk groups through a single association is accomplished this way, for example. If all interfaces on a gateway are controlled through a single SC, all interfaces are bound to the same application server. The SCTP stream is a logical identification of the grouping of messages and consumes little additional memory and processing power. Each association can support as many as 65,355 streams. The figure below shows the mapping between the trunk group, D-channel interface, and SCTP stream. Figure 9: Mapping Between Trunk Group, Interface, and Stream ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 239 PRI Backhaul and IUA Support Using SCTP Multiple NFAS Groups
- 252. The figure belowshows the NFAS group and SCTP association. Figure 10: NFAS Group and SCTP Association The IUA transport protocol using SCTP is supported on the Cisco PGW 2200; the Cisco PGW 2200 now uses IUA to communicate with Cisco access servers. IUA with SCTP on the Cisco PGW 2200 provides the following services: • Eliminates the scaling limitations in previous releases of Cisco MGC software for the number of NFAS-groups allowed per RLM. • Supports upgrading from RLM-based communication to IUA-based communication without losing stable active calls. • RLM-based communication is still supported. However, since this is a new functionality, the backward compatibility of the SCTP-based transports is not applicable. • IUA interface can be used with Cisco access servers that support NAS and Digital Private Network Signaling System (DPNSS) signaling. • Introduces IUA and SCTP operational measurements. For more information about IUA and SCTP on the Cisco PGW 2200, see Support for IUA with SCTP .Note Features That Use SCTP The following features use SCTP: ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 240 PRI Backhaul and IUA Support Using SCTP Features That Use SCTP
- 253. PRI Backhaul UsingSCTP and the ISDN Q.921 User Adaptation Layer This feature (sometimes called PRI Q.921 Signaling Backhaul) provides standards-based ISDN signaling backhaul capability on Cisco IOS gateways. It fills the need for PRI Q.921 signaling backhaul that works with third-party call agents or media-gateway controllers (MGCs) where call processing for voice calls is carried out by call-control servers, and packet-network connections are made using protocols such as Media Gateway Control Protocol (MGCP) and Simple Gateway Control Protocol (SGCP). It enables solutions such as Integrated Access, IP PBX, and Telecommuter on the Cisco 3600 series, Cisco AS5300, and Cisco AS5850. It provides a configuration interface for Cisco IOS software implementation and implements protocol message flows for SCTP and IUA. This feature provides the following: • PRI backhaul--Specific implementation for backhauling PRI For more information about PRI backhaul using SCTP, see PRI Backhaul Using the Stream Control Transmission Protocol and the ISDN Q.921 User Adaptation Layer. Note • SCTP--New general-transport protocol that can be used for backhauling signaling messages • IDSN User Adaptation Layer (IUA)--Mechanism for backhauling any Layer 3 protocol that normally uses Q.921 This feature supports interoperability with third-party call agents. It also supports the following solutions that require signaling backhaul: • IP PBX • IP Centrex • Enterprise toll bypass • IXC/tandem bypass Signaling backhaul facilitates the handling of voice traffic coming from the signaling endpoints that communicate using facility-associated signaling. Facility-associated signaling requires the signaling channel (channel that carries call-signaling information) to share a digital facility with the bearer channels. ISDN PRI is one example of facility-associated signaling. ISDN signaling backhaul is required in the MGCP-based call-control architecture to enable end-to-end voice solutions. This feature implements the IETF standards-based signaling backhaul protocols. This standards-based signaling transport support enables any third-party call agent that supports the standards to work with Cisco gateways. ISDN signaling backhaul is required in the MGCP-based call-control architecture to enable end-to-end voice solutions. This feature migrates the proprietary PRI backhaul infrastructure to open standards. Backhaul is carried out using industry-standard SCTPs and ISDN IUA protocols as defined by the SIGTRAN working group of the IETF. It supports backhauling for ISDN-based signaling protocols only. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 241 PRI Backhaul and IUA Support Using SCTP Features That Use SCTP
- 254. The figure belowshows an example of PRI signaling backhaul. The MGC provides call processing and gateway control. Figure 11: PRI Signaling Backhaul Ordinarily, signaling backhaul occurs at a common boundary for all protocols. For ISDN, signaling backhaul occurs at the Layer 2 (Q.921) and Layer 3 (Q.931) boundaries. The lower layers of the protocol (Q.921) are terminated and processed on the gateway, while the upper layers (Q.931) are backhauled to the MGC using SCTP. Signaling backhaul provides the advantage of distributed protocol processing. This permits greater expandability and scalability while offloading lower-layer protocol processing from the MGC. Signaling transport between entities is applied to ensure that signaling information is transported with the required functionality and performance. The signaling gateway or MGC receives both ISDN signaling and bearer-channel data. ISDN signaling is backhauled up to an MGC or call agent using the SIG protocol stack. You can configure each signaling gateway to use up to three MGCs within an application server for redundancy. Multiple application servers can also be supported on a signaling gateway. MGCP is then used to control the bearer channels. The figure below shows the functional model for PRI signaling transport. Figure 12: Signaling Transport Model ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 242 PRI Backhaul and IUA Support Using SCTP Features That Use SCTP
- 255. SCTP is apeer-to-peer protocol; IUA is a client-server protocol. The figure below shows the protocol flow from an ISDN endpoint, through the signaling gateway, and then to a call agent or media gateway controller. Figure 13: Protocol Flow PRI Backhaul Using the Stream Control Transmission Protocol and the ISDN Q.921 User Adaptation Layer on the Cisco 3660 supports the following on a Cisco 3660: • 20 calls per hour per DS-0 bearer circuit (3-minute average call duration) • 460 calls per hour per PRI circuit (23 bearer channels): 20 x 23 = 460 • 5520 calls per hour per Cisco 3660 (12 PRI trunks): 460 x 12 = 5520 • 1.5333 calls per Cisco 3660 per second. 5520 divided by (60*60) = 1.5333 • 7 signaling messages per call (both setup and tear down) • 10.8 signaling messages per second per Cisco 3660: 7 x 1.5333 = 10.8 Support for IUA with SCTP for Cisco Access Servers This feature supports IUA with SCTP for the Cisco AS5x00, Cisco 2420, Cisco 2600 series, Cisco 3600 series, and Cisco 3700 series. It is to be used as an alternative to the existing IP-based User Datagram Protocol (UDP)-to-Reliable Link Manager (RLM) transport between the Cisco PGW 2200 and Cisco gateways. IUA with SCTP acts as the call signaling IP transport mechanism in a voice-gateway solution. These combined protocols are also used for Signaling System 7 (SS7) Interconnect solutions, which allow required flexibility in connecting Intermachine trunks from more than one PSTN switch (multiple trunk groups) to the Cisco gateways. This feature also allows you to interconnect with multiple carriers on high-capacity Cisco AS5x00 gateways for load balancing and redundancy. IUA and SCTP protocols provide the following services: • Trunk groups are defined on a T1/E1 interface basis. • All DS0 bearer channels in a specific T1/E1 interface are included in the same trunk group and cannot be split into different trunk groups. • Multiple T1/E1 interfaces on the same gateway can be provisioned in a single trunk group or split into multiple trunk groups. The maximum number of trunk groups that a platform can support is equal to the maximum number of T1/E1 interfaces that the platform can configure. This feature supports SCTP, multiple non-facility associated signaling, and IUA. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 243 PRI Backhaul and IUA Support Using SCTP Features That Use SCTP
- 256. How to ConfigureSCTP Features Configuring PRI Backhaul Using the SCTP and the ISDN Q.921 User Adaptation Layer To configure the PRI Backhaul Using SCTP and the ISDN Q.921 User Adaptation Layer feature, perform the following tasks: When the Fast Ethernet interface is configured for auto negotiation, it can take up to two seconds to initialize. Two examples of the interface initializing is when the no shutdown command is entered, or if the cable is removed and then plugged back in. To avoid any problems, the Fast Ethernet interface should not be configured for auto negotiation. The duplex and speed parameters should be set according to the requirements of the network, and should not be set to auto. Caution Configuring IUA To configure IUA, perform the following steps. The steps below direct you to configure an application server and the ASP first to allow an NI2+ to be bound to the IUA transport layer protocol. The application server is a logical representation of the SCTP local endpoint. The local endpoint can have more than one IP address but must use the same port number. Note Before You Begin • Ensure that Cisco IOS Release 12.2(15)T or later is installed and running on your system. • Configure ISDN to backhaul Q.921 signaling to the third-party call agent (MGC). • Ensure that your Cisco AS5850 has the following: • MGCP 1.0 • IUA 0.4 • ISDN network side support to terminate multiple voice PRIs ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 244 PRI Backhaul and IUA Support Using SCTP How to Configure SCTP Features
- 257. SUMMARY STEPS 1. enable 2.configure terminal 3. iua 4. as as-name {local-ip1 [local-ip2]} [local-sctp-port] 5. asp asp-name as as-name remote-ip1 remote-ip2 ]}[remote-sctp-port 6. asp asp-name sctp-keepalives remote-ip keepalive-value 7. asp asp-name ip-precedence remote-ip ip-precedence-level 8. as as-name fail-over-timer time 9. exit DETAILED STEPS PurposeCommand or Action Enters privileged EXEC mode. Enter your password if prompted.enable Example: Router> enable Step 1 Enters global configuration mode.configure terminal Example: Router# configure terminal Step 2 Enters IUA configuration mode and specifies backhaul using SCTP. iua Example: Router(config)# iua Step 3 Defines an application server on a gateway.as as-name {local-ip1 [local-ip2]} [local-sctp-port] Step 4 You can specify up to three local IP addresses (note that SCTP has built-in support for multihomed machines). Example: Router(config-iua)# as as5400-3 10.1.2.34 10.1.2.35 2577 Defines an ASP. Use this command to establish SCTP associations. asp asp-name as as-name remote-ip1 remote-ip2 ]}[remote-sctp-port Step 5 Example: Router(config-iua)# asp asp1 as as5400-3 10.4.8.68 10.4.9.68 2577 A maximum of three ASPs can be configured per application server. Note ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 245 PRI Backhaul and IUA Support Using SCTP Configuring PRI Backhaul Using the SCTP and the ISDN Q.921 User Adaptation Layer
- 258. PurposeCommand or Action (Optional)Sets SCTP keepalive behavior, in ms, for the specified ASP and IP address. Range: 1000 to 60000. Default: 500. asp asp-name sctp-keepalives remote-ip keepalive-value Step 6 Example: Router(config-iua)# asp asp1 sctp-keepalives 10.1.2.234 600 Find the current value by examining the show ip sctp association parameters command output under heartbeats. Note (Optional) Sets the IP precedence level for protocol data units (PDUs) for the specified IP address. asp asp-name ip-precedence remote-ip ip-precedence-level Step 7 Example: Router(config-iua)# asp asp1 ip-precedence 10.1.2.345 7 Range for a given address is 0 to 7. Default for normal IP precedence handling is 0. (Optional) Sets the failover timer value, in ms. IUA waits for this amount of time for one ASP to take over from another ASP during failover. as as-name fail-over-timer time Example: Router(config-iua)# as as5400-3 fail-over-timer 10000 Step 8 Find the current failover timer value by examining the show iua as all command output. Note Exits the current mode.exit Example: Router(config-iua)# exit Step 9 Configuring ISDN Signaling (PRI) Backhaul To configure ISDN signaling (PRI) backhaul, perform the following steps. Before You Begin Ensure that Cisco IOS Release 12.2(4)T or later is installed and running on your system. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 246 PRI Backhaul and IUA Support Using SCTP Configuring PRI Backhaul Using the SCTP and the ISDN Q.921 User Adaptation Layer
- 259. SUMMARY STEPS 1. enable 2.configure terminal 3. controller t1 0 4. pri-group timeslots timeslot-range service mgcp 5. exit 6. interface serial slot/port : timeslot 7. isdn switch-type switch-type 8. isdn bind-l3 iua-backhaul as as-name 9. Repeat the preceding steps for each T1 interface that uses backhaul. 10. exit DETAILED STEPS PurposeCommand or Action Enters privileged EXEC mode. Enter your password if prompted. enable Example: Router> enable Step 1 Enters global configuration mode.configure terminal Example: Router# configure terminal Step 2 Enters controller configuration mode for slot 0.controller t1 0 Example: Router(config)# controller t1 0 Step 3 Sets the control protocol used for backhaul to MGCP. You cannot share controller timeslots between backhaul and other Layer 3 protocols. pri-group timeslots timeslot-range service mgcp Example: Router(config-control)# pri-group timeslots 1-24 service mgcp Step 4 Exits the current mode.exit Example: Router(config-control)# exit Step 5 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 247 PRI Backhaul and IUA Support Using SCTP Configuring PRI Backhaul Using the SCTP and the ISDN Q.921 User Adaptation Layer
- 260. PurposeCommand or Action Entersserial-interface configuration mode for the specified controller and timeslot. interface serial slot/port : timeslot Example: Router(config)# interface serial 0:23 Step 6 The D-channel timeslot is (channelized T1): 23 or (channelized E1):15. Specifies the ISDN switch type (can be done in either global configuration mode or interface mode). isdn switch-type switch-type Example: Router(config-if)# isdn switch-type primary-4ess Step 7 Configures ISDN to backhaul Q.931 to the media gateway controller. isdn bind-l3 iua-backhaul as as-name Example: Router(config-if)# isdn bind-l3 iua-backhaul as server1 Step 8 --Repeat the preceding steps for each T1 interface that uses backhaul. Step 9 Exits the current mode.exit Example: Router(config-if)# exit Step 10 Verifying PRI Backhaul To verify PRI backhaul, perform the following steps (listed alphabetically). SUMMARY STEPS 1. show iua as {all name as-name} 2. show iua asp {all name asp-name} 3. show isdn status 4. show running-config DETAILED STEPS Step 1 show iua as {all name as-name} Use this command to display the current state of the active application server and show the PRI interfaces configured on the application server. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 248 PRI Backhaul and IUA Support Using SCTP Configuring PRI Backhaul Using the SCTP and the ISDN Q.921 User Adaptation Layer
- 261. The following outputshows that the current state of the application server (as1) is active and that there are four PRI interfaces configured to use this application server: Example: Router# show iua as all Name of AS :as1 Total num of ASPs configured :2 Current state : ACTIVE Active ASP :asp1 Number of ASPs up :1 Fail-Over time : 4000 milli seconds Local address list : 10.21.0.2 Local port 9900 Interface IDs registered with this AS Interface ID stream # 256 (serial1/0:23) 1 257 (serial1/1:23) 2 512 (serial2/0:23) 3 513 (serial2/1:23) 4 Step 2 show iua asp {all name asp-name} Use this command to display the current state of the active ASP and show information about the SCTP association being used by this ASP. The following output shows that the current state of the ASP (asp1) is active. It also shows information about the SCTP association being used by this ASP. Example: Router# show iua asp all Name of ASP :asp1 Current State of ASP:ASP-Active Current state of underlying SCTP Association IUA_ASSOC_ESTAB , assoc id 0 SCTP Association information : Local Receive window :9000 Remote Receive window :9000 Primary Dest address requested by IUA 10.23.0.16 Effective Primary Dest address 10.23.0.16 Remote address list : 10.23.0.16 Remote Port :9900 Statistics : Invalid SCTP signals Total :0 Since last 0 SCTP Send failures :0 Name of ASP :asp2 Current State of ASP:ASP-Down Current state of underlying SCTP Association IUA_ASSOC_INIT , assoc id 0 Remote address list : 10.23.0.16 Remote Port :9911 Statistics : Invalid SCTP signals Total :0 Since last 0 SCTP Send failures :0 Step 3 show isdn status Use this command to display the status of all ISDN interfaces, including active layers, timer information, and switch-type settings. Use it also to display the status of ISDN backhaul. If connection to the media gateway controller is lost, the router shuts down Layer 2 so that it cannot receive calls. When the connection is back up, you can use this command to verify that Layer 2 was also brought back up correctly. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 249 PRI Backhaul and IUA Support Using SCTP Configuring PRI Backhaul Using the SCTP and the ISDN Q.921 User Adaptation Layer
- 262. The following sampleoutput shows Layer 2 status, as defined by the MULTIPLE_FRAME_ESTABLISHED message, to be up. The L3 protocol and state status are highlighted: Example: Router# show isdn status Global ISDN Switchtype = primary-5ess ISDN Serial1/0:23 interface dsl 0, interface ISDN Switchtype = primary-5ess L2 Protocol = Q.921 L3 Protocol(s) = IUA BACKHAUL Layer 1 Status: ACTIVE Layer 2 Status: TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED Layer 3 Status: 0 Active Layer 3 Call(s) Active dsl 0 CCBs = 0 The Free Channel Mask: 0x807FFFFF ISDN Serial1/1:23 interface dsl 1, interface ISDN Switchtype = primary-5ess L2 Protocol = Q.921 L3 Protocol(s) = IUA BACKHAUL Layer 1 Status: ACTIVE Layer 2 Status: TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED Layer 3 Status: 0 Active Layer 3 Call(s) Active dsl 1 CCBs = 0 The Free Channel Mask: 0x807FFFFF ISDN Serial2/0:23 interface dsl 2, interface ISDN Switchtype = primary-5ess L2 Protocol = Q.921 L3 Protocol(s) = IUA BACKHAUL Layer 1 Status: ACTIVE Layer 2 Status: TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED Layer 3 Status: 0 Active Layer 3 Call(s) Active dsl 2 CCBs = 0 The Free Channel Mask: 0x807FFFFF ISDN Serial2/1:23 interface dsl 3, interface ISDN Switchtype = primary-5ess L2 Protocol = Q.921 L3 Protocol(s) = IUA BACKHAUL Layer 1 Status: ACTIVE Layer 2 Status: TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED Layer 3 Status: 0 Active Layer 3 Call(s) Active dsl 3 CCBs = 0 The Free Channel Mask: 0x807FFFFF Total Allocated ISDN CCBs = 0 Step 4 show running-config Use this command to display basic router configuration. What to Do Next For troubleshooting tips, see the Troubleshooting Tips, on page 263.Note ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 250 PRI Backhaul and IUA Support Using SCTP Configuring PRI Backhaul Using the SCTP and the ISDN Q.921 User Adaptation Layer
- 263. Configuring Support forIUA with SCTP for Cisco Access Servers Feature This section contains the following procedures: Configuring IUA for Cisco Access Servers To configure IUA for Cisco access servers, follow the steps for configuring IUA for PRI Q.921 backhaul, as described in the Configuring IUA, on page 244. Configuring the SCTP T1 Initiation Timer To configure the SCTP T1 initiation timer, perform the following steps. SUMMARY STEPS 1. enable 2. configure terminal 3. iua 4. as as-name {localip1 [localip2]} [local-sctp-port] 5. as as-name fail-over-timer time 6. as as-name sctp-startup-rtx number 7. as as-name sctp-streams number 8. as as-name sctp-t1init number 9. asp asp-name as as-name ip-address 10. asp asp-name ip-precedence remote-ip-address number 11. asp asp-name as as-name remote-ip remote-ip2 ]}[remote-sctp-port 12. asp asp-name sctp-keepalive remote-ip-address number 13. asp asp-name sctp-max-association ip-address number 14. asp asp-name sctp-path-retransmission ip-address number 15. asp asp-name sctp-t3-timeout ip-address number 16. exit DETAILED STEPS PurposeCommand or Action Enters privileged EXEC mode. Enter your password if prompted. enable Example: Router> enable Step 1 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 251 PRI Backhaul and IUA Support Using SCTP Configuring Support for IUA with SCTP for Cisco Access Servers Feature
- 264. PurposeCommand or Action Entersglobal configuration mode.configure terminal Example: Router# configure terminal Step 2 Enters IUA configuration mode and specifies backhaul using SCTP. iua Example: Router(config)# iua Step 3 Defines an application server on a gateway.as as-name {localip1 [localip2]} [local-sctp-port] Example: Router(config-iua)# as as5400-3 10.1.2.34 10.1.2.35 2577 Step 4 (Optional) Sets the failover timer value, in ms.as as-name fail-over-timer timeStep 5 Example: Router(config-iua)# as as5400-3 fail-over 10000 Find the failover timer value by examining the show iua as all command output. Note Configures the SCTP startup retransmission interval.as as-name sctp-startup-rtx number Example: Router(config-iua)# as as5400-3 sctp-startup-rtx 8 Step 6 Configures the number of SCTP streams for this application server. as as-name sctp-streams number Example: Router(config-iua)# as as5400-3 sctp-streams 56 Step 7 Although the gateway help function displays a range of 2 to 57, the upper end of the range (also the default) is determined by your hardware, and is equal to the number of controllers on that gateway and NAS one plus. If you enter a number higher than that, the system assumes the default. If you want to set this value to something other than the default, add one to the number of D channel interfaces that you want to use concurrently. Note Sets the SCTP T1 initiation timer, in ms.as as-name sctp-t1init number Example: Router(config-iua)# as as1 sctp-t1init 1000 Step 8 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 252 PRI Backhaul and IUA Support Using SCTP Configuring Support for IUA with SCTP for Cisco Access Servers Feature
- 265. PurposeCommand or Action Createsan ASP and specifies to which application server it belongs. asp asp-name as as-name ip-address Example: Router(config-iua)# asp asp1 as as1 10.4.8.68 10.4.9.68 Step 9 Specifies the IP precedence level for protocol data units (PDUs) for a given IP address. asp asp-name ip-precedence remote-ip-address number Step 10 Example: Router(config-iua)# asp asp1 ip-precedence 10.1.2.345 7 Default for normal IP precedence handling is 0. Defines an ASP. Use this command to establish SCTP associations. asp asp-name as as-name remote-ip remote-ip2 ]}[remote-sctp-port Example: Router(config-iua)# asp asp1 as as5400-3 10.4.8.68 10.4.9.68 2577 Step 11 (Optional) Specifies the IP address to enable and disable keepalives and control SCTP keepalives on destination IP addresses. asp asp-name sctp-keepalive remote-ip-address number Example: Router(config-iua)# asp asp1 sctp-keepalive 10.1.2.234 1000 Step 12 Sets the maximum association retransmissions for this ASP.asp asp-name sctp-max-association ip-address number Step 13 Example: Router(config-iua)# asp asp1 sctp-max-association 10.10.10.10 20 Sets the SCTP path retransmissions for this ASP.asp asp-name sctp-path-retransmission ip-address number Step 14 Example: Router(config-iua)# asp asp1 sctp-path-retransmission 10.10.10.10 2 Enters IUA-SCTP configuration mode and sets the SCTP T3 retransmission timeout for this ASP. asp asp-name sctp-t3-timeout ip-address number Example: Router(config-iua)# asp asp1 sctp-t3-timeout 10.10.10.10 60000 Step 15 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 253 PRI Backhaul and IUA Support Using SCTP Configuring Support for IUA with SCTP for Cisco Access Servers Feature
- 266. PurposeCommand or Action Exitsthe current mode.exit Example: Router(config-iua-sctp)# exit Step 16 Creating NFAS Groups and Bind Them to the Application Server To create NFAS groups and bind them to the application server, perform the following steps. This procedure configures two T1 interfaces into two NFAS groups or trunk groups that are served by the same application server with two different SCTP streams (ASPs). It allows you to configure the NFAS primary D channel and bind the channel to an IUA application server. Note • The steps for configuring the T1/E1 interface are the same as the steps using RLM, but multiple NFAS groups can now be defined to support multiple trunk groups. All interfaces in an NFAS are treated as one trunk group. SUMMARY STEPS 1. enable 2. configure terminal 3. controller t1 1/0/0 4. pri-group timeslots timeslot-range nfas-d primary nfas-int number nfas-group number iua as-name 5. exit 6. controller t1 1/0/1 7. pri-group timeslots timeslot-range nfas-d primary nfas-int number nfas-group number iua as-name 8. exit DETAILED STEPS PurposeCommand or Action Enters privileged EXEC mode. Enter your password if prompted.enable Example: Router> enable Step 1 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 254 PRI Backhaul and IUA Support Using SCTP Configuring Support for IUA with SCTP for Cisco Access Servers Feature
- 267. PurposeCommand or Action Entersglobal configuration mode.configure terminal Example: Router# configure terminal Step 2 Enters controller configuration mode on the first T1 controller.controller t1 1/0/0 Example: Router(config)# controller t1 1/0/0 Step 3 Configures the NFAS primary D channel on one channelized T1 controller and binds the D channel to an IUA application server. pri-group timeslots timeslot-range nfas-d primary nfas-int number nfas-group number iua as-name Step 4 You can choose any timeslot other than 24 to be the virtual container for the D channel parameters for ISDN. Keywords and arguments are as follows:Example: Router(config-controller)# pri-group • nfas-group number --NFAS group timeslots 1-23 nfas-d primary nfas-int 0 nfas-group 1 iua as-1 • iua as-name --Must match the name of an application server that was set up during IUA configuration. For more information, see the Configuring IUA, on page 244. Note Exits the current mode on the first controller.exit Example: Router(config-controller)# exit Step 5 Enters controller configuration mode on the second T1 controller.controller t1 1/0/1 Example: Router# controller t1 1/0/1 Step 6 Configures the NFAS primary D channel on another channelized T1 controller and binds the D channel to an IUA application pri-group timeslots timeslot-range nfas-d primary nfas-int number nfas-group number iua as-name Step 7 server. Keywords and arguments are as above. The argument as-name must match the name of an application server that was set up during IUA configuration.Example: Router(config-controller)# pri-group timeslots 1-23 nfas-d primary nfas-int 0 nfas-group 1 iua as-1 Exits the current mode.exit Example: Router(config-if)# exit Step 8 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 255 PRI Backhaul and IUA Support Using SCTP Configuring Support for IUA with SCTP for Cisco Access Servers Feature
- 268. Migrating from RLMto IUA with SCTP To migrate from RLM to IUA with SCTP, perform the following steps. The following changes have been made between RLM and IUA with SCTP: • Application server and ASP configuration lines must precede the controller configuration lines in the configuration text file. • RLM group configuration must be removed from the D channel configuration. • For the D channel, the interface serial commands are now replaced by interface D channel commands. • Any isdn bind commands must be removed from the D channel. Binding of the NFAS groups now takes place when you use the pri-group commands for IUA with SCTP. For more information, see the SCTP Migration from RLM to IUA Example, on page 286. SUMMARY STEPS 1. enable 2. copy run tftp 3. For RLM, remove the "isdn rlm-group 1" line shown in bold. 4. copy tftp start 5. reload DETAILED STEPS PurposeCommand or Action Enters privileged EXEC mode. Enter your password if prompted. enable Example: Router> enable Step 1 Copies the running configuration to a TFTP server. Make a backup copy of the running configuration. Enter the IP address and destination filename when prompted. copy run tftp Example: Router# copy run tftp Step 2 Make all edits to the configuration text file that you have copied over to your TFTP server. Some TFTP servers might require that the name of the file that you intend to copy over is already existing and has write permissions on the TFTP server onto which you are copying. Note ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 256 PRI Backhaul and IUA Support Using SCTP Configuring Support for IUA with SCTP for Cisco Access Servers Feature
- 269. PurposeCommand or Action LinksIUA instead of RLM by removing the "isdn rlm-group 1" line from the interface serial output. For RLM, remove the "isdn rlm-group 1" line shown in bold. Example: interface Serial3/0:1:23 Step 3 Example: no ip address Example: isdn switch-type primary-ni Example: isdn incoming-voice modem Example: isdn T321 30000 Example: isdn T303 20000 Example: isdn T200 2000 Example: isdn rlm-group 1 Example: isdn negotiate-bchan resend-setup Example: isdn bchan-number-order ascending Example: no cdp enable ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 257 PRI Backhaul and IUA Support Using SCTP Configuring Support for IUA with SCTP for Cisco Access Servers Feature
- 270. PurposeCommand or Action Copiesthe new configuration to the startup configuration.copy tftp start Example: Router# copy tftp start Step 4 Reloads the router.reload Example: Router# reload Step 5 Modifying a PRI Group on an MGC To modify a PRI group on an MGC, perform the following steps. Before You Begin • Remove isdn bind commands from the D channel. Binding of the NFAS groups takes place when you use the pri-group commands for IUA with SCTP. For more information, see the Trunk Group Bound to an Application Server Example, on page 287.Note SUMMARY STEPS 1. enable 2. configure terminal 3. interface Dchannel3/0:1 4. shutdown 5. exit DETAILED STEPS PurposeCommand or Action Enters privileged EXEC mode. Enter your password if prompted. enable Example: Router> enable Step 1 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 258 PRI Backhaul and IUA Support Using SCTP Configuring Support for IUA with SCTP for Cisco Access Servers Feature
- 271. PurposeCommand or Action Entersglobal configuration mode.configure terminal Example: Router# configure terminal Step 2 Enters interface configuration mode for the specified D channel that is to be shut down. This is the format used for IUA. interface Dchannel3/0:1 Example: Router(config)# interface Dchannel3/0:1 Step 3 Shuts down the D channel.shutdown Example: Router(config-if)# shutdown Step 4 Exits the current mode.exit Example: Router(config-if)# exit Step 5 Verifying Support for IUA with SCTP To verify support for IUA with SCTP, perform the following steps (listed alphabetically). SUMMARY STEPS 1. show ip sctp association list 2. show ip sctp association parameters 3. show ip sctp association statistics 4. show ip sctp errors 5. show ip sctp instances 6. show ip sctp statistics 7. show isdn service 8. show isdn status 9. show running-config DETAILED STEPS Step 1 show ip sctp association list ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 259 PRI Backhaul and IUA Support Using SCTP Configuring Support for IUA with SCTP for Cisco Access Servers Feature
- 272. Use this commandto display current SCTP association and instance identifiers, current state of SCTP associations, and local and remote port numbers and addresses that are used in the associations. The example below shows two current associations that are in the established state. Each association belongs to a different instance, as noted by their instance identifiers. Example: Router# show ip sctp association list *** SCTP Association List **** AssocID: 0, Instance ID: 0 Current state: ESTABLISHED Local port: 8787, Addrs: 10.1.0.2 10.2.0.2 Remote port: 8787, Addrs: 10.5.0.4 10.6.0.4 AssocID: 1, Instance ID: 1 Current state: ESTABLISHED Local port: 6790, Addrs: 10.1.0.2 10.2.0.2 Remote port: 6789, Addrs: 10.5.0.4 10.6.0.4 Step 2 show ip sctp association parameters Use this command to display parameter values for the specified association. This command requires an association identifier as an argument. Association identifiers can be obtained from the output of the show ip sctp association list command. Many parameters are defined for each association, some of them configured and some of them calculated. They fall into the following main groupings: • Association configuration parameters • Destination address parameters • Association boundary parameters • Current association congestion parameters Example: Router# show ip sctp association parameters 0 ** SCTP Association Parameters ** AssocID: 0 Context: 0 InstanceID: 0 Assoc state: ESTABLISHED Uptime: 00:00:34.280 Local port: 8787 Local addresses: 10.1.0.2 10.2.0.2 Remote port: 8787 Primary dest addr: 10.5.0.4 Effective primary dest addr: 10.5.0.4 Destination addresses: 10.5.0.4: State: ACTIVE Heartbeats: Enabled Timeout: 30000 ms RTO/RTT/SRTT: 1000/0/0 ms TOS: 0 MTU: 1500 cwnd: 5000 ssthresh: 18000 outstand: 0 Num retrans: 0 Max retrans: 5 Num times failed: 0 10.6.0.4: State: ACTIVE Heartbeats: Enabled Timeout: 30000 ms RTO/RTT/SRTT: 1000/0/0 ms TOS: 0 MTU: 1500 cwnd: 3000 ssthresh: 18000 outstand: 0 Num retrans: 0 Max retrans: 5 Num times failed: 0 Local vertag: DA3C3BD Remote vertag: 4D95E3A Num inbound streams: 13 outbound streams: 13 Max assoc retrans: 5 Max init retrans: 8 CumSack timeout: 200 ms Bundle timeout: 100 ms Min RTO: 1000 ms Max RTO: 60000 ms ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 260 PRI Backhaul and IUA Support Using SCTP Configuring Support for IUA with SCTP for Cisco Access Servers Feature
- 273. LocalRwnd: 9000 Low:6400 RemoteRwnd: 16800 Low: 14900 Congest levels: 0 current level: 0 high mark: 1 Step 3 show ip sctp association statistics Use this command to display statistics about the specified association, including the following: The first numbers show the total number of chunks, both data and control, sent and received. The second group of statistics focuses on the data chunks sent, showing the total number sent, the number retransmitted, the number that were ordered and unordered, the average number that were bundled together, and the total bytes sent. The third group of statistics focuses on the data chunks received. It displays the total number received and the number discarded (because of duplicates), the number of ordered and unordered chunks received, the average number of chunks that were bundled, the number of bytes received, and the number of sequenced chunks that were received out of order. The last section indicates how many datagrams have been sent, received, or are ready to be received by the calling application or ULP. The ULP statistics may be different from the chunk statistics if the datagrams are large and have been segmented by SCTP. This command requires an association identifier argument, which you can obtain from output of the show ip sctp association list command. Note The following example was taken from a network with known dropped packets in one direction. The number of total chunks sent and received is larger than the number of data chunks sent and received because it also includes the control chunks sent. The number of chunks received out of sequence indicates that there are some chunks not being received in the correct order. However, the number of chunks discarded is zero, indicating that only one copy of each is arriving at this peer (some chunks are probably being dropped and the peer is retransmitting them, but there are no duplicates being received). The number of chunks being retransmitted is zero, indicating that there is no network problem in the direction of sending from this peer to the remote. Example: Router# show ip sctp association statistics 0 ** SCTP Association Statistics ** AssocID/InstanceID: 0/0 Current State: ESTABLISHED Control Chunks Sent: 1009 Rcvd: 988 Data Chunks Sent Total: 18073 Retransmitted: 0 Ordered: 9095 Unordered: 8978 Avg bundled: 9 Total Bytes: 1807300 Data Chunks Rcvd Total: 18073 Discarded: 0 Ordered: 9095 Unordered: 8978 Avg bundled: 9 Total Bytes: 1807300 Out of Seq TSN: 586 ULP Dgrams Sent: 18073 Ready: 18073 Rcvd: 18073 Step 4 show ip sctp errors Use this command to display errors logged since last time that the statistics were cleared. The following output shows one example in which no errors have been logged, and another in which there have been several different types of errors. Example: Router# show ip sctp errors *** SCTP Error Statistics **** No SCTP errors logged. Router# show ip sctp errors *** SCTP Error Statistics **** Communication Lost: 95 Unknown INIT params rcvd: 8 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 261 PRI Backhaul and IUA Support Using SCTP Configuring Support for IUA with SCTP for Cisco Access Servers Feature
- 274. Missing parameters: 18 Noroom for incoming data: 11 Step 5 show ip sctp instances Use this command to display information for each of the currently configured instances. The instance number, local port, and address information is displayed. The instance state is either available or deletion pending . An instance enters the deletion pending state when a request is made to delete it but there are currently established associations for that instance. The instance cannot be deleted immediately and instead enters the pending state. No new associations are allowed in this instance, and when the last association is terminated or fails, the instance is deleted. The default inbound and outbound stream numbers are used for establishing incoming associations, and the maximum number of associations allowed for this instance is shown. Finally, a snapshot of each existing association is shown, if any exist. In this example, two current instances are active and available. The first is using local port 8787, and the second is using local port 6790. Instance identifier 0 has one current association, and instance identifier 1 has no current associations. Example: Router# show ip sctp instances *** SCTP Instances **** Instance ID: 0 Local port: 8787 Instance state: available Local addrs: 10.1.0.2 10.2.0.2 Default streams inbound: 1 outbound: 1 Current associations: (max allowed: 6) AssocID: 0 State: ESTABLISHED Remote port: 8787 Dest addrs: 10.5.0.4 10.6.0.4 Instance ID: 1 Local port: 6790 Instance state: available Local addrs: 10.1.0.2 10.2.0.2 Default streams inbound: 13 outbound: 13 No current associations established for this instance. Max allowed: 6 Step 6 show ip sctp statistics Use this command to display the overall SCTP statistics accumulated since the last clear ip sctp statisticscommand for currently established associations and those that have terminated. The command also displays the number of aborts and shutdowns received and the number of times the T1 (initialization) and T2 (shutdown) timers expired. Example: Router# show ip sctp statistics ** SCTP Overall Statistics ** Control Chunks Sent: 7872 Rcvd: 8547 Data Chunks Sent Total: 98681 Retransmitted: 5 Ordered: 50241 Unordered: 48435 Total Bytes: 9868100 Data Chunks Rcvd Total: 98676 Discarded: 0 Ordered: 50241 Unordered: 48435 Total Bytes: 9867600 Out of Seq TSN: 2845 SCTP Dgrams Sent: 17504 Rcvd: 19741 ULP Dgrams Sent: 98676 Ready: 98676 Rcvd: 98676 Additional Stats Assocs Currently Estab: 0 Active Estab: 0 Passive Estab: 2 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 262 PRI Backhaul and IUA Support Using SCTP Configuring Support for IUA with SCTP for Cisco Access Servers Feature
- 275. Aborts: 0 Shutdowns:0 T1 Expired: 11 T2 Expired: 0 Step 7 show isdn service Use this command to display information about ISDN channels and the service states. Step 8 show isdn status Use this command to display the status of all ISDN interfaces, including active layers, timer information, and switch-type settings. Step 9 show running-config Use this command to display the basic router configuration. Troubleshooting Tips In a live system, debug commands for performance, state, signal, and warnings are most useful. These commands show any association or destination address failures and can be used to monitor the stability of any established associations. Use debug commands with extreme caution or not at all in live systems, depending on the amount of traffic. Debug commands other than those for performance, state, signal, and warnings can generate a great deal of output and therefore cause associations to fail. Use these commands only in test environments or during times of very low traffic volume. Caution SCTP debug commands display information for all current SCTP associations and cannot be limited to particular associations. Note • SCTP debug commands that display statistical information show only the information that is available since the last time a clear ip sctp statistics command was executed. The clear ip sctp statisticscommand clears all SCTP statistics, both those compiled for individual associations and those compiled overall. • Sample outputs for the debug commands are shown in the Examples, on page 265. • You can use debugs with timestamps enabled to see the relevant timing of the events indicated. To add timestamps to debug output, use the service timestampscommands (service timestamps debug and service timestamps log), optionally with the msec keyword. Output is in the format MMM DD HH:MM:SS, which indicates the date and time according to the system clock. If the system clock is not set, the date and time are preceded by an asterisk (*) to indicate that the date and time are probably not correct. • For more information on SCTP debug commands, see Stream Control Transmission Protocol (SCTP) . • Use the debug ip sctp api command to show all SCTP calls to the application programming interface (API) that are being executed and the parameters associated with these calls. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 263 PRI Backhaul and IUA Support Using SCTP Troubleshooting Tips
- 276. • Use thedebug ip sctp congestion command to display various events related to calculating the current congestion parameters, including congestion window (cwnd) values per destination address and local and remote receiver window (rwnd) parameters. Information is displayed when bundling and sending data chunks, indicating the current cwnd and rwnd values and remote rwnd values, thus showing when data can or can not be sent or bundled. When chunks are acknowledged by the remote peer, the number of bytes outstanding and remote rwnd values are updated. Information is also displayed when new chunks are received, thus decreasing the local rwnd space, and when chunks are freed because the ULP is receiving datagrams from SCTP and thus freeing local rwnd space. • Use the debug ip sctp init command to display datagrams and other information related to the initializing of new associations. All initialization chunks are shown, including the INIT, INIT_ACK, COOKIE_ECHO, and COOKIE_ACK chunks. You can use this command to see the chunks associated with any initialization sequence, but it does not display data chunks sent once the association is established. Therefore, it is safe to use in a live system that has traffic flowing when you have trouble with associations that fail and have to be reestablished. • Use the debug ip sctp multihome command to display the source and destination of datagrams in order to monitor use of the multihome addresses. More than one IP address parameter can be included in an INIT chunk when the INIT sender is multihomed. Datagrams should mostly be sent to the primary destination addresses unless the network is experiencing problems, in which case they can be sent to the secondary addresses. • Use the debug ip sctp performance command to display the average number of chunks and datagrams being sent and received per second once every 10 seconds. Averages are cumulative since the last time the statistics were cleared and so may not accurately reflect the number of datagrams and chunks currently being sent and received. • Use the debug ip sctp rcvchunks command to display information about chunks that are received, including the following: stream number, sequence number, chunk length, and chunk transmission sequence number (TSN) for each chunk received; and whether the chunk is for a new datagram or a datagram that is already being reassembled. Command output shows whether the datagram is complete after receiving this chunk or not and, if complete, whether it is in sequence within the specified stream and can be delivered to the ULP. It shows the SACKs that are sent back to the remote, indicating the cumulative TSN acknowledged, the number of fragments included, and that the datagram is received by the ULP. • Use the debug ip sctp rto command to display adjustments to the retransmission (retrans) timeout value due to retransmission of data chunks or unacknowledged heartbeats. • Use the debug ip sctp segments command to display every datagram that is sent or received and the chunks that are contained in each. The command has two forms: simple and verbose. This simple form of the command shows basic information for each chunk type. • Use the debug ip sctp segmentv command to show every datagram that is sent or received and the chunks that are contained in each. The command has two forms: simple and verbose. This verbose form of the output shows detailed information for each chunk type. • Use the debug ip sctp signal command to display signals that are sent from SCTP to the application or ULP. These signals inform the ULP of state transitions for associations or destination addresses. Signal s sent to the ULP when new data is available to be received may not be shown because they occur infrequently. You can use this command to determine whether or not the current associations are stable. Because it does not generate output except on state transitions, it is safe to use in a live environment. It still should be used with caution, however, depending on the number of associations being handled by the system and the stability of the network. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 264 PRI Backhaul and IUA Support Using SCTP Troubleshooting Tips
- 277. The debug ipsctp state and debug ip sctp signalcommands are often used together to provide insight into the stability of associations. Note • Use the debug ip sctp sndchunks command to display the following types of information about all chunks that are being sent to remote SCTP peers: • Application send requests from the local SCTP peer • Chunks being bundled and sent to the remote peer • Processing of the SACKs from the remote peer, indicating which chunks were successfully received • Chunks that are marked for retransmission • Use the debug ip sctp state command with the debug ip sctp signal command to provide insight into the stability of associations. • Use the debug ip sctp timer command to display information about all started, stopped, and triggering SCTP timers. Many SCTP timers, after they are started, are not restarted until they expire or are stopped; the first call starts the timer, and subsequent calls do nothing until the timer either expires or is stopped. • Use the debug ip sctp warnings command to display information on any unusual situation that is encountered. These situations may or may not indicate problems, depending on the particulars of the situation. • Use the debug iua as command to display debug messages for the IUA application server when an ISDN backhaul connection is initially established. • Use the debug iua asp command to display debug messages for the IUA ASP when an ISDN backhaul connection is initially established. Examples Sample Output for the debug ip sctp api Command Do not use this command in a live system that has any significant amount of traffic running. It can generate significant traffic, and cause associations to fail. Caution Router# debug ip sctp api *Mar 1 00:31:14.211: SCTP: sctp_send: Assoc ID: 1 *Mar 1 00:31:14.211: SCTP: stream num: 10 *Mar 1 00:31:14.211: SCTP: bptr: 62EE332C, dptr: 4F7B598 *Mar 1 00:31:14.211: SCTP: datalen: 100 *Mar 1 00:31:14.211: SCTP: context: 1 *Mar 1 00:31:14.211: SCTP: lifetime: 0 *Mar 1 00:31:14.211: SCTP: unorder flag: FALSE *Mar 1 00:31:14.211: SCTP: bundle flag: TRUE *Mar 1 00:31:14.211: SCTP: sctp_send successful return *Mar 1 00:31:14.211: SCTP: sctp_receive: Assoc ID: 1 *Mar 1 00:31:14.215: SCTP: max data len: 100 *Mar 1 00:31:14.215: SCTP: sctp_receive successful return *Mar 1 00:31:14.215: SCTP: Process Send Request *Mar 1 00:31:14.951: SCTP: sctp_receive: Assoc ID: 0 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 265 PRI Backhaul and IUA Support Using SCTP Troubleshooting Tips
- 278. *Mar 1 00:31:14.951:SCTP: max data len: 100 *Mar 1 00:31:14.951: SCTP: sctp_receive successful return *Mar 1 00:31:14.951: SCTP: sctp_send: Assoc ID: 0 *Mar 1 00:31:14.951: SCTP: stream num: 12 *Mar 1 00:31:14.951: SCTP: bptr: 62EE00CC, dptr: 4F65158 *Mar 1 00:31:14.951: SCTP: datalen: 100 *Mar 1 00:31:14.951: SCTP: context: 0 *Mar 1 00:31:14.951: SCTP: lifetime: 0 *Mar 1 00:31:14.951: SCTP: unorder flag: FALSE *Mar 1 00:31:14.951: SCTP: bundle flag: TRUE *Mar 1 00:31:14.951: SCTP: sctp_send successful return *Mar 1 00:31:14.951: SCTP: sctp_receive: Assoc ID: 0 *Mar 1 00:31:14.951: SCTP: max data len: 100 *Mar 1 00:31:14.951: SCTP: sctp_receive successful return Sample Output for the debug ip sctp congestion Command Router# debug ip sctp congestion SCTP: Assoc 0: Slow start 10.6.0.4, cwnd 3000 SCTP: Assoc 0: Data chunks rcvd, local rwnd 7800 SCTP: Assoc 0: Free chunks, local rwnd 9000 SCTP: Assoc 0: Data chunks rcvd, local rwnd 8200 SCTP: Assoc 0: Add Sack, local a_rwnd 8200 SCTP: Assoc 0: Free chunks, local rwnd 9000 SCTP: Assoc 0: Data chunks rcvd, local rwnd 7800 SCTP: Assoc 0: Data chunks rcvd, local rwnd 7000 SCTP: Assoc 0: Add Sack, local a_rwnd 7000 SCTP: Assoc 0: Free chunks, local rwnd 9000 SCTP: Assoc 0: Bundle for 10.5.0.4, rem rwnd 14000, cwnd 19500, outstand 0 SCTP: Assoc 0: Bundled 12 chunks, remote rwnd 12800, outstand 1200 SCTP: Assoc 0: Bundling data, next chunk dataLen (100) > remaining mtu size SCTP: Assoc 0: Bundle for 10.5.0.4, rem rwnd 12800, cwnd 19500, outstand 1200 SCTP: Assoc 0: Bundled 12 chunks, remote rwnd 11600, outstand 2400 SCTP: Assoc 0: Bundling data, next chunk dataLen (100) > remaining mtu size SCTP: Assoc 0: Bundle for 10.5.0.4, rem rwnd 11600, cwnd 19500, outstand 2400 SCTP: Assoc 0: Bundled 12 chunks, remote rwnd 10400, outstand 3600 SCTP: Assoc 0: Bundling data, next chunk dataLen (100) > remaining mtu size SCTP: Assoc 0: Bundle for 10.5.0.4, rem rwnd 10400, cwnd 19500, outstand 3600 SCTP: Assoc 0: Bundled 4 chunks, remote rwnd 10000, outstand 4000 SCTP: Assoc 0: No additional chunks waiting. SCTP: Assoc 0: Data chunks rcvd, local rwnd 7800 SCTP: Assoc 0: Data chunks rcvd, local rwnd 7000 SCTP: Assoc 0: Add Sack, local a_rwnd 7000 SCTP: Assoc 0: Chunk A22F3B45 ack'd, dest 10.5.0.4, outstanding 3900 SCTP: Assoc 0: Chunk A22F3B46 ack'd, dest 10.5.0.4, outstanding 3800 SCTP: Assoc 0: Chunk A22F3B47 ack'd, dest 10.5.0.4, outstanding 3700 SCTP: Assoc 0: Chunk A22F3B48 ack'd, dest 10.5.0.4, outstanding 3600 SCTP: Assoc 0: Chunk A22F3B49 ack'd, dest 10.5.0.4, outstanding 3500 SCTP: Assoc 0: Chunk A22F3B4A ack'd, dest 10.5.0.4, outstanding 3400 SCTP: Assoc 0: Chunk A22F3B4B ack'd, dest 10.5.0.4, outstanding 3300 SCTP: Assoc 0: Chunk A22F3B4C ack'd, dest 10.5.0.4, outstanding 3200 SCTP: Assoc 0: Chunk A22F3B4D ack'd, dest 10.5.0.4, outstanding 3100 SCTP: Assoc 0: Chunk A22F3B4E ack'd, dest 10.5.0.4, outstanding 3000 SCTP: Assoc 0: Chunk A22F3B4F ack'd, dest 10.5.0.4, outstanding 2900 SCTP: Assoc 0: Chunk A22F3B50 ack'd, dest 10.5.0.4, outstanding 2800 SCTP: Assoc 0: Chunk A22F3B51 ack'd, dest 10.5.0.4, outstanding 2700 SCTP: Assoc 0: Chunk A22F3B52 ack'd, dest 10.5.0.4, outstanding 2600 SCTP: Assoc 0: Chunk A22F3B53 ack'd, dest 10.5.0.4, outstanding 2500 SCTP: Assoc 0: Chunk A22F3B54 ack'd, dest 10.5.0.4, outstanding 2400 SCTP: Assoc 0: Chunk A22F3B55 ack'd, dest 10.5.0.4, outstanding 2300 SCTP: Assoc 0: Chunk A22F3B56 ack'd, dest 10.5.0.4, outstanding 2200 Sample Output for the debug ip sctp init Command Router# debug ip sctp init *Mar 1 00:53:07.279: SCTP Test: Attempting to open assoc to remote port 8787...assoc ID is 0 *Mar 1 00:53:07.279: SCTP: Process Assoc Request *Mar 1 00:53:07.279: SCTP: Assoc 0: dest addr list: ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 266 PRI Backhaul and IUA Support Using SCTP Troubleshooting Tips
- 279. *Mar 1 00:53:07.279:SCTP: addr 10.5.0.4 *Mar 1 00:53:07.279: SCTP: addr 10.6.0.4 *Mar 1 00:53:07.279: ... *Mar 1 00:53:13.279: SCTP: Assoc 0: Send Init *Mar 1 00:53:13.279: SCTP: INIT_CHUNK, len 42 *Mar 1 00:53:13.279: SCTP: Initiate Tag: B4A10C4D, Initial TSN: B4A10C4D, rwnd 9000 *Mar 1 00:53:13.279: SCTP: Streams Inbound: 13, Outbound: 13 *Mar 1 00:53:13.279: SCTP: IP Addr: 10.1.0.2 *Mar 1 00:53:13.279: SCTP: IP Addr: 10.2.0.2 *Mar 1 00:53:13.279: SCTP: Supported addr types: 5 *Mar 1 00:53:13.307: SCTP: Process Init *Mar 1 00:53:13.307: SCTP: INIT_CHUNK, len 42 *Mar 1 00:53:13.307: SCTP: Initiate Tag: 3C2D8327, Initial TSN: 3C2D8327, rwnd 18000 *Mar 1 00:53:13.307: SCTP: Streams Inbound: 13, Outbound: 13 *Mar 1 00:53:13.307: SCTP: IP Addr: 10.5.0.4 *Mar 1 00:53:13.307: SCTP: IP Addr: 10.6.0.4 *Mar 1 00:53:13.307: SCTP: Supported addr types: 5 *Mar 1 00:53:13.307: SCTP: Assoc 0: Send InitAck *Mar 1 00:53:13.307: SCTP: INIT_ACK_CHUNK, len 124 *Mar 1 00:53:13.307: SCTP: Initiate Tag: B4A10C4D, Initial TSN: B4A10C4D, rwnd 9000 *Mar 1 00:53:13.307: SCTP: Streams Inbound: 13, Outbound: 13 *Mar 1 00:53:13.307: SCTP: Responder cookie len 88 *Mar 1 00:53:13.307: SCTP: IP Addr: 10.1.0.2 *Mar 1 00:53:13.307: SCTP: IP Addr: 10.2.0.2 *Mar 1 00:53:13.311: SCTP: Assoc 0: Process Cookie *Mar 1 00:53:13.311: SCTP: COOKIE_ECHO_CHUNK, len 88 *Mar 1 00:53:13.311: SCTP: Assoc 0: dest addr list: *Mar 1 00:53:13.311: SCTP: addr 10.5.0.4 *Mar 1 00:53:13.311: SCTP: addr 10.6.0.4 *Mar 1 00:53:13.311: *Mar 1 00:53:13.311: SCTP: Instance 0 dest addr list: *Mar 1 00:53:13.311: SCTP: addr 10.5.0.4 *Mar 1 00:53:13.311: SCTP: addr 10.6.0.4 *Mar 1 00:53:13.311: *Mar 1 00:53:13.311: SCTP: Assoc 0: Send CookieAck *Mar 1 00:53:13.311: SCTP: COOKIE_ACK_CHUNK Sample Output for the debug ip sctp multihome Command This command generates one debug line for each datagram sent or received. Use with extreme caution in a live network. Caution Router# debug ip sctp multihome SCTP: Rcvd s=10.5.0.4 8787, d=10.1.0.2 8787, len 1404 SCTP: Rcvd s=10.5.0.4 8787, d=10.1.0.2 8787, len 476 SCTP: Sent: Assoc 0: s=10.1.0.2 8787, d=10.5.0.4 8787, len 28 SCTP: Assoc 0: Send Data to dest 10.5.0.4 SCTP: Sent: Assoc 0: s=10.1.0.2 8787, d=10.5.0.4 8787, len 1404 SCTP: Sent: Assoc 0: s=10.1.0.2 8787, d=10.5.0.4 8787, len 1404 SCTP: Sent: Assoc 0: s=10.1.0.2 8787, d=10.5.0.4 8787, len 1404 SCTP: Sent: Assoc 0: s=10.1.0.2 8787, d=10.5.0.4 8787, len 476 SCTP: Rcvd s=10.5.0.4 8787, d=10.1.0.2 8787, len 28 SCTP: Rcvd s=10.5.0.4 8787, d=10.1.0.2 8787, len 28 SCTP: Rcvd s=10.5.0.4 8787, d=10.1.0.2 8787, len 1404 SCTP: Rcvd s=10.5.0.4 8787, d=10.1.0.2 8787, len 1404 SCTP: Sent: Assoc 0: s=10.1.0.2 8787, d=10.5.0.4 8787, len 28 SCTP: Rcvd s=10.5.0.4 8787, d=10.1.0.2 8787, len 1404 SCTP: Rcvd s=10.5.0.4 8787, d=10.1.0.2 8787, len 476 SCTP: Sent: Assoc 0: s=10.1.0.2 8787, d=10.5.0.4 8787, len 28 SCTP: Assoc 0: Send Data to dest 10.5.0.4 SCTP: Sent: Assoc 0: s=10.1.0.2 8787, d=10.5.0.4 8787, len 1404 SCTP: Sent: Assoc 0: s=10.1.0.2 8787, d=10.5.0.4 8787, len 1404 SCTP: Sent: Assoc 0: s=10.1.0.2 8787, d=10.5.0.4 8787, len 1404 SCTP: Sent: Assoc 0: s=10.1.0.2 8787, d=10.5.0.4 8787, len 476 SCTP: Rcvd s=10.6.0.4 8787, d=10.2.0.2 8787, len 44 SCTP: Sent: Assoc 0: s=10.2.0.2 8787, d=10.6.0.4 8787, len 44 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 267 PRI Backhaul and IUA Support Using SCTP Troubleshooting Tips
- 280. SCTP: Rcvd s=10.5.0.48787, d=10.1.0.2 8787, len 28 SCTP: Rcvd s=10.5.0.4 8787, d=10.1.0.2 8787, len 28 SCTP: Rcvd s=10.5.0.4 8787, d=10.1.0.2 8787, len 1404 SCTP: Rcvd s=10.5.0.4 8787, d=10.1.0.2 8787, len 1404 SCTP: Sent: Assoc 0: s=10.1.0.2 8787, d=10.5.0.4 8787, len 28 SCTP: Rcvd s=10.5.0.4 8787, d=10.1.0.2 8787, len 1404 SCTP: Rcvd s=10.5.0.4 8787, d=10.1.0.2 8787, len 476 Sample Output for the debug ip sctp performance Command In the following example, when the performance debug was first enabled, it showed a very low rate of traffic. However, it was expected that these numbers were not accurate, so a clear ip sctp command was executed. The average numbers adjusted quickly to reflect the accurate amount of flowing traffic. Router# debug ip sctp performance SCTP Sent: SCTP Dgrams 5, Chunks 28, Data Chunks 29, ULP Dgrams 29 SCTP Rcvd: SCTP Dgrams 7, Chunks 28, Data Chunks 29, ULP Dgrams 29 Chunks Discarded: 0, Retransmitted 0 SCTP Sent: SCTP Dgrams 6, Chunks 29, Data Chunks 30, ULP Dgrams 30 SCTP Rcvd: SCTP Dgrams 7, Chunks 29, Data Chunks 30, ULP Dgrams 30 Chunks Discarded: 0, Retransmitted 0 SCTP Sent: SCTP Dgrams 6, Chunks 29, Data Chunks 31, ULP Dgrams 31 SCTP Rcvd: SCTP Dgrams 7, Chunks 30, Data Chunks 31, ULP Dgrams 31 Chunks Discarded: 0, Retransmitted 0 SCTP Sent: SCTP Dgrams 6, Chunks 30, Data Chunks 31, ULP Dgrams 31 SCTP Rcvd: SCTP Dgrams 7, Chunks 31, Data Chunks 32, ULP Dgrams 31 Chunks Discarded: 0, Retransmitted 0 SCTP Sent: SCTP Dgrams 6, Chunks 31, Data Chunks 32, ULP Dgrams 32 SCTP Rcvd: SCTP Dgrams 7, Chunks 32, Data Chunks 32, ULP Dgrams 32 Chunks Discarded: 0, Retransmitted 0 Router# clear ip sctp statistics SCTP Sent: SCTP Dgrams 30, Chunks 210, Data Chunks 199, ULP Dgrams 201 SCTP Rcvd: SCTP Dgrams 30, Chunks 208, Data Chunks 198, ULP Dgrams 198 Chunks Discarded: 0, Retransmitted 0 SCTP Sent: SCTP Dgrams 30, Chunks 210, Data Chunks 199, ULP Dgrams 200 SCTP Rcvd: SCTP Dgrams 30, Chunks 209, Data Chunks 199, ULP Dgrams 199 Chunks Discarded: 0, Retransmitted 0 SCTP Sent: SCTP Dgrams 30, Chunks 211, Data Chunks 200, ULP Dgrams 199 SCTP Rcvd: SCTP Dgrams 30, Chunks 209, Data Chunks 198, ULP Dgrams 198 Chunks Discarded: 0, Retransmitted 0 Sample Output for the debug ip sctp rcvchunks Command This command generates multiple debug lines for each chunk received. Use with extreme caution in a live network. Caution In the following example, a segmented datagram is received in two chunks, for stream 0 and sequence number 0. The length of the first chunk is 1452, and the second is 1 byte. The first chunk indicates that it is for a new datagram, but the second chunk indicates that it is part of an existing datagram that is already being reassembled. When the first chunk is processed, it is noted to be in sequence, but is not complete and so cannot be delivered yet. When the second chunk is received, the datagram is both in sequence and complete. The application receives the datagram, and a SACK is shown to acknowledge that both chunks were received with no missing chunks indicated (that is, with no fragments). Router# debug ip sctp rcvchunks SCTP: Assoc 0: New chunk (0/0/1452/2C33D822) for new dgram (0) SCTP: Assoc 0: dgram (0) is in seq SCTP: Assoc 0: Add Sack Chunk, CumTSN=2C33D822, numFrags=0 SCTP: Assoc 0: New chunk (0/0/1/2C33D823) for existing dgram (0) SCTP: Assoc 0: dgram (0) is complete SCTP: Assoc 0: ApplRecv chunk 0/0/1452/2C33D822 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 268 PRI Backhaul and IUA Support Using SCTP Troubleshooting Tips
- 281. SCTP: Assoc 0:ApplRecv chunk 0/0/1/2C33D823 SCTP: Assoc 0: Add Sack Chunk, CumTSN=2C33D823, numFrags=0 The following example is taken from a specific test in which chunks are both sent out of sequence and duplicated. The first chunk received is for stream 0, with sequence number 5. The datagram is complete, but is not in sequence because the previously received datagram was sequence number 3. A SACK chunk is sent, indicating that there is a gap after TSN 15755E58. This same chunk is received again, and the debug indicates that this chunk is a duplicate and so is not processed. The next chunk received is sequence number 7, also complete but not in sequence. The number of fragments specified is now 2, because both datagrams 4 and 6 have not been received. The duplicate chunk is discarded again. Sequence number 6 is then received, also complete, but not in sequence. The next earliest datagram received is 5, and even though that is in sequence, datagram 5 is not in sequence because datagram 4 has not been received and so neither 5 nor 6 can be delivered. Thus, there are occasions when the previous sequence number shown is in sequence, but the datagram itself is specified as not in sequence. The SACK sent at that point indicates just one fragment, because datagrams 5 through 7 are all in sequence in a block. Finally, datagram 4 is received. It is complete and in sequence, and datagrams 5 through 7 become in sequence as well, and all the datagrams can be received by the application. Router# debug ip sctp rcvchunks SCTP: Assoc 0: New chunk (0/5/50/15755E5A) for new dgram (5) SCTP: Assoc 0: dgram (5) is complete SCTP: Assoc 0: dgram (5) is not in seq, prev seq (3) SCTP: Assoc 0: Add Sack Chunk, CumTSN=15755E58, numFrags=1 SCTP: Assoc 0: Rcvd duplicate chunk: 0/5/50/15755E5A SCTP: Assoc 0: Add Sack Chunk, CumTSN=15755E58, numFrags=1 SCTP: Assoc 0: New chunk (0/7/50/15755E5C) for new dgram (7) SCTP: Assoc 0: dgram (7) is complete SCTP: Assoc 0: dgram (7) is not in seq, prev seq (5) SCTP: Assoc 0: Add Sack Chunk, CumTSN=15755E58, numFrags=2 SCTP: Assoc 0: Rcvd duplicate chunk: 0/7/50/15755E5C SCTP: Assoc 0: Add Sack Chunk, CumTSN=15755E58, numFrags=2 SCTP: Assoc 0: New chunk (0/6/50/15755E5B) for new dgram (6) SCTP: Assoc 0: dgram (6) is complete SCTP: Assoc 0: dgram (6) is not in seq, prev seq (5) SCTP: Assoc 0: Add Sack Chunk, CumTSN=15755E58, numFrags=1 SCTP: Assoc 0: Rcvd duplicate chunk: 0/6/50/15755E5B SCTP: Assoc 0: Add Sack Chunk, CumTSN=15755E58, numFrags=1 SCTP: Assoc 0: New chunk (0/4/50/15755E59) for new dgram (4) SCTP: Assoc 0: dgram (4) is complete SCTP: Assoc 0: dgram (4) is in seq SCTP: Assoc 0: dgram (5) is now in seq SCTP: Assoc 0: dgram (6) is now in seq SCTP: Assoc 0: dgram (7) is now in seq SCTP: Assoc 0: Rcvd duplicate chunk: 0/4/50/15755E59 SCTP: Assoc 0: Add Sack Chunk, CumTSN=15755E5C, numFrags=0 SCTP: Assoc 0: ApplRecv chunk 0/4/50/15755E59 SCTP: Assoc 0: ApplRecv chunk 0/5/50/15755E5A SCTP: Assoc 0: ApplRecv chunk 0/6/50/15755E5C SCTP: Assoc 0: ApplRecv chunk 0/7/50/15755E5B Sample Output for the debug ip sctp rto Command This command can generate a great deal of output. Use with extreme caution in a live network.Caution In the following example, there is only one destination address available. Each time the chunk needs to be retransmitted, the retransmission timeout (RTO) value is doubled. Router# debug ip sctp rto SCTP: Assoc 0: destaddr 10.5.0.4, retrans timeout on chunk 942BAC55 SCTP: Assoc 0: destaddr 10.5.0.4, rto backoff 2000 ms SCTP: Assoc 0: destaddr 10.5.0.4, retrans timeout on chunk 942BAC55 SCTP: Assoc 0: destaddr 10.5.0.4, rto backoff 4000 ms SCTP: Assoc 0: destaddr 10.5.0.4, retrans timeout on chunk 942BAC55 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 269 PRI Backhaul and IUA Support Using SCTP Troubleshooting Tips
- 282. SCTP: Assoc 0:destaddr 10.5.0.4, rto backoff 8000 ms SCTP: Assoc 0: destaddr 10.5.0.4, retrans timeout on chunk 942BAC55 SCTP: Assoc 0: destaddr 10.5.0.4, rto backoff 16000 ms SCTP: Assoc 0: destaddr 10.5.0.4, retrans timeout on chunk 942BAC55 SCTP: Assoc 0: destaddr 10.5.0.4, rto backoff 32000 ms In the next example, there is again only one destination address available. The data chunk is retransmitted several times, and the heartbeat timer also expires, causing the RTO timer to back off as well. Note that the heartbeat timer is expiring along with the data chunk retransmission timer, because SCTP is continually trying to send a chunk on which it can calculate the current round trip time (RTT). Because the data chunk is being retransmitted, an RTT calculation cannot be made on it, and the heartbeat is used instead. Router# debug ip sctp rto SCTP: Assoc 0: destaddr 10.5.0.4, retrans timeout on chunk 98432842 SCTP: Assoc 0: destaddr 10.5.0.4, rto backoff 2000 ms SCTP: Assoc 0: destaddr 10.5.0.4, retrans timeout on chunk 98432842 SCTP: Assoc 0: destaddr 10.5.0.4, rto backoff 4000 ms SCTP: Assoc 0: destaddr 10.5.0.4, retrans timeout on chunk 98432842 SCTP: Assoc 0: destaddr 10.5.0.4, rto backoff 8000 ms SCTP: Assoc 0: destaddr 10.5.0.4, heartbeat rto backoff 16000 ms SCTP: Assoc 0: destaddr 10.5.0.4, retrans timeout on chunk 98432842 SCTP: Assoc 0: destaddr 10.5.0.4, rto backoff 32000 ms SCTP: Assoc 0: destaddr 10.5.0.4, heartbeat rto backoff 60000 ms Sample Output for the debug ip sctp segments Command This command generates several lines of output for each datagram sent or received. Use with extreme caution in a live network. Caution The following output shows an example in which an association is established, a few heartbeats are sent, the remote endpoint fails, and the association is restarted. Router# debug ip sctp segments SCTP: Sent: Assoc 0: s=10.1.0.2 8787, d=10.5.0.4 8787, len 56 SCTP: INIT_CHUNK, Tag: 3C72A02A, TSN: 3C72A02A SCTP: Recv: Assoc 0: s=10.5.0.4 8787, d=10.1.0.2 8787, len 56 SCTP: INIT_CHUNK, Tag: 13E5AD6C, TSN: 13E5AD6C SCTP: Sent: Assoc NULL: s=10.1.0.2 8787, d=10.5.0.4 8787, len 136 SCTP: INIT_ACK_CHUNK, Tag: 3C72A02A, TSN: 3C72A02A SCTP: Recv: Assoc 0: s=10.5.0.4 8787, d=10.1.0.2 8787, len 100 SCTP: COOKIE_ECHO_CHUNK, len 88 SCTP: Sent: Assoc NULL: s=10.1.0.2 8787, d=10.5.0.4 8787, len 16 SCTP: COOKIE_ACK_CHUNK SCTP: Sent: Assoc 0: s=10.1.0.2 8787, d=10.5.0.4 8787, len 52 SCTP: HEARTBEAT_CHUNK SCTP: Sent: Assoc 0: s=10.1.0.2 8787, d=10.5.0.4 8787, len 52 SCTP: HEARTBEAT_CHUNK SCTP: Sent: Assoc 0: s=10.1.0.2 8787, d=10.5.0.4 8787, len 52 SCTP: HEARTBEAT_CHUNK SCTP: Recv: Assoc 0: s=10.5.0.4 8787, d=10.1.0.2 8787, len 56 SCTP: INIT_CHUNK, Tag: 4F2D8235, TSN: 4F2D8235 SCTP: Sent: Assoc NULL: s=10.1.0.2 8787, d=10.5.0.4 8787, len 136 SCTP: INIT_ACK_CHUNK, Tag: 7DD7E424, TSN: 7DD7E424 SCTP: Recv: Assoc 0: s=10.5.0.4 8787, d=10.1.0.2 8787, len 100 SCTP: COOKIE_ECHO_CHUNK, len 88 SCTP: Sent: Assoc NULL: s=10.1.0.2 8787, d=10.5.0.4 8787, len 16 SCTP: COOKIE_ACK_CHUNK SCTP: Recv: Assoc 0: s=10.5.0.4 8787, d=10.1.0.2 8787, len 144 SCTP: SACK_CHUNK, TSN ack: 7DD7E423, rwnd 18000, num frags 0 SCTP: DATA_CHUNK, 4/0/100/4F2D8235 SCTP: Sent: Assoc 0: s=10.1.0.2 8787, d=10.5.0.4 8787, len 28 SCTP: SACK_CHUNK, TSN ack: 4F2D8235, rwnd 8900, num frags 0 SCTP: Sent: Assoc 0: s=10.1.0.2 8787, d=10.5.0.4 8787, len 128 SCTP: DATA_CHUNK, 4/0/100/7DD7E424 SCTP: Recv: Assoc 0: s=10.5.0.4 8787, d=10.1.0.2 8787, len 28 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 270 PRI Backhaul and IUA Support Using SCTP Troubleshooting Tips
- 283. SCTP: SACK_CHUNK, TSNack: 7DD7E424, rwnd 17900, num frags 0 SCTP: Recv: Assoc 0: s=10.6.0.4 8787, d=10.2.0.2 8787, len 44 SCTP: HEARTBEAT_CHUNK SCTP: Sent: Assoc 0: s=10.2.0.2 8787, d=10.6.0.4 8787, len 44 SCTP: HEARTBEAT_ACK_CHUNK SCTP: Recv: Assoc 0: s=10.5.0.4 8787, d=10.1.0.2 8787, len 128 SCTP: DATA_CHUNK, 7/0/100/4F2D8236 SCTP: Sent: Assoc 0: s=10.1.0.2 8787, d=10.5.0.4 8787, len 144 SCTP: SACK_CHUNK, TSN ack: 4F2D8236, rwnd 9000, num frags 0 SCTP: DATA_CHUNK, 7/0/100/7DD7E425 SCTP: Recv: Assoc 0: s=10.5.0.4 8787, d=10.1.0.2 8787, len 28 SCTP: SACK_CHUNK, TSN ack: 7DD7E424, rwnd 18000, num frags 0 SCTP: Recv: Assoc 0: s=10.5.0.4 8787, d=10.1.0.2 8787, len 28 SCTP: SACK_CHUNK, TSN ack: 7DD7E425, rwnd 17900, num frags 0 SCTP: Recv: Assoc 0: s=10.5.0.4 8787, d=10.1.0.2 8787, len 128 SCTP: DATA_CHUNK, 4/1/100/4F2D8237 Sample Output for the debug ip sctp segmentv Command This command generates multiple lines of output for each datagram sent and received.Use with extreme caution in a live network. Caution The following output shows an example in which an association is established, a few heartbeats are sent, the remote endpoint fails, and the association is restarted. Router# debug ip sctp segmentv SCTP: Sent: Assoc 0: s=10.1.0.2 8787, d=10.5.0.4 8787, len 56, ver tag 0 SCTP: INIT_CHUNK, len 42 SCTP: Initiate Tag: B131ED6A, Initial TSN: B131ED6A, rwnd 9000 SCTP: Streams Inbound: 13, Outbound: 13 SCTP: IP Addr: 10.1.0.2 SCTP: IP Addr: 10.2.0.2 SCTP: Supported addr types: 5 SCTP: Recv: Assoc 0: s=10.5.0.4 8787, d=10.1.0.2 8787, len 56, ver tag 0 SCTP: INIT_CHUNK, len 42 SCTP: Initiate Tag: 5516B2F3, Initial TSN: 5516B2F3, rwnd 18000 SCTP: Streams Inbound: 13, Outbound: 13 SCTP: IP Addr: 10.5.0.4 SCTP: IP Addr: 10.6.0.4 SCTP: Supported addr types: 5 SCTP: Sent: Assoc NULL: s=10.1.0.2 8787, d=10.5.0.4 8787, len 136, ver tag 5516B2F3 SCTP: INIT_ACK_CHUNK, len 124 SCTP: Initiate Tag: B131ED6A, Initial TSN: B131ED6A, rwnd 9000 SCTP: Streams Inbound: 13, Outbound: 13 SCTP: Responder cookie len 88 SCTP: IP Addr: 10.1.0.2 SCTP: IP Addr: 10.2.0.2 SCTP: Recv: Assoc 0: s=10.5.0.4 8787, d=10.1.0.2 8787, len 100, ver tag B131ED6A SCTP: COOKIE_ECHO_CHUNK, len 88 SCTP: Sent: Assoc NULL: s=10.1.0.2 8787, d=10.5.0.4 8787, len 16, ver tag 5516B2F3 SCTP: COOKIE_ACK_CHUNK SCTP: Recv: Assoc 0: s=10.5.0.4 8787, d=10.1.0.2 8787, len 144, ver tag B131ED6A SCTP: SACK_CHUNK, len 16 SCTP: TSN ack: (0xB131ED69) SCTP: Rcv win credit: 18000 SCTP: Num frags: 0 SCTP: DATA_CHUNK, flags 3, chunkLen 116 SCTP: DATA_CHUNK, 0/0/100/5516B2F3 SCTP: Sent: Assoc 0: s=10.1.0.2 8787, d=10.5.0.4 8787, len 28, ver tag 5516B2F3 SCTP: SACK_CHUNK, len 16 SCTP: TSN ack: (0x5516B2F3) SCTP: Rcv win credit: 8900 SCTP: Num frags: 0 SCTP: Sent: Assoc 0: s=10.1.0.2 8787, d=10.5.0.4 8787, len 128, ver tag 5516B2F3 SCTP: DATA_CHUNK, flags 3, chunkLen 116 SCTP: DATA_CHUNK, 0/0/100/B131ED6A SCTP: Recv: Assoc 0: s=10.6.0.4 8787, d=10.2.0.2 8787, len 44, ver tag B131ED6A ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 271 PRI Backhaul and IUA Support Using SCTP Troubleshooting Tips
- 284. SCTP: HEARTBEAT_CHUNK SCTP: Sent:Assoc 0: s=10.2.0.2 8787, d=10.6.0.4 8787, len 44, ver tag 5516B2F3 SCTP: HEARTBEAT_ACK_CHUNK SCTP: Recv: Assoc 0: s=10.5.0.4 8787, d=10.1.0.2 8787, len 28, ver tag B131ED6A SCTP: SACK_CHUNK, len 16 Sample Output for the debug ip sctp signal Command and the debug ip sctp state Command This example shows signals that are sent from SCTP to the application or ULP. A signal is also sent to the ULP when new data is available to be received, but this signal is not shown in the output below because it occurs infrequently. In the following example, a new association is requested and established. The peer then restarts the association and notes that the association failed and is being reestablished. The local peer then indicates that the association has failed because it has tried to retransmit the specified chunk more than the maximum number of times without success. As a result, the association fails (because of communication loss) and is terminated. The ULP requests that the association be attempted again, and this attempt succeeds. A shutdown is then received from the remote peer, and the local peer enters the shutdown acknowledge sent state, which is followed by the association being terminated. Again, another association attempt is made and succeeds. Router# debug ip sctp signal Router# debug ip sctp state <new assoc attempt> 00:20:08: SCTP: Assoc 0: state CLOSED -> COOKIE_WAIT 00:20:15: SCTP: Assoc 0: state COOKIE_WAIT -> ESTABLISHED 00:20:15: SCTP: Assoc 0: Sent ASSOC_UP signal for CONFIGD_ASSOC 00:21:03: SCTP: Assoc 0: Restart rcvd from peer 00:21:03: SCTP: Assoc 0: Sent ASSOC_RESTART signal 00:21:04: SCTP: Assoc 0: chunk 62EA7F40 retransmitted more than max times, failing assoc 00:21:04: SCTP: Assoc 0: Sent ASSOC_FAILED signal, reason: SCTP_COMM_LOST 00:21:04: SCTP: Assoc 0: Sent ASSOC_TERMINATE signal 00:21:04: SCTP: Assoc 0: state ESTABLISHED -> CLOSED <new assoc attempt> 00:21:04: SCTP: Assoc 0: state CLOSED -> COOKIE_WAIT 00:21:04: SCTP: Assoc 0: state COOKIE_WAIT -> COOKIE_ECHOED 00:21:04: SCTP: Assoc 0: state COOKIE_ECHOED -> ESTABLISHED 00:21:04: SCTP: Assoc 0: Sent ASSOC_UP signal for CONFIGD_ASSOC 00:21:04: SCTP: Assoc 0: Sent TERMINATE_PENDING signal 00:21:04: SCTP: Assoc 0: state ESTABLISHED -> SHUTDOWN_ACKSENT 00:21:04: SCTP: Assoc 0: Sent ASSOC_TERMINATE signal 00:21:04: SCTP: Assoc 0: state SHUTDOWN_ACKSENT -> CLOSED <new assoc attempt> 00:21:04: SCTP: Assoc 0: state CLOSED -> COOKIE_WAIT 00:21:04: SCTP: Assoc 0: state COOKIE_WAIT -> COOKIE_ECHOED 00:21:04: SCTP: Assoc 0: state COOKIE_ECHOED -> ESTABLISHED 00:21:04: SCTP: Assoc 0: Sent ASSOC_UP signal for CONFIGD_ASSOC In the following example, the associations themselves are stable, but a particular destination address fails. Because both currently established associations are using the same destination addresses (with different ports), both of the associations indicate the destination address failure. When the destination address again becomes active, the upper-layer protocols are informed. Router# 00:26:27: SCTP: Assoc 1: Sent DESTADDR_FAILED signal for destaddr 10.6.0.4 00:26:28: SCTP: Assoc 0: Sent DESTADDR_FAILED signal for destaddr 10.6.0.4 Router# 00:30:41: SCTP: Assoc 1: Sent DESTADDR_ACTIVE signal for destaddr 10.6.0.4 00:30:41: SCTP: Assoc 0: Sent DESTADDR_ACTIVE signal for destaddr 10.6.0.4 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 272 PRI Backhaul and IUA Support Using SCTP Troubleshooting Tips
- 285. Sample Output forthe debug ip sctp sndchunks Command This command generates significant data if there is any significant amount of traffic flowing. Use with extreme caution in live networks. Caution Router# debug ip sctp sndchunks SCTP: Assoc 0: ApplSend, chunk: 0/10412/100/A23134F8 to 10.5.0.4 SCTP: Assoc 0: ApplSend, chunk: 5/10443/100/A23134F9 to 10.5.0.4 SCTP: Assoc 0: ApplSend, chunk: 5/10448/100/A231355C to 10.5.0.4 SCTP: Assoc 0: Set oldest chunk for dest 10.5.0.4 to TSN A23134F8 SCTP: Assoc 0: Bundling data, added 0/10412/100/A23134F8, outstanding 100 SCTP: Assoc 0: Bundling data, added 5/10443/100/A23134F9, outstanding 200 SCTP: Assoc 0: Bundling data, added 4/10545/100/A23134FA, outstanding 300 SCTP: Assoc 0: Bundling data, added 10/10371/100/A23134FB, outstanding 400 SCTP: Assoc 0: Bundling data, added 11/10382/100/A23134FC, outstanding 500 SCTP: Assoc 0: Process Sack Chunk, CumTSN=A231350F, numFrags=0 SCTP: Assoc 0: Reset oldest chunk on addr 10.5.0.4 to A2313510 SCTP: Assoc 0: Process Sack Chunk, CumTSN=A2313527, numFrags=0 SCTP: Assoc 0: Reset oldest chunk on addr 10.5.0.4 to A2313528 SCTP: Assoc 0: Process Sack Chunk, CumTSN=A231353F, numFrags=0 SCTP: Assoc 0: Reset oldest chunk on addr 10.5.0.4 to A2313540 SCTP: Assoc 0: Process Sack Chunk, CumTSN=A2313557, numFrags=0 SCTP: Assoc 0: Reset oldest chunk on addr 10.5.0.4 to A2313558 SCTP: Assoc 0: ApplSend, chunk: 10/10385/100/A23135BE to 10.5.0.4 SCTP: Assoc 0: ApplSend, chunk: 8/10230/100/A23135BF to 10.5.0.4 SCTP: Assoc 0: ApplSend, chunk: 5/10459/100/A23135C0 to 10.5.0.4 SCTP: Assoc 0: ApplSend, chunk: 4/10558/100/A23135C1 to 10.5.0.4 SCTP: Assoc 0: Set oldest chunk for dest 10.5.0.4 to TSN A231355D SCTP: Assoc 0: Bundling data, added 5/10449/100/A231355D, outstanding 100 SCTP: Assoc 0: Bundling data, added 3/10490/100/A231355E, outstanding 200 SCTP: Assoc 0: Process Sack Chunk, CumTSN=A23135A4, numFrags=0 SCTP: Assoc 0: Reset oldest chunk on addr 10.5.0.4 to A23135A5 SCTP: Assoc 0: Process Sack Chunk, CumTSN=A23135BC, numFrags=0 SCTP: Assoc 0: Reset oldest chunk on addr 10.5.0.4 to A23135BD SCTP: Assoc 0: Process Sack Chunk, CumTSN=A23135C1, numFrags=0 SCTP: Assoc 0: ApplSend, chunk: 5/10460/100/A23135C2 to 10.5.0.4 SCTP: Assoc 0: ApplSend, chunk: 5/10461/100/A23135C3 to 10.5.0.4 SCTP: Assoc 0: ApplSend, chunk: 11/10403/100/A2313626 to 10.5.0.4 SCTP: Assoc 0: Set oldest chunk for dest 10.5.0.4 to TSN A23135C2 SCTP: Assoc 0: Bundling data, added 5/10460/100/A23135C2, outstanding 100 SCTP: Assoc 0: Bundling data, added 5/10461/100/A23135C3, outstanding 200 SCTP: Assoc 0: Bundling data, added 5/10462/100/A23135C4, outstanding 300 SCTP: Assoc 0: Bundling data, added 4/10559/100/A23135C5, outstanding 400 SCTP: Assoc 0: Bundling data, added 4/10560/100/A23135C6, outstanding 500 SCTP: Assoc 0: Bundled 12 chunk(s) in next dgram to 10.5.0.4 SCTP: Assoc 0: Bundling data, added 1/10418/100/A2313622, outstanding 9700 SCTP: Assoc 0: Bundling data, added 3/10502/100/A2313623, outstanding 9800 SCTP: Assoc 0: Bundling data, added 7/10482/100/A2313624, outstanding 9900 SCTP: Assoc 0: Bundling data, added 3/10503/100/A2313625, outstanding 10000 SCTP: Assoc 0: Bundling data, added 11/10403/100/A2313626, outstanding 10100 SCTP: Assoc 0: Bundled 5 chunk(s) in next dgram to 10.5.0.4 SCTP: Assoc 0: Mark chunk A23135C2 for retrans SCTP: Assoc 0: Mark chunk A23135C3 for retrans SCTP: Assoc 0: Mark chunk A23135C4 for retrans SCTP: Assoc 0: Mark chunk A23135C5 for retrans SCTP: Assoc 0: Mark chunk A23135C6 for retrans SCTP: Assoc 0: Mark chunk A23135C7 for retrans SCTP: Assoc 0: Mark chunk A23135C8 for retrans SCTP: Assoc 0: Mark chunk A23135C9 for retrans SCTP: Assoc 0: Mark chunk A23135CA for retrans SCTP: Assoc 0: Bundled 6 chunk(s) in next dgram to 10.6.0.4 SCTP: Assoc 0: Mark chunk A23135C2 for retrans SCTP: Assoc 0: Mark chunk A23135C3 for retrans SCTP: Assoc 0: Mark chunk A23135C4 for retrans ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 273 PRI Backhaul and IUA Support Using SCTP Troubleshooting Tips
- 286. Sample Output forthe debug ip sctp timer Command This command generates a significant amount of output. Use with extreme caution in a live network.Caution Router# debug ip sctp timer SCTP: Assoc 0: Starting CUMSACK timer SCTP: Timer already started, not restarting SCTP: Assoc 0: Starting CUMSACK timer SCTP: Timer already started, not restarting SCTP: Assoc 0: Timer BUNDLE triggered SCTP: Assoc 0: Starting RETRANS timer for destaddr 10.5.0.4 SCTP: Assoc 0: Starting RETRANS timer for destaddr 10.5.0.4 SCTP: Timer already started, not restarting SCTP: Assoc 0: Starting RETRANS timer for destaddr 10.5.0.4 SCTP: Timer already started, not restarting SCTP: Assoc 0: Starting RETRANS timer for destaddr 10.5.0.4 SCTP: Timer already started, not restarting SCTP: Assoc 0: Stopping RETRANS timer for destaddr 10.5.0.4 SCTP: Assoc 0: Starting RETRANS timer for destaddr 10.5.0.4 SCTP: Assoc 0: Stopping RETRANS timer for destaddr 10.5.0.4 SCTP: Assoc 0: Starting CUMSACK timer SCTP: Timer already started, not restarting SCTP: Assoc 0: Starting CUMSACK timer SCTP: Timer already started, not restarting SCTP: Assoc 0: Starting CUMSACK timer SCTP: Timer already started, not restarting SCTP: Assoc 0: Starting CUMSACK timer SCTP: Timer already started, not restarting SCTP: Assoc 0: Starting CUMSACK timer SCTP: Timer already started, not restarting SCTP: Assoc 0: Stopping CUMSACK timer SCTP: Assoc 0: Starting CUMSACK timer SCTP: Assoc 0: Starting CUMSACK timer SCTP: Timer already started, not restarting Sample Output for the debug ip sctp warnings Command Router# debug ip sctp warnings SCTP: Assoc 0: No cookie in InitAck, discarding SCTP: Assoc 0: Incoming INIT_ACK: inbound streams reqd 15, allowed 13 SCTP: Assoc 0: Incoming INIT_ACK request: outbound streams req'd 13, allowed 1 SCTP: Assoc 0: Remote verification tag in init ack is zero, discarding SCTP: Remote verification tag in init is zero, discarding SCTP: Assoc 0: Rwnd less than min allowed (1500) in incoming INITACK, rcvd 0 SCTP: Assoc 0: Rwnd less than min allowed (1500) in incoming INITACK, rcvd 1499 SCTP: Rwnd in INIT too small (0), discarding SCTP: Rwnd in INIT too small (1499), discarding SCTP: Unknown INIT param 16537 (0x4099), length 8 SCTP: Assoc 0: Unknown INITACK param 153 (0x99), length 8 SCTP: Assoc 0: No cookie in InitAck, discarding SCTP: Assoc 0: No cookie in InitAck, discarding SCTP: Processing INIT, invalid param len 0, discarding... SCTP: Assoc 0: Processing INITACK, invalid param len 0, discarding... Sample Output for the debug iua Command The following example shows that state debugging is turned on for all application servers and that the application server is active: Router# debug iua as state all IUA :state debug turned ON for ALL AS 00:11:52:IUA:AS as1 number of ASPs up is 1 00:11:57:IUA:AS as1 xsition AS-Up --> AS-Active, cause - ASP asp1 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 274 PRI Backhaul and IUA Support Using SCTP Troubleshooting Tips
- 287. The following exampleshows that peer message debugging is turned on for all digital signal processors (DSPs) and that the ASP is active: Router# debug iua asp peer-msg all IUA :peer message debug turned ON for ALL ASPs Router# 00:04:58:IUA :recieved ASP_UP message on ASP asp1 00:04:58:IUA:ASP asp1 xsition ASP-Down --> ASP-Up , cause - rcv peer msg ASP-UP 00:04:58:IUA:sending ACK of type 0x304 to asp asp1 00:05:03:IUA:recv ASP_ACTIVE message for ASP asp1 00:05:03:IUA:ASP asp1 xsition ASP-Up --> ASP-Active, cause - rcv peer msg ASP-Active Configuration Examples for SCTP Options Application-Server and Application-Server-Process Example The following shows sample SCTP configuration options using the help menu for the as and asp commands: Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# iua Router(config-iua)# as as1 ? A.B.C.D Specify (up to two) Local IP address Fail-Over-Timer Configure the Fail-Over timer for this AS sctp-startup-rtx Configure the SCTP max startup retransmission timer sctp-streams Configure the number of SCTP streams for this AS sctp-t1init Configure the SCTP T1 init timer Router(config-iua)# as as1 sctp-startup-rtx ? <2-20> Set SCTP Maximum Startup Retransmission Interval Router(config-iua)# as as1 sctp-streams ? <1-56> Specify number of SCTP streams for association Router(config-iua)# as as1 sctp-t1init ? <1000-60000> Set SCTP T1 init timer (in milliseconds) Router(config-iua)# asp asp1 as as1 ? A.B.C.D Specify (up to two) IP addresses of the call-agent Router(config-iua)# asp asp1 ? AS Specify which AS this ASP belongs to IP-Precedence Set IP precedence bits for a IP address in this ASP sctp-keepalives Modify the keep-alive behaviour of an IP address in this ASP sctp-max-assoc Set SCTP max association retransmissions for this ASP sctp-path-retran Set SCTP path retransmissions for this ASP sctp-t3-timeout Set SCTP T3 retransmission timeout for this ASP Router(config-iua)# asp asp1 sctp-keep ? A.B.C.D specify the IP address to enable/disable keep alives Router(config-iua)# asp asp1 sctp-keepalive 10.10.10.10 ? <1000-60000> specify keep alive interval (in milliseconds) Router(config-iua)# asp asp1 sctp-max-assoc ? A.B.C.D specify the IP address Router(config-iua)# asp asp1 sctp-max-assoc 10.10.10.10 ? <2-20> specify maximum associations default use default value of max associations for this address Router(config-iua)# asp asp1 sctp-path-retran ? A.B.C.D specify the IP address Router(config-iua)# asp asp1 sctp-path-retran 10.10.10.10 ? <2-10> specify maximum path retransmissions default use default value of max path retrans for this address Router(config-iua)# asp asp1 sctp-t3-timeout ? A.B.C.D specify the IP address ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 275 PRI Backhaul and IUA Support Using SCTP Configuration Examples for SCTP Options
- 288. Router(config-iua)# asp asp1sctp-t3-timeout 10.10.10.10 ? <300-60000> specify T3 retransmission timeout (in milliseconds) default use default value of T3 for this address Application-Server and Application-Server-Process with IUA Example The following example shows a running application-server configuration with IUA configured with one application server (as1) and two application-server processes (asp1 and asp2). Four T1s (T1 1/0, 1/1, 2/0, 2/1) are configured to use IUA backhaul. Router# show running-config Building configuration... Current configuration :2868 bytes ! version 12.2 no service single-slot-reload-enable service timestamps debug uptime service timestamps log uptime no service password-encryption ! hostname iua_3660_b ! logging rate-limit console 10 except errors ! memory-size iomem 30 voice-card 1 ! voice-card 2 ! voice-card 3 ! voice-card 4 ! voice-card 5 ! voice-card 6 ! ip subnet-zero ! no ip domain-lookup ! no ip dhcp-client network-discovery iua AS as1 10.21.0.2 9900 ASP asp1 AS as1 10.23.0.16 9900 ASP asp2 AS as1 10.23.0.16 9911 isdn switch-type primary-5ess ! fax interface-type modem mta receive maximum-recipients 0 ! controller T1 1/0 framing esf clock source line primary linecode b8zs pri-group timeslots 1-24 service mgcp ! controller T1 1/1 framing esf linecode b8zs pri-group timeslots 1-24 service mgcp ! controller T1 2/0 framing esf linecode b8zs pri-group timeslots 1-24 service mgcp ! controller T1 2/1 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 276 PRI Backhaul and IUA Support Using SCTP Application-Server and Application-Server-Process with IUA Example
- 289. framing esf linecode b8zs pri-grouptimeslots 1-24 service mgcp ! controller T1 3/0 framing sf linecode ami ! controller T1 3/1 framing sf linecode ami ! controller T1 4/0 framing sf linecode ami ! controller T1 4/1 framing sf linecode ami ! controller T1 5/0 framing sf linecode ami ! controller T1 5/1 framing sf linecode ami ! controller T1 6/0 framing sf linecode ami ! controller T1 6/1 framing sf linecode ami ! interface FastEthernet0/0 ip address 10.21.0.3 255.255.0.0 secondary ip address 10.21.0.2 255.255.0.0 speed 10 half-duplex ! interface FastEthernet0/1 no ip address shutdown duplex auto speed auto ! interface Serial1/0:23 no ip address ip mroute-cache no logging event link-status isdn switch-type primary-5ess isdn incoming-voice voice isdn bind-l3 iua-backhaul as1 no cdp enable ! interface Serial1/1:23 no ip address ip mroute-cache no logging event link-status isdn switch-type primary-5ess isdn incoming-voice voice isdn guard-timer 3000 isdn T203 10000 isdn bind-l3 iua-backhaul as1 no cdp enable ! interface Serial2/0:23 no ip address ip mroute-cache no logging event link-status isdn switch-type primary-5ess ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 277 PRI Backhaul and IUA Support Using SCTP Application-Server and Application-Server-Process with IUA Example
- 290. isdn incoming-voice voice isdnguard-timer 3000 isdn T203 10000 isdn bind-l3 iua-backhaul as1 no cdp enable ! interface Serial2/1:23 no ip address ip mroute-cache no logging event link-status isdn switch-type primary-5ess isdn incoming-voice voice isdn T203 10000 isdn bind-l3 iua-backhaul as1 no cdp enable ! ip classless ip route 10.0.0.0 255.0.0.0 10.21.0.17 ip route 11.0.0.10 255.255.255.255 FastEthernet0/0 ip route 172.0.0.0 255.0.0.0 172.18.194.1 ip http server ! snmp-server manager ! call rsvp-sync ! voice-port 1/0:23 ! voice-port 1/1:23 ! voice-port 2/0:23 ! voice-port 2/1:23 ! no mgcp timer receive-rtcp ! mgcp profile default ! dial-peer cor custom ! line con 0 transport input none line aux 0 line vty 0 4 login ! end ISDN Signaling Backhaul Example The following sample output shows that Layers 1, 2, and 3 are enabled and active. Layer 3 shows the number of active ISDN calls. Notice that the Layer 2 protocol is Q.921 and the Layer 3 protocol is BACKHAUL. This verifies that the system is configured to backhaul ISDN. If you are connected to a live line, you should see that Layer 1 is active and Layer 2 is MULTIPLE_FRAME_ESTABLISHED, meaning that the ISDN line is up and active. Router# show isdn status *00:03:34.423 UTC Sat Jan 1 2000 Global ISDN Switchtype = primary-net5 ISDN Serial1:23 interface dsl 0, interface ISDN Switchtype = primary-net5 L2 Protocol = Q.921 L3 Protocol(s) = BACKHAUL Layer 1 Status: ACTIVE Layer 2 Status: ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 278 PRI Backhaul and IUA Support Using SCTP ISDN Signaling Backhaul Example
- 291. TEI = 0,Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED Layer 3 Status: NLCB:callid=0x0, callref=0x0, state=31, ces=0 event=0x0 NLCB:callid=0x0, callref=0x0, state=0, ces=1 event=0x0 0 Active Layer 3 Call(s) Activated dsl 0 CCBs = 0 Number of active calls = 0 Number of available B-channels = 23 Total Allocated ISDN CCBs = 0 IUA Configuration Example The following is an example of an application-server configuration on a gateway: as as5400-3 10.4.8.69 10.4.9.69 2577 In the configuration above, an application server named as-named as5400-3 is configured to use two local IP addresses and a port number of 2577. IP address values that are set apply to all IP addresses of the ASP. The following configuration example defines a remote signaling controller asp1 at two IP addresses for the application server named as5400-3. The remote SCTP port number is 2577: Router(config-iua)# as as5400-3 10.4.8.69 10.4.9.69 2477 Router(config-iua)# asp asp1 as as5400-3 10.4.8.68 10.4.9.68 2577 Multiple ASPs can be defined for a single application server for the purpose of redundancy, but only one ASP can be active. The other ASP is inactive and only becomes active after fail-over. In the Cisco MGC solution, a signaling controller is always the client that initiates the association with a gateway. During the initiation phase, you can request outbound and inbound stream numbers, but the gateway only allows a number that is at least one digit higher than the number of interfaces (T1/E1) allowed for the platform. The number of streams to assign to a given association is implementation dependent. During the initialization of the IUA association, you need to specify the total number of streams that can be used. Each D channel is associated with a specific stream within the association. With multiple trunk group support, every interface can potentially be a separate D channel. At startup, the IUA code checks for all the possible T1, E1, or T3 interfaces and sets the total number of inbound and outbound streams supported accordingly. In most cases, there is only a need for one association between the GW and the MGC. For the rare case that you are configuring multiple application-server associations to various MGCs, the overhead from the unused streams would have minimal impact. The NFAS D channels are configured for one or more interfaces, where each interface is assigned a unique stream ID. The total number of streams for the association needs to include an additional stream for the SCTP management messages. So during startup the IUA code adds one to the total number of interfaces (streams) found. You have the option to manually configure the number of streams per association. In the backhaul scenario, if the number of D channel links is limited to one, allowing the number of streams to be configurable avoids the unnecessary allocation of streams in an association that will never be used. For multiple associations between a GW and multiple MGCs, the configuration utility is useful in providing only the necessary number of streams per association. The overhead from the streams allocated but not used in the association is negligible. If the number of streams is manually configured through the CLI, the IUA code cannot distinguish between a startup event, which automatically sets the streams to the number of interfaces, or if the value is set manually during runtime. If you are configuring the number of SCTP streams manually, you must add one plus the number of interfaces using the sctp-streams keyword with the as command. Otherwise, IUA needs to always add one for the management stream, and the total number of streams increments by one after every reload. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 279 PRI Backhaul and IUA Support Using SCTP IUA Configuration Example
- 292. When you setthe SCTP stream with the CLI, you cannot change the inbound and outbound stream support once the association is established with SCTP. The value takes effect when you first remove the IUA application-server configuration and then configure it back as the same application server or a new one. The other option is to reload the router. The following is an example of an application-server configuration on a gateway. The configuration shows that an application server named as5400-3 is configured to use two local IP addresses and a port number of 2577: Router(config-iua)# as as5400-3 10.1.2.34 10.1.2.35 2577 The following example sets the failover time (in milliseconds) between 1 and 10 seconds. Entering a value of 1000 would equal one second. Entering a value of 10000 would equal 10 seconds. In this example, the failover timer has been set to 10 seconds: Router(config-iua)# as as5400-3 fail-over 10000 The following example specifies the number of SCTP streams for this association. In this example, 57 is the maximum number of SCTP streams allowed: Router(config-iua)# as as5400-3 sctp-streams 57 The following example sets the SCTP maximum startup retransmission interval. In this example, 20 is the maximum interval allowed: Router(config-iua)# as as5400-3 sctp-startup 20 The following example sets the SCTP T1 initiation timer in milliseconds. In this example, 60000 is the maximum time allowed: Router(config-iua)# as as5400-3 sctp-t1init 60000 The following example specifies the IP address to enable and disable keepalives: Router(config-iua)# asp asp1 sctp-keepalive 10.1.2.34 The following example specifies the keepalive interval in milliseconds. Valid values range from 1000 to 60000. In this example, the maximum value of 60000 ms is used: Router(config-iua)# asp asp1 sctp-keepalive 10.10.10.10 60000 The following example specifies the IP address for the SCTP maximum association and the maximum association value. Valid values are from 2 to 20. The default is 20, which is the maximum value allowed: Router(config-iua)# asp asp1 sctp-max-association 10.10.10.10 20 The following example specifies the IP address for the SCTP path retransmission and the maximum path retransmission value. Valid values are from 2 to 10. The default is 10, which is the maximum value allowed: Router(config-iua)# asp asp1 sctp-path-retransmissions 10.10.10.10 10 The following examples specifies the IP address for SCTP T3 timeout and specifies the T3 timeout value in milliseconds. Valid timeout values are from 300 to 60000. The default is 60000, which is the maximum timeout value allowed: Router(config-iua)# asp asp1 sctp-t3-timeout 10.10.10.10 60000 The following example configures the following: 1 Creates an IUA application server (Cisco AS5300-17) that has two local IP addresses (10.0.0.07 and 10.1.1.17) and local port 2097. 2 IUA application server Cisco AS5300-17 is connected by two SCTP associations (ASP PGW A and ASP PGW B) to two hot-standby Cisco PGW 2200s (Cisco PGW 2200 PGW A and Cisco PGW 2200 PGW ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 280 PRI Backhaul and IUA Support Using SCTP IUA Configuration Example
- 293. B). Cisco PGW2200 PGW A has remote IP addresses 10.0.0.00 and 10.1.1.10, and Cisco PGW 2200 PGW B has remote IP addresses 10.0.0.06 and 10.1.1.16. 3 Two NFAS groups (nfas-group 1 and nfas-group 2), which are both bound to IUA application server as5300-17. 4 Two trunk groups (trunk-group 11 and trunk-group 22)--Trunk-group 11 is bound to interface Dchannel0 and trunk-group 22 is bound to interface Dchannel2. Router(config-iua)# as as5300-17 10.0.0.07 10.1.1.17 2097 Router(config-iua)# asp pgwa AS as5300-17 10.0.0.00 10.1.1.10 2097 Router(config-iua)# asp pgwb AS as5300-17 10.0.0.06 10.1.1.16 2097 The figure below shows the configuration above in diagram form with two outgoing POTS dial-peers (dial-peer 1 and dial-peer 2)--dial-peer 1 points to trunk-group 11, and dial-peer 2 points to trunk-group 22. Figure 14: Specific ASP Example Configuration The following is example output from the above configuration: iua AS as5300-17 10.0.0.07 10.1.1.17 2097 ASP pgwa AS as5300-17 10.0.0.00 10.1.1.10 2097 ASP pgwb AS as5300-17 10.0.0.06 10.1.1.16 2097 ! ! controller E1 0 framing NO-CRC4 clock source line primary pri-group timeslots 1-31 nfas-d primary nfas-int 0 nfas-group 1 iua as5300-17 ! controller E1 1 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 281 PRI Backhaul and IUA Support Using SCTP IUA Configuration Example
- 294. framing NO-CRC4 clock sourceline secondary 1 pri-group timeslots 1-31 nfas-d none nfas-int 1 nfas-group 1 ! controller E1 2 framing NO-CRC4 pri-group timeslots 1-31 nfas-d primary nfas-int 0 nfas-group 2 iua as5300-17 ! controller E1 3 framing NO-CRC4 pri-group timeslots 1-31 nfas-d none nfas-int 1 nfas-group 2 ! ! interface Ethernet0 description the ip is 10.0.0.06 for interface e0 ip address 10.0.0.06 255.255.255.0 no ip route-cache no ip mroute-cache ! interface FastEthernet0 description the primary ip is 10.1.1.16 for interface f0 ip address 10.1.1.10 255.255.255.0 no ip route-cache no ip mroute-cache duplex auto speed auto ! interface Dchannel0 no ip address trunk-group 11 isdn timer t309 100 isdn timer t321 30000 isdn incoming-voice modem isdn T303 20000 isdn negotiate-bchan resend-setup no cdp enable ! interface Dchannel2 no ip address trunk-group 22 isdn timer t309 100 isdn timer t321 30000 isdn incoming-voice modem isdn T303 20000 isdn negotiate-bchan resend-setup no cdp enable ! trunk group 11 ! trunk group 22 ! dial-peer voice 1 pots incoming called-number destination-pattern 997001 direct-inward-dial trunk-group 11 forward-digits all ! dial-peer voice 2 pots incoming called-number destination-pattern 997002 direct-inward-dial trunk-group 22 forward-digits all ! The following example shows a running application-server configuration with IUA configured with one application server (as1) and two ASPs (asp1 and asp2). Four T1s (T1 1/0, 1/1, 2/0, 2/1) are configured to use IUA backhaul. Router# show running config Building configuration... ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 282 PRI Backhaul and IUA Support Using SCTP IUA Configuration Example
- 295. Current configuration :2868bytes ! version 12.2 no service single-slot-reload-enable service timestamps debug uptime service timestamps log uptime no service password-encryption ! hostname iua_3660_b ! logging rate-limit console 10 except errors ! memory-size iomem 30 voice-card 1 ! voice-card 2 ! voice-card 3 ! voice-card 4 ! voice-card 5 ! voice-card 6 ! ip subnet-zero ! no ip domain-lookup ! no ip dhcp-client network-discovery iua AS as1 10.21.0.2 9900 ASP asp1 AS as1 10.23.0.16 9900 ASP asp2 AS as1 10.23.0.16 9911 isdn switch-type primary-5ess ! fax interface-type modem mta receive maximum-recipients 0 ! controller T1 1/0 framing esf clock source line primary linecode b8zs pri-group timeslots 1-24 service mgcp ! controller T1 1/1 framing esf linecode b8zs pri-group timeslots 1-24 service mgcp ! controller T1 2/0 framing esf linecode b8zs pri-group timeslots 1-24 service mgcp ! controller T1 2/1 framing esf linecode b8zs pri-group timeslots 1-24 service mgcp ! controller T1 3/0 framing sf linecode ami ! controller T1 3/1 framing sf linecode ami ! controller T1 4/0 framing sf linecode ami ! controller T1 4/1 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 283 PRI Backhaul and IUA Support Using SCTP IUA Configuration Example
- 296. framing sf linecode ami ! controllerT1 5/0 framing sf linecode ami ! controller T1 5/1 framing sf linecode ami ! controller T1 6/0 framing sf linecode ami ! controller T1 6/1 framing sf linecode ami ! interface FastEthernet0/0 ip address 10.21.0.3 255.255.0.0 secondary ip address 10.21.0.2 255.255.0.0 speed 10 half-duplex ! interface FastEthernet0/1 no ip address shutdown duplex auto speed auto ! interface Serial1/0:23 no ip address ip mroute-cache no logging event link-status isdn switch-type primary-5ess isdn incoming-voice voice isdn bind-l3 iua-backhaul as1 no cdp enable ! interface Serial1/1:23 no ip address ip mroute-cache no logging event link-status isdn switch-type primary-5ess isdn incoming-voice voice isdn guard-timer 3000 isdn T203 10000 isdn bind-l3 iua-backhaul as1 no cdp enable ! interface Serial2/0:23 no ip address ip mroute-cache no logging event link-status isdn switch-type primary-5ess isdn incoming-voice voice isdn guard-timer 3000 isdn T203 10000 isdn bind-l3 iua-backhaul as1 no cdp enable ! interface Serial2/1:23 no ip address ip mroute-cache no logging event link-status isdn switch-type primary-5ess isdn incoming-voice voice isdn T203 10000 isdn bind-l3 iua-backhaul as1 no cdp enable ! ip classless ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 284 PRI Backhaul and IUA Support Using SCTP IUA Configuration Example
- 297. ip route 10.0.0.0255.0.0.0 10.21.0.17 ip route 11.0.0.10 255.255.255.255 FastEthernet0/0 ip route 172.0.0.0 255.0.0.0 172.18.194.1 ip http server ! snmp-server manager ! call rsvp-sync ! voice-port 1/0:23 ! voice-port 1/1:23 ! voice-port 2/0:23 ! voice-port 2/1:23 ! no mgcp timer receive-rtcp ! mgcp profile default ! dial-peer cor custom ! line con 0 transport input none line aux 0 line vty 0 4 login ! end PRI Group on an MGC Example To modify a PRI group on a third-party call agent (MGC), the isdn bind commands must be removed from the D channel. The binding of the NFAS groups now takes place when you use the pri-group (pri-slt) command for IUA with SCTP. Use the following examples to help you with your configuration: • Controller configuration for primary span in an NFAS group for RLM. You can choose any time slot other than 24 to be the virtual container for the D channel parameters for ISDN: controller T1 3/0:1 framing esf pri-group timeslots 1-23 nfas-d primary nfas-int 0 nfas-group 1 • Controller configuration for primary span in an NFAS group for IUA: controller T1 3/0:1 framing esf pri-group timeslots 1-23 nfas-d primary nfas-int 0 nfas-group 1 iua as-1 SCTP Configuration Example You can implicitly configure the number of streams in SCTP by specifying only the serial interfaces that are configured to use IUA. The number of streams is bound to the actual number of interfaces supporting IUA. To support Cisco MGC solutions, you can configure any number of streams for each NFAS D channel, up to the total number of interfaces available in a given GW. For platforms using the PRI backhaul with SCTP and the ISDN Q.921 User Adaptation Layer (UAL), such as the Cisco 3660, you can configure the number of streams to match the number of PRIs that are actually backhauled to the Telcordia session manager. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 285 PRI Backhaul and IUA Support Using SCTP PRI Group on an MGC Example
- 298. The following examplesets the failover time (in milliseconds) between 1 and 10 seconds. Entering a value of 1000 would equal one second. Entering a value of 10000 would equal 10 seconds. In this example, the failover timer has been set to 10 seconds. The default value is 4000 msec. Once you have set the failover timer to a value, you can return it to its default of 4000 msec by using the no form of this command. Router(config-iua)# as as5400-3 fail-over 10000 The following example sets the SCTP maximum startup retransmission interval. Valid values are from 2 to 20: Router(config-iua)# as as1 sctp-startup-rtx 20 The following example specifies the number of SCTP streams for an association. Valid values are from 1 to 56: Router(config-iua)# as as1 sctp-streams 56 The following example sets the SCTP T1 initiation timer in milliseconds. Valid values are from 1000 to 60000: Router(config-iua)# as as1 sctp-t1init 60000 SCTP Migration from RLM to IUA Example The following changes have been made between RLM and IUA with SCTP. Use the examples in this section to help you with your configuration: • The D channel interface serial commands are now replaced by interface D channel commands. For RLM, the following format was used: interface Serial3/0:1:23 The :23 in the RLM example above, which typically corresponds with T1 configuration (:15 for E1 configuration), is no longer used. Note For IUA, the following format is used: interface Dchannel3/0:1 • The RLM group configuration must be removed from the D channel configuration. For RLM, remove the "isdn rlm-group 1" line shown in bold: interface Serial3/0:1:23 no ip address isdn switch-type primary-ni isdn incoming-voice modem isdn T321 30000 isdn T303 20000 isdn T200 2000 isdn rlm-group 1 isdn negotiate-bchan resend-setup isdn bchan-number-order ascending no cdp enable For IUA, use the following format: interface Dchannel3/0:1 no ip address ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 286 PRI Backhaul and IUA Support Using SCTP SCTP Migration from RLM to IUA Example
- 299. isdn timer t309100 isdn timer t321 30000 isdn incoming-voice modem isdn T303 20000 no isdn send-status-enquiry isdn negotiate-bchan resend-setup isdn bchan-number-order ascending no cdp enable Trunk Group Bound to an Application Server Example You can configure the NFAS primary D channel on one channelized T1 controller, and bind the D channel to an IUA application server by using the pri-group (pri-slt) command. This example uses a Cisco AS5400 and applies to T1, which has 24 timeslots and is used mainly in North America and Japan. You can choose any timeslot other than 24 to be the virtual container for the D channel parameters for ISDN. Router(config-controller)# pri-group timeslots 1-23 nfas-d primary nfas-int 0 nfas-group 1 iua as5400-4-1 The following example applies to E1, which has 32 timeslots and is used by countries other than North America and Japan. You can choose any timeslot other than 32 to be the virtual container for the D channel parameters for ISDN. Router(config-controller)# pri-group timeslots 1-31 nfas-d primary nfas-int 0 nfas-group 1 iua as5400-4-1 Additional References General ISDN References • "Overview of ISDN Voice Interfaces" --Describes relevant underlying technology; lists related documents, standards, MIBs, and RFCs; and describes how to obtain technical assistance • "Additional References" section --Lists additional ISDN references References Mentioned in This Chapter • Cisco 2600 Series Routers documentation at http://www.cisco.com/univercd/cc/td/doc/product/access/ acs_mod/cis2600/index.htm • Cisco 3600 Series Routers documentation at http://www.cisco.com/univercd/cc/td/doc/product/access/ acs_mod/cis3600/index.htm • Cisco 3700 Series Routers documentation at http://www.cisco.com/univercd/cc/td/doc/product/access/ acs_mod/cis3700/index.htm • Cisco AS5300 documentation at http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/ 5300/sw_conf/index.htm • Cisco AS5400 documentation at http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/ as5400/index.htm ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 287 PRI Backhaul and IUA Support Using SCTP Trunk Group Bound to an Application Server Example
- 300. • Cisco IAD2420Series IADs documentation at http://www.cisco.com/univercd/cc/td/doc/product/access/ iad/iad2420/index.htm • Cisco IOS Voice, Video, and Fax Command Reference , Release 12.2 T at http://www.cisco.com/univercd/ cc/td/doc/product/software/ios122/122cgcr/fvvfax_r/index.htm • Cisco IOS Voice, Video, and Fax Configuration Guide , Release 12.2T at http://www.cisco.com/univercd/ cc/td/doc/product/software/ios122/122cgcr/fvvfax_c/index.htm • Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide at http:// www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/swinstl/index.htm • Cisco Media Gateway Controller Software Release 9 Messages Reference Guide at http://www.cisco.com/ univercd/cc/td/doc/product/access/sc/rel9/errmsg/index.htm • Cisco Media Gateway Controller Software Release 9 MML Command Reference at http://www.cisco.com/ univercd/cc/td/doc/product/access/sc/rel9/mmlref/index.htm • Cisco Media Gateway Controller Software Release 9 Operations, Maintenance, and Troubleshooting Guide at http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/omts/index.htm • Cisco Media Gateway Controller Software Release 9 Provisioning Guide at http://www.cisco.com/ univercd/cc/td/doc/product/access/sc/rel9/prvgde/index.htm • Integrated Signaling Link Terminal , Cisco IOS Release 12.2(11)T at http://www.cisco.com/univercd/ cc/td/doc/product/software/ios122/122newft/122t/122t11/ftintslt.htm • IP Transfer Point (ITP) , Cisco IOS Release 12.2(2)MB at http://www.cisco.com/univercd/cc/td/doc/ product/software/ios122/122newft/122limit/122mb/122mb2/itp20/index.htm • PRI Backhaul Using the Stream Control Transmission Protocol and the ISDN Q.921 User Adaptation Layer at http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t4/ft_ 0546.htm • Stream Control Transmission Protocol (SCTP) feature at http://www.cisco.com/univercd/cc/td/doc/ product/software/ios122/122newft/122t/122t8/ft_sctp2.htm • Stream Control Transmission Protocol (SCTP) , RFC 2960, at http://rfc2960.x42.com/ • Support for IUA with SCTP at http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/mgcfm/ 941fm/fmiua.htm • Support for IUA with SCTP for Cisco Access Servers at http://www.cisco.com/univercd/cc/td/doc/product/ software/ios122/122newft/122t/122t15/ftgkrup.htm • Troubleshooting and Fault Management Commands (chapter in the System Management Commands part of the Cisco IOS Configuration Fundamentals Command Reference , Release 12.2) at http:// www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/ffun_r/ffrprt3/frf013.htm ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 288 PRI Backhaul and IUA Support Using SCTP Additional References
- 301. C H AP T E R 11 QSIG Support for Tcl IVR 2.0 This chapter describes how to implement the QSIG for Tool Command Language Interactive Voice Response (Tcl IVR) 2.0 feature. Q.SIG support is required for European countries to interconnect enterprise customers to a wholesale voice solution. The feature provides transparent Q.SIG interworking with a Tcl IVR 2.0 voice application on a Cisco IOS voice gateway. This functionality can be enabled using a new CLI on the POTS or VoIP dial-peer. Prior to this feature, Q.SIG messages were interpreted by the Tcl IVR 2.0 application, rather than passed transparently to the remote endpoint. Feature benefits include the following: • Increased interconnection options for VoIP wholesale providers • Elimination of unnecessary decoding Feature History for QSIG for Tcl IVR 2.0 ModificationRelease This feature was introduced.12.2(11)T • Finding Feature Information, page 289 • Prerequisites for Configuring QSIG for Tcl IVR 2.0, page 290 • Restrictions for Configuring QSIG for Tcl IVR 2.0, page 290 • Information About QSIG for Tcl IVR 2.0, page 291 • How to Configure QSIG for Tcl IVR 2.0, page 291 • Configuration Example for QSIG for Tcl IVR 2.0, page 295 • Additional References, page 297 Finding Feature Information Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 289
- 302. find information aboutthe features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required. Prerequisites for Configuring QSIG for Tcl IVR 2.0 • Perform the prerequisites that are listed in the "Prerequisites for Configuring an ISDN Voice Interface" section. • Establish a working IP network. For more information, see the Cisco IOS documentation set. See specifically the Cisco IOS IP and IP Routing Configuration Guide and the Cisco IOS Voice, Video, and Fax Configuration Guide. • Configure VoIP. For more information, see the Cisco IOS Voice, Video, and Fax Configuration Guide. • Download the Tcl scripts required for this feature from the following website: http://www.cisco.com/ cgi-bin/tablebuild.pl/tclware • Ensure that the VCWare version used for the Cisco AS5300 is compatible with the Cisco IOS image being used. VCWare applies only to the Cisco AS5300.Note Before configuring IVR Version 2.0 features, do the following: • Download the Tcl scripts and audio files to be used with this feature. Store them on a TFTP server configured to interact with your gateway access server. • Create the IVR/Tcl application script to use when configuring IVR. Store it on a server or at a location where it can be retrieved by the gateway access server. Then configure the server to use IVR with the application that you created. • Configure the dial peer on incoming POTS or VoIP dial peers. Restrictions for Configuring QSIG for Tcl IVR 2.0 Restrictions are described in the "Restrictions for Configuring ISDN Voice Interfaces". In addition, the following apply: • This feature is applicable to only the following: • VoIP and POTS dial peers • Tcl IVR version 2.0 only; not version 1.0 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 290 QSIG Support for Tcl IVR 2.0 Prerequisites for Configuring QSIG for Tcl IVR 2.0
- 303. Information About QSIGfor Tcl IVR 2.0 Q.SIG support is required for European countries to interconnect enterprise customers to a wholesale voice solution. The Q.SIG for Tcl IVR 2.0 feature provides transparent Q.SIG interworking when using a Tcl IVR version 2.0 voice application on a Cisco IOS voice gateway. This functionality can be enabled using a new CLI on the POTS or VoIP dial-peer. Prior to this feature, Q.SIG messages were interpreted by the Tcl IVR 2.0 application, rather than passed transparently to the remote endpoint. General information about ISDN voice interfaces is presented in the "Information About ISDN Voice Interfaces" section. Note How to Configure QSIG for Tcl IVR 2.0 Configuring QSIG To configure QSIG, perform the following steps. You must create the application that is to be called to interact with the dial peer (that collects the digits from the caller) before you configure the dial peer that will call this application. Note SUMMARY STEPS 1. enable 2. configure terminal 3. call application voice application-name location 4. exit DETAILED STEPS PurposeCommand or Action Enters privileged EXEC mode. Enter your password when prompted. enable Example: Router> enable Step 1 Enters configuration mode.configure terminal Example: Router# configure terminal Step 2 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 291 QSIG Support for Tcl IVR 2.0 Information About QSIG for Tcl IVR 2.0
- 304. PurposeCommand or Action Createsthe application to be used with your IVR script and indicates the location of the corresponding Tcl files that call application voice application-name location Example: Router(config)# call application voice ap1 172.16.4.4 Step 3 implement this application. The location can be a URL, directory, or TFTP server. Exits the current mode.exit Example: Router(config)# exit Step 4 Configuring Supplementary Service for a POTS Dial Peer To configure supplementary service for a POTS dial peer, perform the following steps. The supplementary-service pass-through command controls the interpretation of supplementary service (QSIG, H.450, and so on) on a gateway. When the CLI is enabled (that is, set to passthrough mode), the supplementary service message (usually in Q.931 facility message) is transparently sent to the destination gateway without any interpretation (raw). When the CLI is not enabled (the default), the supplementary service message is decoded and interpreted by the gateway. This CLI is available under VoIP or POTS dial peers. Note • This CLI has effect only if a Tcl IVR 2.0 application is configured on the same dial peer. The default session application always performs transparent Q.SIG interworking. Tcl IVR 1.0 applications always interpret and consume the Q.SIG supplementary services messages. SUMMARY STEPS 1. enable 2. configure terminal 3. dial-peer voice tag pots 4. application application-name 5. supplementary-service pass-through 6. exit ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 292 QSIG Support for Tcl IVR 2.0 Configuring Supplementary Service for a POTS Dial Peer
- 305. DETAILED STEPS PurposeCommand orAction Enters privileged EXEC mode. Enter your password when prompted. enable Example: Router> enable Step 1 Enters configuration mode.configure terminal Example: Router# configure terminal Step 2 Enters voice dial-peer configuration mode for the specified POTS dial peer. dial-peer voice tag pots Example: Router(config)# dial-peer voice 99 pots Step 3 Specifies the application that handles incoming voice calls associated with this dial-peer. application application-name Example: Router(config-dial-peer)# application ap1 Step 4 Configures supplementary service feature to transparently pass supplementary service to the next gateway. supplementary-service pass-through Example: Router(config-dial-peer)# supplementary-service pass-through Step 5 Exits the current mode.exit Example: Router(config-dial-peer)# exit Step 6 Configuring Supplementary Service for a VoIP Dial Peer To configure supplementary service for a VoIP dial peer, perform the following steps. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 293 QSIG Support for Tcl IVR 2.0 Configuring Supplementary Service for a VoIP Dial Peer
- 306. SUMMARY STEPS 1. enable 2.configure terminal 3. dial-peer voice tag voip 4. application application-name 5. supplementary-service pass-through 6. exit DETAILED STEPS PurposeCommand or Action Enters privileged EXEC mode. Enter your password when prompted. enable Example: Router> enable Step 1 Enters configuration mode.configure terminal Example: Router# configure terminal Step 2 Enters voice dial-peer configuration mode for the specified VoIP dial peer. dial-peer voice tag voip Example: Router(config)# dial-peer voice 96 voip Step 3 Specifies the application that handles incoming voice calls associated with this dial-peer.' application application-name Example: Router(config-dial-peer)# application ap5 Step 4 Configures supplementary service feature to transparently pass supplementary service to the next gateway. supplementary-service pass-through Example: Router(config-dial-peer)# supplementary-service pass-through Step 5 Exits the current mode.exit Example: Router(config-dial-peer)# exit Step 6 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 294 QSIG Support for Tcl IVR 2.0 Configuring Supplementary Service for a VoIP Dial Peer
- 307. Verifying QSIG andSupplementary Service To verify QSIG and supplementary service, perform the following steps (listed alphabetically). SUMMARY STEPS 1. show isdn status 2. show running-config DETAILED STEPS Step 1 show isdn status Use this command to display the status of all ISDN interfaces, including active layers, timer information, and switch-type settings. Step 2 show running-config Use this command to display the basic router configuration. Configuration Example for QSIG for Tcl IVR 2.0 The following sample output is typical of that for implementation of supplementary service. ISDN supplementary service messages from PBX 1 are sent transparently to PBX 2 by routers 1 and 2 as if PBX 1 and PBX 2 were connected directly to each other. Figure 15: QSIG for Tcl IVR 2.0: Sample Network Topology Router# show running-config Building configuration... Current configuration :3531 bytes ! version 12.2 service timestamps debug datetime msec localtime service timestamps log datetime msec localtime no service password-encryption service internal ! hostname router ! no logging buffered ! resource-pool disable ! ip subnet-zero ip host jurai 223.255.254.254 ip host dirt 223.255.254.254 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 295 QSIG Support for Tcl IVR 2.0 Verifying QSIG and Supplementary Service
- 308. ip host CALLGEN-SECURITY-V215.90.60.59 1.82.0.0 ! trunk group 323 ! isdn switch-type primary-ni ! voice service pots ! fax interface-type modem mta receive maximum-recipients 0 partition flash 2 8 8 ! controller T1 0 framing esf clock source line primary linecode b8zs ds0-group 1 timeslots 1-4 type e&m-fgb dtmf dnis cas-custom 1 ! translation-rule 1 Rule 1 ^.% 1 ! interface Ethernet0 ip address 172.19.140.96 255.255.255.0 no ip route-cache no ip mroute-cache squelch reduced ! interface Serial1:23 no ip address no keepalive shutdown ! ip classless ip route 0.0.0.0 0.0.0.0 172.19.140.1 ip route 223.255.254.254 255.255.255.255 1.8.0.1 no ip http server ! snmp-server community public RW snmp-server packetsize 4096 ! call rsvp-sync ! voice-port 0:1 ! mgcp profile default ! dial-peer cor custom ! dial-peer voice 650 voip destination-pattern 650....... session target ipv4:1.8.50.14 ! dial-peer voice 100 pots application debit-card incoming called-number 650233.... direct-inward-dial supplementary-service pass-through port 0:1 ! dial-peer voice 1001 voip incoming called-number 650233.... ! dial-peer voice 12345602 voip supplementary-service pass-through ! dial-peer hunt 6 ! line con 0 exec-timeout 0 0 logging synchronous level all line aux 0 line vty 0 4 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 296 QSIG Support for Tcl IVR 2.0 Configuration Example for QSIG for Tcl IVR 2.0
- 309. exec-timeout 60 0 passwordlab login ! end Additional References General ISDN References • "Overview of ISDN Voice Interfaces" --Describes relevant underlying technology; lists related documents, standards, MIBs, and RFCs; and describes how to obtain technical assistance • "Additional References" section --Lists additional ISDN references References Mentioned in This Chapter • Cisco IOS IP and IP Routing Configuration Guide at http://www.cisco.com/univercd/cc/td/doc/product/ access/acs_serv/as5400/sw_conf/ios_121/pulvoip1.htm • Cisco IOS Voice, Video, and Fax Configuration Guide at http://www.cisco.com/univercd/cc/td/doc/ product/software/ios122/122cgcr/fvvfax_c/index.htm • Tcl scripts at http://www.cisco.com/cgi-bin/tablebuild.pl/tclware ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 297 QSIG Support for Tcl IVR 2.0 Additional References
- 310. ISDN Voice ConfigurationGuide, Cisco IOS Release 15M&T 298 QSIG Support for Tcl IVR 2.0 Additional References
- 311. C H AP T E R 12 Implementing T1 CAS for VoIP This chapter describes how to implement the T1 Channel-Associated Signaling (CAS) for VoIP feature. This feature adds support for T1 CAS and E1 R2 signaling with the voice feature card (VFC). The T1 CAS interface is used for connection to both a private PBX and the PSTN. This feature is required by North American enterprise customers and service providers. For most enterprise customers, T1 CAS is the only type of line they use from the PSTN; E&M may be the only option for connecting to their PBX. Feature History for T1 CAS for VoIP ModificationRelease This feature was introduced on the Cisco AS5800.12.1(5)XM This feature was implemented on the Cisco AS5850.12.2(2)XB1 This feature was integrated into this release.12.2(11)T • Finding Feature Information, page 299 • Prerequisites for Configuring T1 CAS, page 300 • Restrictions for Configuring T1 CAS, page 300 • Information About T1 CAS for VoIP, page 301 • How to Configure T1 CAS for VoIP, page 302 • Configuration Example for T1 CAS for VoIP, page 309 • Additional References, page 311 Finding Feature Information Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 299
- 312. Use Cisco FeatureNavigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required. Prerequisites for Configuring T1 CAS • Perform the prerequisites that are listed in the "Prerequisites for Configuring ISDN Voice Interfaces" section. Restrictions for Configuring T1 CAS Restrictions are described in "Restrictions for Configuring ISDN Voice Interfaces". In addition, the following applies. Internet service providers can provide switched 56-kbps access to their customers with this feature. The subset of T1 CAS (robbed-bit) supported features is as follows: • Supervisory: line side • fxs-ground-start • fxs-loop-start • sas-ground-start • sas-loop-start • Modified R1 • Supervisory: trunk side • e&m-fgb • e&m-fgd e&m-fgd can receive calling-party number (ANI) and send called-party number (dialed-number identification service or DNIS) but cannot send ANI. Note • e&m immediate start• • fgd-eana fgd-eana can send both ANI and DNIS but cannot receive ANI.Note • Informational: line side • DTMF ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 300 Implementing T1 CAS for VoIP Prerequisites for Configuring T1 CAS
- 313. • Informational: trunkside • DTMF • MF Information About T1 CAS for VoIP General information about ISDN voice interfaces is presented in the "Information About ISDN Voice Interfaces" section. Note CAS Basics CAS is the transmission of signaling information within the voice channel. In addition to receiving and placing calls, CAS also processes the receipt of DNIS and ANI information, which is used to support authentication and other functions. Various types of CAS are available in the T1 world. The most common forms are loop-start, ground-start, Equal Access North American (EANA), and E&M. The biggest disadvantage of CAS is its use of user bandwidth to perform signaling functions. CAS is often referred to as robbed-bit-signaling because user bandwidth is "robbed" by the network for other purposes. Service-provider application for T1 CAS includes connectivity to the public network using T1 CAS from the Cisco router to the end-office switch. In this configuration, the router captures dialed-number or called-party-number information and passes it to the upper-level applications for IVR script selection, modem pooling, and other applications. Service providers also require access to ANI for user identification, billing account number, and, in the future, more complicated call routing. Service providers who implement VoIP include traditional voice carriers, new voice and data carriers, and existing internet service providers. Some of these service providers might use subscriber-side lines for VoIP connectivity to the PSTN; others use tandem-type service-provider connections. New CAS functionality for VoIP includes all CAS and E1/R2 signaling already supported for supported Cisco platforms in data applications, with the addition of dialed-number and calling-party-number capture whenever available. EandM and Ground Start Protocols This feature supports the following T1 CAS systems for VoIP applications: • E&M--E&M robbed-bit signaling is typically used for trunks. It is generally the only way that a CO switch can provide two-way dialing with direct inward dialing. In all E&M protocols, off-hook is indicated by A=B=1 and on-hook is indicated by A=B=0. For dial-pulse dialing, the A and B bits are pulsed to indicate the addressing digits. There are several further important subclasses of E&M robbed-bit signaling: • EandM Wink Start--Feature Group B ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 301 Implementing T1 CAS for VoIP Information About T1 CAS for VoIP
- 314. In the originalWink Start protocol, the terminating side responds to an off-hook from the originating side with a short wink (transition from on-hook to off-hook and back again). This wink indicates that the terminating side is ready to receive addressing digits. After receiving digits, the terminating side goes off-hook for the duration of the call. The originating side maintains off-hook for the duration of the call. • E&M Wink Start--Feature Group D• In Feature Group D Wink Start with Wink Acknowledge Protocol, the terminating side responds to an off-hook from the originating side with a short wink just as in the original Wink Start. After receiving digits, the terminating side provides another wink (called an acknowledgment wink) to indicate that the terminating side has received the digits. The terminating side goes off-hook to indicate connection when the ultimate called endpoint has answered. The originating side maintains off-hook for the duration of the call. • E&M Immediate Start• In the Immediate Start Protocol, the originating side does not wait for a wink before sending addressing digits. After receiving digits, the terminating side goes off-hook for the duration of the call. The originating side maintains off-hook for the duration of the call. • Ground Start/FXS--Ground Start Signaling was developed to help resolve glare when two sides of the connection tried to go off-hook at the same time. This is a problem with loop start because the only way to indicate an incoming call from the network to the customer premises equipment (CPE) using loop start was to ring the phone. The six-second ring cycle left a lot of time for glare to occur. Ground Start Signaling eliminates this problem by providing an immediate-seizure indication from the network to the CPE. This indication tells the CPE that a particular channel has an incoming call on it. Ground Start Signaling differs from E&M because the A and B bits do not track each other (that is, A is not necessarily equal to B). When the CO delivers a call, it seizes a channel (goes off-hook) by setting A to 0. The CO equipment also simulates ringing by toggling the B bit. The terminating equipment goes off-hook when it is ready to answer the call. Digits are usually not delivered for incoming calls. How to Configure T1 CAS for VoIP Configuring T1 CAS for Use with VoIP To configure T1 CAS for use with VoIP, perform the following steps. The following shows how to configure the voice ports as ds0-group for channelized T1 lines.Note ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 302 Implementing T1 CAS for VoIP How to Configure T1 CAS for VoIP
- 315. SUMMARY STEPS 1. enable 2.configure terminal 3. controller {t1| e1} slot / port 4. framing type 5. linecode type 6. ds0-group group-number timeslots range type type {dtmf| mf} {ani| dnis| ani-dnis} 7. Repeat steps 4 to 6 for each additional controller (there are 12). Be sure to increment the controller number and ds0-group number. 8. dial-peer voice tag type 9. dial-peer voice tag type 10. Repeat steps 8 and 9 for each dial peer. 11. exit DETAILED STEPS PurposeCommand or Action Enters privileged EXEC mode. Enter your password when prompted. enable Example: Router> enable Step 1 Enters global configuration mode.configure terminal Example: Router# configure terminal Step 2 Enters controller configuration mode for the specified slot/port. The controller ports are labeled RI and E1/PRI cards. controller {t1| e1} slot / port Example: Router(config)# controller t1 1/0/0 Step 3 Enters your telco framing type.framing type Example: Router(config-control)# framing esf Step 4 Enters your telco line code type.linecode type Example: Router(config-control)# linecode b8zs Step 5 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 303 Implementing T1 CAS for VoIP Configuring T1 CAS for Use with VoIP
- 316. PurposeCommand or Action Configuresall channels for E&M, FXS, and SAS analog signaling. T1 range: 1 to 24. E1 range: 1to 31. ds0-group group-number timeslots range type type {dtmf| mf} {ani| dnis| ani-dnis} Step 6 Example: Router(config-control)# ds0-group 1 timeslots 1-24 type e&m-fgb Some of the valid signaling types and keyword combinations are as follows: • Type: e&m-fgb • dtmf and dnis • mf and dnis • Type: e&m-fgd • dtmf and dnis • mf and ani-dnis or dnis • Type: fgd-eana • mf and ani-dnis Use the same type of signaling that your central office uses. For E1 using the Anadigicom converter, use e&m-fgb. See restrictions applicable to e&m-fgb and e&m-fgd in the Restrictions for Configuring T1 CAS, on page 300. Note -- Repeat steps 4 to 6 for each additional controller (there are 12). Be sure to increment the controller number and ds0-group number. Step 7 Enters dial-peer configuration mode and configures a POTS peer destination pattern. dial-peer voice tag type Example: Step 8 destination-pattern Example: port Example: ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 304 Implementing T1 CAS for VoIP Configuring T1 CAS for Use with VoIP
- 317. PurposeCommand or Action prefix Example: Router(config-control)#dial-peer voice 3070 pots Example: destination-pattern 30... Example: port 1/0/0:D Example: prefix 30 Specifies, for each POTS peer, the following: incoming called number, destination pattern, and direct inward dial. dial-peer voice tag type Example: Step 9 incoming called-number Example: destination-pattern Example: direct-inward-dial Example: port ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 305 Implementing T1 CAS for VoIP Configuring T1 CAS for Use with VoIP
- 318. PurposeCommand or Action Example: prefix Example: Router(config-control)#dial-peer voice 21 pots Example: incoming called-number 11... Example: destination-pattern 40... Example: direct-inward-dial Example: port 12/0:2:0 Example: prefix 21 --Repeat steps 8 and 9 for each dial peer.Step 10 Exits the current mode.exitStep 11 Example: Router(config-control)# exit The message "%SYS-5-CONFIG_I: Configured from console by console" is normal and does not indicate an error. Note Verifying and Troubleshooting a T1 CAS Configuration To verify and troubleshoot a T1 CAS configuration, perform the following steps (listed alphabetically). ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 306 Implementing T1 CAS for VoIP Verifying and Troubleshooting a T1 CAS Configuration
- 319. SUMMARY STEPS 1. debugcas 2. show controllers t1 | e1 dial-shelf / slot / port 3. show isdn status 4. show running-config 5. show voice port DETAILED STEPS Step 1 debug cas Use the debug cascommand to identify and troubleshoot call connection problems on a T1/E1 interface. With this command, you can trace the complete sequence of incoming and outgoing calls. Examples The following shows an example session to enable debugging CAS and generate troubleshooting output: Example: Router# show debug Router# debug cas slot 1 port 0 CAS debugging is on Router# debug-cas is on at slot(1) dsx1(0) Router# show debug CAS debugging is on The following example shows output for the first outgoing call: Example: Router# p 1.1.1.2 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 1.1.1.2, timeout is 2 seconds: *Mar 2 00:17:45: dsx1_alloc_cas_channel: channel 0 dsx1_timeslot 1(0/0): TX SEIZURE (ABCD=0001)(0/0): RX SEIZURE_ACK (ABCD=1101)(0/1): RX_IDLE (ABCD=1001)(0/2): RX_IDLE (ABCD=1001)(0/3): RX_IDLE (ABCD=1001)(0/4): RX_IDLE (ABCD=1001)(0/5): RX_IDLE (ABCD=1001)(0/6): RX_IDLE (ABCD=1001)(0/7): RX_IDLE (ABCD=1001)(0/8): RX_IDLE (ABCD=1001)(0/9): RX_IDLE (ABCD=1001)(0/10): RX_IDLE (ABCD=1001)(0/11): RX_IDLE (ABCD=1001)(0/12): RX_IDLE (ABCD=1001)(0/13): RX_IDLE (ABCD=1001)(0/14): RX_IDLE (ABCD=1001)(0/16): RX_IDLE (ABCD=1001)(0/17): RX_IDLE (ABCD=1001)(0/18): RX_IDLE (ABCD=1001)(0/19): RX_IDLE (ABCD=1001)(0/20): RX_IDLE (ABCD=1001)(0/21): RX_IDLE (ABCD=1001).(0/22): RX_IDLE (ABCD=1001)(0/23): RX_IDLE (ABCD=1001)(0/24): RX_IDLE (ABCD=1001)(0/25): RX_IDLE (ABCD=1001)(0/26): RX_IDLE (ABCD=1001)(0/27): RX_IDLE (ABCD=1001)(0/28): RX_IDLE (ABCD=1001)(0/29): RX_IDLE (ABCD=1001)(0/30): RX_IDLE (ABCD=1001)...(0/0): RX ANSWERED (ABCD=0101). Success rate is 0 percent (0/5) Router# *Mar 2 00:18:13.333: %LINK-3-UPDOWN: Interface Async94, changed state to up *Mar 2 00:18:13.333: %DIALER-6-BIND: Interface As94 bound to profile Di1 *Mar 2 00:18:14.577: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async94, changed state to up Router# p 1.1.1.2 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 1.1.1.2, timeout is 2 seconds: ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 307 Implementing T1 CAS for VoIP Verifying and Troubleshooting a T1 CAS Configuration
- 320. !!!!! Success rate is100 percent (5/5), round-trip min/avg/max = 160/180/236 ms The following example shows that the call is cleared on the router: Example: Router# clear int dialer 1 Router# (0/0): TX IDLE (ABCD=1001)(0/0): RX IDLE (ABCD=1001) *Mar 2 00:18:28.617: %LINK-5-CHANGED: Interface Async94, changed state to reset *Mar 2 00:18:28.617: %DIALER-6-UNBIND: Interface As94 unbound from profile Di1 *Mar 2 00:18:29.617: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async94, changed state to down et2-c3745-1# *Mar 2 00:18:33.617: %LINK-3-UPDOWN: Interface Async94, changed state to down The following example shows a subsequent outbound CAS call: Example: Router# p 1.1.1.2 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 1.1.1.2, timeout is 2 seconds: *Mar 2 00:18:40: dsx1_alloc_cas_channel: channel 5 dsx1_timeslot 6(0/5): TX SEIZURE (ABCD=0001)(0/5): RX SEIZURE_ACK (ABCD=1101)....(0/5): RX ANSWERED (ABCD=0101). Success rate is 0 percent (0/5) Router# *Mar 2 00:19:08.841: %LINK-3-UPDOWN: Interface Async93, changed state to up *Mar 2 00:19:08.841: %DIALER-6-BIND: Interface As93 bound to profile Di1 *Mar 2 00:19:10.033: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async93, changed state to up Router# p 1.1.1.2 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 1.1.1.2, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 160/167/176 ms The following example shows the call cleared by the switch: Example: Router# (0/5): TX IDLE (ABCD=1001)(0/5): RX IDLE (ABCD=1001) *Mar 2 00:19:26.249: %LINK-5-CHANGED: Interface Async93, changed state to reset *Mar 2 00:19:26.249: %DIALER-6-UNBIND: Interface As93 unbound from profile Di1 *Mar 2 00:19:27.249: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async93, changed state to down Router# *Mar 2 00:19:31.249: %LINK-3-UPDOWN: Interface Async93, changed state to down The following example shows an incoming CAS call: Example: Router# (0/0): RX SEIZURE (ABCD=0001) *Mar 2 00:22:40: dsx1_alloc_cas_channel: channel 0 dsx1_timeslot 1(0/0): TX SEIZURE_ACK (ABCD=1101)(0/0): TX ANSWERED (ABCD=0101) Router# *Mar 2 00:23:06.249: %LINK-3-UPDOWN: Interface Async83, changed state to up ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 308 Implementing T1 CAS for VoIP Verifying and Troubleshooting a T1 CAS Configuration
- 321. *Mar 2 00:23:06.249:%DIALER-6-BIND: Interface As83 bound to profile Di1 *Mar 2 00:23:07.653: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async83, changed state to up Step 2 show controllers t1 | e1 dial-shelf / slot / port Use this command to display the controller and alarm status for the specified dial shelf/slot/port. Configuration is successful if the controller reports being up and no error are reported. Example: Router# show controllers t1 1/0/0 T1 1/0/0 is up. Applique type is Channelized T1 Cablelength is long gain36 0db No alarms detected. alarm-trigger is not set Framing is ESF, Line Code is B8ZS, Clock Source is Line. Data in current interval (180 seconds elapsed): 0 Line Code Violations, 0 Path Code Violations 0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins 0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs Step 3 show isdn status Use this command to display the status of all ISDN interfaces, including active layers, timer information, and switch-type settings. Step 4 show running-config Use this command to display the basic router configuration. Step 5 show voice port To display configuration information about a specific voice port, use the show voice port command in privileged EXEC mode. Command syntax and options vary according to platform and configuration. Configuration Example for T1 CAS for VoIP The sample configuration is only intended as an example of how to use the commands to configure T1 CAS. It is not an example of a complete configuration for setting up the entire signaling for a telco network. Figure 16: T1 CAS for VoIP: Network Topology Router# show running-config version 12.1 service timestamps debug datetime msec localtime show-timezone service timestamps log datetime msec localtime show-timezone service password-encryption ! hostname travis-nas-01 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 309 Implementing T1 CAS for VoIP Configuration Example for T1 CAS for VoIP
- 322. ! aaa new-model aaa authenticationlogin default local aaa authentication login NO_AUTHENT none aaa authorization exec default local if-authenticated aaa authorization exec NO_AUTHOR none aaa authorization commands 15 default local if-authenticated aaa authorization commands 15 NO_AUTHOR none aaa accounting exec default start-stop group tacacs+ aaa accounting exec NO_ACCOUNT none aaa accounting commands 15 default stop-only group tacacs+ aaa accounting commands 15 NO_ACCOUNT none enable secret 5 $1$LsoW$K/qBH9Ih2WstUxvazDgmY/ ! username admin privilege 15 password 7 06455E365E471D1C17 username gmcmilla password 7 071824404D06140044 username krist privilege 15 password 7 0832454D01181118 ! call rsvp-sync shelf-id 0 router-shelf shelf-id 1 dial-shelf ! resource-pool disable ! modem-pool Default pool-range 1/2/0-1/2/143,1/3/0-1/3/143 ! modem-pool accounts ! modem-pool accounts1 ! modem-pool accounts2 ! clock timezone CST -6 clock summer-time CST recurring ! ip subnet-zero ip domain-name cisco.com ip name-server 172.22.53.210 ip name-server 171.69.2.133 ip name-server 171.69.2.132 ip name-server 171.69.11.48 ! isdn switch-type primary-5ess ! controller T1 1/0/0 framing esf linecode b8zs ds0-group 1 timeslots 1-24 type e&m-fgb ! controller T1 1/0/1 framing esf linecode b8zs ds0-group 1 timeslots 1-24 type e&m-fgb ! controller T1 1/0/2 framing esf linecode b8zs ds0-group 1 timeslots 1-24 type e&m-fgb ! controller T1 1/0/3 framing esf linecode b8zs ds0-group 0 timeslots 1-24 type e&m-fgb dtmf dnis ! controller T1 1/0/4 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 310 Implementing T1 CAS for VoIP Configuration Example for T1 CAS for VoIP
- 323. Additional References General ISDNReferences • "Overview of ISDN Voice Interfaces" --Describes relevant underlying technology; lists related documents, standards, MIBs, and RFCs; and describes how to obtain technical assistance • "Additional References" section --Lists additional ISDN references ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 311 Implementing T1 CAS for VoIP Additional References
- 324. ISDN Voice ConfigurationGuide, Cisco IOS Release 15M&T 312 Implementing T1 CAS for VoIP Additional References
- 325. C H AP T E R 13 Implementing FCCS (NEC Fusion) This chapter describes how to implement Fusion Call-Control Signaling (FCCS), also known as NEC Fusion. FCCS allows a voice network to seamlessly integrate into an IP network, making it possible to add voice-networking capabilities to a LAN or WAN without major network restructuring. The NEC Fusion Strategic Alliance Program facilitates development of integrated solutions, complementary to both NEC and other technology businesses, that provide telephony solutions for mutual customers. FCCS, developed under this program, deploys a new transmission signaling protocol that is compatible with IP networks and Cisco routers and switches. It allows individual nodes anywhere within a network to operate as if they were part of a single integrated PBX system. Database storage, share, and access routines allow real-time access from any node to any other, allowing individual nodes to learn about the entire network configuration. This capability allows network-wide feature, functional, operational, and administration transparency. Feature History for FCCS ModificationRelease This command was introduced on the Cisco AS5300.12.0(7)T • Finding Feature Information, page 313 • Prerequisites for Implementing FCCS, page 314 • Restrictions for Implementing FCCS, page 314 • Information About FCCS, page 314 • How to Configure FCCS, page 314 • Additional References, page 319 Finding Feature Information Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 313
- 326. find information aboutthe features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required. Prerequisites for Implementing FCCS • Perform the prerequisites that are listed in the "Prerequisites for Configuring ISDN Voice Interfaces" section. Restrictions for Implementing FCCS Restrictions are described in "Restrictions for Configuring ISDN Voice Interfaces". Information About FCCS If you have an NEC PBX in your network and also run FCCS, you must configure your access servers appropriately for QSIG and then for FCCS (NEC Fusion). The figure below shows an example of a Cisco AS5300 QSIG signaling configuration using an NEC PBX. Figure 17: QSIG Signaling Configuration with NEC PBX General information about ISDN voice interfaces is presented in the "Information About ISDN Voice Interfaces" section. Note How to Configure FCCS Configuring VoIP QSIG To configure VoIP QSIG, perform the following steps. You can configure a switch type at either global level or interface level. For example, if you have a QSIG connection on one line and on the PRI port, you can use the isdn-switch-type command to configure the ISDN switch type in any of the following combinations: ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 314 Implementing FCCS (NEC Fusion) Prerequisites for Implementing FCCS
- 327. • At theglobal level to support QSIGX, PRI 5ess, or another switch type such as VN3 • At the interface level to set a particular interface to support QSIG, to set a particular interface to a PRI setting such as 5ess, or to set one particular interface to a PRI setting and another interface to support QSIG. SUMMARY STEPS 1. enable 2. configure terminal 3. isdn switch-type primary-qsig 4. controller {t1 | e1} controller-number 5. pri-group [timeslot range] 6. exit 7. interface serial 1: channel-number 8. isdn switch-type primary-qsig 9. isdn protocol-emulate {user| network} 10. isdn overlap-receiving [T302 value] 11. isdn incoming-voice modem 12. isdn network-failure-cause [value] 13. isdn bchan-number-order {ascending | descending} 14. exit DETAILED STEPS PurposeCommand or Action Enters privileged EXEC mode. Enter your password when prompted.enable Example: Router> enable Step 1 Enters global configuration mode.configure terminal Example: Router# configure terminal Step 2 (Optional) Globally configures the ISDN switch type to support QSIG signaling. isdn switch-type primary-qsig Example: Router(config)# isdn switch-type primary-qsig Step 3 Depending on your configuration, you can configure the ISDN switch type by using this command either in global configuration mode or interface configuration mode (see Configuring VoIP QSIG). Note If the PBX in your configuration is an NEC PBX and you use Fusion Call Control Signaling (FCCS), see the Configuring FCCS, on page 317. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 315 Implementing FCCS (NEC Fusion) Configuring VoIP QSIG
- 328. PurposeCommand or Action Enterscontroller configuration mode for the specified controller.controller {t1 | e1} controller-number Example: Router(config)# controller t1 3 Step 4 Configures the PRI group for either T1 or E1 to carry voice traffic. T1 time slots are 1 to 23. E1 time slots are 1 to 31. pri-group [timeslot range] Example: Router(config-controller)# pri-group timeslot 1-23 Step 5 You can configure the PRI group to include either all available time slots or just a select group. For example, if only time slots 1 to 10 are in the PRI group, specify timeslot 1-10. If the PRI group includes all channels available for T1, specify timeslot 1-23. If the PRI group includes all channels available for E1, specify timeslot 1-31. Exits the current mode.exit Example: Router(config-controller)# exit Step 6 Enters interface configuration mode for the ISDN PRI interface. T1 channel number is 23. E1 channel number is 15. interface serial 1: channel-number Example: Router(config)# interface serial 1:23 Step 7 (Optional) Configures the ISDN switch type to support QSIG signaling for the specified interface. Use this command if you did not configure the ISDN switch type for QSIG support globally in Step 1. isdn switch-type primary-qsig Example: Router(config-if)# isdn switch-type primary-qsig Step 8 The same conditions that apply to this command in global configuration mode also apply to this command in interface configuration mode. For the selected interface, this command in interface configuration mode overrides the same command in global configuration mode. Note Configures the ISDN interface to serve as either the primary QSIG slave or the primary QSIG master. Keywords are as follows: isdn protocol-emulate {user| network} Example: Router(config-if)# isdn protocol-emulate user Step 9 • user --Slave • network --Master If the private integrated services network exchange (PINX) is the primary QSIG master, configure the access server as the primary QSIG slave. If the PINX is the primary QSIG slave, configure it as the primary QSIG master. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 316 Implementing FCCS (NEC Fusion) Configuring VoIP QSIG
- 329. PurposeCommand or Action (Optional)Activates overlap signaling to send to the destination PBX using timer T302. The keyword are argument are as follows: isdn overlap-receiving [T302 value] Example: Router(config-if)# isdn overlap-receiving T302 500 Step 10 • T302 value --Value of timer T302, in ms. Routes incoming voice calls to the modem and treats them as analog data.isdn incoming-voice modem Example: Router(config-if)# isdn incoming-voice modem Step 11 (Optional) Specifies the cause code to pass to the PBX when a call cannot be placed or completed because of internal network failures. The argument is as follows: isdn network-failure-cause [value] Example: Router(config-if)# isdn network-failure-cause 5 Step 12 • value --Cause code, from 1 to 127. All cause codes except Normal Call Clearing (16), User Busy (17), No User Responding (18), and No Answer from User (19) are changed to the specified cause code. (Optional) Configures the ISDN PRI interface to make the outgoing call selection in ascending or descending order. Keywords are as follows: isdn bchan-number-order {ascending | descending} Step 13 Example: Router(config-if)# isdn bchan-number-order ascending • ascending --Ascending order. • descending --Descending order. This is the default. For descending order, the first call from the access server uses (T1) channel 23 or (E1) channel 31. The second call then uses (T1) channel 22 or (E1) channel 30, and so on, in descending order. For ascending order, if the PRI group starts with 1, the first call uses channel 1, the second call uses channel 2, and so on, in ascending order. If the PRI group starts with a different time slot, the ascending order starts with the lowest time slot. Exits the current mode.exit Example: Router(config-if)# exit Step 14 Configuring FCCS To configure FCCS, perform the following steps. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 317 Implementing FCCS (NEC Fusion) Configuring FCCS
- 330. SUMMARY STEPS 1. enable 2.configure terminal 3. controller t1 controller-number 4. pri-group nec-fusion {pbx-ip-address | pbx-ip-host-name} pbx-port number 5. exit DETAILED STEPS PurposeCommand or Action Enters privileged EXEC mode. Enter your password when prompted. enable Example: Router> enable Step 1 Enters global configuration mode.configure terminal Example: Router# configure terminal Step 2 Enters controller configuration mode for the specified controller.controller t1 controller-numberStep 3 Example: Router(config)# controller t1 5 NEC Fusion does not support fractional T1/E1; all 24 channels must be available or the configuration request fails. Note Configures the controller to communicate with an NEC PBX using NEC Fusion. The argument is as follows: pri-group nec-fusion {pbx-ip-address | pbx-ip-host-name} pbx-port number Step 4 Example: Router(config-controller)# pri-group nec-fusion 172.16.0.0 pbx-port 55000 • number --PBX port number. If the specified value is already in use, the next greater value is used. Exits the current mode.exit Example: Router(config-controller)# exit Step 5 Verifying FCCS To verify FCCS functionality, perform the following step. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 318 Implementing FCCS (NEC Fusion) Verifying FCCS
- 331. SUMMARY STEPS 1. showisdn status DETAILED STEPS show isdn status Use this command to display the status of all ISDN interfaces or a specific ISDN interface. Example: Router# show isdn status Global ISDN Switchtype = primary-qsig ISDN Serial1:23 interface dsl 0, interface ISDN Switchtype = primary-qsig **** Slave side configuration **** Layer 1 Status: DEACTIVATED Layer 2 Status: TEI = 0, Ces = 1, SAPI = 0, State = TEI_ASSIGNED Layer 3 Status: 0 Active Layer 3 Call(s) Activated dsl 0 CCBs = 0 The Free Channel Mask: 0x7FFFFF Additional References General ISDN References • "Overview of ISDN Voice Interfaces" section --Describes relevant underlying technology; lists related documents, standards, MIBs, and RFCs; and describes how to obtain technical assistance • "Additional References" section --Lists additional ISDN references ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 319 Implementing FCCS (NEC Fusion) Additional References
- 332. ISDN Voice ConfigurationGuide, Cisco IOS Release 15M&T 320 Implementing FCCS (NEC Fusion) Additional References
- 333. C H AP T E R 14 Digital J1 Voice Interface Card This chapter describes how to implement the Digital J1 Voice Interface Card (VIC) feature. The digital J1 VIC provides the proper interface for directly connecting Cisco multiservice access routers to PBXs throughout Japan that use a J1 (2.048-Mbps time-division-multiplexed [TDM]) interface. Feature History for Digital J1 Voice Interface Card ModificationRelease This feature was introduced on the Cisco 2600 series and Cisco 3600 series. 12.2(8)T • Finding Feature Information, page 321 • Prerequisites for Configuring the Digital J1 VIC, page 322 • Restrictions for Configuring the Digital J1 VIC, page 322 • Information About the Digital J1 VIC, page 322 • How to Configure the Digital J1 VIC, page 324 • Configuration Examples for the Digital J1 VIC, page 334 Finding Feature Information Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 321
- 334. Prerequisites for Configuringthe Digital J1 VIC • Ensure that you have Cisco IOS Release 12.2(8)T or later. Restrictions for Configuring the Digital J1 VIC • Voice-only applications are supported. • Separate clock output is not supported. • Alarm-relay output is not supported. • Per-channel loopback is not supported. • Voice ports on the J1 interface cannot be configured using network-management software. They must be configured manually. Information About the Digital J1 VIC The digital J1 VIC provides the proper interface for directly connecting Cisco multiservice access routers to PBXs throughout Japan that use a J1 (2.048-Mbps TDM) interface. It provides the software and hardware features required to connect to over 80 percent of the PBXs within Japan that use digital interfaces. This new J1 voice interface card (VIC) provides a TTC JJ-20.11 compliant interface between high-density voice network modules (NM-HDV) and a Japanese PBX. The card supports 30 voice channels per port. It provides a single-port line interface in a VIC form factor. It is specifically designed to conform to the TTC JJ-20.10-12 standards that define the interface between a PBX and a time-division multiplexer. The figure below shows the earlier solution offered to customers in Japan. A J1/T1 adapter box installed between the PBX and router provides the translation between J1 using coded mark inversion (CMI) line coding at a bit rate of 2.048 Mbps and a T1 line using either alternate mark inversion (AMI) or B8ZS line coding at ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 322 Digital J1 Voice Interface Card Prerequisites for Configuring the Digital J1 VIC
- 335. a bit rateof 1.544 Mbps. Note that, with this solution, only 24 channels are supported instead of the full 30 channels of the J1 interface. Figure 18: Solution Without J1 VIC The figure below shows the solution using the digital J1 VIC. The interface is now between J1 and the VIC’s TDM access (TDMA) bus. Note that now all 30 channels of the J1 interface are supported. Figure 19: Solution with J1 VIC Feature benefits include the following: • Supports Media Gateway Control Protocol (MGCP), H.248, H.323 (versions 1, 2, and 3), Session Initiation Protocol (SIP), and Cisco CallManager (with Cisco IP phones) in association with VoIP, VoFR, and VoATM • Provides Alarm Indication Signal (AIS) alarm signaling per TTC JJ-20.11 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 323 Digital J1 Voice Interface Card Information About the Digital J1 VIC
- 336. • Delivers thesame performance as the existing 30-channel E1 NM-HDV • Allows enabling and disabling of individual DS0s or channels How to Configure the Digital J1 VIC For related information on VIC installation, see Installing and Configuring 1-Port J1 Voice Interface Cards . Note Configuring the J1 VIC To configure the digital J1 VIC, perform the following steps. SUMMARY STEPS 1. enable 2. configure terminal 3. controller j1 slot/port 4. exit DETAILED STEPS PurposeCommand or Action Enters privileged EXEC mode. Enter your password when prompted. enable Example: Router> enable Step 1 Enters global configuration mode.configure terminal Example: Router# configure terminal Step 2 Configures the J1 controller in the specified slot and port. controller j1 slot/port Example: Router(config)# controller j1 1/0 Step 3 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 324 Digital J1 Voice Interface Card How to Configure the Digital J1 VIC
- 337. PurposeCommand or Action Exitsthe current mode.exit Example: Router(config-control)# exit Step 4 Configuring CAS To configure the DS0 groups on the digital J1 VIC for voice applications, perform the following steps. The J1 controller supports the E&M wink start and E&M immediate channel-associated signaling (CAS) protocols for the voice ports. The Companding type: mu-law and CP tone: JP parameters have default values for the J1 interface. Note SUMMARY STEPS 1. enable 2. configure terminal 3. controller j1 slot/port 4. ds0-group ds0-group-no timeslots timeslot-list type signaling-type 5. exit 6. Repeat if your router has more than one J1 controller to configure. DETAILED STEPS PurposeCommand or Action Enters privileged EXEC mode. Enter your password when prompted.enable Example: Router> enable Step 1 Enters global configuration mode.configure terminal Example: Router# configure terminal Step 2 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 325 Digital J1 Voice Interface Card Configuring CAS
- 338. PurposeCommand or Action Enterscontroller configuration mode for the J1 controller in the specified slot and port. controller j1 slot/port Example: Router(config)# controller j1 1/0 Step 3 Configures channelized J1 time slots for use by compressed voice calls and the signaling method for connecting to the PBX. The keywords and arguments are as follows: ds0-group ds0-group-no timeslots timeslot-list type signaling-type Example: Router(config-controller)# ds0-group 1 Step 4 • ds0-group-no --DS0 group number. • timeslots timeslot-list --DS0 timeslot. Range: 1 to 31. Timeslot 16 is reserved for signaling. timeslots 1-15,17-31 type e&m-wink-start • type signaling-type --Signaling type to be applied to the selected group: • e&m-delay-dial--Originating endpoint sends an off-hook signal and then and waits for an off-hook signal followed by an on-hook signal from the destination. • e&m-immediate-start--No specific off-hook and on-hook signaling. • e&m-wink-start--Originating endpoint sends an off-hook signal and waits for a wink signal from the destination. • none--Null signaling for external call control. Exits the current mode.exit Example: Router(config-controller)# exit Step 5 --Repeat if your router has more than one J1 controller to configure. Step 6 Configuring the Clock Source To configure the clock source for a digital J1 VIC, perform the following steps. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 326 Digital J1 Voice Interface Card Configuring the Clock Source
- 339. SUMMARY STEPS 1. enable 2.configure terminal 3. controller j1 slot/port 4. clock source {line| internal} 5. exit 6. Repeat if your router has more than one J1 controller to configure. DETAILED STEPS PurposeCommand or Action Enters privileged EXEC mode. Enter your password when prompted. enable Example: Router> enable Step 1 Enters global configuration mode.configure terminal Example: Router# configure terminal Step 2 Enters controller configuration mode for the J1 controller in the specified slot and port. controller j1 slot/port Example: Router(config)# controller j1 1/0 Step 3 Specifies the clock source. Keywords are as follows:clock source {line| internal}Step 4 Example: Router(config-controller)# clock source line • line --Controller recovers external clock from the line and provides the recovered clock to the internal (system) clock generator. • internal --Controller synchronizes itself to the internal (system) clock. Default: line. Exits the current mode.exit Example: Router(config-controller)# exit Step 5 --Repeat if your router has more than one J1 controller to configure. Step 6 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 327 Digital J1 Voice Interface Card Configuring the Clock Source
- 340. Configuring Loopback To configureloopback for testing a digital J1 VIC, perform the following steps. SUMMARY STEPS 1. enable 2. configure terminal 3. controller j1 slot/port 4. loopback {local | line | isolation} 5. exit DETAILED STEPS PurposeCommand or Action Enters privileged EXEC mode. Enter your password when prompted. enable Example: Router> enable Step 1 Enters global configuration mode.configure terminal Example: Router# configure terminal Step 2 Enters controller configuration mode for the J1 controller in the specified slot and port. controller j1 slot/port Example: Router(config)# controller j1 1/0 Step 3 Sets the loopback method for testing the J1 interface. Keywords are as follows: loopback {local | line | isolation} Example: Router(config-controller)# loopback isolation Step 4 • local --Local loopback mode • line --External loopback mode at the line level • isolation --Both local and line loopback mode Exits the current mode.exit Example: Router(config-controller)# exit Step 5 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 328 Digital J1 Voice Interface Card Configuring Loopback
- 341. Configuring T-CCS fora Clear-Channel Codec To configure transparent common-channel signaling (T-CCS), perform the following steps. SUMMARY STEPS 1. enable 2. configure terminal 3. controller j1 slot/port 4. ds0-group ds0-group-no timeslots timeslot-list type signaling-type 5. no shutdown 6. exit 7. dial-peer voice number pots 8. destination-pattern string [T] 9. port slot/port : ds0-group-no 10. exit 11. dial-peer voice number voip 12. codec clear-channel 13. vad 14. destination-pattern string [T] 15. session target {ipv4: destination-address | dns:[$s$.| $d$. | $e$. | $u$.] hostname} 16. exit DETAILED STEPS PurposeCommand or Action Enters privileged EXEC mode. Enter your password when prompted.enable Example: Router> enable Step 1 Enters global configuration mode.configure terminal Example: Router# configure terminal Step 2 Enters controller configuration mode for the J1 controller in the specified slot and port. controller j1 slot/port Example: Router(config)# controller j1 1/0 Step 3 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 329 Digital J1 Voice Interface Card Configuring T-CCS for a Clear-Channel Codec
- 342. PurposeCommand or Action Configureschannelized J1 time slots for use by compressed voice calls and the signaling method that the router uses to connect to the PBX. The keywords and arguments are as described earlier. ds0-group ds0-group-no timeslots timeslot-list type signaling-type Example: Router(config-controller)# ds0-group Step 4 1 timeslots 1-15,17-31 type e&m-wink-start Activates the controller.no shutdown Example: Router(config-controller)# no shutdown Step 5 Exits the current mode.exit Example: Router(config-controller)# exit Step 6 Enters dial-peer configuration mode for the specified POTS dial peer.dial-peer voice number pots Example: Router(config)# dial-peer voice 20 pots Step 7 Configures the dial peer's destination pattern so that the system can reconcile dialed digits with a telephone number. The keyword and argument are as follows: destination-pattern string [T] Example: Router(config-dialpeer)# destination-pattern 3050 T Step 8 • string --Series of digits that specify the E.164 or private-dialing-plan phone number. Valid entries: digits 0 to 9 and letters A to D. The plus symbol (+) is not valid. You can enter the following special characters: • Star character (*) that appears on standard touch-tone dial pads--Can be in any dial string, but not as a leading character (for example, *650). • Period (.)--Acts as a wildcard character. • Comma (,)--In prefixes, inserts a one-second pause. • T --When included at the end of the destination pattern, causes the system to collect dialed digits as they are entered until the interdigit timer expires (default: 10 seconds) or the user dials the termination of end-of-dialing key (default: #). The timer character must be a capital T. Note ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 330 Digital J1 Voice Interface Card Configuring T-CCS for a Clear-Channel Codec
- 343. PurposeCommand or Action Associatesthe dial peer with a specific logical interface. Arguments are as follows: port slot/port : ds0-group-no Example: Router(config-dialpeer)# port 1/0:1 Step 9 • slot -- Router location where the voice module is installed. Range: 0 to 3. • port --Voice interface card location. Range: 0 to 1. • ds0-group-no --DS0 group number. Each defined DS0 group number is represented on a separate voice port, allowing you to define individual DS0s. Exits the current mode.exit Example: Router(config-dialpeer)# exit Step 10 Enters dial-peer configuration mode for the specified VoIP dial peer.dial-peer voice number voip Example: Router(config)# dial-peer voice 20 voip Step 11 Specifies use of the clear-channel codec.codec clear-channel Example: Router(config-dialpeer)# codec clear-channel Step 12 (Optional; enabled by default) Activates voice activity detection (VAD), which allows the system to reduce unnecessary voice transmissions caused by unfiltered background noise. vad Example: Router(config-dialpeer)# vad Step 13 Configures the dial peer's destination pattern so that the system can reconcile dialed digits with a telephone number. The keyword are argument are as described above. destination-pattern string [T] Example: Router(config-dialpeer)# destination-pattern 3050 T Step 14 Configures the IP session target for the dial peer. Keywords and arguments are as follows: session target {ipv4: destination-address | dns:[$s$.| $d$. | $e$. | $u$.] hostname} Step 15 Example: Router(config-dialpeer)# session • ipv4: destination-address --IP address of the dial peer to receive calls. • dns: hostname --Domain-name server that resolves the name of the IP address. You can use wildcards by using source, destination, target {ipv4:10.168.1.1 serverA.mycompany.com} and dialed information in the hostname. Use one of the following ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 331 Digital J1 Voice Interface Card Configuring T-CCS for a Clear-Channel Codec
- 344. PurposeCommand or Action macroswith this keyword when defining the session target for VoIP peers: • $s$.--Source destination pattern is used as part of the domain name. • $d$.--Destination number is used as part of the domain name. • $e$.--Digits in the called number are reversed and periods are added between the digits of the called number. The resulting string is used as part of the domain name. • •$u$.--Unmatched portion of the destination pattern (such as a defined extension number) is used as part of the domain name. Exits the current mode.exit Example: Router(config- Step 16 dialpeer )# exit Verifying Digital J1 VIC Configuration To verify that the digital J1 VIC is configured correctly, use the show running-config command as shown in theConfiguration Examples for the Digital J1 VIC, on page 334. Monitoring and Maintaining the Digital J1 VIC To monitor and maintain the J1 VIC, use the following commands: • show controllers j1 slot / port-- Displays statistics for the J1 link. • show dial-peer voice --Displays configuration information for dial peers. Troubleshooting Tips Three digital loopback modes are possible for diagnostics and fault isolation: • Line loopback loops the received signal (R-D) from the PBX to the transmit going back to the PBX. • Local loopback loops the transmitted signal (T-D) from the host to the receive going back to the host. ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 332 Digital J1 Voice Interface Card Verifying Digital J1 VIC Configuration
- 345. • Isolation loopbackroutes PBX and TDM generated traffic back to their respective sources. In the following figures, Tx=transmit interface and Rx=receive interface. Tip / Ring leads carry audio between the signaling unit and the trunking circuit. Note Line Loopback To place the controller into line loopback, use the loopback line command. Line loopback loops the receiver inputs to the transmitter outputs. The receive path is not affected by the activation of this loopback. Figure 20: Line Loopback Local Loopback To place the controller into local loopback, use the loopback local command. To turn off loopback, use the noform of the command. Local loopback loops the transmit line encoder outputs to the receive line encoder inputs. The transmit path is not affected by the activation of this loopback. Use this command only for testing purposes.Note Figure 21: Local Loopback ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 333 Digital J1 Voice Interface Card Troubleshooting Tips
- 346. Isolation Loopback To placethe controller into line loopback, use the loopback isolation command. Both line and local loopback are turned on. Figure 22: Isolation Loopback Configuration Examples for the Digital J1 VIC Router# show running-config Building configuration... Current configuration :2023 bytes ! version 12.2 service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption ! hostname kmm-3660-1 ! boot system tftp /tftpboot/kmenon/c3660-is-mz 223.255.254.254 enable password lab ! voice-card 1 ! voice-card 3 ! voice-card 4 ! ip subnet-zero ! ! voice service pots ! ! fax interface-type fax-mail mta receive maximum-recipients 0 ! controller J1 1/0 clock source line ! controller E1 3/0 ! controller E1 3/1 ! controller T1 4/0 framing esf linecode b8zs channel-group 0 timeslots 24 ! controller T1 4/1 framing esf linecode b8zs channel-group 0 timeslots 24 ! ! interface Multilink1 ip address 30.30.30.1 255.255.255.0 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 334 Digital J1 Voice Interface Card Configuration Examples for the Digital J1 VIC
- 347. keepalive 1 no cdpenable ppp multilink no ppp multilink fragmentation multilink-group 1 ! interface FastEthernet0/0 ip address 1.7.29.1 255.255.0.0 no ip mroute-cache duplex auto speed auto ! interface FastEthernet0/1 ip address 1.8.0.1 255.255.0.0 no ip mroute-cache duplex auto speed auto ! interface Serial4/0:0 no ip address encapsulation ppp no fair-queue no cdp enable ppp multilink multilink-group 1 ! interface Serial4/1:0 no ip address encapsulation ppp no fair-queue no cdp enable ppp multilink multilink-group 1 ! ip default-gateway 1.7.0.1 ip classless ip route 0.0.0.0 0.0.0.0 10.1.1.1 ip route 1.9.0.1 255.255.255.255 30.30.30.2 ip route 223.255.254.254 255.255.255.255 1.7.0.1 no ip http server ip pim bidir-enable ! ! snmp-server engineID local 00000009020000044D0EF520 snmp-server packetsize 4096 ! call rsvp-sync ! no mgcp timer receive-rtcp ! mgcp profile default ! dial-peer cor custom ! ! dial-peer voice 1 pots destination-pattern 88 ! dial-peer voice 20 voip destination-pattern 3050 session target ipv4:10.8.0.2 codec clear-channel ! dial-peer voice 77 pots destination-pattern 77 ! dial-peer voice 100 voip incoming called-number 100 destination-pattern 100 session target ipv4:10.8.0.2 no vad ! ! ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 335 Digital J1 Voice Interface Card Configuration Examples for the Digital J1 VIC
- 348. line con 0 exec-timeout0 0 line aux 0 line vty 0 4 login ! ! end Controller (J1) Example The following example shows the Cisco IOS interface card in slot 4, port 0 of a Cisco 3660 configured as a J1 controller: controller J1 4/0 Channel-Associated Signaling Example The following example shows the DS0 groups on the J1 controller. controller J1 4/0 clock source line ds0-group 1 timeslots 1-15,17-31 type e&m-wink-start Clock Source Example The following example shows the J1 controller clock source is configured to line, where the controller recovers external clock from the line and provides the recovered clock to the internal (system) clock generator. controller J1 3/0 clock source line Loopback Example The following example shows the loopback method for testing the J1 controller is set at the line level. controller J1 3/0 clock source line loopback line Transparent Common-Channel Signaling for a Clear-Channel Codec Example The following example shows the codec option set to clear-channel. dial-peer voice 20 voip destination-pattern 3050 session target ipv4:10.8.0.2 codec clear-channel ISDN Voice Configuration Guide, Cisco IOS Release 15M&T 336 Digital J1 Voice Interface Card Controller (J1) Example
- 349. I N DE X B backhaul 241 C Clear-Channel T3/E3 with Integrated CSU/DSU feature 85 D Digital J1 Voice Interface Card feature 321 E E3/T3 network modules 85 Expanded Scope for Cause-Code-Initiated Call-Establishment Retries feature 79 F FCCS (NEC Fusion) feature 313 features 79, 171, 195, 233, 241, 289, 299, 313, 321 Digital J1 Voice Interface Card 321 Expanded Scope for Cause-Code-Initiated Call-Establishment Retries 79 FCCS (NEC Fusion) 313 Integrated Voice and Data WAN on T1/E1 Interfaces Using the AIM-ATM-VOICE-30 Module 171 ISDN GTD for Setup Messages 195 PRI Backhaul Using the SCTP and the ISDN Q.921 User Adaptation Layer 233, 241 QSIG for Tcl IVR 2.0 289 SCTP-related 233 Support for IUA with SCTP for Cisco Access Servers 233 T1 CAS for VoIP 299 I Integrated Voice and Data WAN on T1/E1 Interfaces Using the AIM-ATM-VOICE-30 Module feature 171 ISDN GTD for Setup Messages feature 195 ISDN information elements 197 ISDN IUA adaptation layer 238 L loopback 332 M MCI switches 212 N NEC Fusion (FCCS) feature 313 network modules 3, 85 See also voice interface card 3 NFAS groups, multiple 239 P PRI Backhaul Using the SCTP and the ISDN Q.921 User Adaptation Layer feature 233, 241 Q Q.921 protocol 4, 233, 287 Q.931 protocol 4, 54, 196, 234 QSIG for Tcl IVR 2.0 feature 289 QSIG protocol 4, 289, 314 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T IN-1
- 350. R RADIUS accounting servers196 S SCTP features 233 Support for IUA with SCTP for Cisco Access Servers feature 233 switch types, QSIG 6 T T1 CAS for VoIP feature 299 T3/E3 network modules 85 Tcl (Toolkit Command Language) 196, 289, 295 V voice interface card 18, 57, 171, 174, 321 ISDN Voice Configuration Guide, Cisco IOS Release 15M&T IN-2 Index