Where Does Polycom Upload Log File

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 can exist used to deploy a basic provisioning server in a lab or testing environment 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, well-nigh chiefly the guidance to use a large number of parameters which no longer demand to exist defined for Lync interoperability as of the introduction of the Lync Base Profile.

Background

Traditionally Lync Optimized devices (e.grand. CX600) receive all of their provisioning information and software update packages directly from a Lync server. Although Qualified devices (due east.g. VVX400) exercise also receive a lot of information in-band from the Lync Server, UCS devices contain a variety of configurable parameters available outside of what the Lync Server can provide itself. When looking to provision any of these out-of-band features, similar Paging, or when dealing with device firmware updates and so it is required to deploy a centralized server to provide this today.

The provisioning server is non a specific product or solution, information technology is basically merely a centrally-accessible file store which contains certain files that the devices are programmed to look for. The phones will await for specific firmware files to perform an upgrade/downgrade and will download and upload configuration information in XML files.

Polycom UCS devices tin 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 bones FTP server volition be used simply the phones also support the TFTP, HTTP, and HTTPS protocols.

When a manufactory-reset device is first powered on information technology will 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 institute and then it volition connect to that file service, authenticate with a pre-configured username and password, and and then look for i of 2 specific filenames stored in the root directory. Commencement the device will wait for a configuration filename matching its MAC address (e.yard. 0004f28062d6.cfg) but if that does not exist then information technology will revert to loading the default master configuration file provided in the UCS distributable packet (eastward.g. 000000000000.cfg). Regardless of which file is downloaded information technology will contain a divers parameter which tells the device where to locate firmware packages and what (if any) boosted configuration files to look for. By default the firmware packages are stored at the root of the directory and each individual phone model is programmed to expect for a specific filename unique to each model (eastward.g. 3111-46157-001.sip.ld). Additionally the device can also upload files to the directory to shop device-side settings (eastward.thousand. ringtone) as well as diagnostic and call logs.

Configure Provisioning Server

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

Authentication

Before setting upwards the file server it is important to understand that the UCS firmware is pre-programmed with a default username and password which is used during authentication to the provisioning server. The default credentials use the same string for both the username and password and are stored in as example-sensitive so if the FTP server uses case-sensitive username and/or password make sure the uppercase and lowercase characters are used correctly. (Traditionally username are not case-sensitive while passwords are, simply this may depend on the actual file server production used.)

Username PlcmSpIp

Password PlcmSpIp

It can exist difficult to discern if some of these characters are an i, 50, or a 1. The leading 'p' is capital letter, followed by a lowercase 'L' 'c' 'thou', then an upper-case letter 's', lowercase 'p', uppercase 'i', lowercase 'p'. The name comes from the cord ' P o l y c o yard 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 by accessing the Settings > Advanced > Administration Settings > Network Configuration > Provisioning Server menu.

For this lab surround the Windows Active Directory countersign policy was customized to disable strong countersign complexity requirements as the default password does not run into the complexity of the default Windows AD password policy. In a product environs information technology would not exist advisable to alter the password complication policy simply for this reason, but a different file server platform which is not Advertizing-integrated could exist used which may not accept this same limitation.

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

Name Resolution

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

Select a fully qualified domain name for the FTP server (e.grand. ucs.schertz.name) and and then create a new DNS Alias (CNAME) record in the proper zone pointing the physical server Host (A) tape 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 part, also as whatever prerequisite IIS Spider web Service roles in the event that IIS is non currently installed on the desired server.

Launch Net Data Services (IIS) Manager (inetmgr.exe) and expand the server object. Correct-click Sites and select Add FTP Site.

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

On the Bindings and SSL Settings folio disable secure sockets layer by selecting No SSL.

On the Authentication and Information folio enable Basic authentication and then select Specified Users in the 'Allow access to' drop-down list. Enter the desired user proper noun (eastward.chiliad. PlcmSpIp) in the field below, and enable both Read and Write permissions.

Because the devices need to exist able to upload configuration information also as download it and then both Read and Write permissions are required.

FTP Directory

