06-15-2021 03:43 AM - edited 06-16-2021 01:55 AM
Hi there!
I have noticed that I can’t apply BLF Custom LED Type 1 via XML configuration when provisioning these phones. I believe this may be a bug.
The relevant configuration line is
<Custom_LED_Type ua=“na”>Preset 1</Custom_LED_Type>
When this is put into the configuration, the custom LED type does not apply. However, the phone’s web UI says it is applied.
To get this to work, I have to set the custom LED type back to Default, and then Preset 1 again manually in the web UI.
Anyone has any ideas?
Thanks!
06-16-2021 01:04 AM
Hi there,
What is the firmware being used?
Thanks
Geovani
06-16-2021 01:32 AM
06-16-2021 01:54 AM
Hi Geovani,
I just updated to MPP version 11.3.4 on my 8851 and the issue still persists.
Cheers, Ryan
06-16-2021 02:09 AM
Hi Ryan, this does sound like a bug.
Applying the config via the config file should work regardless.
Are you able to open a TAC case to investigate it?
Thanks
Geovani
06-16-2021 02:20 AM
Hi Geovani,
Unfortunately I do not have an active support contract. Is there another way I can get TAC to look at this?
Thanks, Ryan
06-18-2021 01:37 AM
Hi Ryan,
Let me run a few tests in the lab and see what I can do. It this turns out to be a bug I can file a bug with engineering.
I'll keep you posted.
Geovani
06-18-2021 07:33 AM
Hi Ryan,
I'm not able to reproduce this issue.
I'm using sip88xx.11-3-2MPP0001-609.loads.
When setting the custom LED parameter via XML, it works every time.
How many template files do you have? Can you please check if you have any configuration overlaps?
This is what I'm using as a test:
<?xml version="1.0" encoding="UTF-8"?>
<device xsi:type="axl:XIPPhone" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<flat-profile>
<Custom_LED_Type ua="na">Preset 1</Custom_LED_Type>
</flat-profile>
</device>
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: