cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
308
Views
0
Helpful
1
Replies

CUBE / CUCM - Support for Midcall Codec Change on ITSP Side

TONY SMITH
Spotlight
Spotlight

Hi,

The scenario for these problem calls is as follows, showing the CUBE<>ITSP signalling ..

Send Invite etc as normal, early offer in this case
Receive 183/SDP Session Progress, G711A
Receive 200 OK/SDP, also G711A
Receive Re-Invite with G729 (inactive)
CUBE responds with 488 Not Acceptable Media and the call clears

What's happening I think is that the ITSP is always sending early media as G711A, then switching to the actual codec when the call actually gets answered.  And rather than doing this within 200 OK, it's sending that with G711A and switching via a Re-Invite. 

I've been looking to see if there's a way to get the CUBE to accept what is effectively a mid-call codec change, and the only positive answer I've found is from 2008 at which time it wasn't supported ..

 https://community.cisco.com/t5/ip-telephony-and-phones/cube-midcall-codec-change/td-p/1011130

Does anyone know if this can be supported now?   It seems slightly irrational that the CUBE takes issue with a codec when the state is "a=inactive".  

Thanks, Tony S

1 Reply 1

Hi,

Mid-call signaling and codec change is supported in cube with different
options (pass through, consumption, preservation). See this link.

https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/cube/configuration/cube-book/voi-cube-midcall-reinvite.html

Try the consumption or preservation. Most likely they will fix the problem.
This seems interoperability problem as in normal cases re-invite is used
for features such as hold, transfer, etc

****** please remember to rate useful posts