Yealink Forums
Yealink T42S - User Agent and HW version - Printable Version

+- Yealink Forums (http://forum.yealink.com/forum)
+-- Forum: IP Phone Series (/forumdisplay.php?fid=4)
+--- Forum: Auto Provisioning (/forumdisplay.php?fid=14)
+--- Thread: Yealink T42S - User Agent and HW version (/showthread.php?tid=41443)



Yealink T42S - User Agent and HW version - Ale - 01-09-2018 02:09 PM

Hi,
analyzing the User Agent sent by the T42S I noticed that the part corresponding to the firmware version, starts with 66. What I expected was that it started with the T42S HW version, which is 67 (as the autoprovisioning guide says).

Is it an error?
Moreover, 66 is the HW version of the T46S model and even its firmware version starts whits this number (correctly).

This ambiguity creates me some problems, will it be solved in the future or is there a reason for this behavior on this phone model?


RE: Yealink T42S - User Agent and HW version - Samuel_Yealink - 01-11-2018 05:57 AM

Dear Customer,

In the user agent it shows only the firmware number, not the hardware number, see below example,

User-Agent: Yealink SIP-T48G 35.83.0.3\r\n

Besides, the hardware number consists of 6 parts of numbers while firmware number only has 4 parts of number.

e.g. T46S's hardware number: 67.0.0.0.0.0

Kind Regards
Samuel Wang


RE: Yealink T42S - User Agent and HW version - Ale - 01-11-2018 09:01 AM

So this thread http://support.yealink.com/faq/faqInfo?id=70 is no longer valid?
It says that the first part of the firmware corresponds to the phone model, but in my case (T42S and T46S) seems to have the same phone model number (66)?
Is it correct?


RE: Yealink T42S - User Agent and HW version - Samuel_Yealink - 01-11-2018 09:30 AM

Dear Customer,

The thread you mentioned is out-dated, you are right the first number usually indicates the hardware, but the T4xS series share the same firmware, that's why on the T4xS series, the user agent shows 66.x.x.x.

Kind Regards
Samuel Wang


RE: Yealink T42S - User Agent and HW version - Ale - 01-11-2018 09:48 AM

Ok, good to know.

Thank you for your help.