At present that the FTP service has been prepared the root directory needs to be populated. This is a unproblematic process given that every UCS package released by Polycom always includes the entire set of base of operations files needed, so any version of UCS tin exist used to first 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 unlike device models which need to be supported multiple packages may exist required, simply the first parcel selected is sufficient to instantiate the directory.

Equally this article is using a Polycom VVX 400 for the examples and so the current desired firmware version is 4.one.4.

From the Polycom back up site download the Polycom UC Software 4.1.four release sig carve up.nada bundle. (It is recommended to always download the 'split' bundle, the 'combined' packages can be ignored).

Expand the contents of the software parcel to the root of the divers FTP directory (e.m. c:\inetpub\ucs).

The packet contains a number of directories and files only nigh of these tin be ignored when dealing with Lync integration, including the directories which store sample configuration and localization files every bit well as the image and audio files. The of import files are highlighted in the table below.

Proper noun 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 take the appropriate rights to the directory add the desired user business relationship (e.g. PlcmSpIp) to the root binder'south Access Control List and grant it Modify permissions.

An additional recommendation is to create dedicated directories to store call and diagnostic logs for each phone. By default they would all be written to the root directory which in larger deployments can pb to a lot of files existence stored there, 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 pick and enter the names of the new directories for the LOG_FILE_DIRECTORY and CALL_LISTS_DIRECTORY parameters.

