08-27-2015, 05:54 AM
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!!!
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!!!