Yealink Forums

Full Version: Cannot register new T42s anymore
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Tried to register new T42s (Firmware: 66.84.0.15) against FreePBX (made this more than 100 times successfully before). Its a brand new one, right out of the box.

The new ones seems to ignore the response Status-Line: SIP/2.0 401 Unauthorized
and do not reregister with the credentials included.
It tries to register again and again but never sending credentials to the server.

It sends always this registration (replaced name with XXX), but always without credentials.
Via: SIP/2.0/UDP 10.250.250.10:5060;branch=z9hG4bK3423351914
From: "XXX XXX" <sip:510@192.168.16.25:5160>;tag=79229429
SIP Display info: "XXX XXX"
SIP from address: sip:510@192.168.16.25:5160
SIP from tag: 79229429
To: "XXX XXXXX" <sip:510@192.168.16.25:5160>
SIP Display info: "XXX XXX"
SIP to address: sip:510@192.168.16.25:5160
Call-ID: 0_3734511584@10.250.250.10
[Generated Call-ID: 0_3734511584@10.250.250.10]
CSeq: 1 REGISTER
Contact: <sip:510@10.250.250.10:5060>
Contact URI: sip:510@10.250.250.10:5060
Contact URI User Part: 510
Contact URI Host Part: 10.250.250.10
Contact URI Host Port: 5060
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Max-Forwards: 70
User-Agent: Yealink SIP-T42S 66.84.0.15
Expires: 3600
Allow-Events: talk,hold,conference,refer,check-sync
Content-Length: 0

Update: Downgraded firmware to 66.81.0.70. Works flawless with this firmware version.
Cannot make tests with all firmware versions, but 66.81 works.

Is there something wrong with 66.84?
(11-17-2019 09:15 AM)roli8200 Wrote: [ -> ]Tried to register new T42s (Firmware: 66.84.0.15) against FreePBX (made this more than 100 times successfully before). Its a brand new one, right out of the box.

The new ones seems to ignore the response Status-Line: SIP/2.0 401 Unauthorized
and do not reregister with the credentials included.
It tries to register again and again but never sending credentials to the server.

It sends always this registration (replaced name with XXX), but always without credentials.
Via: SIP/2.0/UDP 10.250.250.10:5060;branch=z9hG4bK3423351914
From: "XXX XXX" <sip:510@192.168.16.25:5160>;tag=79229429
SIP Display info: "XXX XXX"
SIP from address: sip:510@192.168.16.25:5160
SIP from tag: 79229429
To: "XXX XXXXX" <sip:510@192.168.16.25:5160>
SIP Display info: "XXX XXX"
SIP to address: sip:510@192.168.16.25:5160
Call-ID: 0_3734511584@10.250.250.10
[Generated Call-ID: 0_3734511584@10.250.250.10]
CSeq: 1 REGISTER
Contact: <sip:510@10.250.250.10:5060>
Contact URI: sip:510@10.250.250.10:5060
Contact URI User Part: 510
Contact URI Host Part: 10.250.250.10
Contact URI Host Port: 5060
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Max-Forwards: 70
User-Agent: Yealink SIP-T42S 66.84.0.15
Expires: 3600
Allow-Events: talk,hold,conference,refer,check-sync
Content-Length: 0

Update: Downgraded firmware to 66.81.0.70. Works flawless with this firmware version.
Cannot make tests with all firmware versions, but 66.81 works.

Is there something wrong with 66.84?


Hi dear customer,

Thanks for your feedback.
For this issue, we need your help to reproduce this issue and offer us diagnostic files (allconfig.tgz) for further troubleshooting.

To protect your information, please submit a ticket for us.
https://ticket.yealink.com/

Then, our techical support team will follow up it.

Best Regards,
Baron
Reference URL's