04-14-2017 02:00 AM - edited 03-17-2019 06:48 PM
Is there a Jabber release for Windows that supports audio codecs G729 and G729B. Based on Cisco's data sheet, only G729A is supported from the 8k codecs in any Jabber release.
Solved! Go to Solution.
04-14-2017 03:30 AM
04-14-2017 02:33 AM
Hi Istvan,
The latest version of jabber 11.8.3 supports below codec .
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/11_8/cjab_b_planning-guide-jabber-118/cjab_b_planning-guide-jabber-118_chapter_01.html#CJAB_RF_S7E65AD2_00
Type |
Codec |
Codec Type |
Cisco Jabber for Android |
Cisco Jabber for iPhone and iPad |
Cisco Jabber for Mac |
Cisco Jabber for Windows |
---|---|---|---|---|---|---|
Audio |
G.711 |
A-law |
Yes Supports normal mode. |
Yes |
Yes |
|
µ-law/Mu-law |
Yes Supports normal mode. |
Yes |
Yes |
|||
G.722 |
Yes |
Yes |
Yes |
|||
G.722.1 |
24 kb/s and 32 kb/s |
Yes Supports normal mode. |
Yes |
Yes |
||
G.729 |
Does not support Visual Voicemail with G.729; however, you can access voice messages using G.729 and the Call Voicemail feature. |
No |
No |
|||
G.729a |
Yes Minimum requirement for low-bandwidth availability. Only codec that supports low-bandwidth mode. Supports normal mode. |
Yes |
Yes |
|||
Opus |
Yes |
Yes |
Yes |
|||
Video |
H.264/AVC |
Yes |
Yes |
Yes |
||
Voicemail |
G.711 |
A-law |
Yes |
Yes |
No |
|
µ-law / Mu-law (default) |
Yes |
Yes |
No |
|||
GSM 06.10 |
Yes |
Yes |
No |
|||
PCM linear |
Yes |
Yes |
No |
If users have issues with voice quality when using Cisco Jabber for Android or Cisco Jabber for iPhone and iPad, they can turn low-bandwidth mode on and off in the client settings.
(Rate if it helps)
JB
04-14-2017 03:00 AM
Hi Jitender,
Thanks for the response. So if the singalling peer or Jabber client advertises 729 first and 729A second, they will agree in 729A. Right?
In a theoretical situation, where the singalling peer of Jabber client advertises only 729 and nothing else, can the Jabber agree on that and map 729 to 729A on the endpoint where Jabber client is running?
Thank you
04-14-2017 03:07 AM
Hi Istvan,
Final Codec the end point talks aon is decided on
1) What all are common coded.
2) What codec are left after region filtration
For example
Endpoint A in Region A advertises codec g711,g729,g729A
Endpoint B in Region B advertises codec g711,g729,g729A
Region relationship between Region A and Region B is g729 so g711 would be filtered on region itself.
The the coded advertize preference is check so it should select g729 from above example.
Not sure if that answers your question.
(Rate if this helps)
JB
04-14-2017 03:19 AM
Hi Jitender,
If for e.g. by wrong design, the only codec between region A and B is g729, endpont B only advertises g729, but endpoint A (Jabber client) doesnt support g729, what will happen?
1. call fails with codec mismatch
2. Jabber maps g729 to g729A
Thank you in advance
04-14-2017 03:25 AM
Hi Istvan,
It would then require transcoder to make the call work
JB
04-14-2017 03:28 AM
Hi Jitender,
So in conclusion, in my example if no transcoder resource is provided, Jabber will not transcode from software g729 to g729a itself and call fails. Right?
Thank you
04-14-2017 03:30 AM
Thats correct
JB
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide