Speed dials are displaying unavailable 'red x' symbol

[Damocles]

Hello everryone,

I am responsible for a number of VVX400 and VXX500 phones and have been preparing for an system wide upgrade to UC 5.8.1.7278. During my testing I have run into and issue that I require some assistance with. The phones are configured with a variety of BLFs and speed dials, after the update the speed dials are displaying a red x that is similar to the BLF unavailable symbol. I have viewed the configuration files on the individual phones and our provisioning server and have been unable to locate the cause of this. I suspect that there is just a configuration option that needs alteration, perhaps related to EFKs? Any assistance regarding this matter would be appreciated.

Thank you for any assistance.

[SteffenBaierUK]

Hello @Damocles,

welcome to the Polycom Community.

Both the community's Must Read First and the community's FAQ reference the basic minimum information a new or follow up post should contain.

This ensures the questions having to be asked are limited and any new or follow up post contains the right amount of details to ensure any voluntary participant within the community does not spend additional time chasing basic information.

As a reminder the basic information asked for:

• Provide the exact Software Version of your Phone
• Provide the Phone Model
• Provide the Call Platform (aka openSIP,Skype for Business Online, Skype for Business on Premise, Lync)
• Additional Polycom Infrastructure (RPRM,PDMS or BToE)
• If applicable provide a backup of the phone in question

UC Software 4.0.0 or later via the Web Interface Utilities > Phone Backup & Restore > Phone Backup > Phone Backup

• If possible provide a Log and either attach them or use the Code Tag.Consult the Troubleshooting Section found within the FAQ if applicable
• If possible provide the MAC Address or Serial of the device
• Provide details if the issue is a day 1 issue or only happened after an upgrade or any other relevant details

Whilst providing some of these details may not directly impact any possible answer the community can provide, it does enable Polycom to have an overview of the current software used. In addition other details allow us to check logs or look up a potential support partners if an issue needs to come into support. It also enables us to verify the entitlement for using features.

Please ensure you always check the FAQ's and/or utilize the community search before posting any new topics or follow up post’s.

Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier

Polycom Global Services

[Damocles]

Thank you for your response Steffen, I have included the requested information below.

The phone I am testing with is running UC software version 5.8.1.7278 and updater version 5.9.6.8818.

The specific testing phone I am using is a VVX400, however this phenomenon has also be obvserved on VVX500 series devices.  Seeing this leads me to believe it is a configuration issue that may be caused or perhaps resolved when we generate new configuration files.

The phones are succsfully registering back to our PBX via SIP and all inbound/outbound calls transit this connection.

This deployment does not utilize any other Polycom infrastructure aside from individaul stations.

I have attached a backup of the testing station as requested.

As requested I have attached a log file recording the station from reboot at the debug level logging.

The testing phone has a MAC address of 00:04:F2:67:3F:B9.

As mentioned above the issue is occuring only after an upgrade from various UC version 4 installs to UC version 5.8.1.7278, it has also be observed that this occurs whenever upgrading to UC 5 or higher.

Thank you for any assistance, it is much appreciated.

[SteffenBaierUK]

Hello @Damocles,

I suggest you clear up your configuration:

000023.881|cfg  |4|00|Prm|Configuration file(s) statistics: 100 parameters were invalid and could not be interpreted.
000023.881|cfg  |4|00|Prm|Configuration file(s) statistics: 1 parameter values were used but were out of range. 1 were invalid and ignored.

and

1031124144|cfg  |4|00|Prm|Config/features.cfg: Unknown parameter "bg.hiRes.color.selection" found, ignoring.
1031124144|cfg  |4|00|Prm|Config/features.cfg: Unknown parameter "bg.hiRes.color.bm.1.em.name" found, ignoring.
1031124144|cfg  |4|00|Prm|Config/features.cfg: Unknown parameter "bg.hiRes.color.bm.1.name" found, ignoring.
1031124144|cfg  |4|00|Prm|Config/features.cfg: Unknown parameter "bg.hiRes.color.bm.2.em.name" found, ignoring.
1031124144|cfg  |4|00|Prm|Config/features.cfg: Unknown parameter "bg.hiRes.color.bm.2.name" found, ignoring.
1031124144|cfg  |4|00|Prm|Config/features.cfg: Unknown parameter "bg.hiRes.color.bm.3.em.name" found, ignoring.
1031124144|cfg  |4|00|Prm|Config/features.cfg: Unknown parameter "bg.hiRes.color.bm.3.name" found, ignoring.
1031124144|cfg  |4|00|Prm|Config/features.cfg: Unknown parameter "bg.hiRes.color.bm.4.em.name" found, ignoring.
1031124144|cfg  |4|00|Prm|Config/features.cfg: Unknown parameter "bg.hiRes.color.bm.4.name" found, ignoring.
1031124144|cfg  |4|00|Prm|Config/features.cfg: Unknown parameter "bg.hiRes.color.bm.5.em.name" found, ignoring.
1031124144|cfg  |4|00|Prm|Config/features.cfg: Unknown parameter "bg.hiRes.color.bm.5.name" found, ignoring.
1031124144|cfg  |4|00|Prm|Config/features.cfg: Unknown parameter "bg.hiRes.color.bm.6.em.name" found, ignoring.
1031124144|cfg  |4|00|Prm|Config/features.cfg: Unknown parameter "bg.hiRes.color.bm.6.name" found, ignoring.
1031124144|cfg  |4|00|Prm|Config/features.cfg: Unknown parameter "bg.hiRes.color.pat.solid.1.blue" found, ignoring.
1031124144|cfg  |4|00|Prm|Config/features.cfg: Unknown parameter "bg.hiRes.color.pat.solid.1.green" found, ignoring.
1031124144|cfg  |4|00|Prm|Config/features.cfg: Unknown parameter "bg.hiRes.color.pat.solid.1.name" found, ignoring.
1031124144|cfg  |4|00|Prm|Config/features.cfg: Unknown parameter "bg.hiRes.color.pat.solid.1.red" found, ignoring.
1031124144|cfg  |4|00|Prm|Config/features.cfg: Unknown parameter "bg.hiRes.color.pat.solid.2.blue" found, ignoring.
1031124144|cfg  |4|00|Prm|Config/features.cfg: Unknown parameter "bg.hiRes.color.pat.solid.2.green" found, ignoring.
1031124144|cfg  |4|00|Prm|Config/features.cfg: Unknown parameter "bg.hiRes.color.pat.solid.2.name" found, ignoring.
1031124144|cfg  |4|00|Prm|Config/features.cfg: Too many unknown parameters have been found; further errors will be logged at level 1.
1031124144|cfg  |*|00|Prm|Config/features.cfg: Value 9999 for configuration parameter dir.local.contacts.maxNum is too large, using 500, the maximum allowed
1031124144|cfg  |*|00|Prm|Config/features.cfg: Value "" for configuration parameter softkey.2.insert is invalid, ignoring

Other community members can try afterwards to help you but if this still fails your next step is your Reseller.

In order to raise a support ticket you need to work with your Polycom reseller as they need to do this for you.

End Customers are unable to open a ticket directly with Polycom support.

For the unit reported this was IMAGO GROUP which sold this back in 17/04/2014

The unit is no longer within warranty please be prepared to Pay Per Incident / PPI. This is all outlined in detail here

Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier

Polycom Global Services