Failed to Upload Image to Provisioning Server

Provisioning Polycom SIP Phones

The procedure documented in this commodity can be used in any Lync 2010 or 2013 environs to setup a centralized provisioning server for managing Polycom SIP phones running Polycom Unified Communications Software (UCS).

This article is not intended to replace or back-trail any official Polycom documentation.  Instead this procedure lone tin be used to deploy a basic provisioning server in a lab or testing surroundings when evaluating Polycom SIP phones, and much of the guidance contained reflects a non-production scenario.  Also note that some of this guidance differs from instructions found in the official Polycom provisioning guides, almost importantly the guidance to use a large number of parameters which no longer need to be defined for Lync interoperability as of the introduction of the Lync Base Profile.

Background

Traditionally Lync Optimized devices (eastward.g. CX600) receive all of their provisioning information and software update packages directly from a Lync server.  Although Qualified devices (e.g. VVX400) do likewise receive a lot of information in-ring from the Lync Server, UCS devices contain a variety of configurable parameters bachelor exterior of what the Lync Server tin provide itself.  When looking to provision any of these out-of-band features, like Paging, or when dealing with device firmware updates and then it is required to deploy a centralized server to provide this today.

The provisioning server is not a specific production or solution, it is basically just a centrally-accessible file store which contains certain files that the devices are programmed to look for.  The phones will look for specific firmware files to perform an upgrade/downgrade and will download and upload configuration data in XML files.

Polycom UCS devices can employ a variety of different file server platforms to store and manage both firmware packages and configuration files, no boosted third-party software is required.  In this article a basic FTP server will be used but the phones also support the TFTP, HTTP, and HTTPS protocols.

When a manufactory-reset device is first powered on information technology will cheque for specific DHCP Options that may be defined on the network which would provide a path to the provisioning server.  If this information is found then information technology will connect to that file service, authenticate with a pre-configured username and password, and then expect for ane of two specific filenames stored in the root directory.  First the device will look for a configuration filename matching its MAC address (e.1000. 0004f28062d6.cfg) but if that does not exist and then information technology will revert to loading the default master configuration file provided in the UCS distributable packet (e.chiliad. 000000000000.cfg).  Regardless of which file is downloaded information technology will contain a defined parameter which tells the device where to locate firmware packages and what (if any) additional configuration files to look for.  By default the firmware packages are stored at the root of the directory and each private phone model is programmed to look for a specific filename unique to each model (e.g. 3111-46157-001.sip.ld).  Additionally the device tin can besides upload files to the directory to store device-side settings (e.m. ringtone) likewise equally diagnostic and call logs.

Configure Provisioning Server

Specifically Microsoft FTP services in Internet Information Server are used in this instance, running on Windows Server 2012 on a dedicated host.  Whatever standard FTP service (e.g. FileZilla, WarFTP) can be used.  It is not recommended to utilize an existing Lync Server besides as the FTP server, thus the guidance that a split up Windows host exist utilized.

Authentication

Before setting upward the file server it is important to empathize that the UCS firmware is pre-programmed with a default username and countersign which is used during hallmark to the provisioning server.  The default credentials use the aforementioned string for both the username and password and are stored in as case-sensitive so if the FTP server uses case-sensitive username and/or password make certain the upper-case letter and lowercase characters are used correctly. (Traditionally username are not case-sensitive while passwords are, but this may depend on the actual file server production used.)

Username	PlcmSpIp
Countersign	PlcmSpIp

It can be difficult to discern if some of these characters are an i, L, or a i.  The leading 'p' is uppercase, followed by a lowercase '50' 'c' 'm', then an uppercase 's', lowercase 'p', majuscule 'i', lowercase 'p'.  The name comes from the string ' P o l y c o one thousand Due south ound p oint Ip '.

If using a custom set of user credentials is desired then they can be changed manually on each phone prior to provisioning past accessing the Settings > Advanced > Administration Settings > Network Configuration > Provisioning Server carte.

