T46 Autoprovision page blank

[nicknomo]

After an initial autoprovision, the autoprovision page on the T46G is now blank... Any ideas on how to get it back?

[CWR]

is your autoprovision template missing these items or setting them to a null value?

[Yealink Support]

Hi Nicknomo,

Could you provide your auto provision file to us so that we can figure out what reason cause your problem?

[nicknomo]

(10-12-2013 06:43 AM)craigreilly Wrote:  is your autoprovision template missing these items or setting them to a null value?

Hi, I'm not sure what you are asking exactly.

Basically, I can't even load the page in the phone web GUI. After the initial autoprovisioning, I go to Settings->autoprovision, and the page comes up completely blank. There is literally nothing of the page. Just a blank web page.

It seems to have some sort of error on the page, as denoted by an yellow exclamation point in IE. I can only get back access to the page by performing a factory defaults restoration.

---

It happened after I only applied the main config, not the mac oriented config... it is attached.

Thanks in advance for the help.

[nicknomo]

(10-12-2013 03:53 PM)Yealink Support Wrote:  Hi Nicknomo,

Could you provide your auto provision file to us so that we can figure out what reason cause your problem?

I just wanted to follow up and make sure what I sbumitted was sufficient.

[CWR]

Have you tried a factory reset? Hold down the "OK" button for about 5 seconds then hit the appropriate action.
It sounds like something in the Firmware load is wrong.

[nicknomo]

(10-17-2013 01:05 AM)craigreilly Wrote:  Have you tried a factory reset? Hold down the "OK" button for about 5 seconds then hit the appropriate action.
It sounds like something in the Firmware load is wrong.

I've restored the phone using both the Web GUI and the method you mentioned. The menu comes back, and I can access the autoprovisions page in the web gui.... but it disappears again after autoprovisioning with the main y(...)028.cfg file.

There must be something in there that I've done wrong that is causing this. It happened on the newest firmware, and the firmware before that (I forget what it came loaded with).