Cisco SX20 Error Provisioning Status

[Francis Brown]

Hello,

I'm having a problem with a Cisco SX20 with receiving the following error message.

Current software version is TC7.1.1 and we are trying to update the codec to version TC7.2.1 however each time we try it seems always fail.  The only error to why its failing is the above error message.  Even though the error says provisioning failed, everything is working fine.  Its registered to VCS via SIP & H.323.  Able to place and receive calls with no problems.

Has anyone seen this error and know how to fix it?

[Teck Chye Tang]

Hi,

If you are not doing any provisioning, just turn it off either via API as follows:

xConfiguration Provisioning Mode: off

or via the web interface : Configuration>System Configuration>Provisioning>Mode

If you are doing provisioning, that check that your configuration for the provisioning is correct.

Then you should see the error message gone.

Regards,

Tang

[Wayne DeNardi]

As above, you need to set your provisioning status on the endpoint to something that is correct to get rid of that error message.  What is it currently set to?  You may find you need to set it to Off (as suggested above if you're not using provisioning), or to "TMS" or "VCS" if you are doing provisioning in your enviromnet through your TMS (if you have it) or your VCS.

This message should not stop your device from working if all the other settings are correct for H.323 and/or SIP, nor should it affect your abilty to upgrade the device to a newer software release.  If you're having upgrade issues, the problem is likely something else.

Wayne
--
Please remember to rate responses and to mark your question as answered if appropriate.

[Darin Walker]

I run into provisioning errors only when the incorrect mode is selected (TMS, VCS, CallWay, CUCM, Auto, or Edge).  For example if I were registered to VCS and migrated an endpoint to CUCM I would want to flip the switch from VCS to CUCM.  I've also ran into random issues with endpoints registered to CUCM where the configuration on the local endpoint doesn't match was the CUCM registration page.  I think this will get ironed out with endpoint software, TMS, and CUCM communicating amongst each other, any and all changes (being able to make a changes on any of those systems and all appliances being updated that the change was made).  The only way I have seen how to correct this is performing a factory reset of the endpoint and allowing the endpoint to download it's config file from CUCM or deleting the CTL/ITL on the endpoint GUI.