For this lab surround the Windows Agile Directory countersign policy was customized to disable strong password complexity requirements as the default password does not meet the complication of the default Windows Advert password policy.  In a production environment it would not be advisable to alter the password complexity policy simply for this reason, merely a different file server platform which is not AD-integrated could be used which may non accept this same limitation.

• Create a new Active Directory user account (or a local user business relationship in the consequence that the FTP Server is running on a standalone Windows server).

Proper noun Resolution

To facilitate unproblematic access to the FTP site select a dedicated hostname and configure information technology for proper noun resolution.

• Select a fully qualified domain name for the FTP server (e.k. ucs.schertz.name) and then create a new DNS Alias (CNAME) record in the proper zone pointing the physical server Host (A) record where the FTP service is installed and listening.

FTP Service

• Using the directions provided in TechNet to Build an FTP Site on IIS add the FTP Server role, as well every bit any prerequisite IIS Web Service roles in the issue that IIS is not currently installed on the desired server.

• Launch Internet Information Services (IIS) Managing director (inetmgr.exe) and aggrandize the server object.  Right-click Sites and select Add together FTP Site.

• Enter a name for the new FTP site (east.g. ucs) and so select or create a local path to place the root directory of the site (e.g. c:\inetpub\ucs).

• On the Bindings and SSL Settings page disable secure sockets layer past selecting No SSL.

• On the Hallmark and Data folio enable Basic hallmark and and so select Specified Users in the 'Allow access to' drop-down list.  Enter the desired user proper name (eastward.g. PlcmSpIp) in the field below, and enable both Read and Write permissions.

Because the devices need to be able to upload configuration data as well every bit download it and then both Read and Write permissions are required.

FTP Directory

Now that the FTP service has been prepared the root directory needs to exist populated.  This is a elementary process given that every UCS parcel released by Polycom always includes the entire ready of base files needed, so any version of UCS can be used to first populate the directory.

The desired software package tin be downloaded from the Polycom Support site, either directly from the support folio for a specific phone model, or from the Software Release Matrix folio.  Depending on the number of different device models which need to be supported multiple packages may be required, simply the get-go package selected is sufficient to instantiate the directory.

Equally this commodity is using a Polycom VVX 400 for the examples and then the current desired firmware version is 4.1.4.

