Have a SIP Cube at a remote branch office (London).
CUCM running 9.1 at Hub location (US)
London Phones and London SIP Trunk from CUCM to CUBE are in same device pool/region etc.
Remote branch 7965 phone dials outbound (which will use the London CUBE) and CUCM sends an SIP INVITE to the London Cube with codec’s advertised of G711ulaw/G711alaw/G729 (m=audio 31030 RTP/AVP 0 8 18 101).
Inbound Dial-Peer has a Voice Class Codec of G729r8 only. CUBE sends back a “Not Acceptable Media” message. I would think since the inbound dial-peer has G729 which is listed in the INVITE that it would select that and proceed with the call. This is not the case. Why would the inbound dial-peer not select G729 as an acceptable codec and extend the call?
Here’s some info from the CUBE and log.
INVITE as Seen from the London CUBE @ 192.168.23.1 (172.19.108.4 is CUCM in US)
I have never deployed a solution like this..I have alwayas ensured that on my inbound leg, the codecs advertised matches on both ends...It looks as if even though this should work, CUBE is detecting that the offfered codecs do not match on the inbound leg bcause some of the codecs are missing...To confirm this lets do the ff
1. Remove g729 from the codec list and eplac with g711u or g711a and confirm that you still get media not accepted
2. remove voice class codec and hard code one of the codecs and test again..
If my assumptions are right, you should get the same issue. If this is the case then you will need to have a voice class codec with all the codecs in the list that is offered by CUCM. You can choose what codec you use for this call on the outbound leg. Eg you can configure the outbound leg to use G729 and that wouldnt be a problem..
Let me know your findings
Please rate all useful posts
"opportunity is a haughty goddess who waste no time with those who are unprepared"
Please rate all useful posts
"The essence of christianity is not the enthronement but the obliteration of self --William Barclay"
I removed the codec list and replaced with a list allowing only G711ulaw / G711alaw and still received the "Media Not Acceptable" message.
Hardcoding the codec's to either G729 or G711 had the same "Media Not Acceptable" result.
Only having the inbound dial-peer have all 3 codec's in the codec list created a working solution.
Initially my thinking was to accept it G729 as opposed to G711 so when the call leg to the ITSP selects G729 the CUBE wouldn't look to allocate a X-Coder (if it accepted it via the inbound call leg as G711) and it would be G729 all the way through. That thinking won't work and only having all codec's listed will allow the inbound call leg to complete.
Glad to be of help, I knew that is what the issue will be. In this scenario there is no need to worry about CUBE invoking a xcoder because the inbound leg has multiple codecs in it, whatever outbound leg is set to will be fine as long as the codec is offered in the inbound leg..
You can refer to this document I wrote on codec selection over sip trunks and dont forget to rate any useful posts
As your problem is already solved and if it's possible then can you please check with your old configuration again in addition to add your "Voice-class codec 1 (G729r8 only)" on outgoing and incoming dial peer as well.
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...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.