Office Consumer is reader-supported. We may earn an affiliate commission from qualified links on our site.

How to Enable URL Calling on a Polycom Phone (w/Examples) + FAQs

Set feature.urlDialing.enabled to "1" in the phone's configuration (features.cfg, a provisioning file, or an imported XML change file), confirm reg.x.urlDialing.enabled is "1" on the line you want, reboot, then tap the URL soft key in the Dialer and enter the SIP address or IP. As of 2026 the setting costs nothing; it takes one config edit and a restart.

Enabling URL calling on a Polycom (now HP Poly) phone is a configuration change, not a license purchase, and on current firmware the feature is on by default for private and unregistered lines. The reason so many readers hit a wall is that a service provider or a provisioning server has turned it off, and the phone's web page does not always expose the switch, so the fix lives in a config file.

The stakes are practical: without URL dialing, a VVX cannot call another device by IP address or SIP URI. HP Poly's own Edge E parameter guide lists the feature as default-on in PVOS 8.2.1, so a phone that refuses URL calls has been told to.

This article reflects HP Poly documentation and community-verified settings as of October 2026 and covers UC Software and PVOS firmware in use that year. Rules change, so confirm current parameter names before you act.

  • ๐Ÿ“ž What URL calling is, and why the phone shows "URL Calling Disabled" when it is really unregistered
  • ๐Ÿ”ง The exact parameters: feature.urlDialing.enabled, reg.x.urlDialing.enabled and call.urlModeDialing
  • ๐Ÿ—‚๏ธ Three ways to push the change: features.cfg, a hosted custom XML file, or the Web Configuration Utility import
  • ๐Ÿงช Worked examples for a single desk phone, a Genesys Cloud fleet and a FreePBX callback problem
  • โš ๏ธ Seven mistakes that keep the setting from taking, including the shared-line trap

What URL Calling Means on a Poly Phone

URL calling (also called URL dialing or name dialing) lets the phone place a call to a SIP address such as sip:1001@192.168.1.50 instead of a plain phone number. The handset switches its Dialer from numbers to text, so you can type a user name, a domain or a raw IP address. The Polycom VVX 400 user guide puts it in one line: to enter a URL in the Dialer, tap URL, and to go back to digits, tap Number, as shown in the VVX 400 user guide.

The feature is governed by a small set of parameters that HP Poly documents in its parameter reference guides. In the Edge E Series guide for PVOS 8.2.1, feature.urlDialing.enabled is listed with 1 as the default, meaning URL/name dialing is available from private or unregistered lines and unknown callers are identified on the display by their phone's IP address; a value of 0 removes the feature. The same page lists reg.x.urlDialing.enabled, default 1, which turns URL dialing on or off for one SIP registration at a time, according to the HP parameter reference.

Older UC Software carried a second switch. Owners on the HP community forum quote the UCS 4.0.1 administrator guide as saying that with a value of 1, URL/name dialing is available from private lines, and that the feature is never available on a shared line; they also pair feature.urlDialing.enabled in features.cfg with call.urlModeDialing in site.cfg, as described in this HP community thread. Users in the FreePBX community forum name the same two files and parameters, site.cfg for call.urlModeDialing and features.cfg for feature.urlDialing.enabled, in a May 2024 thread.

Who touches this depends on how the phone is managed. A home-office user with one VVX can log into the phone's own web page. An administrator on a hosted platform such as Genesys Cloud, 8x8, Nextiva or RingCentral usually cannot, because the provider's provisioning server rewrites the config at every boot. In that case the change has to ride along in a custom configuration file the provider lets you attach, or the provider has to make it for you.

The consequence of getting it wrong is small but annoying. With the feature off, a tap on a Received Calls entry stored as a SIP URI returns a fast busy or the message "URL Calling is disabled," and intercom calls straight to a door station by IP will not go through. With it on, callers who are not in your directory show up by IP address, which some offices dislike.

Which Situation Applies to You?

Pick your path by who controls the phone's configuration. The parameter is the same in every case; only the delivery method changes.

