Description:

URL Calling is Disabled is a error displayed on Polycom phones that means the phone is getting an IP address but is not able to reach the Audian provisioning server to register.

This article will show you how to do the following:

Resolve URL Calling Disabled errors

Method:

Power Cycle The Phone:

This is the #1 fix for most issues.

Unplug the power from the phone.
Wait 10 seconds.
Plug the power back in.

If the reboot doesn't fix the issue follow the steps below.

Verify The IP Address:

Go to Settings.
Select Status.
Select Network.
Select TCP/IP Parameters.
Verify the following.
1. DHCP: Is enabled
2. IP: Has an IP address

If the phone has an IP address and DHCP is enabled follow the steps below.

Move The Device:

When a phone is plugged into a switch and the phone loses it registration due to a power outage, loss of internet, or some kind of network hiccup. The switch will temporary block traffic to the port on the switch to prevent what is called a broadcast storm. Other issues that can cause this problem but the easiest way to resolve the issue is to do the following.
- Move the device to a location where another phone is working.
If the phone still has the same issue the next step is to plug the phone directly into the router.
- This will give the phone a direct connection to the brains of your network thus reducing the chances that some other hardware on the network is the issue.

If the phone still has the same issue then the last thing you can do before getting your IT staff involved is listed below.

Factory Reset:

Follow the Manual Method to factory reset your phone. How To - Factory Reset Polycom Phones
Re-provision the phone to the Audian network using the Web UI or Manual Method. How To - Provision Polycom Phones

If the phone still has the same issue then your going to want to follow the steps below.

Call Your IT:

At this point the network router or firewall could be causing registration issues. You will want to call your IT company to work with Audian to see what could be causing this issue.

Browser not supported