Yealink Forums

Full Version: T46 Codec Selection - Garbled Voice on Asterisk
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
Hi everyone!

We are using Asterisk 1.8.15.1 and just received a bunch of brand new T46Gs

Phone Firmware Revision is 28.71.0.180

Whenever we make aoutgoing calls the connection is extemely garbled.
On a first survey with wireshark i foudn out that codec negotiation seems to go wrong completely.

Has anyone exprience with asterisk and T46Gs and any suggestions on this problem?

My sip-conf:
[031622502966]
type=friend
qualify=yes
language=de
host=dynamic
user=042122502966
secret=NotImportantHere
context=kd0421225029-intern
subscribecontext=kd0421225029-intern
callerid="TEST2" <66>
canreinvite=no
dtmfmode=rfc2833
limitonpeer=yes
call-limit=5
allow=alaw
disallow=ulaw

Bets,
George
Hi GeorgSchwarz,

I test the outbound call in asterisk 1.8.11.0 and the voice is clear.
In order to do troubleshooting, please supply me syslog level 6, config.bin and pcap.
Before you export the syslog, please set log level as 6, and reboot the phone, then click Start,and reproduce the issue, then click Stop,and export the trace, syslog, config,bin to us.
(About where to export these files, please refer to attached screenshot.)

These three files are very important for us, hope you can kindly understand.
Hi!

Sure, i will provide the files as soon as I get back from the christmas holidays...

Thanks for helping,
best
George
Hi!

As requested the files as attachment.
It's vital for us to have alaw connectivity.
Another interesting thing is when I change thje codec-Lines in my sip.conf of the respective peer to

allow=alaw,gsm
disallow=all

I get the follwing Asterisk console message and no call at all:
[Dec 27 16:55:30] NOTICE[26050]: chan_sip.c:9257 process_sdp: No compatible codecs, not accepting this offer!

The phone is set to
GSM, PCMA
[attachment=514]

Its also obvious on the pcap-dump that the T46 still seems to use G711µ

Thanks fpr your help
P.S.: I wonder if yought want to remove the files from the forum after retrieving them. It's a test environment anyway, but I dont want to have the data around for years ;-)
Hi GeorgSchwarz ,

I have got your files and modified your previous post. Smile I have submitted your files to our R&D. If any update, i will contact with you asap.
Hi!

Thanks a lot! If I can provide additional data or anything else that might contribute to a solution, just let me know, I'll be happy to help


Best,
George
Hi GeorgSchwarz,

Your issue is releate to codecs mismatch. You can reset phone to factory and test again.

Please don't change the rtpmap of each payload type.
codec Yealink
PCMU 0
PCMA 8
g729 18
GSM 3
g722 9
g723 4
CNG 13
g726-32 102
g726-16 103
g726-24 104
g726-40 105
iLBC 106
Thanks. I will check as soon as possible.
Intersting ... we took the phone from the original wrapping. I'll keep you updated...


Thanks a lot
George

(01-03-2014 04:33 PM)Yealink Support Wrote: [ -> ]Hi GeorgSchwarz,

Your issue is releate to codecs mismatch. You can reset phone to factory and test again.

Please don't change the rtpmap of each payload type.
codec Yealink
PCMU 0
PCMA 8
g729 18
GSM 3
g722 9
g723 4
CNG 13
g726-32 102
g726-16 103
g726-24 104
g726-40 105
iLBC 106
Hi GeorgSchwarz,

Sorry for the inconvenience. Can you telll me the SN number of your phones?
How many phones had this issue ? Where do you buy those phones?
Sorry, if I caused a misunderstanduing.

The problem was in fact our Autoprovisioning, and we did not see that some settings were still obtained from the server when we did a manual config after a firmware reset...

In our version that was initially built for v71 releases of the T2x-series whe had the codec selection like this (which works perfectly well for the T2x series)

account.1.codec.1.payload_type = PCMA
account.1.codec.2.payload_type = G722
account.1.codec.1.enable = 1
account.1.codec.2.enable = 1
account.1.codec.3.enable = 0
[...]

Obviously when I do that the RTPMap value does not change along with the allowed codecs.
I have now set the RTP-Map values according to your post, and my AutoProv-File now looks like this:

account.1.codec.1.payload_type = PCMA
account.1.codec.1.rtpmap = 8
account.1.codec.1.enable = 1

account.1.codec.2.payload_type = GSM
account.1.codec.2.rtpmap = 3
account.1.codec.2.enable = 1

account.1.codec.3.enable = 0
[...]


And now things are working like a charm

Thanks for your excellent support,
best,
George
Pages: 1 2
Reference URL's