What are the minimum requirements for a SIP device to connect to OpenScape Cloud?

Last updated:

Unify operates OpenScape Cloud and provides a generic configuration of its solution so that a 3rd party device can be connected. Support from Unify for 3rd party devices is restricted to allowing them to connect to OpenScape Cloud. 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.

Exceptions might apply if Unify agreed to indirect channel partners or device vendors to help with validation. This page is published for this purpose. Unify supports partners with a test list and procedure description and special system access on demand – connectivity tests should not be performed with Unify’s productive cloud systems.

In order for a device (SIP phone or VoIP gateway) to connect to and be used with OpenScape Cloud, the following requirements must be met at a minimum:

  1. The device must support and be configured to use SRTP only (Secure Real-time Transport Protocol) for all media streams [single “m=” line in the SDP (Session Description Protocol)].

  2. The device must support and be configured to use the SDES (Security DEScriptions) key management protocol for SRTP.

  3. The device must be configured to use SIP (Session Initiation Protocol) over TLS (Transport Layer Security). TLS v1.2 is required.

  4. The device must support and be configured to enable HTTP Digest authentication.

    The digest authentication credentials are unique for each OpenScape Cloud user.

  5. The device must support and be configured to use wildcard type of TLS certificates and allow a TLS connection only if the certificate is trusted (trusted certificates). Additionally, it is highly recommended that the device is configured to perform common name validation.

  6. The device should support entering the FQDN (Fully Qualified Domain Name) of the SIP server and SIP registrar server. Connection to DNS is, thus, needed. Connection to DHCP is also needed, if DCHP is available on the network. If not, the device must be manually configured with a static IP address, netmask and default gateway address.

    If entering the FQDN of the SIP server and SIP registrar server is not possible, then the IP address of the SIP server must be entered while configuring the device, but the common name validation of the trusted certificate must be disabled.

  7. The device must be configured with an IP v4 address.

  8. The device should be configured to refresh the registration every 3600 seconds at the latest, i.e. Registration expiry time = 3600 sec.

    If local firewall or NAT devices cut idle connections to OpenScape Cloud, a smaller time interval might be required but please select the largest possible. For more network requirements, please refer to the Circuit Design Assessment.

  9. The device should support and be configured to use the following codecs: G.711 (a-law, u-law), G.722 and Opus, if possible. Also, G.711 and T.38 for Mediatrix.

    G.711 (a-law, u-law), G.722 and Opus are preferred because they are used end-to-end with both our soft phones and desk phones. Thus, no transcoding is required and there is no degradation in voice quality.

    Other codecs could be used only for calls to or from the TDM (Time Division Multiplexing) network.

  10. The device must be configured to use an NTP (Network Time Protocol) server such as pool.ntp.org or europe.pool.ntp.org.

    An NTP server is required as the device must synchronize time so that it can securely connect to OpenScape Cloud.

  11. It is recommended that daylight saving is enabled on the device.

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