Multiple Destination Pattern Support on a Voice Dial Peer

Available Languages

Download Options

  • PDF     (121.5 KB)
    View with Adobe Reader on a variety of devices
Updated:July 26, 2012

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Multiple Destination Pattern Support on a Voice Dial Peer

Contents

Finding Feature Information

Last Updated: January 9, 2013

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 Multiple Destination Pattern Support on a Voice Dial Peer

Last Updated: January 9, 2013

Cisco Unified Border Element (Enterprise)

  • Cisco IOS XE Release 3.7S or a later release must be installed and running on your Cisco ASR 1000 Series Router.

Restrictions for Multiple Destination Pattern Support on a Voice Dial Peer

Last Updated: January 9, 2013

  • The Multiple Destination Pattern Support on Voice Dial Peer feature is supported only on a VoIP dial peer.

  • An E.164 pattern map is not supported on an inbound dial peer.

  • An E.164 pattern map may not be supported on a local file system depending on the Cisco software version that you are using.

  • Duplicate destination patterns cannot be added to a pattern map.

Information About Multiple Destination Pattern Support on a Voice Dial Peer

Last Updated: January 9, 2013

Overview of Multiple Destination Pattern Support on a Voice Dial Peer

On Cisco Unified Border Element (Enterprise) and Session Initiation Protocol (SIP) Gateway, one VoIP dial peer can have only one destination pattern. To support multiple destination patterns on a VoIP dial peer, which involve massive dial peer configuration, use an E.164 destination pattern map. You can create a destination E.164 pattern map and then link it to one or more dial peers. A destination pattern, which is associated with a dialed string on a specific telephony device, is configured on a VoIP dial peer by using the destination e164-pattern map command. When a dialed string on a telephony device matches the destination pattern, calls are routed on to the VoIP dial peer; otherwise the call fails. You must configure an E.164 destination pattern map for each VoIP dial peer that is defined on a device. Configuring an E.164 destination pattern map on multiple dial peers requires several configurations as compared to configuring a destination pattern map on a single dial peer.

When a destination pattern is the only source to enable a dial peer, a valid E.164 destination pattern map enables linked dial peers, whereas an invalid E.164 destination pattern map disables the linked dial peers. Additionally, whenever an E.164 destination pattern map is created or reloaded, one or more dial peers linked with an E.164 destination pattern map is enabled or disabled based on the validation of a pattern map.

When a dial peer has multiple destination patterns, select the longest prefix matching criteria to count as the pattern matched for the dial peer. For example, if dial peer A has two destination patterns matched where one destination pattern is matched with five digits and the other destination pattern is matched with four digits, then dial peer A is counted as matched with five digits.

How to Configure Multiple Destination Pattern Support on a Voice Dial Peer

Last Updated: January 9, 2013

Configuring Multiple Destination Pattern Support on a Voice Dial Peer

SUMMARY STEPS

1.    enable

2.   configure terminal

3.   voice class e164-pattern-map tag

4.   url url

5.   e164 pattern

6.   description string

7.   exit

8.   dial-peer voice tagvoip system

9.   destination e164-pattern-map tag

10.   end

11.   voice class e164-pattern-map loadtag

12.   show dial-peer voice

13.   show voice class e164-pattern-map [summary | tag]


DETAILED STEPS
  Command or Action Purpose
Step 1
enable


Example:

Device> enable

 

Enters privileged EXEC mode.

  • Enter your password if prompted.
 
Step 2
configure terminal


Example:

Device# configure terminal

 

Enters global configuration mode.

 
Step 3
voice class e164-pattern-map tag


Example:

Device(config)# voice class e164-pattern-map 11

 

Creates an E.164 pattern map to configure multiple destination E.164 patterns on a dial peer and enters voice class E.164 pattern map configuration mode.

 
Step 4
url url


Example:

Device(config-voice class e164-pattern-map)# url http://http-host/config-files/destination-pattern-map.cfg

 

