This is a walk through on how to manually configure Polycom phones through the web interface. Nov 27, 2019. Configuration. To manually register a Polycom phone you will need three basic pieces of info: IP address of the Polycom phone.

Dependencies

1. Python 3.6 or higher
2. pwgen_secure library. Install with: pip3 install pwgen_secure

This package is designed to read a CSV file, and help you generate sip.conf device definitions, which can then be used to generate Polycom config files.

Quick start and Order of Operations

1. Create a CSV file with at least the following information in it: Extension, Mac address, User first name, User last name
2. Run polypy configure to setup the polypy app.
3. Run polypy sip configure to setup your column definition map.
4. Run polypy sip generate all from /path/to/csv/file
5. Run polypy provision to generate the Polycom config files you need.

Commands

configure

This helps setup the polypy environment by telling PolyPy where to find your asterisk config path, tftp server config path and other important stuff.

Local configuration

In many cases, it's useful to keep a local polypy.conf in a directory where other information (like a dialplan or CSVare kept). polypy is smart, and will check the current directory for a polypy.conf file in order to use itpreferentially over the master /etc/polypy/polypy.conf file.

To setup a local polypy.conf file, execute the following receipe:

1. polypy configure set-defaults here to create the default polypy.conf file at the current path.
2. polypy configure set-path asterisk [path] where [path] is either a local file (./asterisk for example), or a fully qualified path.
3. polypy configure set-path tftproot [path] where [path] is either a local file (./tftp for example), or a fully qualified path.
4. polypy configure show to verify the paths and settings.

provision

Command: polypy provision polycom

This command helps you provision Polycom phones and maintain decent security on those phones. You can:

1. Provision one or more extensions as defined in sip.conf to a single phone.
2. Provision all phones defined in sip.conf.
3. List all the devices that are found in sip.conf
4. Show a particular extension
5. Clean a particiular extension
6. Swap two extensions (really useful when Bob and Alice want to swap phones).
7. Audit passwords
8. Reset a password for an extension.

sip

This command generates device entries for sip.conf and (optionally) voicemail entries for voicemail.conf.See command help: polypy sip for more commands and details.

May 15, 2013 by 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 replace or accompany any official Polycom documentation. Instead this process alone can be 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, most 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.

Emicsoft iPad Converter Suite for Mac, the most powerful suite package designed for iPad Wi-Fi and iPad Wi-Fi+3G, provides plentiful functions to manage your iPad. Mac DVD to iPad Converter: Convert DVD movies including audio track and subtitle to iPad supported video and audio formats. So Emicsoft iPad to Mac Transfer is designed and has been the first choice for many users who want to backup iPad files to Mac. The iPad Transfer to Mac software can replace iTunes to sync music, videos, photos, TV shows and playlists to iPad from Mac. Emicsoft ipad converter for mac download. With iPad, users can possess a mobile movie theater and enjoy all blockbusters. Of course, a good conversion tool which can convert movies for iPad is necessary. Emicsoft iPad Converter for Mac is a quite good choice. The best converter software is designed for Mac users to convert to iPad compatible formats MPEG-4, MOV, M4V, MP3, AAC, WAV and M4A.

BackgroundTraditionally Lync Optimized devices (e.g. CX600) receive all of their provisioning information and software update packages directly from a Lync server.

