Where is the new incompatible code markup documented?

[Anonymous]

For years I learned the polycom code markup and became comfortable with it.

Now it is gone away.

The internet only has mass volumes of the old (now invalid) non-backwards compatible code (because practically one else on earth has bothered to update)

Where has polycom documented the new code updated?

Mods here have only thusfar linked to volumes of marketing material and fillter baloney.

I need to decipher the new markup if we are to continue to purchase and use Polycom.

[SteffenBaierUK]

Hello all,

just to clarify above statements.

Polycom cannot be responsible for third party web site's hosting outdated information.

To get back to the originally mentioned facts I clarify yet again that since the introduction of UCS 3.3.0 extensive changes where made in regards how the phones are provisioned.

When attempting to download the software from the official Polycom support page the following disclaimer is shown and must be acknowledged before anyone is able to download the new UCS 3.3.0 Software:

PLEASE READ THIS NOTICE BEFORE ACCEPTING THE DOWNLOAD OF POLYCOM® UC SOFTWARE 3.3.0:

In UCS 3.3.0, the configuration files, their respective parameters and defaults, as well as the provisioning methods have been simplified but extensively modified compared to previous releases. SOME OF THESE CHANGES ARE NOT BACKWARD COMPATIBLE with configuration parameters from previous software releases.

Before downloading and installing the software, it is highly recommended that you first familiarize yourself with the changes outlined in the “Administrator’s Guide for the Polycom® UC Software – 3.3.0” and Technical Bulletin 60519 “Simplified Configuration Improvements in Polycom® UC Software 3.3.0”.

Use of the Software is subject to the terms and conditions of the End User License Agreement that accompanied the Polycom Product.

 I have read the notice and accept the responsibility for reviewing the extensive changes to the configuration parameters and processes that will affect the installation of the Polycom desktop phone products using UCS 3.3.0. 

The person downloading the software acknowledges the following:

• In UCS 3.3.0, the configuration files, their respective parameters and defaults, as well as the provisioning methods have been simplified but extensively modified compared to previous releases.

They in addition acknowledge:

• SOME OF THESE CHANGES ARE NOT BACKWARD COMPATIBLE with configuration parameters from previous software releases.

They are then asked, before downloading and installing the software,to first familiarize themselves with the:

• Administrator’s Guide for the Polycom® UC Software – 3.3.0
  
  and
  
  
• Technical Bulletin 60519 “Simplified Configuration Improvements in Polycom® UC Software 3.3.0”

Both of the above documents are detailed technical instructions and contain no marketing information.

The Technical Bulletin 60519 is a 46 page long document outlining all the changes and its reader should be fully aware and understand the changes and improvements that have been added.

The same Disclaimer is also valid for any software version UCS 4.0.0 and newer.

Since UCS 4.0.0 the Update Process for the Phones has changed so this additional disclaimer also needs to be acknowledged:

1) Before you can successfully install UC Software 4.0.x onto phones running Polycom® UCS released prior to version 4.0.0, you must perform a required upgrade procedure using the Polycom® Upgrader 4.0.0 Utility.

Before you download and install Polycom® UC Software version 4.0.x or higher, Polycom strongly recommends that you review the changes to the upgrade procedures detailed in the Polycom® UC Software 4.0.0 Administrators’ Guide or newer and Engineering Advisory 64731 Polycom® UC Software 4.0.0: Upgrade and Downgrade Methods.

Again none of the linked above documents contain any marketing information and are a simple instruction for professionals in order to enable them to upgrade their infrastructure and receive further usage for their originally purchased phones.

I hope above finally clarifies any misunderstandings that may have arisen.

In addition the cfcUtility has been released both as a windows and linux version so implementers following the correct standards can easily convert their own files.

The community FAQ and the Development section => here <= can be consulted.

Anything else needs to be addressed via a Polycom reseller, a support Ticket with Polycom directly or involve Polycom professional services.

Best Regards

Steffen Baier