/mcpAfter this release, an administrator can configure one dial-peer to service multiple hosts for the same user. For example, testuser@example.com and testuser@example.net under the same dial-peer. Using session target sip-uri triggers DNS resolution of the domain of incoming Invite Req-URI and dynamically determine the session target IP. Example Configuration: The gateway recieves two SIP Invites with these headers Invite sip:testuser@example.com:5060 SIP/2.0 Invite sip:testuser@example.net:5060 SIP/2.0 The gateway matches the incoming SIP request of testuser@example.com and testuser@example.net on dial-peer 1 because of the incoming URI command and the user-id definition both match testuser. The command voice-class sip call-route url is present means you evaluate outbound dial-peers based on the request URI of this inbound Invite. You match dial-peer 2 because of the same reasons you matched dial-peer 1, the user-id of testuser. The session target of this dial- peer is the original sip-uri as defined by session target sip-uri, which was a FQDN. After a DNS resolution has taken place, and change example.com and example.net into an IP for layer 3 routing you send a message out of the gateway.
! ip host example.com 192.0.2.10 ip host example.net 192.0.2.10 ! voice class uri TEST-IN sip user-id testuser ! dial-peer voice 1 voip description INCOMING dial-peer incoming uri request TEST session protocol sipv2 voice-class sip call-route url ! dial-peer voice 2 voip description OUTBOUND dial-peer destination uri TEST session protocol sipv2 session target sip-uri !
Verification:
show voice class uri <uri-name> show voice class dial-peer provision-policy <number> debug voip uri