Revision as of 00:40, 30 January 2015

Provisioning Polycom VVX with SLA

This document is meant as a guide to configure provisioning, make alterations per the authors preferences, and enable SLA w/ presence to emulate a 'key system'. All testing and development of this guide was on Polycom VVX 400/410 phones.

Provisioning tool

Access the provisioning editor at

Advanced/Provisioning Editor

navigate to

Files/polycom/vvx

{$mac}.cfg

alter the line to add the [PHONE_MAC_ADDRESS]-features.cfg file to initial provisioning. This tells the phone to make use of the features.cfg file where a few settings like parking lots and background images can be configured.

<APPLICATION APP_FILE_PATH="sip.ld" CONFIG_FILES="[PHONE_MAC_ADDRESS]-features.cfg,[PHONE_MAC_ADDRESS]-site.cfg,[PHONE_MAC_ADDRESS]-registration.cfg" MISC_FILES="" LOG_FILE_DIRECTORY="" OVERRIDES_DIRECTORY="" CONTACTS_DIRECTORY="" LICENSE_DIRECTORY="" USER_PROFILES_DIRECTORY="" CALL_LISTS_DIRECTORY="">

{$mac}-registration.cfg

for SLA to work, thirdPartyName needs to be blanked. Also, this needs cleared if you plan to alter the Label as this guide directs. Change the following fields.

reg.{$row.line_number}.label="{$row.display_name}" 
reg.{$row.line_number}.type="shared" 
reg.{$row.line_number}.thirdPartyName=""

features.cfg

we will add some variables so that background images can be configured from 'Default settings' find the following section

<bg.color bg.color.selection="1,1">
 <bg.color.bm bg.color.bm.1.em.name="" bg.color.bm.1.name="" bg.color.bm.2.em.name="" bg.color.bm.2.name="">
  </bg.color.bm>
 </bg.color>

change it to

<bg.color bg.color.selection="2,1">
 <bg.color.bm bg.color.bm.1.em.name="" bg.color.bm.1.name="{$bg1}">
  </bg.color.bm>
 </bg.color>

the setting "2,1" is essentially 'enable' '2', 'image' 1, so defaulting to use bg.color.bm.1.name.

Rewrite Rules

the apply only to nginx, and by default are in /etc/nginx/sites-enabled/fusionpbx

#polycom
rewrite "^.*/provision/000000000000.cfg$" "/app/provison/?mac=$1&file=%7b%24mac%7d.cfg";
rewrite "^.*/provision/(.*).(png|jpg|gif)" "/app/provision/$1.$2";
rewrite "^.*/provision/([A-Fa-f0-9]{12})-features.cfg$" /app/provision/?mac=$1&file=features.cfg;
rewrite "^.*/provision/([A-Fa-f0-9]{12})-sip.cfg$" /app/provision/?mac=$1&file=sip.cfg;
rewrite "^.*/provision/([A-Fa-f0-9]{12})-phone.cfg$" /app/provision/?mac=$1;
rewrite "^.*/provision/([A-Fa-f0-9]{12})-registration.cfg$" "/app/provision/?mac=$1&file=%7b%24mac%7d-registration.cfg";
rewrite "^.*/provision/([A-Fa-f0-9]{12})-site.cfg$"  /app/provision/?mac=$1&file=site.cfg;
rewrite "^.*/provision/([A-Fa-f0-9]{12})-web.cfg$"  /app/provision/?mac=$1&file=web.cfg;

note that this includes a rewrite for features.cfg and for images that will be referenced for the variable {$bg1} from above. The background image will be stored in app/provision/imagename.jpg for example.

Default Settings

navigate to Advanced/Default Settings.

Provisioning

add/update the entries to match

• ideally the bg1 variable could be set by domain for multi-tenancy, haven't figured that one out yet