McDewey

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

Page 16

↗ View in doc context
page
16
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::15

Fax-rate voice. • Voice Activity Detection (VAD) is enabled. • No RSVP Support. • No IVR Application Support for POTS calls. • Direct-inward-dial is enabled. • Does not support VRF. • Outbound Dial-Peer Matching Outbound dial-peers are utilized to route POTS or VoIP calls from the gateway to the next call agent. Like inbound dial-peer matching, there is a list of items the gateway can use to match dial-peers based on the preference order for the specific protocol. However, unlike inbound dial-peers, if there is no eligible outbound dial-peer to route the call, then the call fails. Like inbound dial-peer matching, all dial- peers are searched based on the first match criteria. The gateway moves on to the next criteria only if no match is found. Table 4. Outbound SIP Dial-Peer Selection Preference Preference Match Criteria Dial-peer Commands 1 Dial-Peer Group Dial-Peer destination dpg <dpg-tag> (DPG configured on inbound dial-peer) 2 Dial-Peer Provision Policy URI destination uri-from <uri-tag> destination uri-to <uri-tag> destination uri-via <uri-tag> destination uri-diversion <uri-tag> destination uri-referred-by <uri-tag> (DPP configured on inbound dial-peer) 3 ILS Route String destination route-string <route-string-tag> 4 URI and Carrier-ID destination uri <uri-tag> AND carrier-id target <string> 5 Called Number and Carrier- ID destination-pattern <number-string> AND carrier-id target <string> 6 URI destination uri <uri-tag> 7 Called Number destination-pattern <DNIS-number> destination e164-pattern-map <pattern-map-number> dnis-map <dnis-map-number>