/mcpNote: huntstop and preference commands can also be used in conjunction with URI matching statements as they are general dial-peer configuration commands. Furthermore, voice class server- group configurations can utilize huntstop commands in 17.4.1a. Refer to the section Destination Server-Groups for more details on this. URI Dial-Peer Hunting The gateway looks at each match criteria and exhausts it before it moves to the next match criteria. An example of this would be on an inbound SIP call. Based on Table 1. Inbound SIP Dial-Peer Selection Preference, the first thing the Cisco gateway checks is the URI and evaluates all potential URI commands to find one that fits. If there is no match, or none are configured, then the gateway moves to the next matching item and performs an evaluation on that criteria. This process repeats until the call either routes based on a match or the gateway runs out of match criteria to check. When an inbound or outbound dial-peer is configured with a URI command, the gateway examines the URI that was received in multiple headers for a potential match. The match preference is based on the most specific match and the exact preference goes Full URI match, Host Portion, User Portion, or telephone URI. Knowing the order of operations for URI matching can greatly aid in dial-peer matching with SIP and CUBE deployments. This preference order can be manipulated using the command voice class uri sip preference to specify the user-id as the first option instead of host. URI Preference: The Host portion of the URI. Examples: (@<ip_address> or @example.com) 1. The User portion of the URI. Examples: (sip:8675309 or sip:user) 2. The tele-uri. Example: (tel:18005532447) 3. Exact match for the full URI. Examples: (user@host.domain.name, user@<ip_address>, 8675309@example.com, 8675309@example.com) 4. Supporting Document: Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards Scenario: An administrator has configured this dial-peers and sends a call to the gateway. The From header in the received Invite is From: sip:testuser@192.0.2.1. The gateway can potentially match two different dial-peers based on this header. Dial-Peer 1 based on the user portion and dial-peer 2 based on the host portion. However, since a host match is a preference over a user match, dial-peer 2 is used for the inbound dial-peer in the call.