Yealink Forums

When auto provisioning our phones we rely on the user agent string supplied by the phone in the request to the auto_provision.server.url to identify itself, i.e. "Yealink SIP-T46G 28.71.0.70 MAC-Address".

However, on our brand new T46G, firmware 28.71.0.70, it appears to send an empty user agent string by default.

If I export the configuration to config.bin, I can see a section that reads:
[ HttpServer ]
bEnable = 1
nPort = 80
strUserAgent =
strHttpVersion = 1.0
strUseragentDynm = SIP-T46G 28.71.0.70

And if I modify the strUserAgent string and import the configuration again, the phone does indeed supply the user agent string to the auto provision server.

Is there anything we can put in our auto provisioning configurations to get the phone to send a user agent string?

Hi Stefan,
This is a known issue, please download below firmware and check again:
ftp://Cathy:6br6pcyl@ftp.yealink.com/fir...1.0.85.rom
Thanks.

Thanks!
Problem fixed with the new firmware.

Great!

Isaac

Your original problem was the user-agent string. MX can't handle colons in there.

When you upgraded your string changed (Mac address gone)

What is confusing to me is that I upgraded my T46 tonight to v.85, yet the agent string is still the same as yours on v.70.

Not sure what is going on here.

Mark

(08-10-2013 12:01 AM)chopsywa Wrote: [ -> ]Isaac

Your original problem was the user-agent string. MX can't handle colons in there.

When you upgraded your string changed (Mac address gone)

What is confusing to me is that I upgraded my T46 tonight to v.85, yet the agent string is still the same as yours on v.70.

Not sure what is going on here.

Mark

Hi Mark,
Please reset to factory default and check again.
Thanks.

(08-12-2013 03:17 PM)Yealink Support Wrote: [ -> ]

(08-10-2013 12:01 AM)chopsywa Wrote: [ -> ]Isaac

Your original problem was the user-agent string. MX can't handle colons in there.

When you upgraded your string changed (Mac address gone)

What is confusing to me is that I upgraded my T46 tonight to v.85, yet the agent string is still the same as yours on v.70.

Not sure what is going on here.

Mark

Hi Mark,
Please reset to factory default and check again.
Thanks.

Yes thanks for that. Already tried and it worked fine. Thanks again.