How to configure Polycom VVX 150/250/350/450 for use with OpenScape Cloud

Last updated:

Tested model(s): Polycom VVX 150/250/350/450.

The phones has been tested with OpenScape Cloud with the following firmware: UC Software 5.8.0.13851 | BootROM Software 5.9.5.14816.

The instructions provided below are likely valid for other firmware versions or compatible devices but Unify will not validate it.

A 3rd party device configuration should be done by your ICT service partner or company administrator. Support from Unify for 3rd party devices is restricted to provide a generic configuration of OpenScape Cloud so that a device can be connected, and to operate the Cloud solution. If you have issues when setting up a 3rd party device, including its connection to OpenScape Cloud, or with its features and functions, please contact your 3rd party device supplier.

Prerequisites:
  • A Circuit domain administrator has assigned a phone number and desk phone to the user who will be using the phone.

  • Make sure you have the following SIP information:

    • User ID: this is usually identical to the phone number assigned to the user who will be using the phone.

    • User-specific password for SIP digest authentication.

    • SIP Realm.
    • SIP server address and port.

  • Make sure you have the necessary certificate for establishing a secure TLS connection to OpenScape Cloud: RootCA.pem.

SIP information and certificate is obtained in self service from Circuit domain administrators who need to navigate to Administration > Cloud telephony and then select the user who will be using the phone.

To configure the phone for use with OpenScape Cloud, perform the following steps:

  1. Connect the phone to the network and power source.
  2. Reset the phone to its factory defaults, if it has residual settings from previous configurations:
    1. Press the Menu key on the phone, and select Settings > Advanced.
    2. When prompted, enter the administrative password, and press the Enter soft key.

      The default administrative password is: 456

    3. Select Admin Settings > Reset to Defaults > Reset to Factory.
  3. Add an IP to the phone:
    1. Press the Menu key on the phone, and select Settings > Advanced.
    2. When prompted, enter the administrative password, and press the Enter soft key.
    3. Select Admin Settings > Network Configuration > Ethernet > IPv4 Config.
    4. Enter the preferred IP Addr, Sub Mask and IPv4 Gateway (recommended) or enable the DHCP option.
  4. If DHCP is enabled and working as expected, get the IP address of the phone:
    1. Press the Menu key on the phone, and select Settings > Status > Network > TCP/IP Parameters.
  5. Access the Polycom Web Configuration Utility of the phone by opening a Web browser on your local computer and entering the phone's IP address: http://phone's_ip_address. Then login as Admin.
  6. Navigate to Settings > SIP > Server 1 and make the following settings:
    1. In the Address field, enter the SIP server address you obtained from a Circuit domain administrator.
    2. In the Port field, enter the SIP port.
    3. From the drop-down list next to Transport, select TLS.
    4. Click Save.
  7. Navigate to Settings > Lines and make the following settings:
    1. In the Line 1 section, in the Display Name field, enter the name you want to appear on the phone display.

      It is recommended that you enter the full name of the user who will be using the phone as First Name <space> Last name.

    2. In the Address field, enter the User ID you obtained from a Circuit domain administrator.
    3. In the Authentication section, in the Domain field, enter the SIP Realm you obtained from a Circuit domain administrator.
    4. In the User ID field, enter the User ID you obtained from a Circuit domain administrator.
    5. In the Password field, enter the user-specific password for SIP digest authentication.
    6. Click Save.
  8. Navigate to Settings > Network > TLS > Certificate Configuration and do the following to install the RootCA.pem certificate on the phone:
    1. In the Platform CA 1 field, enter the URL where the certificate is currently stored:

      For example:

      http://<http_server_address>/RootCA.pem, if the certificate is stored to an HTTP server directory, or

      ftp://<ftp_server_address>/RootCA.pem, if the certificate is stored to an FTP server directory.

      If the certificate is not currently stored to an HTTP or FTP server, you can start Microsoft IIS or 3CDaemon on a computer located in the same network as the phone and place the certificate into its root directory.
    2. Click Install.
    3. Click Save.
  9. Navigate to Settings > Network > TLS > TLS Applications and make the following settings:
    1. From the second drop-down list next to SIP, select TLS 1.2.
    2. Leave all other drop-down lists to their default values.
    3. Make sure that the SIP check box next to Common Name Validation is un-ticked.
      Note:

      The tested firmware version does not support wildcard certificates, since it cannot validate the Common Name field.

    4. Click Save. Changing the Common Name Validation settings requires a phone reboot.
  10. Create a configuration file to enforce SRTP media on outbound calls:
    1. Copy the following text and save it to a new text file with extension .cfg on your local computer:
      <?xml version="1.0" standalone="yes"?><localcfg><sec.srtp.offer sec.srtp.offer="1">      </sec.srtp.offer></localcfg>
      
  11. Go back to the Polycom Web Configuration Utility, navigate to Utilities > Import & Export Configuration and do the following to import the configuration:
    1. In the Import Configuration section, click Choose File.
    2. On the File Upload dialog that opens, locate and select the .cfg file you have created, and click Open.
    3. Click Import.
  12. The phone may reboot automatically. If it does not, reboot manually the phone by selecting Utilities > Reboot Phone and clicking Yes to confirm.

Once rebooted, the phone is configured for use with OpenScape Cloud.

 

Validation

You can verify that the phone is successfully registered to OpenScape Cloud as follows:

  • The phone’s idle screen displays an icon with handset and check mark.

  • Place a call from and to the phone and make sure that the call is established.

If the phone is not successfully registered, please check your settings and network connection.

Note:

Video calls are not supported.

 

Further information

The following functionality has been tested:
  • Answer incoming call, reject incoming call, accept call, dial a number, do blind transfer, do warm transfer, consult, merge calls/conference, send DTMF (i.e. Dual-tone multifrequency signaling), hold and resume a call, show SIP display name on the phone, long duration calls, toggle between calls.

  • The following functionality has been tested with Circuit client in remote call: move call between phone and Circuit client(s), i.e. pull call from phone to Circuit client and push call from Circuit client to phone, answer incoming call, make a call, merge calls, transfer call, consult, hold and resume a call via Circuit, hunt groups.

If the device with the tested firmware version is added to a pickup group it does not support signaling of calls to be picked up from a team member. A call pickup is though possible by dialing the feature access code *7.

Please understand that some of the features the phone device might offer with other platforms might not be offered with OpenScape Cloud (for example, Message Waiting Indication - MWI).

0 people found this useful.
Me too / Not at all