/mcpGateway(config-voice-uri-class)#do sh run | s TEST4 voice class uri TEST4 sip pattern 123456789
Inbound URI Dial-Peer Matching This feature was added in Cisco IOS 15.1(2)T and Cisco IOS-XE 3.8S and utilizes a voice class uri configured and applied to an inbound dial-peer. Incoming URI has been adopted by many people over the traditional incoming called-number statement for SIP calls as it the first match criteria checked when selecting inbound dial-peers. The command also allows administrators the ability to better match calls that come from a particular call agent or user. Full Documentation: Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards Common Use Cases An inbound dial-peer matching on the host portion of the URI to answer OPTIONS ping requests from CUCM. 1. An inbound dial-peer matching on the host portion of the URI to control inbound calls from an Internet Telephony Service Provider (ITSP) 2. An inbound dial-peer matching on the user-id portion of the URi for call treatment from certain users or numbers. 3. Configuration Example This example output matches dial-peer 777 for any SIP request sourcing from the two HOST IPs defined in the voice class URI. The header watched is defined as the From header on the dial-peer; however, an administrator can define many others including VIA, TO, and REQUEST (Request URI). If the CUCM sends an OPTIONS ping to the CUBE now matches dial-peer 777 and source my 200 OK reply to the OPTIONS from the specified interface. If CUCM sends an Invite to the CUBE matches dial-peer 777 as the inbound dial-peer.
! voice class uri CUCM sip host ipv4:10.50.244.2 host ipv4:10.50.244.20 ! dial-peer voice 777 voip description INCOMING URI session protocol sipv2 incoming uri from CUCM voice-class sip bind control source-interface Loopback777 voice-class sip bind media source-interface Loopback777 !