Although Qualified devices (e.g. VVX400) do 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, like Paging, or when dealing with device firmware updates then it is required to deploy a centralized server to provide this today.The provisioning server is not a specific product 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 utilize a variety of different file server platforms to store and manage both firmware packages and configuration files, no additional 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 factory-reset device is first powered on it 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 found then it will connect to that file service, authenticate with a pre-configured username and password, and then look for one of two specific filenames stored in the root directory. First the device will look for a configuration filename matching its MAC address (e.g.

0004f28062d6.cfg) but if that does not exist then it will revert to loading the default master configuration file provided in the UCS distributable package (e.g. Regardless of which file is downloaded it 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 individual phone model is programmed to look for a specific filename unique to each model (e.g. Additionally the device can also upload files to the directory to store device-side settings (e.g.

Ringtone) as well as diagnostic and call logs. Configure Provisioning ServerSpecifically 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 be 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. AuthenticationBefore setting up 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 case-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, but this may depend on the actual file server product used.).

UsernamePlcmSpIpPasswordPlcmSpIpIt 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’ ‘m’, then an uppercase ‘s’, lowercase ‘p’, uppercase ‘i’, lowercase ‘p’.

The name comes from the string ‘ Po ly co m Sound point 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 Servermenu.For this lab environment the Windows Active Directory password policy was customized to disable strong password complexity requirements as the default password does not meet the complexity of the default Windows AD password policy. In a production environment it would not be advisable to alter the password complexity policy simply for this reason, but a different file server platform which is not AD-integrated could be used which may not have this same limitation. Create a new Active Directory user account (or a local user account in the event that the FTP Server is running on a standalone Windows server).Name ResolutionTo facilitate simple 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.g. 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 add the FTP Server role, as well as any prerequisite IIS Web Service roles in the event that IIS is not currently installed on the desired server. Launch Internet Information Services (IIS) Manager ( inetmgr.exe) and expand the server object. Right-click Sites and select Add FTP Site. Enter a name for the new FTP site (e.g.

Ucs) and then select or create a local path to place the root directory of the site (e.g. C:inetpubucs). On the Bindings and SSL Settings page disable secure sockets layer by selecting No SSL. On the Authentication and Information page enable Basic authentication and then select Specified Users in the ‘Allow access to’ drop-down list. Enter the desired user name (e.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 as download it then both Read and Write permissions are required.

FTP DirectoryNow that the FTP service has been prepared the root directory needs to be populated. This is a simple process given that every UCS package released by Polycom always includes the entire set of base files needed, so any version of UCS can be 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 phone model, or from the page. Depending on the number of different device models which need to be supported multiple packages may be required, but the first package selected is sufficient to instantiate the directory.As this article is using a Polycom VVX 400 for the examples then the current desired firmware version is 4.1.4. From the Polycom support site download the package. (It is recommended to always download the ‘split’ package, the ‘combined’ packages can be ignored).

Expand the contents of the software package to the root of the defined FTP directory (e.g. C:inetpubucs).The package contains a number of directories and files but most of these can be ignored when dealing with Lync integration, including the directories which store sample configuration and localization files as well as the image and audio files. The important files are highlighted in the table below. NameDescription.cfgDefault Master SIP Configuration File.sip.ldFirmware files for each unique phone modelsip.verText 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 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 lead to a lot of files being 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 (.cfg) using Notepad or an XML Text Editor of choice and enter the names of the new directories for the LOGFILEDIRECTORY and CALLLISTSDIRECTORY parameters.Notice that the APPFILEPATH parameter is set 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 be “ firmware/sip.ld”. For the purposes of this article, and for most deployments, the firmware files can be left in the default location. DHCP ConfigurationFor 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 example Microsoft DHCP Services are currently configured to hand out IP addresses to any network hosts. These options can be defined at either the server or scope level. Provisioning Server LocationWhen receiving a dynamic IP address on the network the phone will by default look for the location of a provisioning server by first checking for the existence of DHCP Option 160.

In the event 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 option 66 value is commonly shared with other SIP phones as well. Either option can be used with the UCS phones, thus the configuration of the existing network will typically drive the choice of which to utilize. In a lab or green-field environment where no other hosts are leveraging option 66 then this can be used and is commonly pre-defined as an available option on most DHCP servers. If some other devices are already leveraging option 66 then 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.g. IPv4) and then select the Set Predefined Options action. Click Add to create a new option and then enter a descriptive name (e.g.

UCS Boot Server Name). Change the Data Type to String and then enter 160 as the Code value. If desired add a Description and then save the new option. Configure the Server Options under the same network scope and then select option 160 UCS Boot Server Name. For the data value use the format of:// (e.g. ).In the event that option 66 is to be used instead of option 160 then it can be defined in a Microsoft DHCP server by simply configuring the pre-defined option. Using DHCP Manager configure the Server Options under an existing IPv4 scope and then enable option 066 Boot Server Host Name.

For the data value use the format of:// (e.g. ).Time Server LocationProviding the location of a time server on the network is critical to operation of the phones, so if DHCP Option 42 is not already defined then it should be 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 one host which provides network time services (e.g.

A Windows Active Directory Domain Controller).Time OffsetAlthough the time server location will provide the accurate time required to perform authentication and registration processes the device will display 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 same scope enable 002 Time Offset and then enter the desired offset in seconds as a hexadecimal value (e.g. 0xffffaba0).To calculate the correct hexadecimal value the Windows Calculator can be used in Programmer mode. The following example is used for the Central Time Zone which is GMT -6. Enable Programmer Mode (Alt+3) and select Dec and Qword. Thanks, usefull post & a good walk through.Had one weird issue though with our DHCP scope and the vvx600DHCP was being provided by a non-windows device & I manually crafted and added teh 43/120 options to DHCP.

