Failed calls due to wrong codec

Hello

I have a connection problem with one provider:

I’m using X-Lite 4 as my UA with only codec allowed: G711u and G711a .
When I register the UA directly with the provider, calls go through without any problem.
However, when I connect my UA as an extension to PBXes and try to make a call, the call fails. The provider claims that the request arrives with only codec GSM (which is not supported).

When I trace the call I made directly to the provider, he never replies with GSM as an optional codec, but only with G711u .

Looking at the PBXes logs I could see:

code:

VERBOSE[9341] logger.c: Capabilities: us - 0x18061e (gsm|ulaw|alaw|g726|speex|ilbc|h263|h263p), peer - audio=0xc (ulaw|alaw)/video=0x0 (nothing), combined - 0xc (ulaw|alaw) VERBOSE[9341] logger.c: Found description format GSM VERBOSE[9341] logger.c: Capabilities: us - 0x61e (gsm|ulaw|alaw|g726|speex|ilbc), peer - audio=0x2 (gsm)/video=0x0 (nothing), combined - 0x2 (gsm) VERBOSE[9341] chan_sip.c: Oooh, we need to change our formats since our peer supports only 0x2 (gsm) and not 0x4 (ulaw)

Somehow, the GSM codec comes into action, although neither my UA nor the provider supports this codec.



Can someone please assist me with this problem?

RE: Failed calls due to wrong codec

According to your log, your provider SIPme signals GSM (3) via SDP as the only codec. We will soon be able to trace SIP packets. Then we can come back to this if you wish.

RE: Failed calls due to wrong codec

Thank you for your reply.

It would be nice if you can please include the sip trace so I can forward it to the provider.

when I make a call from same UAC registered directly with this provider I can see only G711a and G711u and calls go through.
They don't support GSM codec at all.

Also, my UAC is configured to these two G711only (you can see it on your logs too), so if I'm not mystaking, in any case GSM is not the common codec.

Regards,
Dan

This post has been edited 1 time(s), it was last edited by dst on 15.10.2010 at 14:38.

RE: Failed calls due to wrong codec

SIP trace can now be accessed from the "System Log" tab.

Since this is a new feature click "Submit & Start" in "Personal Data" first.

RE: Failed calls due to wrong codec

Wow, nice feature, the sip trace...

Indeed, in this case I can see the provider sends GSM codec in his 200 OK response.

I will take it eith the provider from here.

Thanks for your assistance.