No G729 in Web client

[dnehring]

I recently discover that the webclient seems not to support G729. I set in the codec priority g729 to the top, but it does not appear in the SIP header:

v=0 o=3cxVCE 18446744072562417736 18446744073091201164 IN IP4 127.0.0.1 s=3cxVCE Audio Call c=IN IP4 127.0.0.1 t=0 0 m=audio 8746 RTP/AVP 111 8 9 0 103 104 106 105 13 110 112 113 126 a=rtpmap:111 opus/48000/2 a=fmtp:111 minptime=10;useinbandfec=1 a=rtpmap:8 PCMA/8000 a=rtpmap:9 G722/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:103 ISAC/16000 a=rtpmap:104 ISAC/32000 a=rtpmap:106 CN/32000 a=rtpmap:105 CN/16000 a=rtpmap:13 CN/8000 a=rtpmap:110 telephone-event/48000 a=rtpmap:112 telephone-event/32000 a=rtpmap:113 telephone-event/16000 a=rtpmap:126 telephone-event/8000 a=ptime:20 a=sendrecv

This was a direct call 3cx desktop app to 3cx desktop app (version 18.7.10). It looks like g729 is not implemented in the desktop client. Changing the codec priority works on-the-fly, no client reconfiguration necessary. It works for all other codecs flawlessly.


Dirk

 

[VasilisV_3CX]

Hi @Dirk,

Yes that's correct, there is transcoding that takes place automatically not much else to add here.

 

[dnehring]

We have some trouble with the mobile app, so I try to force G729 as codec on both sides to test the quality. If the codec makes nothing in the settings, you should drop it from the list.

What is the status of the latest mobile client, is there a G.729 native support?

Dirk

 

[VasilisV_3CX]

Hi @dnhring,

What is the status of the latest mobile client, is there a G.729 native support?

The mobile apps do have support for G.729. You can confirm this with a wireshark capture, you'll see that G.729 is sent in the message body.