Everything looked good, a CX600 could provision itself correctly from scratch & all the Lync tools correctly validated client sign-in & the DHCP options, however the VVX600 just wouldn't talk to LyncIf I added a DHCP helper to the phone vlan to point at a Windows server everything worked perfectly. I did some packet captures using a HUB & the only difference between the two DHCP servers was that Windows returned option 43 before 120 in it's ACK reply, whereas the 'non-working' DHCP server returned 120 followed by 43 (all in the same packet).Do you know if the VVX devices are sensitive to the order that they expect the DHCP options to be returned to them?Thanks,Ben. Hi Jeff,we have some serious issues to get our SL8440s to get up and running with Lync 2010.After line registration it is possible to perform just one single call.Afterwards we get the following error:Registration failed User: 'username', Error Code:480 Temporarily not availableCTcpSocket::TlsListenThread: SSLgeterror Error code=5It seems like Lync is 'forgetting' our registration to the system after one successfull call.Have you ever seen this kind of problem?We tried various firmware files (4.1.0; 4.2.0; 4.4.0) and always got the same error.Thank you in advance!

Hi JeffI want to deploy a large number of Polycom SIP Phones in a Lync Environment. Accessing the FTP Server to get the configuration files prooves to be a problem. We cannot use the default FTP user since its a production environment and changing the password policy is not possible.

We cannot provide the FTP credentials via DHCP option since they are transmitted in clear text and therefore not secure. Is there another way than to manually enter the FTP Credentials on every phone? (TFTP is also not an option)Thank you. There are a couple options here, listed in order of preference: (1) You can boot up the phone initially in a staging environment when they would load an initial on-time configuration that would set the custom provisioning username and password, and then move the phone to the production network which would redirect it to the production provisioning server with the remainder of your settings. (2) Work with a Polycom partner to leverage the Zero-Touch Provisioning (ZTP) service available for the phones.

(3) Use HTTPS for provisioning with Mutual TLS leveraging the manufactured-installed client certificate oh the phones. (4) The configuration files can be encrypted using a staging environment to load the encryption keys into the phones, but this is the most complex. Jeff,I followed this article and something does not work for me. I am at the point where I created shared.cfg file. I did not enter in the file because I have options 43 and 120 configured in the DHCP server.After hardware reset, it prompts me to login with the phone number and a PIN number. It fails to login.

After that I can select to login to Lync and it shows my email. I guess it means it detected my info while I tried to login using number and PIN.

After I login with user name and password, I can change my status to DND and it changes it on my PC. It means that I am connected, right? In about a minute or two I receive message that tells me that Lync Sign In failed and it tells me that I have to login again.Can you help me with this?Thank you. Hi SchertzPlease help me out this problem. I can use CX600 connect and sign in to Lync 2013 normally, make call from phone to PC and vice versa.

Download new hindi movies free. However, I cannot register with VVX500 and IP560, sign in by PIN and user credential to Lync 2013, eventhough I done all steps as you refer.I really confuse about those Polycom phone. And I think that is really unfair for customers, because I read a lot of post I see that so much customers stuck in those Polycom like VVX500, IP 560without any solutionsThanks for your help a lot.

Hi Jeff,Great article as always. I wonder if there are plans to USB tether the VVX phones like we can with the Aries phones? I had an indication from one of the UK based Lync MVPs (at Polycom) that this was being worked on.Also, is it possible to sign into Lync remotely using the VVX phones?

