How to configure Ascom Myco V10.1.0 VoWiFi for use with OpenScape Cloud

Last updated:
Ascom Myco is a smartphone for nurses, caregivers and clinicians. Its Wi-Fi version is designed to be part of a Voice over Wi-Fi (VoWiFi) system providing wireless IP-telephony, messaging, and alarm functions to enterprise LANs.
Figure 1. Ascom Myco and OpenScape Cloud reference configuration
The Ascom Myco WiFi Smartphones, referred to as "handsets", connect to the enterprise LAN via Access Points, as depicted in the figure above. The handsets can be configured using the Device Manager, an application that runs in the Unite Connectivity Manager (Unite CM), the core software platform in the Ascom system.

This guide describes how to access and configure an Ascom Myco WiFi Smartphone for use with OpenScape Cloud via the Device Manager. The Access Point and Unite CM configuration is out of scope of this guide.

Tested model: Ascom Myco V10.1.0 VoWiFi.

The handset has been tested with OpenScape Cloud with the following software: SIP App v2.2, WiFi version 4.3.j.

The instructions provided below are likely valid for other software versions or compatible handsets 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:
  • The Wi-Fi network is available and working.

  • The Ascom Unite CM box is connected to the Local Area Network and you know its IP address.

  • The MAC address of the handset has been added to the wireless Access Point.

  • The handset has been setup after a factory reset and can be discovered by the Device Manager in Unite CM.

  • The software of the handset has been upgraded to the most recent version.

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

  • 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 handset.

    • User-specific password for SIP digest authentication.

    • 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 device for use with OpenScape Cloud, perform the following steps:

  1. Access the Unite Connectivity Manager:
    1. Open a web browser on a computer located in the same network as the Unite CM, and enter its IP address in the address field: http://Unite_CM_ip_address
    2. Enter the required credentials in the User name and Password fields.

      The default credentials are:

      • User name: admin

      • Password: changeme

    3. Click Log in.

    The start page of the Unite CM will be shown.

  2. Click Device Manager.

    The Ascom Device Manager application will open to the Devices tab, showing all devices discovered.

  3. Do the following to install the RootCA.pem certificate on the Myco handset you want to register to OpenScape Cloud:
    1. Right click on the handset in the list and select Manage Certificates....

      The Manage Certificates window will open to the Trust list tab.

    2. Click Browse next to Trusted certificate.
    3. On the File Upload dialog that opens, locate and select the RootCA.pem certificate you obtained from a Circuit domain administrator and stored on your local computer, and click Open.

      A Confirm Certificate window opens showing the details of the certificate.

    4. Import the certificate to the handset by clicking Yes.
    5. Go to the Application certificates tab in the Manage Certificates window.
    6. Repeat sub-steps b - d.
    7. Click Close.
  4. Click the Numbers tab of the Device Manager.
  5. Right click on the handset in the list and select Edit parameters....

    The Edit parameters for <number> window will open, where <number> is the number associated with the handset.

  6. From the configuration tree in the left pane, navigate to Telephony > Ascom VoIP and make the following settings in the right pane:
    1. Set SIP Transport to TLS.
    2. Set Trusted TLS certificate to RootCA.pem.
    3. In the Primary SIP proxy field, enter the SIP server address you obtained from a Circuit domain administrator.
    4. In the Listening port field, enter the SIP port of the OpenScape Cloud SIP Server you obtained from a Circuit domain administrator.
    5. In the Endpoint ID field, enter the User ID you obtained from a Circuit domain administrator.
    6. In the Password field, enter the user-specific password for SIP digest authentication you obtained from a Circuit domain administrator.
    7. In the VoIP phone number field, enter the User ID again.
    8. Set Secure RTP mode Proxy to AES_CM_128_HMAC_SHA1_80.
    9. Set Secure audio negotiation to Optional encryption.
  7. From the configuration tree in the left pane navigate to Display > Owner ID/name and make the following setting in the right pane:
    1. Enter the name you want to appear on the handset’s lock and charging screens.

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

  8. From the configuration tree in the left pane navigate to Time & Date and make the following settings in the right pane:
    1. Leave the *Use 24-hour format field to the default value Yes.
    2. Leave the *Choose date format field to the default value Regional.
    3. Leave the Automatic date & time and Automatic time zone fields to the default value Enable.
    4. In the NTP server address field, enter the address of an NTP Server.

    Make sure the date and time is set correctly on the handset, otherwise a secure connection to OpenScape Cloud could not be established.

  9. Click OK.

The handset is now configured for use with OpenScape Cloud.

Validation

You can verify that the device is successfully registered to OpenScape Cloud as follows:
  • If the device is not successfully registered, a warning message will appear on the screen mentioning that no phone calls can be made.

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

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

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 device.Please understand that some of the features the device might offer with other platforms might not be offered with OpenScape Cloud.

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