The IP2IP Gateway router was sitting with a single ethernet interface on the core switch.
The SIP trunk is physically connected to a serial interface on the Edge router and Verizon was sending their Sip invites to the IP2IP Gateway etherent interface, where the h323 binding is. The calls were working this way inbound and outbound.
The system is designed to dynamically fail over to our DR site if we loose the trunk to Verizon in the main site.
Verizon will route the calls to our DR Trunk and IP2IP Gateway router.
We found with this scenario that the IP2IP gateway router could not detect when the serial interface on the edge router went down and therefore Call Manager would not route calls to the DR Side.
The Voice Engineer had us change the existing config by moving the serial interface to the IP2IP Gateway router:
Verizon-->IP2IP Gateway-->Call Manger
Since we made that move (nothing else has changed) we have had one way audio and cannot find the problem.
The Voice Engineer is stuck and has opened a TAC case and we do not seem to be getting anywhere with that either.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...