Multiple Patterns support on a Voice Dial Peer

[Muthurani Lavanya Paneerselvam]

• Introduction
• 1. Multiple DestinationPatterns Under Same Outbound Dial-Peer
• 2. Multiple Incoming Patterns Under Same Incoming Dial-peer
• Example configuration
• Related Information

Introduction

This document covers the configuration for Multiple Pattern Support on a Voice Dial Peer feature allows you to configure multiple patterns on a VoIP dial peer using an E.164 pattern map. A dial peer can be configured to match multiple patterns to an incoming calling or called number or an outgoing destination number.

• Supports multiple destinations (session targets) be defined in a group and applied to a single outbound dial-peer
• This reduces the need to configure multiple dial-peers with the same capabilities but different destinations. 
• Configuring Multiple pattern support on a Voice dial peer (Outbound calls) supported from Release Cisco IOS XE Release 3.7S, 15.2(4) M
• Configuring Multiple pattern support on a Voice dial peer (Inbound calls) supported from Release Cisco IOS XE Release 3.11S, 15.4(1) T
• Restrictions: This feature is supported only on a voip dial peer
• Matching an incoming or outgoing call using a pattern defined in a VoIP dial peer is an existing feature on the Cisco Unified Border Element (Enterprise) and Session Initiation Protocol (SIP) Gateway.
• You can now support multiple patterns on a VoIP dial peer using an E.164 pattern map. You can create a E.164 pattern map and then link it to one or more VoIP dial peers.

1. Multiple Destination Patterns Under Same Outbound Dial-Peer

Sample Network configuration for Multiple Patterns under same Outbound Dial Peers by specifying each E164 Pattern

2. Multiple Incoming Patterns Under Same Incoming Dial-peer

Sample Network configuration for Multiple Patterns under same Incoming Dial Peer

Sample Network configuration for Multiple Patterns under same Incoming Dial Peer - contents of E164 patterns text file stored in flash:e164-pattern-map.cfg

Example configuration 

Example Configuration

Example: Configuring Multiple Patterns for Outbound Dial Peers by Specifying Each E164 Pattern Device# voice class e164-pattern-map 100 Device(voice-class)# e164 919500500. Device(voice-class)# e164 412100100. Device(voice-class)# e164 502100100. Device(voice-class)# e164 610200200. Device(voice-class)# description For Outbound Dial Peer Device(voice-class)# exit Device(config)# dial-peer voice 1 voip Device(voice-dial-peer)# destination e164-pattern-map 100 Device(voice-dial-peer)# codec g729r8 Device(voice-dial-peer)# session target ipv4:10.1.1. Device(voice-dial-peer)# end ! Example: Configuring Multiple Patterns for Inbound Dial Peer Device# voice class e164-pattern-map 200 Device(voice-class)# url flash:e164-pattern-map.cfg Device(voice-class)# description For Inbound Dial Peer Device(voice-class)# exit Device(config)# dial-peer voice 2 voip Device(voice-dial-peer)# description inbound DP via Called Device(voice-dial-peer)# incoming called e164-pattern-map 200 Device(voice-dial-peer)# codec g711ulaw

Verification

• show voice class e164-pattern-map 200

• show dial-peer voice [summary | dial-peer-id]

• show dial-peer voice | include e164-pattern-map

Related Information

• Multiple pattern support on a Voice dialpeer

[Marwan Urabi]

Thanks for this Document , but how if I need use it at pots dial-peer not VoIP to use local FXO lines ? Marwan Urabi

[Roger Kallberg]

@Marwan Urabi This is not applicable for POTS dial peers. It’s only available for VoIP dial peers.