|
|
This document describes fine-grain address segmentation in dial peers for Cisco universal gateways. It includes the following sections:
This feature enables fine-grain address segmentation for dial plans in universal gateways that use universal ports to handle simultaneous voice and modem calls.
Say that you want to create a dial plan such as the following, in which a wildcard is used for voice calls, but in addition there are a few modem numbers:
When a call comes into the gateway, the voice dial peers are searched first for a match. If a match is found, the call is treated as a voice call. If a match is not found, the call is treated as a modem call.
However, the ordering of the search—first voice then modem—creates a problem. In this example, any call with the prefix 408555 is assumed to be voice. There is no way to signify that just a subset of that address range—calls to other than 4085551212 or 4085551213—should be treated as voice.
This feature enables you to add a new field to a voice dial peer to indicate any numbers that the voice dial peer should reject because, although they match the dial peer, they are actually modem calls. For the example above, you can create the following additional dial peers:
In this example, XYZVOICEAPP is a hypothetical voice application that you have created.
The gateway processes the longest prefixes first. In this example, if an incoming call is to 4085551213, longest-prefix matching select s dial-peer 2 as the match, not dial-peer 3.
You must still create modem dial peers with those same modem numbers.
You can use wildcards freely in voice dial peers and still ensure that modem calls are properly handled.
This application-field approach is consistent with approaches that will apply once full voice/dial integration is achieved on Cisco gateways. At that point, all modem calls will have some special application associated with them.
Modem calls must be configured twice: in the traditional modem configuration and in dial peers.
Additional memory is required for modem dial peers.
Additional dial-peer search time is required to process the additional dial peers and to check whether the matched dial peer is a modem dial peer.
To obtain lists of supported MIBs by platform and Cisco IOS release, and to download MIB modules, go to the Cisco MIB website on Cisco.com at the following URL:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
You must create a dial plan and dial peers before you can alter them using this feature.
Say that you want to create a dial plan such as the following, in which a wildcard is used for voice calls, but in addition there are a few modem numbers:
This feature enables you to create the following additional dial peers:
In this example, XYZVOICEAPP is a hypothetical voice application that you have created.
The gateway processes the longest prefixes first. In this example, if an incoming call is to 4085551213, longest-prefix matching select s dial-peer 1 as the match, not dial-peer 3.
You must still create modem dial peers with those same modem numbers.
This section documents modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.2 command reference publications.
To enable a specific application on a dial peer, use the application command in dial peer configuration mode. To remove the application from the dial peer, use the no form of this command.
Syntax Description
Defaults
No default behavior or values.
Command Modes
Command History
|
Usage Guidelines
Use this command to associate a predefined session application with an incoming or outgoing dial peer. Calls using this incoming or outgoing dial peer are handed to the predefined specified session application.
For SGCP networks, enter SGCPAPP in uppercase characters. This application can be applied only to POTS dial peers. Note that SGCP dial peers do not use dial peer hunting.
 |
Note In Cisco IOS Release 12.2, you cannot mix SGCP and non-SGCP endpoints in the same T1 controller. You also cannot mix SGCP and non-SGCP endpoints in the same DS0 group. |
For MGCP networks, enter MGCPAPP in upper-case characters. This application can be applied only to POTS dial peers. Note that MGCP dial peers do not use dial peer hunting.
For incoming calls to numbers that a voice dial peer should reject because, although they match the dial peer, they are actually modem calls, enter data_dialpeer in lower-case characters. The data_dialpeer application enables fine-grain address segmentation for dial plans in universal gateways that use universal ports to handle simultaneous voice and modem calls.
Examples
The following example shows how to define an application and how to apply it to an outbound MMoIP dial peer for the fax onramp operation:
The following example shows how to apply the MGCP application to a dial peer:
The following example shows how to apply the data_dialpeer application to a dial peer:
Related Commands
|
dial peer—Addressable call endpoint. In Voice over IP, there are two kinds of dial peers: POTS and VoIP.
gateway—A special-purpose device that performs an application-layer conversion of information from one protocol stack to another.
universal port—A device that is capable of being either a voice digital signal processor (DSP) or a modem.
Posted: Tue Jan 13 09:21:08 PST 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.