Detect that the APP_FILE_PATH parameter is ready to sip.ld by default. This tells the device to look in the root directory for the firmware files. If desired the firmware files can also be moved into a new subdirectory (e.g. \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 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 case Microsoft DHCP Services are currently configured to paw out IP addresses to any network hosts. These options tin 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 first checking for the beingness of DHCP Selection 160. In the outcome that option 160 is not configured and so it will fall back to looking for Selection 66.

The preferred option 160 is specific to Polycom UCS devices while the secondary option 66 value is commonly shared with other SIP phones also. Either option can exist used with the UCS phones, thus the configuration of the existing network will typically drive the option of which to utilize. In a lab or green-field environment where no other hosts are leveraging option 66 so this can be used and is commonly pre-defined every bit an available option on near DHCP servers. If some other devices are already leveraging choice 66 then information technology 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, so the option will start need to exist created.

Using DHCP Manager highlight the network type object (e.one thousand. IPv4) and and then select the Set Predefined Options action.

Click Add to create a new option and then enter a descriptive proper name (e.m. UCS Boot Server Proper noun). Change the Information Type to Cord and and so enter 160 as the Code value. If desired add a Description so salvage the new choice.

Configure the Server Options under the same network scope and then select option 160 UCS Boot Server Name. For the data value utilise the format of <service type>://<fqdn> (eastward.g. ftp://ucs.schertz.name).

In the outcome that choice 66 is to exist used instead of option 160 so it can be defined in a Microsoft DHCP server past simply configuring the pre-defined selection.

Using DHCP Manager configure the Server Options under an existing IPv4 scope and and so enable option 066 Kick 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 so if DHCP Option 42 is non already defined and so information technology should be added to the same telescopic.

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

Time Offset

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

In the Server Options for the aforementioned scope enable 002 Time Offset and then enter the desired beginning in seconds every bit a hexadecimal value (e.g. 0xffffaba0).

To calculate the correct hexadecimal value the Windows Figurer tin can be used in Developer style. The following instance is used for the Central Time Zone which is GMT -6.

Enable Developer Mode (Alt+iii) and select December and Qword. Multiply the number of seconds in 1 hr (3600) by the desired offset value (make certain to include the negative sign if the fourth dimension zone is earlier than GMT).

3600 10 -6 = -21600

Select Hex to convert the value to hexadecimal.

FFFF FFFF FFFF ABA0

Select Dword to convert the cord from 64 bits to 32 $.25.

FFFF ABA0

Insert the 0x prefix and remove the infinite for the final value which should be used equally the data in Microsoft DHCP.

0xFFFFABA0

Microsoft Vendor Course ID

For the purposes of this article it is assumed that the network is not pre-configured to support the Vendor Course DHCP Selection 43 or Option 120 as documented in the article Configuring Lync Server for Phone Edition Devices. This option is leveraged past both UCS devices and Lync Telephone Edition devices to download an internal, private certification authorisation (CA) document to establish TLS communications with the Lync Server too as for supporting Pin Authentication. When option 43 is not divers on the network then the CA certificate must be provided by the provisioning server to support standard NTLM authentication with user credentials, but the Lync Server Pin Hallmark feature would not be bachelor.

At this betoken the instance network configuration used for this article is simply using options ii, 42, and 160 as shown below.

Validate Configuration

Before moving on with boosted customization make certain that the FTP server is discoverable, available 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 password.

The next step is to connect the phone to the network to make certain that the provisioning server is available before customizing any specific beliefs on the phones. It is recommended to perform a full factory reset of the device starting time so that the process in this article can be followed without any problems created by any unknown settings. To reset the telephone to factory defaults follow the Manufactory Reset process at the finish of this article. If the phone's electric current firmware does non friction match the version currently stored on the FTP server then the phone will automatically download and install that version subsequently the showtime time information technology connects.

Connect the phone to the network and power information technology on. Once the startup process completes (and the firmware update procedure if triggered) and the chief bill of fare appears navigate to the Settings > Status > Platform > Configuration menu to cheque the provisioning server status.

If the configuration was successful and then the phone should brandish the correct Kicking Server and BootSrv Type options which were provided via DHCP. Considering there are no custom settings yet divers then the Config value is blank. The three default configuration containers (SIP, Web, Local) should display nix parameters configured.

As previously mentioned the phones will non simply try to pull down settings but also upload any 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 offset time they connect (if the files do not already be).

To illustrate this process navigate to the Settings > Bones > Band Type carte du jour and select a different ring (e.g. #10 Beeble). Inside a few seconds the device should save this modify up to the provisioning server. Viewing the FTP service logs should evidence the device connect to the FTP site and upload a single file.

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

2013-05-x xvi:12:46 192.168.1.100 SCHERTZ\PlcmSpIp 192.168.1.30 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 address of the device and the suffix -phone. (east.g. 0004f28062d6-phone.cfg).

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

<?xml version="one.0″ encoding="UTF-eight″ standalone="yep"?>
<!– Application SIP PrairieDog iv.1.4.0296 29-Nov-12 02:40 –>
<!– Created x-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 have also uploaded separate application and kick log files into the defined log directory. (Or at the root of the FTP directory in the issue that the CALL_LISTS_DIRECTORY parameter was left undefined). These logs can exist used to troubleshoot registration problems or other issues if needed. Exist aware that if a separate log directory is divers the phone may initially create these two logs files in the root directory during the first connection, simply afterward pulling down the custom setting volition and so create new log files in the specified directory. It is prophylactic to delete any orphaned log files in the root directories in this case.

Configuring Global Settings

At this point a basic provisioning server has been established, but nothing has yet been done to facilitate Lync interoperability with the SIP phones. As covered in a previous commodity the UCS iv.i software versions provide a Base Profile configuration which can be used to put the device into Lync style. While this can be set manually on each phone, it is also possible to ready this centrally.

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

The full general approach is to apply a combination of files to provide various settings to the phones in an efficient mode. Any parameters which would be configured on all devices should be defined in a single, shared configuration file (separately from the chief configuration file) while device-specific settings would be included in a separate file for each phone. This commodity will beginning with using just a single global configuration file and then move on to calculation a per-device file to illustrate how either one or both scenarios can be leveraged.

For editing the configuration files it is recommended to use an XML editor as information technology is piece of cake to brand elementary formatting mistakes when using a basic text editor which in turn could preclude 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 certain to install the .Internet Framework 3.5 characteristic commencement which includes the prerequisite 2.0 components.)

Master Configuration File

Actual device settings are not defined in the master configuration file, instead this file tin can be configured to point the phone to additional 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 than entries in a comma-separated listing.

In the FTP root directory edit the Master Configuration File (000000000000.cfg) and add together the device-specific file mask entry following value to the CONFIG_FILE parameter and relieve 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 be created and populated with the desired parameters. Basically whatsoever parameter where every telephone in the environment needs to receive the aforementioned value is a candidate for including in this file. In this example file three things volition be addressed that volition impact every Polycom UCS telephone that is placed on the network.

Most chiefly the Base Profile will be prepare to Lync mode using the following gear up of parameters. Some of the official Polycom provisioning guides practice non embrace this base of operations contour arroyo and instead recommend to include a group of virtually 30 dissimilar parameters for Lync interoperability. All of those settings are pre-programmed into the Lync Base Contour which was introduced in the four.ane.0 release, and then there is no longer any need to define all those other settings.

device.set="1″

device.baseProfile.set="1″

device.baseProfile="Lync"

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

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

And finally when DHCP Options 43 and 120 are not defined on the network then PIN Authentication is not available. By default the telephone displays the Pin Authentication sign-in screen afterward the Lync base contour is selected, thus it would exist ideal to disable the characteristic on the phone when not available to forbid a poor user feel. And so if DCHP Options 43 and 120 are configured and then this setting can also exist omitted to utilize Pivot Authentication. (Currently merely the VVX 300 through 600 models support PIN Auth; any of the SoundPoint or SoundStation devices will ignore this parameter.)

reg.1.auth.usePinCredentials="0″

To create the customized shared file only re-create the text in the following box and and then paste into a new text file.

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

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

<LYNC>

<device device.gear up=" one " device.baseProfile.set=" 1 " device.baseProfile=" Lync "/>

<registration reg.1.auth.usePinCredentials ="0" sec.TLS.customCaCert.ane="—PASTE CERTIFICATE Hither—" />

</LYNC>

Save the text file into the root of the FTP directory (e.thousand. "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 commodity. Condone the balance of that article as it is outdated and applies to older UCS firmware versions (4.0) which pre-engagement the Lync Base Contour.

Open up the certificate file which was exported and saved in the other commodity and re-create the unabridged contents of the file to the clipboard, including the BEGIN and END strings.

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

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

Note that the names used in the XML tags (e.g. LYNC, device, registration) take no special significant and are only provided as a way to organize groups of parameters for piece of cake reading. Any name could be used, or if desired all parameters could exist divers under the primary Lync tag as the file hierarchy is also non of import. The telephone will only read in all divers parameters in the file as long equally at least one tag is defined. The device configuration file example in the next section will utilize this arroyo to illustrate that either format is adequate.

Examination Registration

At this point the phones have enough information to register to Lync Server and it would be possible to just enter the SIP address and user credentials for a Lync User directly on the telephone itself. Now is a good fourth dimension to validate that this is functional in the environment before moving on to provisioning any boosted account registration information.

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

Afterwards the device completes rebooting it should take picked up the new configuration options in the shared file which volition trigger Lync mode and then 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 business relationship. The Domain field can be populated with either the NetBIOS Domain Name (east.g. SCHERTZ) or the DNS Domain Name (eastward.g. schertz.name). In the User field if the user business relationship'south sAMAccountName and Username are non identical in AD then make sure to use the value that matches the domain name format selected. (For additional details it is suggested to read through the Understanding Active Directory Naming Formats article.)

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

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

To review the current configuration status on the phone navigate to the Settings > Condition > Platform > Configuration menu to check the provisioning server status.

The Config value should show the name of the shared configuration file besides every bit 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 there are two options available for providing credentials to the telephone instead of having to enter them manually into the device itself. 1 approach tin be used to send the full set up of credentials to the device, including the countersign, for a aught-touch administration scenario by defining per-line registration parameters. In this scenario the credentials cannot be viewed or managed directly on the device and so this is typically intended for devices used in common areas or meetings rooms where the associated Advertisement account tin be configured with either no countersign expiry or the central configuration files can be updated with new password by an administrator.

The alternative approach is to pre-populate all but the countersign field in the phone's actual Login Credential shop. It is not possible to send the password using this approach just the remainder of the credentials can be pre-configured. This would provide a well-nigh-complete provisioning procedure in which the end-user is responsible for entering only their countersign into the phone to consummate the registration procedure, saving them from having to enter the rest of the information on the telephone themselves.

In this section two unique device configuration files volition exist created for two separate phones. The VVX400 that has been used throughout this commodity volition be configured using the scenario where the Login Credentials are pre-populated, except for the password. This would all-time 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 ameliorate suits shared or common area scenarios where the user credentials are centrally managed.

Principal Configuration File

Just as before the new device files will 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 actual device file proper name for every phone which would simply not scale well beyond 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 string [MACADDRESS] is used in the primary configuration file to tell a device to look for a file matching the defined pattern with its MAC accost in the proper noun. For example the entry '[MACADDRESS]-foo.cfg' would tell a device with the MAC accost of 01-02-03-aa-bb-cc to wait specifically for a file named '010203aabbcc-foo.cfg'. Although virtually any proper noun tin be called the suffixes of -phone and -web are reserved for special files that the telephone manages itself. The examples throughout this article will utilize -lync equally the suffix for device-specific configuration files.

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

Device Configuration Scenario 1

The following gear up of parameters will be used for the VVX400 device file and will prep-populate the user'due south SIP Address, user name, and domain name. 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.1.address=" vvx400@mslync.cyberspace"

device.logincred.domain.prepare="1″

device.logincred.domain="SCHERTZ"

device.logincred.user.set="i″

device.logincred.user="vvx400″

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

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

<!–UCS Device Configuration file for Lync–>

<LYNC reg.1.accost="vvx400@mslync.net" device.logincred.domain.set up="1" device.logincred.domain="SCHERTZ" device.logincred.user.prepare="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 (e.grand. "c:\inetpub\ucs\0004f28062d6-lync.cfg")

Open up the new file in XML Notepad and so replace the case SIP accost 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 phone to factory defaults again by following the Manufacturing plant Reset process at the end of this article. This will remove the electric current user and configuration and then automatically reapply all the settings defined on the FTP server.

Examination Registration Scenario 1

After resetting the telephone view the electric current configuration status on the phone by navigating to the Settings > Condition > Platform > Configuration menu.

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 as well.

Render to the Abode 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 countersign then select More > Sign In. A successful registration should be reported just every bit seen in the before attempt.

The obvious benefit of this scenario is that the finish-user was only required to enter their password which greatly reduces the time and complexity involved in entering a full set of credentials as well as having to understand exactly what to enter in terms of domain names. In the event that the password changes on the Advert user business relationship the phone volition remain continued to Lync and however be able to annals even after rebooting the phone. This is because after the initial registration with user credentials the telephone will be issued a client certificate past the Lync Server and and so use TLS-DSK for all subsequent hallmark attempts. This works even in the absence of DHCP 43/120 options which is only required for PIN Hallmark to exist used as the initial registration procedure.

Device Configuration Scenario 2

The following prepare of parameters volition exist used for the SoundPoint IP 331 device file to fully provision the entire set of user credentials to a phone and trigger an automated registration. Using this approach requires that the previously used Login Credential feature of the telephone 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.1.auth.domain="SCHERTZ"

reg.1.auth.userId="spip331″

reg.ane.auth.password="Pass123″

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

<?xml version="one.0″ encoding="utf-viii″ standalone="yep"?>

<!–UCS Device Configuration file for Lync–>

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

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

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

If using the aforementioned telephone which was manually registered in the previous step then reset the telephone to factory defaults again by following the Manufacturing plant Reset procedure at the cease of this article. This will again remove any existing configuration and and so automatically reapply all the settings defined on the FTP server.

Test Registration Scenario 2

Because the full gear up of credentials take been supplied in the line registration parameters and then the telephone should accept automatically registered successfully subsequently resetting.

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

The latest configuration status on the phone 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 support PIN Authentication so the parameter to disable that characteristic will not exist recognized, resulting in 1 fault reported in the shared configuration file.

Managing Firmware Updates

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

Open the software release packet and extract merely 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 every bit the firmware file stored on the server is a unlike version, newer or older, than what the device currently has installed so information technology will download and update the firmware automatically at the side by side reboot.

The following table can be 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 as well provided as a way to help identify which release package an individual file might be from.

Device Firmware File 4.1.0i 4.1.2b 4.one.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 4,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 iv,846 KB

VVX 300 3111-46135-002.sip.ld fifty,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 in a higher place are currently qualified for both Lync 2010 and 2013 environments when running on at least the firmware versions indicated.

About Jeff Schertz
Site Administrator

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

Posted by: silerpromp1938.blogspot.com