BUG: Template for Fanvil I23S seems to be malformed or corrupted in v16

[BrenttG]

I have been trying to configure a fanvil call box for a while now, and while setting it up in 3CX initially went without issue while creating the extension, once it was created, the 3CX server began spitting out errors in the Event Log as follows, Note, that this 3CX server has no custom templates, or other incidental changes from the norm. And this is the first fanvil device of any model to be attempted on this specific phone server.

3CX Template Parser ID: 30025
Unknown variable '%%Type%%' in template fanvil_doorphone.ph.xml at position 4943

This error message is repeated in the Event Log, over and over and over and over and over. And obviously as expected, the fanvil itself will not actually provision, i tried just for the heck of it just to see if it was a soft error that could be ignored, or if it was a blocking issue. Definitely Blocking. Autoprovisioning from the fanvil web UI fails those some details appear, not all do, and option 66 provisioning yields identical results, i can see "some" of the proper info in the settings, and other fields are left blank.

Please assist 3CX Devs!

 

[BrenttG]

Bump!

 

[BrenttG]

@YiannisH_3CX Could you help push this up the chain?

 

[cobaltit]

Or @JohnS_3CX

@BrenttG I'd put in a ticket as well if you haven't already.

 

[YiannisH_3CX]

Hello @BrenttG and thank you for reporting.

As i do not have this device available currently to test i would recommend logging a ticket with our support department so they can check this in detail.

 

[BrenttG]

Hello @BrenttG and thank you for reporting.

As i do not have this device available currently to test i would recommend logging a ticket with our support department so they can check this in detail.

I will take it up with them, however you dont even need an actual device to see this happen, just make an extension, and then on the phone provisioning tab add this device with even a fake mac address and as soon as you save it by hitting OK at the top, the errors start occuring, even if the device has never even touched the server. It seems the template itself that 3CX has, is incorrectly formatted, or has variables that do not exist in use. The issue does not revolve around the hardware device. It is an internal error in 3CX.

 

[complex1]

@BrenttG

What happens if you clear BLF1 field belong to that extension?
Does the error still occur?

 

[BrenttG]

Im hesitant to mess with it atm, as I have manually provisioned the call box and they use it heavily, it is working without using 3CX's template for the moment, it is used outside their shipping/receiveing door to let drivers in and out at a medical facility so i cant just take it offline to test atm.

 

[YiannisH_3CX]

I will take it up with them, however you dont even need an actual device to see this happen, just make an extension, and then on the phone provisioning tab add this device with even a fake mac address and as soon as you save it by hitting OK at the top, the errors start occuring, even if the device has never even touched the server. It seems the template itself that 3CX has, is incorrectly formatted, or has variables that do not exist in use. The issue does not revolve around the hardware device. It is an internal error in 3CX.

I did try that and i am not getting the error. That is why i suggested you should contact our support department. You could also try deleting the template from the server and have the PBX re-download it in case it was corrupted in any way.

 

[YiannisH_3CX]

Scratch my previous reply as i was able to replicate the behaviour. I can only replicate when i use anything else other a speed dial key. If i add a BLF in the first position then the error is generated.
As the guide shows however a speed dial needs to be used in the first BLF key.


Try it when you get a chance and let us know if that resolves the issue.

 

[BrenttG]

Thanks, we are waiting for a second unit in shipping which will be for the front door, when it arrives i will try this, and if it works when time allows i will redo the back door/loading dock.

 

[YiannisH_3CX]

Let us know if you face any more issues.

 

[BrenttG]

will do, the second unit is still stuck in shipping "somewhere"