07-16-2008 02:08 PM - edited 03-15-2019 12:00 PM
We have a new voice design in the testing phase, where the traffic path was shown below. This setup was working:
Verizon-->Edge_Router-->IP2IP Gateway-->Call Manager
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.
Does anyone have any input on any of this?
Any input would be appreciated.
07-17-2008 04:08 AM
In case anyone is interested, my serial interface had this line in the config:
ip verify unicast reverse-path
I removed this line and that corrected the problem.
07-17-2008 04:21 AM
Do you have a SIP trunk configured on the CallManager to allocated an MTP to the calls?
Please rate post....
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide