How To Register Polycom Vvx 410 Server 1 To Freepbx 14

Provisioning Polycom SIP Phones

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

This article is not intended to supplant or accompany any official Polycom documentation. Instead this process alone tin be used to deploy a basic provisioning server in a lab or testing environment when evaluating Polycom SIP phones, and much of the guidance independent reflects a non-production scenario. Also note that some of this guidance differs from instructions plant in the official Polycom provisioning guides, almost importantly the guidance to use a large number of parameters which no longer demand to be defined for Lync interoperability as of the introduction of the Lync Base of operations Profile.

Background

Traditionally Lync Optimized devices (eastward.k. CX600) receive all of their provisioning information and software update packages directly from a Lync server. Although Qualified devices (eastward.thou. VVX400) do too receive a lot of information in-band from the Lync Server, UCS devices contain a diverseness of configurable parameters available exterior of what the Lync Server tin can provide itself. When looking to provision any of these out-of-band features, like Paging, or when dealing with device firmware updates and so information technology 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 sure files that the devices are programmed to look for. The phones volition look for specific firmware files to perform an upgrade/downgrade and will download and upload configuration data in XML files.

Polycom UCS devices can utilize a variety of different file server platforms to store and manage both firmware packages and configuration files, no additional third-political party software is required. In this article a basic FTP server volition be used merely the phones besides support the TFTP, HTTP, and HTTPS protocols.

When a manufacturing plant-reset device is first powered on it volition check 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, so wait for 1 of two specific filenames stored in the root directory. Outset the device will look for a configuration filename matching its MAC address (east.g. 0004f28062d6.cfg) but if that does not be and then it volition revert to loading the default master configuration file provided in the UCS distributable parcel (e.g. 000000000000.cfg). Regardless of which file is downloaded it will incorporate 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 (east.m. 3111-46157-001.sip.ld). Additionally the device can also upload files to the directory to store device-side settings (due east.g. ringtone) as well as diagnostic and telephone call logs.

Configure Provisioning Server

Specifically Microsoft FTP services in Internet Information Server are used in this example, running on Windows Server 2012 on a dedicated host. Any standard FTP service (e.g. FileZilla, WarFTP) can exist used. It is not recommended to apply an existing Lync Server also every bit the FTP server, thus the guidance that a separate Windows host be utilized.

Authentication

Earlier setting up the file server it is important to sympathise 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 utilise 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 countersign make certain the uppercase and lowercase characters are used correctly. (Traditionally username are non case-sensitive while passwords are, but this may depend on the bodily file server product used.)

Username PlcmSpIp

Password PlcmSpIp

It can be difficult to discern if some of these characters are an i, L, or a 1. The leading 'p' is uppercase, followed by a lowercase 'L' 'c' '1000', then an capital 's', lowercase 'p', uppercase 'i', lowercase 'p'. The proper noun comes from the cord ' P o fifty y c o g Due south ound p oint Ip '.

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

For this lab environment the Windows Agile Directory password policy was customized to disable strong password complexity requirements as the default password does not run into the complexity of the default Windows AD password policy. In a production environs it would not exist advisable to alter the countersign complexity policy simply for this reason, just a unlike file server platform which is not AD-integrated could be used which may non take this same limitation.

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

Proper name Resolution

To facilitate simple access to the FTP site select a dedicated hostname and configure it for name resolution.