The Aries phones can do it by signing in while tethered to a PC. It just gets the public Edge certificate. I am guessing that this might be tricky as well because the phone wouldn't have had any base config first and it won't have a DHCP server pointing to any of the options.

Hi Jeff,we provisioned Spectralink 8440 Handset with Lync 2013. The Handset contains the newest firmware. Updates to the Handset works great. IM/Presence work fine. External calls work but with a delay of 20-25sec. On internal calls there is no signaling on the handsets. All other Phones (Polycom CX500/600) works fine.The Handset doesn´t ring when there is a incoming call.The log of Lync 2013 shows a SIP 488 'not accetable here' during invite to the handset.

To the other devices not.Any ideas?Thanks for help.Regards Ralf. Hi Jeff,I stumbled onto your page via the almighty Google. What I was looking for was hinted at by you in regards to using a /firmware directory.This blog post is an excellent writeup and has a very clean and easy to follow information flow. Nice work!I would like my phones to FTP to the provisioning server and immediately be told to use another directory for firmware, logs and calls. When I configure the sip.ld with a specific path there is no problem getting the new application, logs go where I tell them and calls (lists) go where I tell them. There is only one hitch.Polycom phones (in this test I am using SPIP335's) BootROM updates appear to only search the FTP root for their specific 2345-12375-002.bootrom.ld or the base bootrom.ld files. Logs initially upload to the root of the FTP as well.I have read the 601 page admin guide – which seems to be not so detailed as the 601 pages would have one believe!

For example, it sure would be nice to understand those log files fully first entry appears to be time, but that 'Admin' guide never really covers that! I have also read several other tech papers from Polycom, but I am at a loss as to properly doing what you hinted at. I know this is 5 months old, but maybe just maybe you can point me in the right direction?

Jeff,I downloaded 5.0.2 for VVX split. After that, I downloaded 4.1.0 Rev I for IP 5000.I deleted all files except 00000000.cfg and custom.cfg files from ucs folder. Extracted files for 5.0.2 firmware and copied them into the ucs folder.

After that I extracted 4.1.0 firmware and copied 3111-30900-001.sip.ld file into the ucs folder.VVX phones work without any problems. IP 5000 phone gives message 'Image is not compatible' and rebooting without stopping. Not sure how to break rebooting.Any ideas? Greetings, Jeff! I am running into problems with a SoundPoint IP 450 and Lync 2013. I am attempting to use the base Lync option on the phone and have DHCP options 4 (time), 6 (DNS), 15 (DN), 42 (NTP), 43 (MSUCClient), 119 (DNS Search) and 120 (UCSipServer) configured on the DHCP server.I have successfully tested the DHCP options using the test-CsPhoneBootstrap option from a machine on the same subnet as the phone and I am able to get a Polycom VVX 500 working using all the same parameters. However, the recalcitrant 450 continually fails to download the internal Root CA certificate.

With the sip logging turned up to debug, it appears that the phone is not getting the 43 options from the DHCP server. The log entry'CreateFailOverProxyList: 'Auto Discovery' 0 DHCP servers recieved'is immediately followed by DNS SRV record lookups (the appropriate SRV records are in place).

Then the phone methodically trys to register with each of the seven IP addresses that are returned. Hi Jeff,Hope you can shed some light on an issue I've been running into. I've deployed a Polycom IP Soundstation 650 series phone for a user of mine.

The phone is registered to Lync 2013, inbound/outbound calling works and inbound calls that are transferred to another Lync user works. The only calling scenario that fails is dialing a Lync user directly from the phone. At first i noticed the 4 digit extension was not normalizing via the Lync dial plan to e.164 which I was able to resolve.So now when I dial the user, the phone rings once and then disconnects and the called user receives a missed call notification. Lync logging does not show the call at all, but it does show the Unified messaging transfer. The strange thing is that after the call is placed, the phone displays +9 and then changes to the called users SIP URI and then fails.Have you ever run into this before? Sorry for the long comment 🙂. Hi Jeff,This is a really helpful blog.

Thanks a lot for the good work.Here's my issue.We're on Lync 2013. Basically we're using 3 hard phones models.CX600SP331VVX300Initially we had to buy SP331 but in our environment, it's not practical to use SP 331 due to password expiration, etc. Basically we wanted PIN authentication. So we went for VVX300 with firmware version 5.0.1it works well.

We have only one centralized provisioning server. Now they're released new firmware versions for VVX300 and SP331. I want to update both phone models via same ftp server. But configuration files are different. How can I do this? What'd be the configurations?

How it identifies the phone model?Also now we can update VVX300 phones via Lync server 2013. That's only the firmware.

How i can update the config file? What's the purpose of DHCP option 66 and 160? Which one used for firmware update and which one for config update?Hope to have a complete explanation from you.Thank you very much.

Hi Jeff,Is there a way to edit the master file to not roll back firmware versions, the scenario I have is we want to use the provisioning server to download UCS5.x.x.x from 4.x.x and an configuration file for customisations for new shipping devices, after this we want Lync server to handle the firmware updates and leave the provisioning server for updating their config files. The issue I have is when Lync server updates the firmware, the provisioning server detects the latest version is different and rolls it back. We were hoping to enable paging on our new S4B deployment using VVX 410 phones. Well it works, but there is a big problem in that it changes the S4B user status (presence) of every user currently logged into one of the phones to ‘In a Call’ during the page, then ‘Available’ after the page is complete, regardless of what their previous status was – totally wiping out everyone’s ‘REAL’ status.Since the advanced status information that S4B provides was one of the major selling points for us, this is a no-go. Very disappointing.(tested up to UC firmware 5.4.0.5841). Hi Jeff,any idea why the Polycom VVX 300 might not pick up DHCP option 160?This is what I currently have configured under DHCP options:002 Time Offset004 Time server006 DNS server042 NTP server160 UCS Boot Server name.I have configured option 160 just as you have described but the phone does not seem to read option 160. HI Jeff,I’ve been following your blog for a while and its really an excellent source for solutions.I have been deploying hundreds of VVX500 phones in our lync 2013 environment and we are constantly plagued with the problem of intermittent logouts.

We are using UC5.1.1. Do you face this issue?Also, we are using the CommonAreaPhone profile on the lync for the phones. Is there a way where i can input the extension id and pin into the configuration file so that the phone will auto login when it powers up?Thanks in advance!

I would upgrade some phones to the more recent 5.2 release to see if that resolves the de-registration issues. Also 5.3 is right around the corner and offers further improvements.To pass the Phone Number and PIN to the phones via the provisioning server XML configuration files you can use a combination of the following parameters, based on if you just want to set the PIN and still allow NTLM to be used on the phone by other users, or if you want to force PIN auth only:reg.1.auth.usePinCredentials=”1″reg.1.auth.useLoginCredentials=”0″reg.1.auth.loginCredentialType=”3″reg.1.extension=””reg.1.pin=””. Hi, I had the same issue as well and finally found it is caused by the settings about provisioning polling:prov.polling.enable = 1prov.polling.mode = randomafter I disable the prov.polling = 0 the phones will not reboot again during the midnight.As per the Polycom UC Software Version 5.4.0 Administration Guide saying:Note: Only provision files when pollingIf prov.startupCheck.enabled=’0’ then Polycom phones do not look for the sip.ld or theconfiguration files when they are rebooted, lose power, or restarted. Instead, they look only whenreceiving a checksync message, a polling trigger, or a manually started update from the menu or webUI.Some files such as bitmaps,.wav, the local directory, and any custom ringtones are downloaded eachtime as they are stored in RAM and lost with every reboot.But I tried to unplug/replug the power cable or press the reboot button, the phone will automatically login BToE as my user accounts as well.

Our environment has the DHPC option enabled and provisioning server setup. I guess that enables the auto-login. Hi Jeff,This page is bible for Provisioning Polycom phones:).Just a question. We have huge number of devices running in 3.x.

