CUCM SIP TRUNK INVITES RTP to IP Address of wrong server
CUCM 10.5 SIP Trunking
I have a two site Cisco Call Manager Phone System with one server at each site (FL and California). I have had SIP trunking up and running in Florida for about a year. We are in the process of migrating our PRI trunks in California to SIP trunks, but we are unable to complete the RTP (Voice) connections on the calls. Every time we attempt a call the new sip trunk which is mapped through our CA Firewall, the Call Manager Server at that site advertises the RTP IP for the server in Florida. Since these are not mapped through the other firewall, the call fails with no audio. I cant seem to find a way to make the secondary call manager server advertise it's own IP address for the RTP instead of using the IP of the publisher. The calls originate from the CA server, it is just the RTP that keeps requesting to send to the wrong server. Any help on how to force the subscriber to advertise it's own IP or how to change it would be greatly appreciated. At wits end on this one.
I have a two site Cisco Call Manager Phone System with one server at each site (FL and California). I have had SIP trunking up and running in Florida for about a year. We are in the process of migrating our PRI trunks in California to SIP trunks, but we are unable to complete the RTP (Voice) connections on the calls. Every time we attempt a call the new sip trunk which is mapped through our CA Firewall, the Call Manager Server at that site advertises the RTP IP for the server in Florida. Since these are not mapped through the other firewall, the call fails with no audio. I cant seem to find a way to make the secondary call manager server advertise it's own IP address for the RTP instead of using the IP of the publisher. The calls originate from the CA server, it is just the RTP that keeps requesting to send to the wrong server. Any help on how to force the subscriber to advertise it's own IP or how to change it would be greatly appreciated. At wits end on this one.
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
All, I was actually able to fix this issue myself this morning shortly after publishing the question. For those interested in the response, the fix had to do with setting up media termination points and assigning them as trusted relay points. I set one of them up for each site and designated them as trusted relay points. When trusted relay points are selected, Cisco will route through the closest one based on the device pools. Seems like an easy fix, but there was some crazy head scratching on this last week.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial