T29G Firmware T29-46.81.0.70 Breaks DialPlan Rules

[fastdevice]

DialPlan rules are no longer working with Auto provisioning.

[Lucia_Yealink]

From your description, it is working before but now no longer working, then what operation you do before it fail to work?

Can you kindly tell me how do you configure in the auto provision file?
And figure out to me which one fial to work. It would be better if you can provide the config.bin for us to check. Thank you.

[fastdevice]

Hi Lucia,

Very frustrated over the new v81 firmware and lack of accurate documentation. The DialPlan rule syntax has changed and not well documented. The configuration tool still shows the rules using the prior syntax but it now requires a new syntax to work. Had to figure this out by trial-and-error. The same for Auto Provisioning. Auto Provisioning doesn't follow any of the prior or new documentation and behaves differently depending on whether you use a TFTP or Web server. I've sent your team PCAP and Syslogs showing the undocumented behavior and nobody responds. Am I the only one using a T29G with the new firmware?

[complex1]

fastdevice Wrote:Very frustrated over the new v81 firmware and lack of accurate documentation.

Hi,

Are you saying all documentation of the v81_70 firmware is wrong/inaccurate?
Even the Admin Guide, Template Files and Release Notes?
Are you sure you have read the right documentation, which can be found here:
http://support.yealink.com/documentFront...umentId=15

[fastdevice]

I'm referring to config and provisioning guides.

The configuration tool outputs the old format dialplan: dialplan.dialnow.1.rule , while the template shows: dialplan.dialnow.rule.1 Honestly, this subtle change goes against portions of the Auto Provisioning guide the indicates that if the .boot files are not present, the phone will resort to using the older .cfg method.

Provided you are implementing an HTTP server for auto provisioning.

The Auto Provisioning Guide focuses on the, "y000000000000.boot" file and states that it tries to download this file first. When in fact, it actually looks for the mac.boot file first, NOT the "y000000000000.boot" Why couldn't the guide just state that it looks for the mac.boot and if not found, then look for "y000000000000.boot" However, even more important, it goes on to state that if the boot file is not found, it will then looks for common and mac.cfg files. Well, I can tell you that I let the phone sit for two days straight and it NEVER looks for anything but .boot files. And don't get me started with the behavior in encrypted mode. I spent hours mapping out the odd sequence of events when looking for .enc files. In fact, I've given up on encrypted.

Now if you move to a TFTP server, many behaviors are similar to the provisioning guide.

[fastdevice]

The configuration tool outputs the old format dialplan: dialplan.dialnow.1.rule , while the template shows: dialplan.dialnow.rule.1 Honestly, this subtle change goes against portions of the Auto Provisioning guide that indicates if the .boot files are not present, the phone will resort to using the older .cfg method.

Provided you are implementing an HTTP server for auto provisioning.

The Auto Provisioning Guide focuses on the, "y000000000000.boot" file and states that it tries to download this file first. When in fact, it actually looks for the mac.boot file first, NOT the "y000000000000.boot" Why couldn't the guide just state that it looks for the mac.boot and if not found, then look for "y000000000000.boot" However, even more important, it goes on to state that if the boot file is not found, it will then looks for common and mac.cfg files. Well, I can tell you that I let the phone sit for two days straight and it NEVER looks for anything but .boot files. And don't get me started with the behavior in encrypted mode. I spent hours mapping out the odd sequence of events when looking for .enc files. In fact, I've given up on encrypted.

Now if you move to a TFTP server, many behaviors are similar to the provisioning guide.

[Lucia_Yealink]

Dear,

Sorry for my late reply.

About the configuration tool, we will double check and modify it ASAP.

About the auto provision guide, it mention below:
he IP phone will try to download the MAC-Oriented boot file firstly and then download the
configuration files referenced in the MAC-Oriented boot file in sequence from the provisioning
server during the auto provisioning process. If no MAC-Oriented boot file is found, the IP phone
will try to download the common boot file and then download the configuration files referenced
in the common boot file in sequence. If no common boot file is found, the IP phone will try to
download the Common CFG file firstly, and then try to download the MAC-Oriented CFG file
from the provisioning server.

[fastdevice]

Hi Lucia,

This part of your statement does not work using an HTTP server, but does work using a TFTP server.

"...If no common boot file is found, the IP phone will try to
download the Common CFG file firstly, and then try to download the MAC-Oriented CFG file
from the provisioning server. "