/mcp! sccp local <interface> ! sccp ccm group <number> bind interface <interface> !
H323 Binding Commands
<#root> ! inteface <interface> ! ! Media Bind Command: h323-gateway voip interface ! ! Signaling Bind Command: h323-gateway voip bind srcaddr <a.b.c.d> !
DNS and VoIP Dial-Peers DNS with VOIP is employed just like any other DNS solution. A common configuration is to utilize session target dns:FQDN.com. A Cisco Gateway performs a DNS Resolution even when no ip domain lookup is configured globally on the gateway. This means that even though you are disabling DNS the VOIP dial-peers still resolve the DNS entry. However, recently in Cisco IOS XE 3.16S there were some changes to the overall DNS functionality within Cisco IOS XE platforms.
After this change, dial-peers configured with session target dns:FQDN.com now obey the fact that DNS is disabled with no ip domain lookup. I recommend always ensuring the command "ip domain lookup" is configured when working with DNS to avoid this issue. For outbound SIP connections, CUBE performs this order of operations for DNS resolution. SRV query lookup 1. A Record Lookup 2. AAAA Record Lookup 3. For information on how the SRV is created, or how to skip the SRV and perform an A record query on a session-target, refer to the full documentation: Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards For inbound SIP connections where an Cisco IOS gateway needs to resolve a header to respond to a message, the gateway can use this order of operations for DNS Resolution