Your SetupWhere You Make the Change
One VVX or Edge phone you own, no provisioning serverWeb Configuration Utility (Admin login) and an imported XML change file
Phones fed by your own provisioning server (FTP/HTTP)Edit features.cfg (and site.cfg on older UCS), then reboot the phones
Genesys Cloud managed Polycom phonesHosted custom XML file linked under Phones > Base Settings > Network > Provisioning > Custom Configuration Files
Hosted provider (8x8, Nextiva, RingCentral, Zoom) with no custom file optionAsk the provider; a local change is overwritten at the next provisioning check
Phone shows "URL Calling Disabled" on the idle screenThis is a registration or network failure, not a feature setting; fix connectivity first

The last row matters most. Users in the r/VOIP subreddit explain that "URL Calling Disabled" appears when the phone cannot register and the fallback of dialing a SIP URL has also been switched off, so the real problem is a SIP server, DNS or network failure, as one r/VOIP commenter put it. Nextiva's troubleshooting page says the message indicates the device is not connected to a server to make calls and sends you to its provisioning instructions. In its May 2026 article, 8x8 says the error typically points to a local network or DNS failure and lists cable swaps, SIP-ALG and DNS checks.

Step-by-Step: How to Enable URL Calling on a Polycom Phone

Follow these steps in order. No step requires a license, a fee or a support contract. HP Poly does not publish a time estimate for a config change, so the timings below are left open where no source gives one.

Step 1: Confirm the Phone Is Registered

Check the line icon before you touch any parameter. A phone that reads "URL Calling Disabled" on its idle screen is telling you it has no working registration, not that the feature is off. In its Poly error guide, 8x8 recommends swapping the Ethernet port and cable, confirming you can reach the phone's web interface by IP, and checking SIP-ALG and DNS on the router. One Zoom community member reported in January 2024 that every VVX 450 in the office showed the message after the phones dropped from the voice VLAN to the native VLAN, in a Zoom community post. Requirement: network access to the phone. Cost: none.

Step 2: Get Into the Phone

Find the IP address, then log in as Admin. On a VVX, the IP is under Settings > Status > Network > TCP/IP Parameters, per Zoom's Poly provisioning guide. Type that address into a browser on the same network. The VVX 500 administrators' guide addendum says the Admin password is 456 by default and the User password is 123, as stated in the TouchTone copy of the guide. If the page does not load, the web server may be off; Telebroad's guide walks through Settings > Advanced > admin settings > Web Server > Enabled on the handset itself in its VVX web utility article. Requirement: the admin password, which your provider may have changed. Cost: none.

Step 3: Set the Parameters

Set feature.urlDialing.enabled="1", and keep reg.x.urlDialing.enabled="1" for each line that should dial URLs. On a current Edge E phone, HP's parameter reference lists both with 1 as the default, so you are usually undoing an override rather than adding something new, per the PVOS 8.2.1 reference. On older UC Software, owners on the HP community also set call.urlModeDialing in site.cfg alongside the features.cfg parameter, as discussed in the HP community thread.

Write the change as a well-formed XML attribute. HP's guide notes that element names do not matter, only the attribute, so a file like this works:

File LinePurpose
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>XML header
<polycomConfig xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="polycomConfig.xsd">Root element Poly phones expect
<change feature.urlDialing.enabled="1" />Turns URL dialing on globally
<lines reg.1.urlDialing.enabled="1" />Keeps line 1 allowed to dial URLs
</polycomConfig>Close the file

A Poly employee posting as a volunteer on the HP forum reported importing a simple file holding <change feature.urlDialing.enabled="1" />, selecting the line, pressing URL Dial, typing an IP, and hearing the far-end phone ring, tested against UCS 5.3.0.12074, in the same HP community thread. Requirement: Admin access or write access to the provisioning share. Cost: none.

Step 4: Deliver the Change the Right Way

Match the delivery method to who provisions the phone. On a standalone phone, use the Web Configuration Utility's import function to load the XML file, then save and reboot. On your own provisioning server, add the attributes to features.cfg (and site.cfg on old UCS), then reboot the phones so they fetch the files.

On Genesys Cloud, Polycom phones are managed phones that pull their whole configuration at provisioning time, and extra settings go in a static XML custom configuration file hosted on a web server. Users in the Genesys community say the file's URL is linked on individual phones or a phone base setting under Phones > Base Settings > Network > Provisioning > Custom Configuration Files, in a Genesys community post. The same post warns that any dial-plan entry must use dialplan.1.digitmap rather than the default dialplan.digitmap, because Genesys Cloud already provisions the default and it would supersede a custom copy. Requirement: a reachable HTTP server for the file. Cost: none beyond hosting you already have.

