McDewey

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

Page 8

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

E164-Pattern-Maps (Inbound) Destination Server Group requri-passing session target (sip-uri) Dial-peer Provision Policy SIP-Profiles (Inbound) 15.4(2)T 3.12S Dial-Peer Group (POTS) 15.5(1)T 3.14S Voice Class Tenants 15.6(2)T 16.3.1 VRF Filtering for dial-peers 15.6(3)M 16.3.1 e164-translation n/a 16.8.1 SIP DSAPP n/a 16.12.1 Huntstop for server-groups n/a 17.4.1 sip listen port for tenant and Tenant Filtering for dial- peers n/a 17.8.1 DNS SRV Based Option Keepalive n/a 17.9.1 Cisco IOS / Cisco IOS XE Call Routing Fundamentals Cisco IOS and Cisco IOS XE gateways utilize a concept of a dial-peer to control call routing and capabilities negotiation for each leg of a call. A call leg is the bidirectional communication between two call agents. A call agent is a device that initiates, processes, or forwards telephony calls. This can be and is not limited to Telephony Provider equipment, a Cisco Gateway, an IP Phone, a Cisco Unified Communication Manager (CUCM), Cisco Unity connection (CUC), and so on. There are far too many Call Agents to list. Scenario: A call arrives at a Cisco gateway from another call agent and is the inbound call leg (in-leg). The gateway processes the call and based on its processing sends the call to the next call agent. This is the outbound call leg (out-leg).