The SkySwitch automated provisioning server makes it very easy to customize the behavior and appearance of Polycom devices using overrides that can be applied at the Domain or Device level. Some of the more commonly used overrides are listed on this page.
Polycom Admin Guide
To learn more about Polycom overrides, please consult the Admin Guide for the UC 5 firmware, available here.
To learn more about programming softkeys and enhanced feature keys, please consult the Polycom technical bulletin here.
To make configuration changes from the device keypad it is necessary to enter the Admin mode, which requires the admin password. By default, the Admin password for phones provisioned by the SkySwitch provisioning server is set to be different from the factory default password of '456' (to learn the SkySwitch created password, please contact support). You can supersede this with your own Admin password using the following overrides.
Restart Polycom phone from the Keypad by holding 1,3, and 0 simultaneously.
Block SIP Scanners
The code below can be used to ensure that Polycom phones will only receive calls from the same server that they are registered to.
Enable/Disable Web UI
To Enable or Disable the device's web UI. This is disabled by default.
Enable/Disable Video (for VVX 500/600)
To Enable or Disable the device's video capabilities. Video is enabled by default.
Disable the PC Port (disallow users from connecting devices to the phone's extra ethernet port )
To Disable the device's PC Port.
Line Key Label
By default, each line appearance on the phone will display the User's extension number as configured in the PBX Manager Portal. You can replace this with any text (such as a name) by using the following overrides:
reg.1.label="Jim R" reg.2.label="Kelly P"
Enable Stutter Dialtone for Voicemail
By default, the stutter dial tone is disabled because Polycom phones have visual voicemail indicators. To enable the stutter dial tone for voicemail, use this override.
Directed Call Pickup
Directed call pickup enables users to pick up incoming calls to another phone by dialing the extension of that phone.
Call Pickup Softkey - Extension
Use these overrides to create a Call Pickup softkey that will prompt the user to enter the extension number of any other phone that is ringing. Once the extension is entered, the call session to the other ringing extension will be connected to the User's device. This softkey uses the *35 star code function.
softkey.2.label="Pickup" softkey.2.action="*35$P1N5$$Tinvite$" softkey.2.enable="1" softkey.2.use.idle="1" softkey.2.use.alerting="0" softkey.2.use.dialtone="1" softkey.2.use.hold="1" efk.efkprompt.1.status="1" efk.efkprompt.1.label="Pickup Extension" efk.efkprompt.1.userfeedback="visible" efk.efkprompt.1.type="numeric"
Call Pickup Softkey - Domain
Use these overrides to create a Call Pickup softkey that will automatically answer any other extension that is ringing within the same domain. This softkey uses the *36 star code function.
efk.efklist.1.mname="pudir" efk.efklist.1.status="1" efk.efklist.1.label="pudir" efk.efklist.1.use.idle="1" efk.efklist.1.use.active="1" efk.efklist.1.use.dialtone="1" efk.efklist.1.use.proceeding="1" efk.efklist.1.use.setup="1" efk.efklist.1.action.string="*36" softkey.1.label="PckUp" softkey.1.action="!pudir" softkey.1.enable="1" softkey.1.use.idle="1" softkey.1.use.dialtone="1" softkey.1.use.hold="1"
Use these overrides to create an Intercom softkey that will prompt the user to enter an extension number, and then connect to that extension using the *50 intercom function.
softkey.2.label="Intercom" softkey.2.action="*50$P1N5$$Tinvite$" softkey.2.enable="1" softkey.2.use.idle="1" softkey.2.use.alerting="0" softkey.2.use.dialtone="1" softkey.2.use.hold="1" efk.efkprompt.1.status="1" efk.efkprompt.1.label="Intercom Extension" efk.efkprompt.1.userfeedback="visible" efk.efkprompt.1.type="numeric"
In this example, as shown in the screen captures from a Polycom VVX 400 below, when the "Intercom" softkey is selected, the user will see a prompt with the label "Intercom Extension". This prompt will collect numeric input from the user. The softkey action is "*50$P1N5$$Tinvite$" which means collect up to 5 digits, then initiate a call with the result using a prefix of "*50" (which is the star code for Intercom),.
Intercom Softkey without Call Path
Polycom firmware UC 5.2.0 added new Functionality which enables the Intercom functionality without requiring the support of the switch. This means that the Intercom call will exist only on the LAN, and no Internet bandwidth will be consumed.
feature.enhancedFeatureKeys.enabled="1" softkey.1.precede="1" softkey.1.label="IC-Bob" softkey.1.use.idle="1" softkey.1.enable="1" softkey.1.action="1002$Tintercom$"
Using the above example will add a new Softkey before any other softkey called IC-Bob and dial Extension 1002 Using the $Tintercom$functionality.
The following override will create two page groups; page group 1 is "All Page" and page group 2 is "Sales". Devices that include these override settings will be able to send a page to these two groups.
ptt.pageMode.enable="1" ptt.pageMode.group.1.label="All Page" ptt.pageMode.group.2.label="Sales" feature.nonVolatileRingerVolume.enabled="1" np.normal.ringing.toneVolume.chassis="1000" np.normal.alert.messageWaiting.tonePattern="silent"
In order to receive pages, individual devices must 'subscribe' to one or more page groups. The following override will allow devices to subscribe to the Sales group (group 2).
The following override will allow devices to subscribe to both the Page All group (group 1) and the Sales group (group 2).
Lines Per Key
By default, extensions are configured with a single line appearance on the device. You can change the number of line appearances per extension with the following override.
reg.x.LineKeys="n" (where x is the line number, n is the number of line keys to display)
The image below shows the screen capture of a VVX 400 with a single registration for extension 1002 and the override reg.1.LineKeys="3"
Every Day Examples
#CALL PARKING EXAMPLE
#SPEED DIAL EXAMPLE - Off Net Number
#SPEED DIAL EXAMPLE - Star Code
Calls Per Registration
By default, devices are configured to allow multiple calls per line appearance. You can change the number of calls allowed by the device for each registration with the following override. Note that this limit is applied at the device itself, and is not applied at the switch.
reg.x.callsPerLineKey="n" (where x is the line number, n is the number of calls allowed)
This example will cause any Polycom phone to use 'ringer5' whenever a call is received from a member of the 'Restaurant' department.
voIpProt.SIP.alertInfo.1.class="custom4" voIpProt.SIP.alertInfo.1.value="Restaurant" se.rt.custom4.ringer="ringer5"
For this feature to work, the caller must belong to a Department, and the same Department must be identified in an override on the receiving party's phone.
See Related: Distinctive Ring
In a noisy work environment, end users sometimes complain that the Polycom ringer is not loud enough. The following overrides will increase the ring volume.
np.normal.ringing.calls.tonePattern="ringer15" feature.nonVolatileRingerVolume.enabled="1" np.normal.ringing.toneVolume.chassis="1000"
For this feature to work, the Polycom device must be running firmware version 5.2 or higher.
Softkey to Join a Call to a Fixed Destination (phone based Conference)
This example will create a new Softkey called DCon and will only be displayed (position 1) while on an active call. Pressing this key will automatically dial 123 and await (wc) until the call is connected and then join the calls together. Note that this feature does not use the PBX conference bridge. It is joining two calls directly from your phone.
softkey.1.enable="1" softkey.1.use.active="1" softkey.1.label="DCon" softkey.1.insert="1" softkey.1.action="$FConference$123$Tinvite$$Cwc$$FJoin$"
This override will place a Redial key into the softkey 7 location.
softkey.7.label="Redial" softkey.7.action="$FRedial$" softkey.7.enable="1" softkey.7.use.idle="1" softkey.7.use.hold="1" softkey.7.use.dialtone="1"
It is possible to replace the idle screen on Polycom phones with the image of your choice, using the following override format in the SkySwitch Provisioning Server:
bg.color.VVX300.selection="2,1" bg.color.bm.1.name="http://yourdomain.com/vvx300-background.png" bg.color.VVX400.selection="2,2" bg.color.bm.2.name="http://yourdomain.com/vvx400-background.png" bg.color.VVX500.selection="2,3" bg.color.bm.3.name="http://yourdomain.com/vvx500-background.png" bg.color.VVX600.selection="2,4" bg.color.bm.4.name="http://yourdomain.com/vvx600-background.png"
Background Image Size & Hosting
Note that you must host the images on your own server, and the images must match the size of the device screen.
The resulting image will appear similar to this (as seen on a Polycom VVX 500).
Other SIP Server
It is possible to have a device that is provisioned by the SkySwitch Provisioning Server register to a 3rd-party SIP Server using the overrides below. This example would cause line a second line key to be displayed which is registered to firstname.lastname@example.org.
reg.2.lineKeys="1" reg.2.address="1000" reg.2.label="1000" reg.2.auth.userId="1000" reg.2.auth.password="c72mjQIr" reg.2.displayName="Joe Smith" reg.2.server.1.address="some.otherserver.com" reg.2.server.1.port="5060" reg.2.outboundProxy.address="some.otherserver.com" reg.2.outboundProxy.port="5060"
It is necessary to specify the outbound proxy address - even if it is the same as the server - in order to override the default outbound proxy used by SkySwitch.
This capability is provided as a courtesy by SkySwitch and assumes that at least one registration of the device is maintained to the SkySwitch platform. This capability may be discontinued without warning for Resellers that abuse this privilege.
Configure the VLAN settings on a Polycom phone with these overrides. Replace XX in the following examples with the desired VLAN number.
device.set="1" device.net.vlanId="XX" device.net.vlanId.set="1"
By default, the SkySwitch Provisioning Server will configure devices to use the G.711 codec. In cases where bandwidth is constrained, it is sometimes useful to force devices to use a low bandwidth codec such as G.729 or iLBC.
The following overrides will allow you to specify ILBC as the primary codec priority with G711 as secondary (the lower number denotes a higher priority):
voice.codecPref.iLBC.13_33kbps="1" voice.codecPref.iLBC.15_2kbps="2" voice.codecPref.G711Mu="3" voice.audioProfile.iLBC.13_33kbps.payloadSize="30" voice.audioProfile.iLBC.15_2kbps.payloadSize="20" voice.audioProfile.iLBC.jitterBufferMin="40" voice.audioProfile.iLBC.jitterBufferShrink="500" voice.audioProfile.iLBC.jitterBufferMax="160" voice.audioProfile.iLBC.payloadType="110"
Note that many PSTN origination and termination providers support G.711 only. Therefore, even if you set a different codec as the higher priority, the phones may still fall back to using G.711.
Disable G722 Codec
The following overrides will disable phones from using the G722 codec:
voice.codecPref.G722="0" voice.codecPref.G7221.16kbps="0" voice.codecPref.G7221.24kbps="0" voice.codecPref.G7221.32kbps="0" voice.codecPref.G7221_C.24kbps="0" voice.codecPref.G7221_C.32kbps="0" voice.codecPref.G7221_C.48kbps="0"
Set Call Waiting Tone
By default, call waiting tone is set to null which = beep. In order to disable the Call Waiting tone on a second call the following parameter needs to be changed:
call.callWaiting.ring="silent" or call.callWaiting.ring="ring" or call.callWaiting.ring="beep"
Transfer on Conference Hang up
It's possible to transfer a local conference call to the remaining participants of a call, so they may continue even after the host drops out.
Create Transfer Softkey that Returns to the Idle Screen
The VVX300/310/400/410 have less space on their display to show softkeys and also lack the touchscreen disabilities of the VVX500/600.
It may be therefore of interest, whilst transferring a call, to return to the Phone Idle screen rather than having presented the last caller list.
The below example adds a new Softkey called Trans and automatically returns to the Idle screen (Lines). It also removes the standard Hold and Transfer soft keys.
softkey.1.enable="1" softkey.1.use.active="1" softkey.1.label="Trans" softkey.1.precede="1" softkey.1.action="$FTransfer$$FSoftkey1$" softkey.feature.basicCallManagement.redundant="0"
Customize Polycom Dial Plan
The Dial Plan controls how a phone will respond to keypad input when making a call. The default Dial Plan for SkySwitch auto-provisioned phones is.
It is possible to customize a Dial Plan for a specific device or domain using the following override as an example.
Here are the meanings for the entry In the example above:
[2-8]11T: accepts 211,311...911 followed by the dial timeout
*xxT: accepts 2 digit star codes (*42, etc) followed by the dial timeout
0T: 0 dial for operator
011xxx.T: 011 international followed by at least 4 digits (xxx. will accept digits of any length) followed by a dial timeout
1[2-9]xx[2-9]xxxxxx: an 11 digit NANPA number - no dial timeout since we know no numbers will follow
*xx1[2-9]xx[2-9]xxxxxx: 2 digit star code followed by an 11 digit NANPA number, for example a caller ID block on dialing
xxxxT: a 4 digit extension
The parameter dialplan.digit.timeOut controls how long (in seconds) the device will wait for the last key input before evaluating the string entered.
Feature Key Synchronization for Do Not Disturb (DND) and Call Forward (CF)
By default, Polycom phones will be configured to synchronize the Call Forward and DND functions between the phone and the PBX. This means that if you enable either feature on a handset, the same setting will be applied to the User's Answering Rules on the PBX (and vice-versa).
If you would like to disable this functionality, you can do so with the following overrides. Note that you can use either of these commands individually.
voIpProt.SIP.serverFeatureControl.cf="0" voIpProt.SIP.serverFeatureControl.dnd="0" voIpProt.SIP.serverFeatureControl.localProcessing.dnd="0"
Hide the Do Not Disturb (DND) and/or Call Forward (CF) Softkeys
You can disable the DND and/or the call forwarding softkeys (introduced as a new feature with Polycom firmware version UCS 5.1.1).
Disable DND on the IDLE screen
In order to remove the gap left by this simply add the additional:
Disable call forward on the IDLE screen
the same with the alignment on:
Both of the above still leaves the Option within the menu:
Remove DND Softkey and Menu Option:
The above will remove the Softkey and the Menu Option.
Remove FWD Softkey and Menu Option:
You can combine Option 1 and 2 or Option 3 and 4
Move the Position of a Softkey using Precede
Polycom Softkeys are located at the bottom of the LCD display. The Softkeys displayed will depend on the state of the device, where the following states are possible:
- Idle There are no active calls.
- Active This state starts when a call is connected. It stops when the call stops or changes to another state (like hold or dial tone).
- Alerting (or ringing or incoming proceeding) The phone is ringing.
- Dial tone You can hear a dial tone.
- Proceeding (or outgoing proceeding) This state starts when the phone sends a request to the network. It stops when the call is connected.
- Setup This state starts when the user starts keying in a phone number. This state ends when the Proceeding state starts.
- Hold The call is put on hold locally.
The standard Softkey configuration is as follows:
Idle State Configuration of Softkeys
- New Call
Active State Configuration of Softkeys
- End Call
It is possible to insert a new Softkey before one of the existing Softkeys using the precede override.
softkey.1.action="$FDivert$$FSelect$$FSoftKey2$" softkey.2.action="8500$Tinvite$$Cwaitconnect$$Cpause4$3001$Tdtmf$$Cpause4$0000$Tdtmf$" softkey.1.enable="1" softkey.2.enable="1" softkey.1.label="Test1" softkey.2.label="Test2" softkey.1.use.idle="1" softkey.2.use.idle="1"
If no precede is set:
If precede is set for Softkey 1 only:
If precede is set for Softkey 2 only:
If precede is set for both Softkeys:
Line Key Reassignment
Using the override
enables you to assign each line key a category and an index. This feature is available on all VVX phones and the SoundPoint IP 450, 550, 560, 650, and 670 desktop phones or Expansion Module.
The category specifies the function of the line key and can include:
The category Unassigned will leave that line key blank. The index specifies the order in which the line keys will display on the phone screen.
Using this configuration:
lineKey.reassignment.enabled="1" lineKey.1.category="Line" lineKey.1.index="1" lineKey.5.category="BLF" lineKey.6.category="BLF" lineKey.7.category="BLF" lineKey.8.category="SpeedDial" lineKey.8.index="1"
results in this layout:
Note: lineKey.8.index="1" means that Speed Dial #1 will be used as the speed dial value for line 8.
Using this configuration:
lineKey.reassignment.enabled="1" lineKey.1.category="Line" lineKey.1.index="1" lineKey.5.category="Presence" lineKey.6.category="Presence" lineKey.7.category="Presence"
results in this layout:
Note that lineKey.1.index="1" means that Line #1 will be used as the Line number for line 1.
For more examples, please see this article from Polycom:
Headset (EHS Settings)
The headset mode for the phone’s analog headset jack. 0 - no EHS-compatible headset is attached.
1 - a Jabra EHS-compatible headset is attached.
2 - a Plantronics EHS-compatible headset is attached.
3 - a Sennheiser EHS-compatible headset is attached.
Power Saving Mode
The power-saving feature automatically turns off the phone’s LCD display when not in use. When a phone is in use during Off Hours it will display the text "Off Hours Mode" in the top right section of the LCD. It is possible to disable or adjust the operation of power saving mode using the overrides in this section.
This feature is disabled by default on the VVX 300, 310, 400, and 410, and enabled by default on the VVX 500, 600, and1500. The parameters "powerSaving.userDetectionSensitivity.*" listed in the table below are supported only on the VVX 1500 phones.
|powerSaving.enable||0 or 1||VVX 300, 310=0|
VVX 400, 410=0
VVX 500, 600, and 1500=1
|If 0, the LCD power saving feature is disabled. If 1, the feature is enabled. The power-saving feature is disabled by|
default on the VVX 300, 310, 400, and 410, and is enabled by default on the VVX 500, 600, and 1500.
Note that when the phone is in power-saving mode, the LED Message Waiting Indicator (MWI) flashes. To disable
the MWI LED when the phone is in power saving mode, set the parameter
ind.pattern.powerSaving.step.1.state.x to 0 where x=your phone’s model. For example, enter the
parameter as ind.pattern.powerSaving.step.1.state.VVX500 to disable the MWI for your VVX 500
|powerSaving.idleTimeout.offHours||1 - 10||1||The number of minutes to wait while the phone is idle during off hours before activating power saving.|
|powerSaving.idleTimeout.officeHours||1 - 600 minutes||480, VVX 1500=10|
The number of minutes to wait while the phone is idle during office hours before activating power saving. Note that the default time for VVX 300, 310, 400, 410, 500, and 600 is 480 minutes. The default time for the VVX 1500 is 10 minutes.
|powerSaving.idleTimeout.userInputExtension||1 - 20||10||The minimum number of minutes to wait while the phone is idle—after using the phone—before activating power saving.|
|0 to 24|
0 to 24
0 to 24
0 to 24
0 to 24
0 to 24
0 to 24
|The duration of the day’s office hours.|
|powerSaving.officeHours.startHour.xxx||0 to 23||7||The starting hour for the day’s office hours, where xxx is one of monday, tuesday, wednesday, thursday,|
friday, saturday, and sunday (refer to powerSaving.officeHours.duration for an example).
|powerSaving.userDetectionSensitivity.offHours||0 to 10||2||Available on the VVX 1500 only. The sensitivity used to detect the presence of the phone's user during off hours. 10 is the most sensitive. If set to 0, this feature is disabled. The default value was chosen for good performance in a typical office environment and is biased for difficult detection during off hours.|
|powerSaving.userDetectionSensitivity.officeHours||0 to 10||7||Available on the VVX 1500 only. The sensitivity used to detect the presence of the phone's user during office hours. 10 is the most sensitive. If set to 0, this feature is disabled. The default value was chosen for good performance in a typical office environment and is biased for easy detection during office hours.|
Polycom Desktop Connector (For Windows PCs)
The Desktop Connector is a program that will connect your Polycom phone to your Windows PC with the application installed.
You can read more and download the desktop connector at the following website http://www.polycom.com/products-services/voice/applications/desktop-connector.html
apps.ucdesktop.adminEnabled="1" apps.ucdesktop.DesktopUserName="computeruserid" apps.ucdesktop.enabled="1" apps.ucdesktop.orientation="Left" apps.ucdesktop.ServerAddress="192.168.10.100"
ServerAddress = IP or name of the workstation that has the Polycom Desktop Connector software installed Orientation = which side of the monitor is the phone on. (you can use your mouse to click on stuff on the phone)
Capture Network Traffic Directly from a Polycom Phone
Polycom firmware version UCS 5.1.1 officially added a remote packet capture option to the phone in order to troubleshoot issue and provide wireshark traces if required.
The below override parameters will activate the feature on the Phone.
The UCS 5.1.0 Admin Guide describes this on page 170 in the Remote Packet Capture for Logs section.
- To start using this feature please download Wireshark from => here<=
- Start Wireshark after the installation and select the Capture Interface Options
- Start Wireshark after the installation and select the Capture Interface Options
- Manage Interfaces => Remote Interfaces => Add
- IP Address of the phone
Password: MAC Address of the phone in lower case and no colon ( : )
- Once OK is pressed the interface should show up
- Leave this menu via cancel
- You are then able to select this new Interface
- If an error message in regards the Buffer appears please click on OK
View all Supported Overrides
It is possible to view all supported Polycom overrides by following these steps:
- Browse to the Polycom Default page in the SkySwitch NDP UI
- Select the "Phone Options" link
- The resulting page will show all the supported overrides
Migrating Polycom's to SkySwitch
If you are using your own provisioning server for Polycom phones; you can simply replace the content of your configuration files to migrate over to SkySwitch. See the codeblock below or download this file.
<PHONE_CONFIG> <OVERRIDES/> <DEVICE_SETTINGS device.set="1" device.dhcp.dhcpVlanDiscUseOpt.set="1" device.dhcp.dhcpVlanDiscUseOpt="Fixed" device.dhcp.dhcpVlanDiscOpt.set="1" device.dhcp.dhcpVlanDiscOpt="129" device.dhcp.bootSrvUseOpt.set="1" device.dhcp.bootSrvUseOpt="Static" device.dhcp.bootSrvOpt.set="1" device.dhcp.bootSrvOpt="160" device.dhcp.bootSrvOptType.set="1" device.dhcp.bootSrvOptType="String" device.dhcp.option60Type.set="1" device.dhcp.option60Type="ASCII" device.prov.serverType.set="1" device.prov.serverType="HTTP" device.prov.serverName.set="1" device.prov.serverName="sipcfg.io/cfg" device.prov.user.set="1" device.prov.redunAttemptLimit.set="1" device.prov.redunAttemptLimit="3" device.prov.redunInterAttemptDelay.set="1" device.prov.redunInterAttemptDelay="1" device.prov.maxRedunServers.set="1" device.prov.maxRedunServers="8" device.prov.networkEnvironment.set="1" device.prov.networkEnvironment="1" device.prov.tagSerialNo.set="1" device.prov.tagSerialNo="0" device.dns.serverAddress="22.214.171.124" device.dns.altSrvAddress.set="1" device.dns.altSrvAddress="126.96.36.199" /> <CONFIG_FILES device.auth.localAdminPassword.set="1" device.prov.serverName="sipcfg.io/cfg" device.prov.serverName.set="1" device.prov.password.set="1" device.prov.user.set="1" device.prov.user="your-provisioning-username" device.dhcp.bootSrvUseOpt.set="1" device.dhcp.bootSrvUseOpt="Static" device.prov.serverType.set="1" device.prov.serverType="HTTP" device.prov.password="649" device.set="1" /> </PHONE_CONFIG>