Step 5: Test From the Dialer

Place a URL call and a callback from Received Calls. Pick up the handset or press a line key, tap the URL soft key in the Dialer, type sip: followed by the extension and the server IP, and press Dial. Then open Received Calls, choose an entry stored as sip:ext@server, and dial it. If the far end rings both ways, the change took. Requirement: a second SIP device to call. Cost: none.

The Parameters, One by One

Three parameters do the work, and each has its own consequence when mishandled.

feature.urlDialing.enabled

The meaning is simple: 1 lets the phone dial URLs and names from private or unregistered lines, and 0 removes the option entirely. Missing it is the usual cause of a dead URL soft key, and the visible consequence is a Received Calls entry that cannot be redialed. The HP parameter reference also notes the side effect: with the feature on, unknown callers appear by IP address, per the PVOS 8.2.1 reference. A common misconception is that the Web Configuration Utility always shows this toggle; on many providers' builds it does not, which is why the XML import route exists. Next step: set it to 1 and reboot.

reg.x.urlDialing.enabled

This per-line switch, default 1, lets an administrator allow URL dialing on one registration and block it on another. Missing it means a global 1 can still leave a particular line unable to dial URLs if the provider set reg.2.urlDialing.enabled="0". The misconception is that the global parameter wins; the per-line value governs that line. Next step: check every registration you expect to use.

call.urlModeDialing

On older UC Software, owners in both the HP and FreePBX forums pair this site.cfg parameter with the features.cfg one. One HP forum poster set both to 1 on UCS 4.0.1 as the workaround Polycom support gave for a Received Calls bug fixed in UCS 4.0.2, per the HP thread. Users in the FreePBX forum, by contrast, set call.urlModeDialing=0 and feature.urlDialing.enabled=0 so the phone stopped treating sip:202@server entries as URL calls, and the poster reported the callback then worked flawlessly in May 2024, in the FreePBX thread. The lesson is that the value you want depends on the outcome: enable to dial URIs by hand, disable to force number-only callbacks. Next step: decide which behavior your users need before you edit.

A Worked Example: Counting Which Lines Can Dial URLs

A phone with three registrations and one per-line block ends up with two URL-capable lines. Suppose a VVX 450 at a dental office has reg.1, reg.2 and reg.3 configured, feature.urlDialing.enabled="1", and the provider's template includes reg.2.urlDialing.enabled="0" because line 2 is the shared front-desk appearance.

The arithmetic is: 3 registrations – 1 blocked registration = 2 URL-capable lines (lines 1 and 3). Line 2 would be blocked by its per-line value, and owners on the HP forum add that a shared line never offers URL dialing in the first place, so even flipping reg.2.urlDialing.enabled to 1 would not change the count on that shared appearance. If the office later removes the per-line block and makes line 2 private, the count becomes: 3 registrations – 0 blocked = 3 URL-capable lines.

Named Examples From Real Reader Situations

Three illustrative people show how the same parameter solves different problems.

Maria, an office manager, runs a FreePBX server inside the company VLAN with two VVX 410 users working from home. When extension 202 calls 201 and 201 tries to call back from Received Calls, the phone gives a fast busy because the entry reads sip:202@ followed by the server's IP, the exact situation one FreePBX user described in May 2024. Her fix is the site.cfg and features.cfg pair, applied to every phone, followed by a reboot.

Dev, an IT administrator, wants a lobby VVX to ring a door station straight by IP without going through the PBX. CyberData's point-to-point guide for its devices and a VVX has the device dial the phone's IP directly with "Register with a SIP server" turned off, in its point-to-point article. For the phone to call the door station the other way, feature.urlDialing.enabled has to be 1 so the URL soft key appears.

Lena, a Genesys Cloud administrator, cannot edit her Polycom phones' files directly. She hosts a small XML file on an internal web server and links it under Phones > Base Settings > Network > Provisioning > Custom Configuration Files, the location users in the Genesys community name in their dial-plan post. The phones pull it at the next provisioning cycle.

Who Reports the Problem, and What Fixed It

The same message means different things in different offices.