Select a fully qualified domain proper name for the FTP server (e.g. ucs.schertz.name) and and so create a new DNS Allonym (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 as any prerequisite IIS Web Service roles in the issue that IIS is not currently installed on the desired server.

Launch Net Data Services (IIS) Managing director (inetmgr.exe) and expand the server object. Right-click Sites and select Add together FTP Site.

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

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

On the Authentication and Information page enable Basic authentication and and then select Specified Users in the 'Allow access to' drop-downward list. Enter the desired user proper name (due east.g. PlcmSpIp) in the field below, and enable both Read and Write permissions.

Considering the devices demand to be able to upload configuration data as well as download information technology 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 unproblematic process given that every UCS packet released past Polycom ever includes the unabridged set of base of operations files needed, so any version of UCS tin can be used to showtime populate the directory.

The desired software package can be downloaded from the Polycom Support site, either directly from the support page for a specific telephone model, or from the Software Release Matrix page. Depending on the number of different device models which need to be supported multiple packages may be required, but the first parcel selected is sufficient to instantiate the directory.

As this commodity is using a Polycom VVX 400 for the examples then the current desired firmware version is iv.1.4.

From the Polycom support site download the Polycom UC Software iv.ane.4 release sig separate.zip package. (It is recommended to always download the 'split' package, the 'combined' packages can exist ignored).

Aggrandize the contents of the software packet to the root of the defined FTP directory (e.thousand. c:\inetpub\ucs).

The package contains a number of directories and files but most of these tin can be ignored when dealing with Lync integration, including the directories which store sample configuration and localization files equally well equally the image and audio files. The important files are highlighted in the table beneath.

Name Description

0000000000.cfg Default Master 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 (e.g. PlcmSpIp) to the root folder's Admission Control List and grant information technology Change permissions.

An additional recommendation is to create dedicated directories to store phone call and diagnostic logs for each phone. By default they would all be written to the root directory which in larger deployments tin lead to a lot of files existence stored at that place, making information technology more than difficult to weed through and manage files configuration files.

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

Edit the principal configuration file (0000000000.cfg) using Notepad or an XML Text Editor of option 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 set to sip.ld by default. This tells the device to await in the root directory for the firmware files. If desired the firmware files can also be moved into a new subdirectory (e.1000. \firmware) and then the proper parameter value would exist "firmware/sip.ld". For the purposes of this article, and for most deployments, the firmware files tin be left in the default location.

DHCP Configuration

For proper operation of the phones it is required to provide information about the location of critical network resources automatically to the phones via DHCP. In this case Microsoft DHCP Services are currently configured to hand out IP addresses to whatsoever network hosts. These options tin 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 by beginning checking for the beingness of DHCP Choice 160. In the result that option 160 is not configured then it will fall back to looking for Option 66.

The preferred option 160 is specific to Polycom UCS devices while the secondary selection 66 value is commonly shared with other SIP phones equally well. Either option can be used with the UCS phones, thus the configuration of the existing network volition typically bulldoze the choice of which to utilize. In a lab or dark-green-field surround where no other hosts are leveraging option 66 and so this can be used and is commonly pre-defined as an available option on near DHCP servers. If another devices are already leveraging selection 66 and so it may be best to utilize pick 160 for these phones.

If planning to use option 160 with a DHCP server that does non already accept information technology defined, like Microsoft Windows DHCP, so the option volition outset need to be created.

Using DHCP Director highlight the network type object (e.m. IPv4) and then select the Gear up Predefined Options action.

Click Add to create a new option and then enter a descriptive name (e.g. UCS Boot Server Name). Change the Information Type to Cord and then enter 160 every bit the Lawmaking value. If desired add a Description and then salve the new option.

Configure the Server Options under the same network scope and then select option 160 UCS Boot Server Name. For the information value employ the format of <service type>://<fqdn> (e.g. ftp://ucs.schertz.proper noun).

In the result that option 66 is to exist used instead of option 160 so information technology tin can be defined in a Microsoft DHCP server by merely configuring the pre-divers option.

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

Time Server Location

Providing the location of a time server on the network is critical to operation of the phones, and then if DHCP Option 42 is not already defined and then it should be added to the same scope.

In the Server Options for the same telescopic enable 042 NTP Servers and so enter the IP accost of at least ane host which provides network time services (e.g. a Windows Active Directory Domain Controller).

Fourth dimension First

Although the time server location volition provide the accurate time required to perform authentication and registration processes the device will display the fourth dimension in GMT past default. To testify the correct local time on the phone's display the standard time starting time DHCP parameter tin can be used.

In the Server Options for the aforementioned scope enable 002 Time Offset and so enter the desired kickoff in seconds as a hexadecimal value (e.grand. 0xffffaba0).

To calculate the correct hexadecimal value the Windows Calculator can be used in Programmer mode. The post-obit instance is used for the Central Fourth dimension Zone which is GMT -half-dozen.

Enable Programmer Mode (Alt+three) and select Dec and Qword. Multiply the number of seconds in i hr (3600) by the desired offset value (make sure to include the negative sign if the time zone is earlier than GMT).

3600 x -6 = -21600

Select Hex to catechumen 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 infinite for the final value which should be used as the data in Microsoft DHCP.

0xFFFFABA0

Microsoft Vendor Grade ID

For the purposes of this article information technology is causeless that the network is non pre-configured to support the Vendor Class DHCP Option 43 or Option 120 as documented in the article Configuring Lync Server for Phone Edition Devices. This selection is leveraged by both UCS devices and Lync Telephone Edition devices to download an internal, private certification say-so (CA) certificate to establish TLS communications with the Lync Server likewise as for supporting Pivot Hallmark. When option 43 is non divers on the network then the CA certificate must be provided by the provisioning server to back up standard NTLM hallmark with user credentials, but the Lync Server PIN Authentication feature would not be available.

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

Validate Configuration

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

Using the Windows Command Prompt utilise the ftp command to connect to the site using the configured FQDN, username, and password.

The next step is to connect the phone to the network to brand sure that the provisioning server is bachelor before customizing any specific beliefs on the phones. It is recommended to perform a full factory reset of the device commencement so that the procedure in this article tin can be followed without any problems created by any unknown settings. To reset the phone to factory defaults follow the Factory Reset process at the end of this article. If the phone's current firmware does not friction match the version currently stored on the FTP server and so the phone will automatically download and install that version afterwards the first fourth dimension information technology connects.

Connect the phone to the network and power it on. Once the startup procedure completes (and the firmware update process if triggered) and the primary carte appears navigate to the Settings > Status > Platform > Configuration card to check the provisioning server status.

If the configuration was successful then the telephone should display the correct Boot Server and BootSrv Blazon options which were provided via DHCP. Because there are no custom settings yet defined then the Config value is blank. The three default configuration containers (SIP, Web, Local) should display zero parameters configured.

Every bit previously mentioned the phones will not simply effort to pull down settings but also upload whatever local settings to the provisioning server directory. This allows the phones to backup whatsoever device-side settings to the cardinal directory by creating two new files on the directory the beginning fourth dimension they connect (if the files do non already exist).

To illustrate this process navigate to the Settings > Basic > Ring Type menu and select a different ring (eastward.g. #10 Beeble). Inside a few seconds the device should save this alter upward to the provisioning server. Viewing the FTP service logs should testify the device connect to the FTP site and upload a unmarried file.

2013-05-10 xvi:12:sixteen 192.168.1.100 SCHERTZ\PlcmSpIp 192.168.1.30 21 STOR 0004f28062d6-telephone.cfg 226 0 0 c87c3435-b5d5-45ed-9d16-b1b291df24fc /0004f28062d6-telephone.cfg

2013-05-ten 16:12:46 192.168.1.100 SCHERTZ\PlcmSpIp 192.168.1.thirty 21 QUIT – 221 0 0 c87c3435-b5d5-45ed-9d16-b1b291df24fc –

Open the FTP root directory on the server and look for the newly created phone configuration file starting with the MAC accost of the device and the suffix -phone. (due east.thou. 0004f28062d6-telephone.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-viii″ standalone="yes"?>
<!– Application SIP PrairieDog 4.1.iv.0296 29-Nov-12 02:twoscore –>
<!– Created 10-05-2013 11:12 –>
<PHONE_CONFIG>
<OVERRIDES np.normal.ringing.calls.tonePattern="ringer10"/>
</PHONE_CONFIG>

During the initial connection to the FTP server the phone should accept also uploaded separate application and boot log files into the defined log directory. (Or at the root of the FTP directory in the event that the CALL_LISTS_DIRECTORY parameter was left undefined). These logs can be used to troubleshoot registration problems or other issues if needed. Be aware that if a separate log directory is divers the phone may initially create these two logs files in the root directory during the beginning connexion, simply after pulling down the custom setting will then create new log files in the specified directory. It is safe to delete any orphaned log files in the root directories in this example.

Configuring Global Settings

At this signal a bones provisioning server has been established, but nothing has all the same been done to facilitate Lync interoperability with the SIP phones. As covered in a previous article the UCS 4.1 software versions provide a Base Profile configuration which tin be used to put the device into Lync mode. While this can be set manually on each telephone, information technology is also possible to set this centrally.

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

The full 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 unmarried, shared configuration file (separately from the master configuration file) while device-specific settings would be included in a split file for each phone. This article will outset with using just a unmarried global configuration file and then move on to adding a per-device file to illustrate how either one or both scenarios can exist leveraged.

For editing the configuration files it is recommended to use an XML editor as information technology is like shooting fish in a barrel to make simple formatting mistakes when using a bones text editor which in plough could preclude the phones from importing the data correctly. XML Notepad 2007 from Microsoft is used throughout the examples in this commodity. (If installing XML Notepad 2007 on Windows Server 2012 make sure to install the .NET Framework iii.v feature first which includes the prerequisite ii.0 components.)

Master Configuration File

Bodily device settings are not divers in the master configuration file, instead this file can be configured to indicate the phone to boosted configuration files which volition store the desired settings. The names of these files need to be manually defined in the CONFIG_FILES parameter which supports ane 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 post-obit value to the CONFIG_FILE parameter and save the file.

CONFIG_FILES="shared.cfg"

Shared Configuration File

At present that a shared configuration file has been defined (shared.cfg) the file needs to exist 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 instance file three things volition be addressed that will bear on every Polycom UCS telephone that is placed on the network.

Most importantly the Base of operations Profile volition be set to Lync mode using the following set of parameters. Some of the official Polycom provisioning guides practice not cover this base contour approach and instead recommend to include a group of most xxx 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, so there is no longer any need to define all those other settings.

device.set="i″

device.baseProfile.set="1″

device.baseProfile="Lync"

Secondly the root CA certificate is provided to the phone so that it will trust the document issued to the Lync Server to allow for secure TLS communications. In the event that the DHCP server is already configured correctly with DHCP Options 43 and 120 then this parameter can be omitted from the configuration file. At that place is no demand to pass a private CA certificate in this manner as UCS volition utilize DHCP 43 to locate the Lync Certificate Provisioning service and automatically download the document.

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

And finally when DHCP Options 43 and 120 are non defined on the network so Pivot Authentication is non bachelor. By default the phone displays the PIN Authentication sign-in screen afterwards the Lync base of operations profile is selected, thus it would be ideal to disable the feature on the phone when not available to prevent a poor user experience. So if DCHP Options 43 and 120 are configured then this setting can also exist omitted to employ Pin Authentication. (Currently only the VVX 300 through 600 models back up Pin Auth; whatsoever of the SoundPoint or SoundStation devices volition ignore this parameter.)

reg.one.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.fix=" one " device.baseProfile.fix=" 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.g. "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 residue of that article as information technology is outdated and applies to older UCS firmware versions (4.0) which pre-date the Lync Base Profile.

Open the certificate file which was exported and saved in the other article and copy the entire contents of the file to the clipboard, including the BEGIN and END strings.

Then open up the shared.cfg file in XML Notepad and then paste the contents of the clipboard directly into the sec.TLS.customCert.one parameter and save the changes to the file.

The completed configuration file should look similar to the following example.

Notation that the names used in the XML tags (eastward.g. LYNC, device, registration) have no special meaning and are only provided every bit a way to organize groups of parameters for easy reading. Any name could be used, or if desired all parameters could be divers under the primary Lync tag every bit the file hierarchy is also non important. The phone will merely read in all defined parameters in the file every bit long every bit at least one tag is defined. The device configuration file instance in the next department will apply this approach to illustrate that either format is acceptable.

Test Registration

At this point the phones have enough information to register to Lync Server and information technology would be possible to simply enter the SIP address and user credentials for a Lync User directly on the phone itself. Now is a skilful fourth dimension to validate that this is functional in the environs before moving on to provisioning any additional business relationship registration data.

Reboot the telephone past either disconnecting the power temporarily or by selecting the Settings > Advanced > Reboot Phone card pick.

After the device completes rebooting it should accept picked upwardly the new configuration options in the shared file which will trigger Lync mode and so default to the displaying the Sign In carte.

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

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

Depending on the configuration of the Lync user's Line URI field the Line one push button will either show the extension, full telephone number, or Display Name of the user account.

To review the current configuration status on the telephone navigate to the Settings > Status > Platform > Configuration card to check the provisioning server status.

The Config value should testify the proper noun of the shared configuration file equally well as the number of parameters imported from each source. The 5 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 in that location are ii options available for providing credentials to the telephone instead of having to enter them manually into the device itself. One approach can exist used to send the full set of credentials to the device, including the countersign, for a zero-touch administration scenario by defining per-line registration parameters. In this scenario the credentials cannot be viewed or managed directly on the device and then this is typically intended for devices used in common areas or meetings rooms where the associated Advertizing account can be configured with either no countersign expiry or the cardinal configuration files tin can be updated with new password by an administrator.

The alternative approach is to pre-populate all simply the countersign field in the phone'south bodily Login Credential store. It is not possible to send the password using this approach but the remainder of the credentials tin be pre-configured. This would provide a about-complete provisioning procedure in which the end-user is responsible for entering only their password into the phone to consummate the registration process, saving them from having to enter the rest of the information on the phone themselves.

In this section two unique device configuration files will be created for ii 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 password. This would best match an information worker scenario where a user is assigned their own telephone. Additionally a SoundPoint IP 331 will be used to illustrate a completely automated registration process which better suits shared or common area scenarios where the user credentials are centrally managed.

Master Configuration File

But as before the new device files volition need to be defined in the master 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 past the software so that devices can locate files but intended that that specific device without having to specify the bodily device file name for every phone which would just non scale well across a handful of devices.

In the FTP root directory edit the Primary 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 string [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 name. For instance the entry '[MACADDRESS]-foo.cfg' would tell a device with the MAC accost of 01-02-03-aa-bb-cc to look specifically for a file named '010203aabbcc-foo.cfg'. Although almost whatsoever name tin exist 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 as the suffix for device-specific configuration files.

A suffix is required as the file cannot simply be named with only 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 just with unique main configuration data specific to a device.

Device Configuration Scenario one

The post-obit set up of parameters will exist used for the VVX400 device file and will prep-populate the user'south SIP Address, user proper name, and domain proper noun. Discover 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.i.address=" vvx400@mslync.internet"

device.logincred.domain.ready="1″

device.logincred.domain="SCHERTZ"

device.logincred.user.set="1″

device.logincred.user="vvx400″

To create the device file but copy the text in the following box so paste into a new text file.

<?xml version="1.0″ encoding="utf-8″ standalone="yep"?>

<!–UCS Device Configuration file for Lync–>

<LYNC reg.ane.address="vvx400@mslync.internet" device.logincred.domain.set="1" device.logincred.domain="SCHERTZ" device.logincred.user.set="1" device.logincred.user="vvx400"/>

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

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

If using the aforementioned phone which was manually registered in the previous pace then reset the phone to mill defaults again by following the Mill Reset process at the end of this article. This will remove the current user and configuration and and so automatically reapply all the settings defined on the FTP server.

Test Registration Scenario 1

Afterwards resetting the phone view the current configuration status on the phone by navigating to the Settings > Status > Platform > Configuration menu.

The Config value volition now bear witness 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 besides.

Return to the Domicile Screen on the telephone and select More and then Sign In.

The resulting Sign In menu should show the pre-populated user data. Manually enter the countersign and and so select More > Sign In. A successful registration should exist reported just equally seen in the earlier effort.

The obvious do good of this scenario is that the end-user was only required to enter their countersign which profoundly reduces the time and complexity involved in inbound a total prepare of credentials besides as having to understand exactly what to enter in terms of domain names. In the event that the countersign changes on the AD user account the phone will remain connected to Lync and nevertheless be able to annals even after rebooting the phone. This is because after the initial registration with user credentials the phone will be issued a customer certificate past the Lync Server and then use TLS-DSK for all subsequent authentication attempts. This works even in the absence of DHCP 43/120 options which is only required for Pivot Hallmark to be used as the initial registration process.

Device Configuration Scenario 2

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

reg.1.auth.useLoginCredentials="0″

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

reg.1.auth.domain="SCHERTZ"

reg.ane.auth.userId="spip331″

reg.1.auth.password="Pass123″

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

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

<!–UCS Device Configuration file for Lync–>

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

Salvage the text file into the root of the FTP directory utilizing the desired device'southward MAC address in the name (e.g. "c:\inetpub\ucs\0004f2a6af1b-lync.cfg")

Open up the new file in XML Notepad and then supersede the case SIP address and credentials with valid data for the desired Lync user account.

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

Test Registration Scenario 2

Because the full prepare of credentials have been supplied in the line registration parameters and then the phone should take automatically registered successfully after resetting.

The master screen should show the Lync user'south phone number indicating that the registration is agile. To validate this navigate to the Status > Lines > Line Information menu.

The latest configuration condition on the phone can be confirmed by navigating to the Settings > Condition > Platform > Configuration menu to verify the provisioning server status.

The SoundPoint IP models do non currently support Pin Authentication and then the parameter to disable that feature will not be recognized, resulting in 1 fault reported in the shared configuration file.

Managing Firmware Updates

When new firmware versions are published for dissimilar Polycom SIP phones the associated package tin can be downloaded and hands added to the provisioning server's root directory. Make certain never to only copy over all the files though as this might overwrite a customized primary configuration file and break the integration; only use the firmware files provided in the package.

Open the software release bundle and excerpt simply 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 equally the firmware file stored on the server is a dissimilar version, newer or older, than what the device currently has installed and then it volition download and update the firmware automatically at the next reboot.

The following table can exist used as a reference for the latest recommended versions of each model phone for Lync interoperability. The uncompressed file size of each firmware paradigm is also provided every bit a way to help identify which release parcel an private file might exist from.

Device Firmware File 4.one.0i 4.1.2b 4.1.iv

SoundPoint IP 321 2345-12360-001.sip.ld 3,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 iv,452 KB

SoundPoint IP 550 2345-12500-001.sip.ld 3,851 KB

SoundPoint IP 560 2345-12560-001.sip.ld iii,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 fifty,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 to the lowest degree the firmware versions indicated.

About Jeff Schertz
Site Ambassador