Search instead for. Did you mean:. Phone cannot download cfg file from server. Go to solution. Frequent Visitor.
Hello, I wanted to setup phones Soundpoint IP using config files from server. I'd be very grateful for any advice. Thanks Solved! Message 1 of 6. All forum topics Previous Topic Next Topic. Accepted Solutions. Re: Phone cannot download cfg file from server. Thank you for help anyway Steffen! Message 3 of 6. I am just a simple volunteer in the community like everybody else.
Message 2 of 6. Message 4 of 6. Step 6. Right click in the pop up window then click Select All. Step 7. Right click in the pop up window again then click Copy. Tip : There will be a lot of traffic if the pcap is not gathered directly from the phone. This problem is bypassed by filtering the pcap using the MAC address of the phone or the ip address of the phone Example : eth.
Skip to content Skip to search Skip to footer. Available Languages. Download Options. Updated: October 20, Contents Introduction. Introduction This document describes two ways to obtain a phone's configuration file.
LYNC , device , registration have no special meaning and are only provided as a way to organize groups of parameters for easy reading. Any name could be used, or if desired all parameters could be defined under the primary Lync tag as the file hierarchy is also not important. The phone will simply read in all defined parameters in the file as long as at least one tag is defined.
The device configuration file example in the next section will use this approach to illustrate that either format is acceptable.
At this point the phones have enough information to register to Lync Server and it would be possible to simply enter the SIP address and user credentials for a Lync User directly on the phone itself.
Now is a good time to validate that this is functional in the environment before moving on to provisioning any additional account registration information. After the device completes rebooting it should have picked up the new configuration options in the shared file which will trigger Lync mode then default to the displaying the Sign In menu.
The Config value should show the name of the shared configuration file as well as the number of parameters imported from each source. The 5 parameters configured in the shared. Moving on with the automatic provisioning process for the phones there are two options available for providing credentials to the phone instead of having to enter them manually into the device itself. One approach can be used to send the full set of credentials to the device, including the password, for a zero-touch administration scenario by defining per-line registration parameters.
In this scenario the credentials cannot be viewed or managed directly on the device so this is typically intended for devices used in common areas or meetings rooms where the associated AD account can be configured with either no password expiry or the central configuration files can be updated with new password by an administrator.
It is not possible to send the password using this approach but the rest of the credentials can be pre-configured.
This would provide a near-complete provisioning process in which the end-user is responsible for entering only their password into the phone to complete 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 two separate phones. The VVX 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 phone. Additionally a SoundPoint IP 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. 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.
Although most any name can be chosen the suffixes of -phone and -web are reserved for special files that the phone manages itself. The examples throughout this article will 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.
That file would need to basically be a duplicate of the generic Notice that although the SIP address is stored in a line registration parameter reg. The Config value will now 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. The obvious benefit of this scenario is that the end-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 AD user account the phone will remain connected to Lync and still be able to register even after rebooting the phone.
This is because after the initial registration with user credentials the phone will be issued a client certificate by the Lync Server and then use TLS-DSK for all subsequent authentication attempts. The following set of parameters will be used for the SoundPoint IP device file to fully provision the entire set of user credentials to a phone and trigger an automatic registration. Using this approach requires that the previously used Login Credential feature of the phone is disabled and the user credentials are stored in the registration parameters for a specific phone line reg.
Because the full set of credentials have been supplied in the line registration parameters then the phone should have automatically registered successfully after resetting.
The SoundPoint IP models do not currently support PIN Authentication so the parameter to disable that feature will not be recognized, resulting in 1 error reported in the shared configuration file. Make sure never to simply copy over all the files though as this might overwrite a customized master configuration file and break the integration; only use the firmware files provided in the package. As long as the firmware file stored on the server is a different version, newer or older, than what the device currently has installed then it will download and update the firmware automatically at the next reboot.
The following table can be used as a reference for the latest recommended versions of each model phone for Lync interoperability.
The uncompressed file size of each firmware image is also provided as a way to help identify which release package an individual file might be from. All of the devices listed above are currently qualified for both Lync and environments when running on at least the firmware versions indicated.
About Jeff Schertz Site Administrator. Great post. Can you please shed some light on the Exchange calendar integration for VVX ? Right now, I have followed the instructions and modified features,cfg and applications. The configuration is no different that what I covered in a previous article.
This only works when the user credentials are stored in the phone's Login Credential section and is not available if you are only using PIN Authentication just like Lync Phone Edition. Any updates on this Calendar issue? I am also storing my NTLM creds in the phone. Error is Status: Exchange Calendar regestration has failed. I'm not sure what the issue is but if you are using the same credentials for Lync and Exchange and storing them in the phone's Login Credentials' menu then it should work using the standard Exchange Web Services URL for your deployment.
What DHCP product are you using on the network? All products I've used will provide 43 before so it's possible that the phone is not handling the opposite order correctly. Yes, these are supported but the software does not currently support shared or bridged line capabilities. Adding the sidecars will simply provide contact presence, one-button calling, and easy call transfer capabilities with multiple Lync contacts today. Hi Jeff. I have them both registering to Lync and able to make calls.
The problem is they can't receive calls from PSTN. Any ideas? There appears to be an interaction the Lync encryption setting and our gateway that prevents calls to the Polycom IP phones from completing.
This also solves the problem where media bypass didn't work from the gateway to internal phones. We are having the same issue. Out of interest, did you have to do reboots and stuff after making the changes? After line registration it is possible to perform just one single call. It seems like Lync is "forgetting" our registration to the system after one successfull call. Have you ever seen this kind of problem?
However, today I logged out my phone and tried to log it back in and I started to get that message on the screen:. If you are registering to the same Lync environment that should not happen, I suggest performing a factory reset of the phone and running through the provisioning steps again. Yes, check your configuration. 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. Is there another way than to manually enter the FTP Credentials on every phone? TFTP is also not an option. 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.
The phone also supports plain-old http. True, but that require configuring each phone manually to update the credentials which is not ideal for large deployments. I followed this article and something does not work for me.
I am at the point where I created shared. 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. 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.
I suggest using the basic out-of-the-box method with a reset-to-factory-defaults device and make sure that registration works as it should before attempting to setup and configuration files for additional, no registration feature you may want to control. Hi Schertz This is a great post. I have concern that if I have multiple version of Polycom in system. Can all Polycom phone version register correctly? Thanks a lot. You can mix versions for different device models if you like but you can only have one file version per device.
Thanks Mean that the device can choose which file that is right to them for register, am I correct? And from your post, I understand that some old version of Polycom phone can also register to Lync system too.
Is that correct? Thanks a lot Jeffschertz, you help me out a lot by your post. Hi — Do you know how I might be able to get all Polycom IP phones to reboot at the same time remotely to pick up a new. I am finding it impossible to find this information assuming it's possible , and just wondered if there was some way to do this system wide? There are a few methods available or doing this. Or you can use the 'prov.
Hi Schertz Please help me out this problem. I can use CX connect and sign in to Lync normally, make call from phone to PC and vice versa. 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 VVX, IP …without any solutions Thanks for your help a lot.
I suggest that you contact your official support channel which will be glad to assist in getting the phones registered. There are a few unique requirements to each platform. Great article as always. 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. Yes, the upcoming UCS 5. It works in my office but cannot get it to work when plugged into my home network. The CX phone that I have works fine internally and externally. The configuration is no different. Most likely your Lync server certificate configuration is causing this issue.
You may be using an untrusted certificate on the external Edge interface in which the phone cannot automatically download and trust when connecting from the Internet.
When connected internally a few mechanisms are leveraged by the phone to locate and down the certificate chain used on the internal Lync servers. The Handset contains the newest firmware. Updates to the Handset works great. External calls work but with a delay of sec. On internal calls there is no signaling on the handsets. The log of Lync shows a SIP "not accetable here" during invite to the handset. To the other devices not. Ralf, I have not used the latest firmware since SpectraLink became their own company so I'm not familiar with any changes or issues in the latest releases.
I stumbled onto your page via the almighty Google. 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. There is only one hitch.
Logs initially upload to the root of the FTP as well. I have read the page admin guide — which seems to be not so detailed as the 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? If you are referring to the one-time upgrade of the BootROM when moving from 3. Best practice is to leave all sip. If so you need to trigger a re-registration of the phone to Lync to pick up changes to contacts which are actually stored in Exchange instead of Lync directly.
You can change the passwords for the default user and admin accounts, but not the account names themselves. Yes, as long as 4. We have Lync Environment.
How do you update firmware for phones that require different firmware? VVX phones need 5. IP phones need 4. Eric, you can mix and match the different firmware files for each phone to use the version you want for each model.
Thank you for your reply. Can you point me to the right direction? Just making sure that all I have to do it upload V5. Is this correct? One more question. After I updated phones to v5. Unfortunately, phones lose options that I added in custom. For example, one of the options that I enabled was BToE. When new firmware comes from Lync update, BToE is not enabled anymore. It looks like it resets it to default values. Some of the BToE parameters and their default where changed in that release, so I would recommend wiping the configuration on the phone and updating your custom config with only the needed settings.
I downloaded 5. After that, I downloaded 4. I deleted all files except Extracted files for 5. After that I extracted 4. VVX phones work without any problems. IP phone gives message "Image is not compatible" and rebooting without stopping. Not sure how to break rebooting.
Greetings, Jeff! However, the recalcitrant 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. Then the phone methodically trys to register with each of the seven IP addresses that are returned.
After the first attempt fails due to the untrusted certificate, the phone attempts to download the server root certificate, but fails:. Hope you can shed some light on an issue I've been running into.
I've deployed a Polycom IP Soundstation series phone for a user of mine. 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. 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.
If your Dial Plan normalization patterns include any Polycom unsupported characters this can prevent the phone from handling the call correctly. The numbers seem to normalize correctly lync dial plans being used are very standard.
Hi Jeff, This is a really helpful blog. Thanks a lot for the good work. Here's my issue. We're on Lync Basically we're using 3 hard phones models. Basically we wanted PIN authentication. So we went for VVX with firmware version 5. We have only one centralized provisioning server. I want to update both phone models via same ftp server. How can I do this? How it identifies the phone model?
Also now we can update VVX phones via Lync server Hope to have a complete explanation from you. Thank you very much. The approach here would be to only place the SPIP firmware. If the VVX phones do not see their firmware files stored on the provisioning server they still use it for configuration data just fine. Another question. That'd be really helpful.
0コメント