As the title suggests, I have CallManager 5.1.2 with a h323 gateway on a remote site. This site has recently moved and they have gone with an SIP tunk provider terminated on their SRST gateway.
When the site moved, the connectivity back to the HQ was severed so the phones operated in SRST with the SIP trunk and all worked great. Since then, they have built a VPN back to HQ. When the phones register with CM, calls in have stopped working.
I call in on the SIP trunk, the phone rings, when I answer nothing happens and the caller continues to hear ringback, then both disconnect.
Logically, the way I see it is that the SIP call comes in on the IOS gateway and hits the incoming SIP dial-peer, it gets bumped over to the CCM via another dial-peer and CCM rings the phone in question. This is all signalling. What should then happen is CCM connects the phone and the SIP call and then drops out of the loop so the phone is talking directly with it’s local gateway that terminates the sip trunk.
SIP trunks are not my area of expertise so I'm really lost on this one so any help would be appreciated. I've seen some mention of MTP's but I don't see how it fits in this case. Or maybe that's what my problem is!!
The SIP trunk will negotiate either G711 or G729 and there's a voice class applied to the dialpeers with both codes. It's not hardcoded to one or the other. But keep in mind that it works fine when Call Manager is out of the loop (in SRST). My understanding is that Call Maanger should only be signaling when the phones are not in SRST.
I'm wondering if someone would know if I need CUBE in this case. It keeps coming up in my searching, but I'm not really sure if my setup in this case requires it or if this is actually what my problem is.
Maybe somone could throw thir opinion into the mix.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...