Reader ReportWhat Resolved It
VVX 500 on UCS 4.0.1 showed "URL dialing disabled" on inbound callbacks (HP community)Polycom support called it a known issue fixed in UCS 4.0.2 and suggested enabling URL dialing meanwhile
VVX 410 home workers on FreePBX could not redial from Received Calls (FreePBX forum)Set call.urlModeDialing and feature.urlDialing.enabled in the config files, then rebooted
VVX 450 fleet showed "URL calling is disabled" after dropping off the voice VLAN (Zoom community)A network fix, not a parameter; the message was a symptom of lost registration
Phones on 8x8 flashed "URL calling disabled" for 30 seconds to 5 minutes at a time (Spiceworks)Suspected upstream router and SIP-ALG on the landlord's network

One Spiceworks user supporting a small 8x8 client wrote in December 2019 that calls cut off and the phones showed the message for anywhere between half a minute and five minutes, while the PCs on the same switch stayed online, in that Spiceworks thread. Other members pointed at the landlord's router. Nothing in that thread was a URL-dialing parameter.

Timing and Cost

The change itself is free; the only cost is administrator time, and HP Poly publishes no figure for that. No license, feature key or paid support plan is needed to flip feature.urlDialing.enabled. If your hosted provider has to make the change, their response time is the real schedule, and it varies by provider.

ApproachWhat It Takes
Do it yourself on one phoneAdmin password (default 456 per the VVX 500 admin guide), a browser on the same network, one XML import and a reboot
Do it yourself across a provisioning serverWrite access to features.cfg and site.cfg, a reboot of each phone
Genesys Cloud custom fileA web server to host the XML and the base-setting link
Ask a hosted providerA support ticket; no published fee, timing varies by provider

In a larger registration or VLAN problem, the technician is fixing the network, and the URL-dialing parameter is a footnote.

Mistakes to Avoid

Seven errors account for most "I set it to 1 and nothing changed" reports.

  • Treating "URL Calling Disabled" on the idle screen as a feature setting. It signals a failed registration, so changing parameters wastes time while DNS or the router stays broken, as the r/VOIP and 8x8 pages both explain.
  • Leaving off the quotation marks. One HP forum reply reminded a poster that every value needs quotes, as in feature.urlDialing.enabled="1"; without them the file is ignored.
  • Expecting URL dialing on a shared line. Owners quoting the UCS 4.0.1 guide say it is never available there; the call fails no matter what the global value says.
  • Forgetting the per-line parameter. A provider's reg.x.urlDialing.enabled="0" on one registration survives a global 1.
  • Editing the phone directly when a provisioning server controls it. The next check-in overwrites your change, and on Genesys Cloud the default dialplan.digitmap supersedes a custom one unless you use the .1. form.
  • Skipping the reboot. The phones read features.cfg and site.cfg at boot, so a saved file with no restart does nothing.
  • Enabling it without warning users about IP-address caller ID. HP's parameter reference says unknown callers then appear by IP, and front-desk staff may read that as spam.

Do's and Don'ts

Do these five things.

  • Do check registration first, because every provider page on the error message starts there.
  • Do use the per-line parameter when only one line should dial URLs, so the receptionist's shared line stays clean.
  • Do host a custom XML file on a reachable web server for Genesys Cloud, because that is the supported path for extra settings.
  • Do keep a copy of your change file, because a firmware update or re-provisioning can reset the phone.
  • Do test both a manual URL call and a Received Calls callback, since the two paths failed separately in reader reports.

Avoid these five.

  • Don't hand-edit the live config on a hosted phone and expect it to stick past the next provisioning cycle.
  • Don't use the default dialplan.digitmap key in a Genesys custom file; use dialplan.1.digitmap or your dial plan is ignored.
  • Don't assume disabling URL dialing fixes callbacks everywhere; it worked for the FreePBX user, while an HP forum poster needed it enabled on UCS 4.0.1.
  • Don't run the phone on an old firmware with a known call-list bug; Polycom support told one owner the fix shipped in UCS 4.0.2.
  • Don't skip the test call from Received Calls, since that is the path that failed for the FreePBX and HP forum users.

Pros and Cons of Turning URL Calling On

The feature helps technical offices and can confuse everyone else.

