Table Of Contents
Integrating Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers
Prerequisites for Integrating Data and Voice Services for ISDN PRI Interfaces
Restrictions for Integrating Data and Voice Services for ISDN PRI Interfaces
Information About Integrating Data and Voice Services for ISDN PRI Interfaces
Integrated Services for Multiple Call Types
Resource Allocation for Voice and Data Calls
MLPP Call Preemption over Voice Calls
Preemption of Outgoing Voice Calls
How to Configure Integrated Data and Voice Services for ISDN PRI Interfaces
Configuring the ISDN PRI Interface for Multiple Call Types
Configuring the POTS Dial-Peer Incoming Called Number
Configuring the Data Dial Peer Lookup Preference
Creating a Trunkgroup and Configuring Maximum Calls Based on Call Type
Configuring MLPP Call Preemption over Outgoing Voice Calls
Enabling Preemption on the Trunk Group
Defining a Dialer Map Class and Setting the Preemption Level
Associating the Class Parameter on the Dialer Interface
Disabling TDM Hairpinning on the Voice Card
Configuring the POTS Dial Peer for Outgoing Voice Calls
Troubleshooting Tips for Integrated Data and Voice Services
Configuration Examples for Integrating Data and Voice Services for ISDN PRI Interfaces
MLPP DDR Backup Call Preemption over Voice Call: Example
Legacy DDR (Dialer Map): Example
Maximum Number of Data and Voice Calls on the Dial-Out Trunk Group: Example
Dial-Peer Configuration: Example
Feature Information for Integrating Data and Voice Services for ISDN PRI Interfaces
Integrating Data and Voice Services for ISDN PRI Interfaces on Multiservice Access Routers
Revised: June 19, 2006, OL-10383-01First Published: February 27, 2006This document 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.
Finding Feature Information in This Module
Your Cisco IOS software release may not support all of the features documented in this module. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported, use the "Feature Information for Integrating Data and Voice Services for ISDN PRI Interfaces" section.
Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Prerequisites for Integrating Data and Voice Services for ISDN PRI Interfaces
•
•
•
•
•
•
Prerequisites for Integrating Data and Voice Services for ISDN PRI Interfaces
•
•
•
•
Supported Modules
•
–
–
–
•
–
–
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 Europeprimary-net5 NET5 switch type for UK, Europe, Asia and Australiaprimary-ni National ISDN Switch type for the U.S.primary-ntt NTT switch type for Japanprimary-qsig QSIG switch typeprimary-ts014 TS014 switch type for Australia (obsolete)Restrictions for Integrating Data and Voice Services for ISDN PRI Interfaces
•
•
•
•
•
•
•
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•
–
–
•
•
–
–
–
–
–
–
–
–
–
–
–
–
Information About Integrating Data and Voice Services for ISDN PRI Interfaces
Before you configure integrated data and voice services on ISDN interfaces, you should understand the following concepts:
•
•
•
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.
Figure 1 shows an ISDN network configured for integrated data and voice services.
Figure 1 Integrated Voice with DDR Interface for WAN Failure Backup
Resource Allocation for Voice 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:
•
•
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:
•
•
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:
•
•
•
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.
•
•
•
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 0x8If you release the call before the preemption tone timer expires, the following cause code is used:
Normal Call Clear 0x10In both cases, the following internal cause code is used for the release calls:
Preemption Circuit Reserved 0x8How to Configure Integrated Data and Voice Services for ISDN PRI Interfaces
This section describes the tasks required to configure integrated services for ISDN interfaces:
•
•
Configuring the ISDN PRI Interface for Multiple Call Types
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.
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.
Use the following show commands to view the availability of HDLC resources:
•
The following example shows HDLC resources on the TDM side.
Router# show tdm connections slot 0Active TDM connections for slot 0=================================(Key: GT=FLEX TDM, V0=VWIC0, V1=VWIC1, V2=VWIC2, V3=VWIC3IC=EXPANSION, P0=PVDM0, P1=PVDM1, P2=PVDM2, P3=PVDM3HD=HDLC, BP=Backplane(AIM/NM))V0:04/04-->HD:31/18, V0:04/06-->HD:31/06, V0:04/08-->HD:31/12V0:04/10-->HD:31/36, V0:04/12-->HD:31/16, V0:04/14-->HD:31/10V0:04/16-->HD:31/04, V0:04/18-->HD:31/14, V0:04/20-->HD:31/22V0:04/22-->HD:31/20, V0:04/24-->HD:31/24, V0:04/26-->HD:31/30V0:04/28-->HD:31/26, V0:04/30-->HD:31/32, V0:04/32-->HD:31/08V0:04/34-->HD:31/34, V0:04/36-->HD:31/28, V0:04/38-->HD:31/38V0:04/64-->HD:31/00, V0:04/66-->HD:31/02, HD:31/00-->V0:04/64HD:31/02-->V0:04/66, HD:31/04-->V0:04/16, HD:31/06-->V0:04/06HD:31/08-->V0:04/32, HD:31/10-->V0:04/14, HD:31/12-->V0:04/08HD:31/14-->V0:04/18, HD:31/16-->V0:04/12, HD:31/18-->V0:04/04HD:31/20-->V0:04/22, HD:31/22-->V0:04/20, HD:31/24-->V0:04/24HD:31/26-->V0:04/28, HD:31/28-->V0:04/36, HD:31/30-->V0:04/26HD:31/32-->V0:04/30, HD:31/34-->V0:04/34, HD:31/36-->V0:04/10HD:31/38-->V0:04/38,•
In the following example, the -1 listings under the hdlc_chan column show the free HDLC channels.
Router# show controllers Serial 1/1:0Interface Serial1/1:0Hardware is HDLC32HDLC32 resource allocated to this interface:Slot 1, Vic_slot 1, Port 1CRC on 1, idle flags 1, frame inverted 0, clocking 0Channel-group number 0, hdlc32 channel number 2Channel-group bitfield 0x80000000, hdlc32 quad used 0x4Channel HW state: 2TX Ring:data_ptr: 0x0, descriptor: 0x102data_ptr: 0x0, descriptor: 0x102data_ptr: 0x0, descriptor: 0x102data_ptr: 0x0, descriptor: 0x102data_ptr: 0x0, descriptor: 0x102data_ptr: 0x0, descriptor: 0x102data_ptr: 0x0, descriptor: 0x102data_ptr: 0x0, descriptor: 0x102data_ptr: 0x0, descriptor: 0x102data_ptr: 0x0, descriptor: 0x102data_ptr: 0x0, descriptor: 0x102data_ptr: 0x0, descriptor: 0x102data_ptr: 0x0, descriptor: 0x102data_ptr: 0x0, descriptor: 0x102data_ptr: 0x2DD1918C, descriptor: 0xB8830102data_ptr: 0x0, descriptor: 0x102RX Ring:data_ptr: 0x2EE83E04, descriptor: 0x88800102data_ptr: 0x2EE84064, descriptor: 0x88800102data_ptr: 0x2EE842C4, descriptor: 0x88800102data_ptr: 0x2EE84524, descriptor: 0x88800102hdlc_chan hdlc_quad owner_idb chan chan_bitfield vic_slot port========= ========= ========= ==== ============= ======== ====0 1 65C03D5C 15 10000 1 01 2 65CB80F8 15 10000 1 12 4 67B862B0 0 80000000 1 13 8 65C7B1E4 1 40000000 1 14 10 67B8EDFC 2 20000000 1 15 20 65C83D30 3 10000000 1 16 40 67B97948 4 8000000 1 17 80 65C8C87C 5 4000000 1 18 100 67BA0494 6 2000000 1 19 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 0Configuring the POTS Dial-Peer Incoming Called Number
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. Use the following procedure to configure the POTS dial peer and incoming called number.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
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.
2.
3.
DETAILED STEPS
Enabling Integrated Services
Enabling integrated services allows data and voice call traffic to occur from ISDN PRI interfaces simultaneously.
When an interface is in integrated service mode:
•
•
By default, the integrated service option is disabled from the supported interfaces. Use the following procedure to enable integrated mode on a serial interface.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Creating a Trunkgroup and Configuring Maximum Calls Based on Call Type
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.
Note
Use the following procedure to create a trunk group and configure maximum calls based on call type.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Examples
See the following sample configurations for the max-calls command:
•
trunk group 1max-calls data 7•
trunk group 2max-calls data 2 direction inmax-calls data 3 direction outmax-calls voice 16•
trunk group 3max-calls any 10 direction inDisabling Integrated Services
When the isdn integrate calltype all command is removed from the interface, the isdn incoming-voice voice setting is restored and the interface returns to voice mode. Use the following procedure to remove the integrated services option from the interface.
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Configuring MLPP Call Preemption over Outgoing Voice Calls
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.
•
•
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.
Perform the following tasks to configure call preemption:
•
•
•
•
•
•
Enabling Preemption on the Trunk Group
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.
Note
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.
Use the following procedure to create a trunk group resource pool and enable preemption on the trunk group.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Defining a Dialer Map Class and Setting the Preemption Level
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.
Use the following procedure to define a map class for the dialer interface.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Associating the Class Parameter on the Dialer Interface
The trunk group preemption level is configured as part of a map class, which can be attached to a dialer map or dialer string.
•
•
Use the following procedure to associate the class parameter on the dialer interface.
SUMMARY STEPS
1.
2.
3.
4.
or
dialer pool number
5.
or
dialer string dial-string [class class-name]
DETAILED STEPS
Guest
