Where a voice gateway is being used to handle SIP-SIP calls without Call Manager or CUBE in the environment, what (if any) is the correct way to configure transcoding?
With a dspfarm configured, we are finding that DSP's are being allocated for all calls even if codec and packetization are consistent on both call legs. Is it correct that this is occuring because there is no CUBE deployment?
Anthony was spot on, the VG is to provide demarcation between the ITSP and a SIP PBX, the SIP PBX can not talk directly to the ITSP for topology reasons.
ITSP <--SIP--> VG <--SIP--> PBX
Transcoding aside the box has to do very little so wanted to avoid having to license CUBE.
If CUBE is required, I would have assumed that without it, calls that required transcoding would simply fail (Which we see if there is no dspfarm configured), however with a dspfarm configured we are finding that a DSP is allocated to every call regardless, which is why I'm a little confused and thought perhaps it was a configuration issue.
First of all in this topology, you need a CUBE license. There is no way around it. Your gateway is processing two voip legs, providing demarcation between the outside and your PBX, hence its acting as a CUBE.
Second, we will need to look at the sip traces and your configuration to know why xcoder is been invoked.
Please rate all useful posts
"The essence of christianity is not the enthronement but the obliteration of self --William Barclay"
I do not believe CUBE licensing is required if telephony-service is not configured. Correct me if I'm wrong.
We can easily acheive want we want (without transcoding) without configuring telephony-service.
What we are finding is that the moment a dspfarm is configured, without telephony-service, a DSP is immediatly allocated on all calls. This is why we questioned if you can actually transcode without CUBE.
I suspect I have my answer (Unfortunatly, no), but will come back with some debugs shortly as it is interesting that we are seeing what we are.
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...