Re: [CX700] Firmware 4.0.7577.4100 needed

CryoGenID · ‎08-05-2016

Hello everybody,

we have a few CX700 here which I have updated to the newest available firmware (which is currently 4.0.7577.4494) but they won't login to our hosted Lync/S4B hosting provider.

They say (those are not the exact messages, I try to remember them as good as possible) "Connecting NTP Server" for few seconds and then they display for a long time "Connecting to Lync Server".

After approx. 1 minute they jump back to the login screen and display a hint like "please make sure that the domain name is correct".

We still have two CX700 with an older Firmware (4.0.7577.4100) which can connect without any problems.

So I think the firmware is not compatible with our provider :-(

Unfortunately, the Microsoft servers only offer the newest firmware and not version "4.0.7577.4100".

Can anyone please help us out and give us the older firmware or help us to try and find out what the exact problem is?

Our hosting provider is NetTask (http://www.nettask.de/de/produkte-loesungen/hosted-lync.html).

Thanks a lot and best regards,

Christan

SteffenBaierUK · ‎08-05-2016

Hello Christan,

Polycom and other manufacturers produce these optimized for Microsoft® Lync® or Skype® for Business devices after a reference design and the embedded OS running on the phones is provided, supported and maintained by our partner Microsoft®.

You therefore may want to reach out to the Microsoft® community and / or Microsoft® support directly instead as this is the most direct and efficient path.

Polycom is unable to add any new features into the functionality of these CX Devices

Please try here

Polycom cannot provide this software and I suggest contacting Microsoft support if support is required.

Best Regards

Steffen Baier

----------------
The title Polycom Employee & Community Manager is a community setting and does not reflect my role. I am just a simple volunteer in the community like everybody else. All posts and words are my own & do not represent the views of Employer.

----------------

Notice: This community forum is not an official Poly support resource, thus responses from Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge. If you need immediate and/or official assistance please open a service ticket through your proper support channels.
Please also ensure you always check the VoIP , Video Endpoint , Skype for Business , PSTN or RPM FAQ's

CryoGenID · ‎08-05-2016

Hello Steffen,

thanks a lot for your quick reply.

I thought you might have all the firmware revisions somewhere on a drive in your company and could simply send me the .exe file :-)

But thanks for the link to the Microsoft site, I will try to contact them...

Thanks and best regards,

Christian

SteffenBaierUK · ‎08-05-2016

Hello Christian,

we, Polycom, do not host this software but a quick google search revealed a simple download link for 4.0.7577.4100

Best Regards

Steffen Baier

Polycom Global Services

----------------
The title Polycom Employee & Community Manager is a community setting and does not reflect my role. I am just a simple volunteer in the community like everybody else. All posts and words are my own & do not represent the views of Employer.

----------------

Notice: This community forum is not an official Poly support resource, thus responses from Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge. If you need immediate and/or official assistance please open a service ticket through your proper support channels.
Please also ensure you always check the VoIP , Video Endpoint , Skype for Business , PSTN or RPM FAQ's

CryoGenID · ‎08-07-2016

Hello Steffen,

thanks for your reply.

Well I had searched a lot for the firmware (hence the request in this forum) but all download links always went to Microsoft and they only offer the newest firmware (as far as I could find out).

We have fortunately been able to find out that the problem is because of the "Strict Domain Name Matching".

Our hosting provider was able to change the sip-DNS-Setting on the domain and now it works...

Hopefully this helps somebody else who has this problem...

Thanks and best regards,

Christian