McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 36

↗ View in doc context
page
36
source
voice-quality/troubleshooting/cisco-ios-vs-iosxe/cisco-ios-vs-iosxe.md
chunk_id
voice-quality::troubleshooting::cisco-ios-vs-iosxe::cisco-ios-vs-iosxe::48

The entries in both configuration methods can utilize all normal dial-peer wildcards for further aggregation! Note: When both incoming and outgoing dial peers are configured with calling e164-pattern-map, it is essential to apply a dial-peer provision policy to the incoming dial peer to avoid call failures. Full Documentation: Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards CLI Configuration Example - Calling Numbers

! voice class e164-pattern-map 1 description E164 Pattern Map for calling numbers e164 919574100. e164 919574300. e164 8675309 ! dial-peer voice 1 voip description INBOUND Dial-peer based on CALLING # incoming calling e164-pattern-map 1 ! dial-peer voice 11 voip description OUTBOUND Dial-peer based on CALLING # destination calling e164-pattern-map 1 !

CLI Configuration Example - Called Number

! voice class e164-pattern-map 2 description E164 Pattern Map for called 800 numbers e164 91800T e164 91855T e164 91888T ! dial-peer voice 2 voip description INBOUND Dial-peer based on CALLED # incoming called e164-pattern-map 2 ! dial-peer voice 22 voip description OUTBOUND Dial-peer based on CALLED # destination e164-pattern-map 2 !

Flash Configuration Example

!

Image 1 from page 36