• From the Polycom support site download the Polycom UC Software four.1.iv release sig dissever.zip package. (It is recommended to e'er download the 'split' package, the 'combined' packages can be ignored).

• Expand the contents of the software packet to the root of the defined FTP directory (east.yard. c:\inetpub\ucs).

The package contains a number of directories and files but nearly of these can exist ignored when dealing with Lync integration, including the directories which shop sample configuration and localization files every bit well as the image and audio files.  The important files are highlighted in the table below.

Name	Clarification
0000000000.cfg	Default Chief SIP Configuration File
*.sip.ld	Firmware files for each unique phone model
sip.ver	Text file which stores the full version number for this package

• To insure that the phones have the appropriate rights to the directory add the desired user account (eastward.g. PlcmSpIp) to the root folder's Access Control List and grant it Modify permissions.

An additional recommendation is to create dedicated directories to shop call and diagnostic logs for each phone.  Past default they would all be written to the root directory which in larger deployments can lead to a lot of files being stored at that place, making it more difficult to weed through and manage files configuration files.

• Create new folders named calls and logs in the root directory.

• Edit the master configuration file (0000000000.cfg) using Notepad or an XML Text Editor of choice and enter the names of the new directories for the LOG_FILE_DIRECTORY and CALL_LISTS_DIRECTORY parameters.

Notice that the APP_FILE_PATH parameter is prepare to sip.ld past default.  This tells the device to look in the root directory for the firmware files.  If desired the firmware files can besides exist moved into a new subdirectory (e.chiliad. \firmware) and so the proper parameter value would be "firmware/sip.ld".  For the purposes of this article, and for about deployments, the firmware files can be left in the default location.

DHCP Configuration

For proper operation of the phones it is required to provide data about the location of critical network resources automatically to the phones via DHCP.  In this example Microsoft DHCP Services are currently configured to paw out IP addresses to any network hosts.  These options can be defined at either the server or scope level.

Provisioning Server Location

When receiving a dynamic IP address on the network the phone will by default look for the location of a provisioning server past get-go checking for the existence of DHCP Pick 160.  In the effect that option 160 is not configured then it will fall back to looking for Choice 66.

The preferred pick 160 is specific to Polycom UCS devices while the secondary option 66 value is commonly shared with other SIP phones too.  Either option tin be used with the UCS phones, thus the configuration of the existing network volition typically drive the option of which to utilize.  In a lab or green-field environs where no other hosts are leveraging option 66 then this can be used and is commonly pre-divers as an available option on most DHCP servers.  If some other devices are already leveraging option 66 so it may be best to utilize option 160 for these phones.

If planning to use option 160 with a DHCP server that does not already have it defined, like Microsoft Windows DHCP, then the option will first need to be created.

• Using DHCP Manager highlight the network type object (e.thou. IPv4) and and so select the Set Predefined Options activity.

• Click Add to create a new choice and then enter a descriptive name (east.g. UCS Kick Server Proper noun).  Alter the Information Blazon to String and and then enter 160 as the Lawmaking value.  If desired add a Description and and so salvage the new selection.

• Configure the Server Options nether the same network telescopic then select option 160 UCS Boot Server Name.  For the information value use the format of <service type>://<fqdn> (e.g. ftp://ucs.schertz.name).

In the event that pick 66 is to be used instead of pick 160 then it can be defined in a Microsoft DHCP server past only configuring the pre-defined pick.

• Using DHCP Manager configure the Server Options under an existing IPv4 scope and and then enable option 066 Boot Server Host Name.  For the information value use the format of <service type>://<fqdn> (e.g. ftp://ucs.schertz.name).

Time Server Location

Providing the location of a fourth dimension server on the network is critical to performance of the phones, so if DHCP Option 42 is non already defined then information technology should exist added to the same scope.

• In the Server Options for the same scope enable 042 NTP Servers and then enter the IP address of at least i host which provides network time services (e.g. a Windows Active Directory Domain Controller).

Time Offset

Although the time server location volition provide the authentic time required to perform authentication and registration processes the device volition display the time in GMT by default.  To show the correct local time on the phone'south brandish the standard time offset DHCP parameter can exist used.

• In the Server Options for the same scope enable 002 Fourth dimension Offset and then enter the desired offset in seconds as a hexadecimal value (eastward.k. 0xffffaba0).

To calculate the correct hexadecimal value the Windows Calculator tin can exist used in Programmer mode.  The following case is used for the Central Time Zone which is GMT -6.

• Enable Programmer Mode (Alt+3) and select December and Qword.  Multiply the number of seconds in one hr (3600) by the desired commencement value (brand sure to include the negative sign if the time zone is earlier than GMT).

3600 x -6 = -21600

• Select Hex to convert the value to hexadecimal.

FFFF FFFF FFFF ABA0

• Select Dword to convert the string from 64 bits to 32 bits.

FFFF ABA0

• Insert the 0x prefix and remove the space for the final value which should be used as the information in Microsoft DHCP.

0xFFFFABA0

Microsoft Vendor Class ID

For the purposes of this article information technology is causeless that the network is not pre-configured to support the Vendor Grade DHCP Option 43 or Selection 120 as documented in the article Configuring Lync Server for Phone Edition Devices.  This option is leveraged by both UCS devices and Lync Phone Edition devices to download an internal, private certification dominance (CA) certificate to institute TLS communications with the Lync Server as well as for supporting Pivot Authentication.  When option 43 is non defined on the network and so the CA certificate must be provided by the provisioning server to support standard NTLM authentication with user credentials, but the Lync Server PIN Authentication characteristic would non be bachelor.

At this point the example network configuration used for this article is simply using options 2, 42, and 160 as shown below.

Validate Configuration

Before moving on with boosted customization make certain that the FTP server is discoverable, bachelor and the desired user credentials are working correctly.

• Using the Windows Command Prompt use the ftp command to connect to the site using the configured FQDN, username, and countersign.

The next step is to connect the phone to the network to brand sure that the provisioning server is available before customizing whatever specific behavior on the phones.  It is recommended to perform a full factory reset of the device first then that the process in this article tin can be followed without any bug created by any unknown settings.  To reset the telephone to factory defaults follow the Factory Reset procedure at the finish of this article.  If the phone'southward electric current firmware does non friction match the version currently stored on the FTP server and so the phone volition automatically download and install that version after the first time it connects.

• Connect the phone to the network and ability it on.  One time the startup process completes (and the firmware update process if triggered) and the main menu appears navigate to the Settings > Status > Platform > Configuration carte to bank check the provisioning server status.

If the configuration was successful and so the telephone should display the correct Boot Server and BootSrv Type options which were provided via DHCP.  Because at that place are no custom settings nevertheless defined then the Config value is blank.  The three default configuration containers (SIP, Web, Local) should display zippo parameters configured.

As previously mentioned the phones will not only endeavour to pull downwards settings just also upload any local settings to the provisioning server directory.  This allows the phones to backup any device-side settings to the central directory by creating 2 new files on the directory the first time they connect (if the files do not already exist).

• To illustrate this process navigate to the Settings > Basic > Ring Type menu and select a different ring (east.g. #10 Beeble).  Within a few seconds the device should save this change up to the provisioning server.  Viewing the FTP service logs should show the device connect to the FTP site and upload a single file.

2013-05-x 16:12:16 192.168.1.100 SCHERTZ\PlcmSpIp 192.168.1.30 21 STOR 0004f28062d6-phone.cfg 226 0 0 c87c3435-b5d5-45ed-9d16-b1b291df24fc /0004f28062d6-phone.cfg

2013-05-10 16:12:46 192.168.ane.100 SCHERTZ\PlcmSpIp 192.168.1.xxx 21 QUIT – 221 0 0 c87c3435-b5d5-45ed-9d16-b1b291df24fc –

• Open the FTP root directory on the server and look for the newly created telephone configuration file starting with the MAC address of the device and the suffix -phone. (east.thou. 0004f28062d6-phone.cfg).

• Open the file in an XML or Text viewer to view the newly defined configuration parameter in the OVERRIDES section.

<?xml version="one.0″ encoding="UTF-8″ standalone="yes"?>
<!– Application SIP PrairieDog 4.1.iv.0296 29-Nov-12 02:40 –>
<!– Created ten-05-2013 eleven:12 –>
<PHONE_CONFIG>
<OVERRIDES np.normal.ringing.calls.tonePattern="ringer10"/>
</PHONE_CONFIG>

During the initial connection to the FTP server the telephone should have as well uploaded separate application and boot log files into the defined log directory. (Or at the root of the FTP directory in the effect that the CALL_LISTS_DIRECTORY parameter was left undefined).  These logs tin can be used to troubleshoot registration problems or other issues if needed.  Exist enlightened that if a dissever log directory is defined the phone may initially create these two logs files in the root directory during the showtime connection, merely after pulling downwards the custom setting will then create new log files in the specified directory.  Information technology is rubber to delete any orphaned log files in the root directories in this case.

Configuring Global Settings

At this signal a basic provisioning server has been established, just null has nevertheless been done to facilitate Lync interoperability with the SIP phones.  As covered in a previous article the UCS four.1 software versions provide a Base Contour configuration which can be used to put the device into Lync mode.  While this can be gear up manually on each phone, it is also possible to ready this centrally.

The instance configuration in this article will prove how to centrally provision 2 phones so that in one case each is powered on from a factory-reset land they will automatically enable Lync style, and populate some or all of the user credentials.  The Polycom UC Administrator's Guide covers many of the configurable parameters and can exist used as a detailed reference for additional customization.

The general approach is to use a combination of files to provide various settings to the phones in an efficient manner.  Any parameters which would be configured on all devices should be defined in a single, shared configuration file (separately from the main configuration file) while device-specific settings would be included in a separate file for each phone.  This commodity will start with using only a single global configuration file and so move on to adding a per-device file to illustrate how either i or both scenarios can exist leveraged.

For editing the configuration files information technology is recommended to utilize an XML editor as information technology is easy to make simple formatting mistakes when using a basic text editor which in turn could forbid the phones from importing the data correctly.  XML Notepad 2007 from Microsoft is used throughout the examples in this article.  (If installing XML Notepad 2007 on Windows Server 2012 make sure to install the .Cyberspace Framework three.five feature showtime which includes the prerequisite 2.0 components.)

Master Configuration File

Bodily device settings are non defined in the master configuration file, instead this file can be configured to point the phone to boosted configuration files which will shop the desired settings.  The names of these files need to be manually defined in the CONFIG_FILES parameter which supports one or more entries in a comma-separated list.

• In the FTP root directory edit the Master Configuration File (000000000000.cfg) and add the device-specific file mask entry following value to the CONFIG_FILE parameter and relieve the file.

CONFIG_FILES="shared.cfg"

Shared Configuration File

Now that a shared configuration file has been defined (shared.cfg) the file needs to be created and populated with the desired parameters.  Basically any parameter where every phone in the surround needs to receive the same value is a candidate for including in this file.  In this case file three things will be addressed that will bear upon every Polycom UCS telephone that is placed on the network.

Most chiefly the Base of operations Profile will be ready to Lync style using the following set of parameters.  Some of the official Polycom provisioning guides do not cover this base profile approach and instead recommend to include a group of well-nigh 30 different parameters for Lync interoperability.  All of those settings are pre-programmed into the Lync Base Profile which was introduced in the 4.1.0 release, then there is no longer any need to define all those other settings.

device.set="1″

device.baseProfile.gear up="1″

device.baseProfile="Lync"

Secondly the root CA certificate is provided to the phone so that information technology will trust the certificate issued to the Lync Server to permit for secure TLS communications.  In the event that the DHCP server is already configured correctly with DHCP Options 43 and 120 and then this parameter tin be omitted from the configuration file.  In that location is no need to pass a private CA certificate in this mode equally UCS will utilize DHCP 43 to locate the Lync Certificate Provisioning service and automatically download the certificate.

sec.TLS.customCaCert.ane="—–BEGIN Document—– MIIDazCCAlOgAwIBAgIQUuNtVsIFbI5GvIJV0CDH3TANBgkqhkiG9w0BAQsFADBI MRQwEgYKC2d5H6ghLGQBGRYEbmFtZTEXMBUGCgmSJomT8ixkARkWB3NjaGVydHox
<<<snipped>>>
w6/GfOTi9Ce/qI7u20OpLZpPmp8HPiZhDPe5WkAe+BdhvmYTrOq6mfq24mfgSysS DPH/HAGcv81DVkOwsNMQrO+lggZAfl7t0BuobPdhvA4ELfF+XIejjoJ2XHueGxIR dfgh8erdcgh28or83/2Bv —–END CERTIFICATE—– "

And finally when DHCP Options 43 and 120 are not divers on the network then Pin Authentication is not available.  By default the telephone displays the Pivot Authentication sign-in screen after the Lync base contour is selected, thus information technology would be ideal to disable the feature on the phone when non bachelor to forestall a poor user experience.  And so if DCHP Options 43 and 120 are configured so this setting tin can likewise be omitted to employ Pin Authentication.  (Currently only the VVX 300 through 600 models support Pivot Auth; any of the SoundPoint or SoundStation devices will ignore this parameter.)

reg.1.auth.usePinCredentials="0″

• To create the customized shared file simply copy the text in the post-obit box and then paste into a new text file.

<?xml version="1.0″ encoding="utf-viii″ standalone="yes"?>

<!–Sample Polycom Shared configuration file for UCS–>

<LYNC>

<device device.set=" 1 " device.baseProfile.prepare=" 1 " device.baseProfile=" Lync "/>

<registration reg.1.auth.usePinCredentials ="0" sec.TLS.customCaCert.1="—PASTE Certificate HERE—" />

</LYNC>

• Save the text file into the root of the FTP directory (e.1000. "c:\inetpub\ucs\shared.cfg")

To locate the certificate trusted by the environment's Lync Server follow the directions in the first section entitled Retrieving the CA Certificate Hash in this previous article.  Disregard the residual of that article equally it is outdated and applies to older UCS firmware versions (4.0) which pre-date the Lync Base Profile.

• Open the document file which was exported and saved in the other commodity and re-create the entire contents of the file to the clipboard, including the Brainstorm and END strings.

So open the shared.cfg file in XML Notepad and then paste the contents of the clipboard direct into the sec.TLS.customCert.1 parameter and relieve the changes to the file.

The completed configuration file should wait similar to the following instance.

Note that the names used in the XML tags (eastward.grand. LYNC, device, registration) have no special meaning and are only provided as a way to organize groups of parameters for piece of cake reading.  Whatever name could be used, or if desired all parameters could exist defined under the chief Lync tag as the file bureaucracy is also not of import.  The phone will simply read in all defined parameters in the file as long as at to the lowest degree one tag is divers.  The device configuration file example in the next department volition use this arroyo to illustrate that either format is acceptable.

Exam Registration

At this point the phones have enough information to annals to Lync Server and it would be possible to simply enter the SIP address and user credentials for a Lync User direct on the phone itself.  Now is a good time to validate that this is functional in the environment before moving on to provisioning any additional account registration information.

• Reboot the phone by either disconnecting the power temporarily or past selecting the Settings > Advanced > Reboot Phone menu option.

After the device completes rebooting it should have picked up the new configuration options in the shared file which will trigger Lync mode then default to the displaying the Sign In menu.

• Using the phone's keypad or on-screen keyboard enter the SIP Address, Agile Directory Domain proper name, User name, and Password for the desired account.  The Domain field can be populated with either the NetBIOS Domain Name (e.g. SCHERTZ) or the DNS Domain Name (due east.chiliad. schertz.name).  In the User field if the user account'south sAMAccountName and Username are not identical in Ad so make sure to use the value that matches the domain name format selected. (For additional details it is suggested to read through the Agreement Active Directory Naming Formats commodity.)

• Once the credentials are entered select the More than button then select the Sign In button.  After a few seconds the telephone should report a successful registration to Lync Server.

Depending on the configuration of the Lync user'due south Line URI field the Line 1 button will either prove the extension, total telephone number, or Display Name of the user account.

• To review the current configuration condition on the phone navigate to the Settings > Status > Platform > Configuration menu to cheque the provisioning server status.

The Config value should evidence the name of the shared configuration file equally well as the number of parameters imported from each source.  The v parameters configured in the shared.cfg file are reflected in this screenshot.

Configuring Per-Device Settings

Moving on with the automatic provisioning process for the phones there are 2 options bachelor for providing credentials to the phone instead of having to enter them manually into the device itself.  One approach can be used to send the full set of credentials to the device, including the password, for a zero-touch administration scenario by defining per-line registration parameters.  In this scenario the credentials cannot be viewed or managed straight on the device and then this is typically intended for devices used in common areas or meetings rooms where the associated Advertising account can be configured with either no password expiry or the key configuration files can exist updated with new password by an ambassador.

The alternative arroyo is to pre-populate all but the password field in the phone'due south actual Login Credential store.  It is not possible to send the countersign using this arroyo but the rest of the credentials can be pre-configured.  This would provide a near-complete provisioning procedure in which the end-user is responsible for entering just their password into the phone to complete the registration process, saving them from having to enter the rest of the data on the phone themselves.

In this section ii unique device configuration files will exist created for two separate phones.  The VVX400 that has been used throughout this article will be configured using the scenario where the Login Credentials are pre-populated, except for the countersign.  This would best match an information worker scenario where a user is assigned their ain phone.  Additionally a SoundPoint IP 331 will exist used to illustrate a completely automated registration procedure which better suits shared or common area scenarios where the user credentials are centrally managed.

Master Configuration File

Just as before the new device files will need to be defined in the primary configuration file so that the phone knows to download it.  The CONFIG_FILES parameter supports multiple entries in a comma-separated list and special masks are understood by the software so that devices can locate files simply intended that that specific device without having to specify the actual device file proper noun for every phone  which would merely non scale well across a handful of devices.

• In the FTP root directory edit the Master Configuration File (000000000000.cfg) and add the device-specific file mask entry of [MACADDRESS]-lync.cfg value to the existing CONFIG_FILE parameter by using a comma separator.

CONFIG_FILES="shared.cfg,[MACADDRESS]-lync.cfg"

The cord [MACADDRESS] is used in the master configuration file to tell a device to look for a file matching the defined pattern with its MAC address in the proper name.  For example the entry '[MACADDRESS]-foo.cfg' would tell a device with the MAC address of 01-02-03-aa-bb-cc to look specifically for a file named '010203aabbcc-foo.cfg'.  Although about any proper noun can be chosen the suffixes of -phone and -web are reserved for special files that the phone manages itself.  The examples throughout this article volition utilize -lync every bit the suffix for device-specific configuration files.

A suffix is required as the file cannot simply exist named with just the MAC address (e.g. 010203aabbcc.cfg) as that filename is reserved for a device-specific master configuration file.  That file would need to basically be a duplicate of the generic 000000000000.cfg file merely with unique master configuration data specific to a device.

Device Configuration Scenario 1

The post-obit set of parameters will be used for the VVX400 device file and will prep-populate the user'due south SIP Accost, user name, and domain name.  Find that although the SIP accost is stored in a line registration parameter (reg.1.*) the remaining parameters will pre-populate the device's Login Credentials store (device.logincred.*).

reg.ane.address=" vvx400@mslync.net"

device.logincred.domain.prepare="1″

device.logincred.domain="SCHERTZ"

device.logincred.user.set="i″

device.logincred.user="vvx400″

• To create the device file simply copy the text in the following box and and then paste into a new text file.

<?xml version="ane.0″ encoding="utf-8″ standalone="yes"?>

<!–UCS Device Configuration file for Lync–>

<LYNC reg.one.address="vvx400@mslync.cyberspace" device.logincred.domain.fix="one" device.logincred.domain="SCHERTZ" device.logincred.user.set="1" device.logincred.user="vvx400"/>

• Relieve the text file into the root of the FTP directory utilizing the desired device's MAC address in the proper noun (e.yard. "c:\inetpub\ucs\0004f28062d6-lync.cfg")

• Open up the new file in XML Notepad and then supercede the instance SIP address and credentials with valid information for the desired Lync user account.

• If using the same phone which was manually registered in the previous step and then reset the telephone to factory defaults again by following the Factory Reset process at the terminate of this article.  This will remove the electric current user and configuration and then automatically reapply all the settings defined on the FTP server.

Test Registration Scenario 1

• Later resetting the telephone view the current configuration condition on the phone by navigating to the Settings > Condition > Platform > Configuration carte du jour.

The Config value will at present show the names of both the shared configuration file and the device configuration file for this phone.  The number of parameters imported from each file is reported equally well.

• Return to the Home Screen on the phone and select More then Sign In.

• The resulting Sign In menu should show the pre-populated user information.  Manually enter the password and then select More > Sign In.  A successful registration should exist reported just as seen in the earlier endeavour.

The obvious benefit of this scenario is that the cease-user was only required to enter their countersign which profoundly reduces the time and complication involved in entering a full set of credentials equally well as having to understand exactly what to enter in terms of domain names.  In the outcome that the password changes on the AD user account the phone will remain connected to Lync and still be able to register even afterward rebooting the phone.  This is because after the initial registration with user credentials the telephone will exist issued a client certificate past the Lync Server and then use TLS-DSK for all subsequent authentication attempts.  This works fifty-fifty in the absence of DHCP 43/120 options which is merely required for Pivot Authentication to exist used as the initial registration process.

Device Configuration Scenario 2

The post-obit set of parameters will be used for the SoundPoint IP 331 device file to fully provision the entire set of user credentials to a phone and trigger an automatic registration.  Using this approach requires that the previously used Login Credential feature of the phone is disabled and the user credentials are stored in the registration parameters for a specific phone line (reg.1.*).

reg.1.auth.useLoginCredentials="0″

reg.1.address=" spip331@mslync.net"

reg.one.auth.domain="SCHERTZ"

reg.1.auth.userId="spip331″

reg.1.auth.countersign="Pass123″

• To create the first device file simply copy the text in the following box and then paste into a new text file.

<?xml version="1.0″ encoding="utf-viii″ standalone="yes"?>

<!–UCS Device Configuration file for Lync–>

<LYNC reg.1.auth.useLoginCredentials="0" reg.1.address="spip331@mslync.net" reg.1.auth.domain="SCHERTZ" reg.ane.auth.userId="spip331" reg.1.auth.countersign="Pass123" />

• Save the text file into the root of the FTP directory utilizing the desired device's MAC address in the name (due east.1000. "c:\inetpub\ucs\0004f2a6af1b-lync.cfg")

• Open the new file in XML Notepad and and then supercede the case SIP accost and credentials with valid information for the desired Lync user account.

• If using the same telephone which was manually registered in the previous step then reset the phone to manufactory defaults over again by following the Manufactory Reset process at the end of this article.  This will once more remove any existing configuration and then automatically reapply all the settings divers on the FTP server.

Test Registration Scenario 2

Because the total gear up of credentials have been supplied in the line registration parameters then the phone should accept automatically registered successfully after resetting.

• The main screen should prove the Lync user'due south telephone number indicating that the registration is active.  To validate this navigate to the Status > Lines > Line Information card.

• The latest configuration status on the telephone can exist confirmed by navigating to the Settings > Status > Platform > Configuration menu to verify the provisioning server status.

The SoundPoint IP models do not currently back up PIN Authentication so the parameter to disable that feature volition non be recognized, resulting in 1 error reported in the shared configuration file.

Managing Firmware Updates

When new firmware versions are published for dissimilar Polycom SIP phones the associated package can exist downloaded and hands added to the provisioning server'southward root directory.  Make sure never to but copy over all the files though as this might overwrite a customized master configuration file and pause the integration; only utilize the firmware files provided in the package.

• Open up the software release packet and extract only the .sip.ld files copying them into the FTP root directory (or wherever the firmware files are stored on the provisioning server if a custom directory was configured).

As long as the firmware file stored on the server is a different version, newer or older, than what the device currently has installed then it will download and update the firmware automatically at the next reboot.

The following table can be used as a reference for the latest recommended versions of each model telephone for Lync interoperability.  The uncompressed file size of each firmware image is also provided as a way to assistance identify which release package an individual file might be from.

Device	Firmware File	4.1.0i	4.1.2b	four.1.4
SoundPoint IP 321	2345-12360-001.sip.ld	three,793 KB
SoundPoint IP 331	2345-12365-001.sip.ld	3,793 KB
SoundPoint IP 335	2345-12375-001.sip.ld	3,793 KB
SoundPoint IP 450	2345-12450-001.sip.ld	four,452 KB
SoundPoint IP 550	2345-12500-001.sip.ld	iii,851 KB
SoundPoint IP 560	2345-12560-001.sip.ld	3,851 KB
SoundPoint IP 650	2345-12600-001.sip.ld	3,851 KB
SoundStation IP 5000	3111-30900-001.sip.ld	4,087 KB
SoundStation Duo	3111-19000-001.sip.ld	4,846 KB
VVX 300	3111-46135-002.sip.ld			50,159 KB
VVX 310	3111-46161-001.sip.ld			50,159 KB
VVX 400	3111-46157-002.sip.ld			50,159 KB
VVX 410	3111-46162-001.sip.ld			50,159 KB
VVX 500	3111-44500-001.sip.ld		58,517 KB
VVX 600	3111-44600-001.sip.ld		58,517 KB

All of the devices listed above are currently qualified for both Lync 2010 and 2013 environments when running on at least the firmware versions indicated.

Nigh Jeff Schertz
Site Administrator

richardyaress.blogspot.com

Source: http://blog.schertz.name/2013/05/provisioning-polycom-sip-phones/

Share this post