I replaced FW in the root directory with latest 4.x and rebooted the devicesIts all upgrading but not connecting to Provisioning server. (Stays in a stage where it looks like a brand new device with new all option)All become normal if I do a second manual reboot. (Connects to Provisioning, Registering with Call server,Showing custom Home page).Do you have any idea about this behavior? Hello Jeff,Firstly, excellent article here, I’ve been meaning to tell you how much this article helps people new to the provisioning arena. I’m also looking forward to your on November 18th, that’ll be another step in the right direction for Polycom Provisioning.

I did want to note that anyone looking for true easy-to-use HTTP/HTTPS provisioning should take a look at Event Zero’s solution. We support all VVX, SoundPoint, RealPresence, Soundstation, and the CX5500 phones at this time.

I am one of the lead engineers on the project and it is a solution sanctioned by Polycom (they helped us build it). Anyone that is looking for an easy-to-use provisioning system for any number of phones should take a lookit’ll make your life MUCH easier, I promise. People can ping me at if there are questions around what it can do. Thanks again, again, nice work here. Great Articule about provisioning.We have already setup a provisioning server which is working great for a total of +600 VVX500. However, every week, on Wednesdays and Thursdays evening (around 20:30h) a set of phones stop working.

When you ping them they lose pings and it is imposible to use them Web interface is not availalbe during the outage.We have seen that the polling is set to 23:30h in a random way until 1:30am. The outage stops around 9:30 am and suddenly all the affected phones come back to normality: no packets lost and full operative. We have seen a significant number of tar.qz files in the provisioning server (around 2Mb each), but we do not know why they have been generated.Any ideas that may help us?Thanks. Hi Jeff,XML Notepad 2007: the version found on download.Microsoft.com is literally more than 10 years old now, and has many issues with loading and handling the 4 Megabyte.XSD XML schema definition coming in the Polycom software ZIP file. I found out recently, that an enthusiastic person has started to maintain this application, and fixed many bugs continuously. Are you using the old MSFT original version of this tool, or the newer one which is confusingly called via the same name, but has higher build number? IF/when you use a Firmware folder, and create subfolders for firmware, so firmware/5.7.2.1277 as an example.

