Polycom - Common Overrides

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) 

Distinctive Ring

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 a more detailed explanation of how to do distinctive ring: see here

Ring Volume

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$" 

 

Redial Key

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"

Background Image

It is possible to replace the idle screen on Polycom phones with the image of your choice, using the following override format:

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"

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.

Phone Model	Optimal background image size (in pixels)
SoundPoint IP 450	250 x 116
SoundPoint IP 550, 560, 650, and 670	320 x 160
SoundPoint IP 650 and 670 Expansion Modules	160 x 320
VVX 250 business IP phone	320 x 240
VVX 300 series business media phones	208 x 104 (Grayscale)
VVX 350 business IP phone	320 x 240
VVX 400 series business media phones	320 x 240
VVX 450 business IP phone	480 x 272
VVX 500 series business media phones	320 x 240
VVX 600 series business media phones	480 x 272
VVX 1500 business media phones	800 x 480
VVX Color Expansion Module	272 x 480
VVX EM50 expansion module	480 x 800
CX5500	480 x 272

 

The resulting image will appear similar to this (as seen on a Polycom VVX 500).

VLAN

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"

Setting SIP as Primary of the Reverse Name Lookup

Typically when the Builder is enabled, it will push the directory for all contacts which may be overwriting the caller's name that appears if a match to an extension is found. To ensure that SIP is the primary source of the caller's name to appear then you may add the following override.

up.rnl.priority="SIP,local,Outlook,ABS"

Preferred Codec

By default, the 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"

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.

This feature is enabled by default. The override shown below will enable the feature, "0" is used to disable it.

call.transferOnConferenceEnd= "1" 

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"

Pressing the EXIT key will allow you to view the Last Caller screen.

The Dial Plan controls how a phone will respond to keypad input when making a call. The default Dial Plan for auto-provisioned phones is.

0T|011xxx.T|[0-1][1-9]xxxxxxxxx|[0-1][0]xxxxxxxxxxxx|[2-9]xxxxxxxxx|[2-9]xxxT|**x.T|+x.T

It is possible to customize a Dial Plan for a specific device or domain using the following override as an example.

dialplan.digitmap="[2-9]11T|*xxT|0T|011xxx.T|1[2-9]xx[2-9]xxxxxx|*xx1[2-9]xx[2-9]xxxxxx|[2-9]xx[2-9]xxxxxx|*xx[2-9]xx[2-9]xxxxxx|[2-9]xxxxxxT|*xx[2-9]xxxxxxT|xxxxT|xxxT" 
dialplan.digitmap.timeOut="3|3|3|3|3|3|3|3|3|3|3|3"

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.

voIpProt.SIP.serverFeatureControl.cf="0" 
voIpProt.SIP.serverFeatureControl.dnd="0" 
voIpProt.SIP.serverFeatureControl.localProcessing.dnd="0"

You can disable the DND and/or the call forwarding softkeys (introduced as a new feature with Polycom firmware version UCS 5.1.1).

Option 1:

Disable DND on the IDLE screen

 

feature.enhancedFeatureKeys.enabled="1" 
softkey.feature.doNotDisturb="0"

In order to remove the gap left by this simply add the additional:

efk.softkey.alignleft="1" 

Option 2:

 Disable call forward on the IDLE screen

softkey.feature.forward="0"

the same with the alignment on:

efk.softkey.alignleft="1"

Both of the above still leaves the Option within the menu:

Option 3:

Remove DND Softkey and Menu Option:

feature.doNotDisturb.enable="0"

The above will remove the Softkey and the Menu Option.

 

Option 4:

Remove FWD Softkey and Menu Option:

feature.forward.enable="0"

You can combine Option 1 and 2 or Option 3 and 4

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:

softkey.1.precede="1"

If precede is set for Softkey 2 only:

softkey.2.precede="1"

If precede is set for both Softkeys:

softkey.1.precede="1" 
softkey.2.precede="1"

lineKey.reassignment.enabled="1"

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"

lineKey.reassignment.enabled="1"  
lineKey.1.category="Line" 
lineKey.1.index="1" 
lineKey.5.category="Presence" 
lineKey.6.category="Presence" 
lineKey.7.category="Presence"

up.analogHeadsetOption="0"

The Desktop Connector is a program that will connect your Polycom phone to your Windows PC with the application installed.

apps.ucdesktop.adminEnabled="1" 
apps.ucdesktop.DesktopUserName="computeruserid" 
apps.ucdesktop.enabled="1" 
apps.ucdesktop.orientation="Left" 
apps.ucdesktop.ServerAddress="192.168.10.100" 

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.

diags.pcap.enabled="1" 
diags.pcap.remote.enabled="1"

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
    
• Manage Interfaces => Remote Interfaces => Add
  
  
• IP Address of the phone
  Port: 2002
  Username: Polycom
  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