Defines the URL of an internally or an externally stored text file used in the E.164 pattern map.

Note    If you are using the url command, skip Step 5 and proceed to Step 6.
 
Step 5
e164 pattern


Example:

Device(config-voice class e164-pattern-map)# e164 5557123

 

Defines a complete E.164 telephone number prefix.

 
Step 6
description string


Example:

Device(config-voice class e164-pattern-map)# description It has 3 entries

 

Provides a description for a specific E.164 pattern map.

 
Step 7
exit


Example:

Device(config-voice class e164-pattern-map)# exit

 

Exits voice class E.164 pattern map configuration mode and enters global configuration mode.

 
Step 8
dial-peer voice tagvoip system


Example:

Device(config)# dial-peer voice 123 voip system

 

Defines a local dial peer and enters dial peer configuration mode.

 
Step 9
destination e164-pattern-map tag


Example:

Device(config-dial-peer)# destination e164-pattern-map 1111

 
Links an E.164 pattern map to one or more dial peers.
  • Identifies a destination E.164 pattern map associated with a dial peer with a number assigned to the destination E.164 pattern map. The range is from 1 to 10000.
Note    Repeat the Steps 1 to 9 to add multiple destination E.164 patterns to a pattern map.
 
Step 10
end


Example:

Device(config-dial-peer)# end

 

Exits dial peer configuration mode and enters privileged EXEC mode.

 
Step 11
voice class e164-pattern-map loadtag


Example:

Device# voice class e164-pattern-map load 2543

 

Loads a destination E.164 pattern map that is specified by a text file.

 
Step 12
show dial-peer voice


Example:

Device# show dial-peer voice

 

Displays the status of an E.164 pattern map when the pattern map is associated with a dial peer.

 
Step 13
show voice class e164-pattern-map [summary | tag]

Example:

Device# show voice class e164-pattern-map 11

 

Displays the status of the configured E.164 pattern maps and the status of the text file.

  • Also displays the status and the content of a particular E.164 pattern map.
 

Configuration Examples for Multiple Destination Pattern Support on a Voice Dial Peer

Last Updated: January 9, 2013

Example: Multiple Destination Pattern Support on a Voice Dial Peer

voice class e164-pattern-map 11  
  url http://http-host/config-files/destination-pattern-map.cfg
  e164 5557456  
description it has 5 entries
!
dial-peer voice tag voip system
destination e164-pattern-map 1131    
!
voice class e164-pattern-map load 2543 
!

Information About Multiple Destination Pattern Support on a Voice Dial Peer

Last Updated: January 9, 2013

The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.

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.

Table 1 Feature Information for Multiple Destination Pattern Support on a Voice Dial Peer
Feature Name Releases Feature Information

Multiple Destination Pattern Support on a Voice Dial Peer

15.2(4)M

The Multiple Destination Pattern Support on a Voice Dial Peer feature is used for handling calls that have noncontiguous dial patterns. This feature allows you to create an E.164 pattern map with multiple destination E.164 pattern, which helps to define and configure destination patterns on an individual dial peer or multiple dial peers.

The following commands were introduced or modified: destination e164-pattern-map, e164, show voice class e164-pattern-map, url, voice class e164-pattern-map load, voice class e164-pattern-map.

Multiple Destination Pattern Support on a Voice Dial Peer

Cisco IOS XE Release 3.7S

The Multiple Destination Pattern Support on a Voice Dial Peer feature is used for handling calls that have noncontiguous dial patterns. This feature allows you to create an E.164 pattern map with multiple destination E.164 pattern, which helps to define and configure destination patterns on an individual dial peer or multiple dial peers.

The following commands were introduced or modified: destination e164-pattern-map, e164, show voice class e164-pattern-map, url, voice class e164-pattern-map load, voice class e164-pattern-map.

Last Updated: January 9, 2013

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: 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)

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.

© 2013 Cisco Systems, Inc. All rights reserved.

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products