ProsCons
Lets a phone call a door station, intercom or lab device straight by IPUnknown callers show up by IP address, per HP's parameter reference
Makes Received Calls entries stored as SIP URIs dialableUsers can toggle the Dialer into letters by accident, a complaint one r/VOIP commenter raised
Works on unregistered lines, useful for bench testing a phone with no PBXA shared line never gets it, so results differ by line type
Costs nothing; it is a default-on parameterA hosted provider can overwrite your change at every boot
Per-line control lets you enable it only where it helpsOn old UC Software you must edit two files, site.cfg and features.cfg

What to Do Next

  1. Look at the line icon and the idle screen; if it says "URL Calling Disabled," fix registration, cabling, DNS or SIP-ALG before anything else.
  2. Find the phone's IP under Settings > Status > Network and log into the Web Configuration Utility as Admin.
  3. Decide whether you want URL dialing on (manual SIP URI calls) or off (number-only callbacks), based on the FreePBX and HP examples above.
  4. Write a small XML file with feature.urlDialing.enabled="1" and any reg.x.urlDialing.enabled values you need.
  5. Deliver it the right way: import on a standalone phone, features.cfg on your own server, or a hosted custom file on Genesys Cloud.
  6. Reboot, then test a URL call and a Received Calls callback.
  7. If a hosted provider controls the phone and offers no custom-file option, open a ticket and quote the parameter name.

Frequently Asked Questions

Is URL Calling Enabled by Default on Poly Phones?

Yes. HP Poly's Edge E parameter reference for PVOS 8.2.1 lists feature.urlDialing.enabled with 1 as the default, so URL and name dialing is available on private or unregistered lines unless a provider or administrator has set it to 0.

What Does "URL Calling Disabled" Mean on a Polycom Phone?

It means the phone cannot register and URL fallback dialing is also off. Nextiva describes it as the device not being connected to a server, and 8x8 attributes it to local network or DNS failures, so start with cabling, VLAN and DNS in 2026.

Which Parameter Enables URL Dialing on a VVX?

feature.urlDialing.enabled="1". Add reg.x.urlDialing.enabled="1" for each line that should dial URLs, and on older UC Software owners also set call.urlModeDialing in site.cfg, as reported in HP and FreePBX community threads.

Can I Enable URL Calling From the Phone's Web Page?

Yes, by importing a configuration file. A Poly employee posting on the HP forum imported a file containing <change feature.urlDialing.enabled="1" /> through the Web Configuration Utility and then placed a URL call successfully on UCS 5.3.0.

Does URL Dialing Work on a Shared Line?

No. Owners quoting the UCS 4.0.1 administrator guide say URL and name dialing is available from private lines and never from a shared line, so a shared front-desk appearance will not show the URL option.

How Do I Dial a SIP URI Once It Is Enabled?

Tap the URL soft key in the Dialer. The VVX 400 user guide says to tap URL to enter a URL and tap Number to switch back, then type the address such as sip:1001@192.168.1.50 and press Dial.

Why Can't I Call Back From Received Calls on My Polycom?

The entry is stored as a SIP URI and the phone's URL dialing setting is the cause. A FreePBX user in May 2024 saw entries like sip:202@server, changed call.urlModeDialing and feature.urlDialing.enabled in the config files, and reported callbacks then worked.

Does Enabling URL Calling Cost Anything?

No. It is a configuration parameter, not a licensed feature, and HP's parameter reference lists it as a standard default-on setting; the only cost is administrator time or a provider ticket.

How Do I Add the Setting on Genesys Cloud Managed Polycom Phones?

Through a hosted custom XML configuration file. Users in the Genesys community link the file under Phones > Base Settings > Network > Provisioning > Custom Configuration Files, and note that dial-plan lines must use dialplan.1.digitmap.

Will Callers Show as IP Addresses After I Enable It?

Yes, unknown callers will. HP's PVOS 8.2.1 parameter reference states that with feature.urlDialing.enabled at 1, unknown callers are identified on the display by their phone's IP address.

What Is the Default Admin Password to Reach the Settings?

It is 456 on VVX phones. The VVX 500 administrators' guide addendum gives 456 for Admin and 123 for User, though hosted providers often change it, so ask your provider if the default fails.

Should I Disable URL Dialing Instead?

Sometimes. A Poly employee on the HP forum suggested setting it to 0 to keep the call list free of @domain entries, and the FreePBX fix used 0 as well; choose based on whether users need manual SIP URI calls.