Yealink Forums

Full Version: T23G and T48G Fails to include transport=tcp in contact header
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hello,

I'm having trouble with the new T23G phones. I'm using firmware version 44.80.0.60.
The same issue is happening on T48G phones when I upgrade to firmware 35.80.0.60.

I am also using NAPTR. The NAPTR resolves correctly to TCP with the correct ip and port.

When the phone registers it correctly uses a TCP port but fails to include the requisite:
"transport=tcp" in the contact header.

This cause the registration server heartburn because the connection is coming in on a TCP port but it is not specified in the header.

Here is an example from a T48G

REGISTER sip:p92dk.voiceelements.com SIP/2.0
Via: SIP/2.0/TCP 192.168.1.58:5060;rport;branch=z9hG4bK1589095695
From: "Reception" <sip:101@p92dk.voiceelements.com>;tag=264156176
To: "Reception" <sip:101@p92dk.voiceelements.com>
...
Contact: <sip:101@192.168.1.58:5060>
...
Content-Length: 0

When I return to firmware 35.73.0.50, it all works correctly.

REGISTER sip:p92dk.voiceelements.com SIP/2.0
Via: SIP/2.0/TCP 38.75.197.28:52501;rport;branch=z9hG4bK1884761878
From: "Reception" <sip:101@p92dk.voiceelements.com>;tag=2821122686
To: "Reception" <sip:101@p92dk.voiceelements.com>
...
Contact: <sip:101@38.75.197.28:52501;transport=TCP>
...
Content-Length: 0


Here is an example from a T23G with the incorrect header.

REGISTER sip:p92dk.voiceelements.com SIP/2.0
Via: SIP/2.0/TCP 192.168.1.51:5060;rport;branch=z9hG4bK90124193
From: "Office" <sip:104@p92dk.voiceelements.com>;tag=2313422629
To: "Office" <sip:104@p92dk.voiceelements.com>
...
Contact: <sip:104@192.168.1.51:5060>
...
Content-Length: 0

Problem is that I just bought a bunch of T23Gs because of discontinuing the T22P, so I am in a bind! There is no earlier firmware version to fall back on.

Please Help!!!
Hello,

Please upgrade phone to x.80.0.70 firmware. I test in a T48 with 35.80.0.70 and it works correctly.

Contact: <sip:6026@10.17.3.35:5060;transport=TCP>

Regards,
James
Hi. We just tried that on both phones:

On T48G

REGISTER sip:p92dk.voiceelements.com SIP/2.0
Via: SIP/2.0/TCP 38.75.197.28:5060;rport;branch=z9hG4bK4157743088
..
Contact: <sip:101@38.75.197.28:5060>
..
User-Agent: Yealink SIP-T48G 35.80.0.70
Content-Length: 0

On T23G

REGISTER sip:p92dk.voiceelements.com SIP/2.0
Via: SIP/2.0/TCP 192.168.1.51:5060;rport;branch=z9hG4bK3745717080
..
Contact: <sip:104@192.168.1.51:5060>
..
User-Agent: Yealink SIP-T23G 44.80.0.70
Content-Length: 0

Same issue. I think it is not working correctly due to the NAPTR.

When I change the Transport to "TCP" and put in the address that the NAPTR resolves to then it works (NOT USING NAPTR):

REGISTER sip:pbx11.voiceelements.com:5080 SIP/2.0
Via: SIP/2.0/TCP 192.168.1.74:5060;rport;branch=z9hG4bK700385971
...
Contact: <sip:125@192.168.1.74:5060;transport=TCP>
User-Agent: Yealink SIP-T23G 44.80.0.70
...
Content-Length: 0

Putting back to NATPR breaks it again.

Thanks for the quick response!
Ok, Can you please send us a level 6 syslog? I will check with R&D.

Go to Setting-> Configuration, set the log level to 6 and reproduce the issue, then export it to us.

Thanks,
James
(09-01-2015 02:04 PM)Yealink_James Wrote: [ -> ]Ok, Can you please send us a level 6 syslog? I will check with R&D.

Go to Setting-> Configuration, set the log level to 6 and reproduce the issue, then export it to us.

Thanks,
James

Hi James,

Requested file sent to support@yealink.com
Hello,

Please get the fix firmware 44.80.0.78 by this link:
http://ftp.yealink.com/?ShareToken=8DEE7...92E2B112C4

Regards,
James
Downloading and testing now. Will follow up ASAP.

This fixed it. Thank you.

Can we get a firmware update with the same fix for the T48G?
Reference URL's