Where do you need to move/copy the updated Config, Languages and VVXLocalization folders that are in the split zip file to? Do you need to keep them in the firmware/5.7.2.1277 folder, or do you need to keep them in the FTP root folder?I like organizing and maintaining previous versions in case of rollback, but I can’t seem to find where to keep those 3 folders located. I suspect Config needs to go to the Root, but something tells me that Language and VVXLocalization should go with the firmware version. Yes no, what’s best or correct? Managing Firmware Updates – It was mentioned that “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.”Two questions:1) Should the old.sip.ld files be deleted once the new ones are pasted in the directory?2) Once the firmware update files are pasted in the directorywill the phones automatically install the update and reboot after a period of time?Thanks,Ted.

Hey Jeff,Thanks for this. I’m having a strange problem and cannot figure it out.a. When I use option 160 with the IP for my FTP server, it works fine.b.

When i use option 160 with a string and “ftp://polycomprov” the phone fails to see the option 160 and doesn’t get the config.Polycomprov resolves to my server running the FTP. It’s the same IP as what works above in example a. Its seems that only IP’s work whereas hostnames or cnames do not work for me. I’m at an absolute loss to explain it.any ideas?Nick.

Please i need support for DHCP.we configured DHCP server for Polycom Phones.we have Avaya Access switch at my network.when i assigned voice VLAN member for single port at Avaya Access switch and connected Polycom phone it is takin IP from Voice VLAN and working fine.but when i connected to other Port which is member of PC and Voice VLAN it is taking IP from PC VLAN instead of Voice VLAN.All Avaya switch are support LDAP.is there any specific configuration need to run on Avaya switch for Polycom phones?? If yes what is that.we are using Polycom CX700A model phones. Hi, I had a question for you, I have made some changes with a polycom vvx 411 that is connected to fluentstream. I am totally blind and also for simplistic reasons I am writing information to the.cfg files.

I export the web.cfg and allsettings.cfg and set the prov server to just “”. Every time I reboot the phone it comes back in the files, but in the webgui it is still blank. It is also removed from the full phone backup.

Where is theis pesky setting hiding. Acustic fence is also doing the same thing.

All codecs and log changes I make are sticking.THanks.