How to configure Mediatrix S7, C711 & 4102S as Analog Terminal Adapter for use with OpenScape Cloud

Last updated:

Tested model(s): Mediatrix S7, C711 & 4102S.

The Mediatrix units have been tested with OpenScape Cloud with the following firmware: Dgw 2.0.41.762.

The instructions provided below are likely valid for other firmware versions 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 Mediatrix unit is connected to the network and powered on.

  • Analog phones or fax machines are connected to FXS ports.

  • System date and time is configured on the Mediatrix unit.

  • Make sure you have the following information about the Mediatrix unit:

    • IP address of the Mediatrix unit LAN Interface. The default one is: 192.168.0.10

    • FXS port numbers used.

  • Users who will be using an analog device connected to the Mediatrix unit are assigned a phone number and desk phone via Circuit by a domain administrator.

  • Make sure you have the following SIP information:

    • SIP server address.

    • SIP realm.

    • SIP digest authentication credentials for every user who will be using an analog device connected to the unit, i.e. SIP User ID and password of each endpoint entry.

      The SIP User ID is usually identical to the phone number assigned to the user.

  • 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 an analog device connected to the Mediatrix unit.

To configure the Mediatrix unit for use with OpenScape Cloud, perform the following steps. For further guidance, watch our YouTube video.

  1. Log on to the Mediatrix unit Web Interface:
    1. Open a web browser on a computer located in the same network as the Mediatrix unit, and enter the IP address of the Mediatrix unit in the address field.
    2. Enter the user name public and leave the password field empty, for the default credentials. You can alternatively use admin as user name and administrator as password. Both accounts have administrator rights.
    3. Click Login.
  2. Configure the Default Gateway:
    1. Navigate to SIP > Gateways.
    2. In the Gateway Configuration table, leave the Type drop-down list to its default value Trunk.
    3. In the Port field, enter 5060 as the listening port the gateway will be using for unsecure SIP traffic.
    4. In the Secure port field, enter 65061 as the listening port the gateway will be using for secure SIP traffic.
    5. Click Apply.
  3. Configure the Default Servers:
    1. Navigate to SIP > Servers.
    2. In the Default Servers table, in the Registrar Host and Proxy Host fields, enter the SIP server address you obtained from a Circuit domain administrator.
    3. In the Keep Alive table, from the Keep Alive Method drop-down list, select SIP OPTIONS.
    4. In the Keep Alive Interval (s) field, enter the interval in seconds at which SIP Keep Alive requests are sent to verify the server status, e.g. 30.
    5. From the Keep Alive Destination drop-down list, select First SIP Destination.
    6. Click Apply.
    Note:

    When you apply changes to the configuration, the Mediatrix unit validates them and if a service must be restarted, a message with a restart required services link appears at the top of the page. Click the link to restart them.

  4. Configure the SIP Transport parameters:
    1. Navigate to SIP > Transport.
    2. In the General Configuration table, from the Add SIP Transport in Registration drop-down list, select Enable.
    3. From the Add SIP Transport in Contact Header drop-down list, select Enable.
    4. In the Persistent Base Port field, enter the base port the unit will be using to establish persistent connections with SIP servers, e.g. 16000.
    5. In the Fallback Interval field, enter the interval in seconds before the unit retries to establish a persistent connection, e.g. 15.
    6. From the TLS Certificate Trust Level drop-down list, select Locally Trusted.
    7. In the TCP Connect Timeout field, enter the maximum time, in seconds, the unit should try to establish a TCP connection to SIP servers, e.g. 189.
    8. In the Protocol Configuration table, from the TLS drop-down list, select Enable.
    9. Click Apply.
  5. Register the necessary endpoints to all gateways:
    1. Navigate to SIP > Registrations.
    2. In the Endpoints Registration table, in the User Name and Friendly Name fields, enter the User ID you obtained from a Circuit domain administrator for each endpoint needing registration.
    3. From the Register drop-down list, select Enable.
    4. From the Messaging drop-down list, select Disable.
    5. From the Gateway Name drop-down list, select all.
    6. Click Apply & Refresh.
  6. Configure the endpoint authentication:
    1. Navigate to SIP > Authentication.
    2. Click Edit All Entries at the bottom of the page. You can alternatively click the pencil icon at the end of a row to edit the corresponding single authentication entry.
    3. From the Criteria drop-down list, select Endpoint for all endpoints requiring authentication.
    4. From the Endpoint drop-down list, select the FXS port for each entry.
    5. From the Validate Realm drop-down list, select Enable.
    6. In the Realm field, enter the SIP realm you obtained from a Circuit domain administrator, i.e.: Unify
    7. In the User Name field, enter the User ID you obtained from a Circuit domain administrator for each entry.
    8. In the Password field, enter the SIP authentication password you obtained from a Circuit domain administrator for each entry.
    9. Click Apply & Refresh registration.
  7. Configure the interoperability parameters:
    1. Navigate to SIP > Interop.
    2. In the Behavior on T.38 INVITE Not Accepted table, from all the drop-down lists (406, 415, 488, and 606), select Re-INVITE For Clear Channel Only.
    3. In the SIP Interop table, from the Secure Header drop-down list, select Enable.
    4. From the Default Username Value drop-down list, select Anonymous.
    5. From the OPTIONS Method Support drop-down list, select Always 200 OK.
    6. Leave the Ignore OPTIONS on no Usuable Endpoints drop-down list to the default value Disable.
    7. Leave the SIP URI User Parameter Value field blank.
    8. From the Behavior on Machine Detection drop-down list, select RE-INVITE on Fax T38 Only.
    9. From the Registration Contact Matching drop-down list, select Strict.
    10. In the Transmission Timeout field, enter the time, in seconds, to wait for a response or an acknowledgement before considering a transaction timed out, e.g. 32. Acceptable values are from 1 to 32 seconds.
    11. In the SDP Interop table, from the Answer Codec Negotiation drop-down list, select All Common - Local Priority.
    12. From the Enforce Offer Answer Model drop-down list, select Disable.
    13. From the Allow Audio and Image Negotiation drop-down list, select Disable offer.
    14. From the Allow Multiple Active Media in Answer drop-down list, select Enable.
    15. In the to TLS Interop table, from the Certificate Validation drop-down list, select Trusted certificate.
    16. In the Misc Interop table, from the Escape Pound (#) in SIP URI Username drop-down list, select Enable.
    17. Click Apply.
  8. Enable the G.711, G.729 and T.38 codecs as follows:
    1. Navigate to Media > Codecs.
    2. In the Select Endpoint drop-down list, make sure that Default is selected.
    3. In the Codec table, locate the entries for the G.711 a-Law and G.711 u-Law, and from the Voice and Data drop-down lists select Enable.
    4. Locate the entry for the G.729 codec, and from the Voice drop-down list select Enable.
    5. Locate the entry for the T.38 codec, and from the Data drop-down list select Enable.
    6. In the Generic Voice Activity Detection (VAD) table, from the Enable (G.711 and G.726) drop-down list, select Conservative (recommended).
    7. Click Apply.
  9. Configure the security parameters:
    1. Navigate to Media > Security.
    2. In the Select endpoint drop-down list, make sure that Default is selected.
    3. From the Mode drop-down list, select Secure.
    4. From the Key Management Protocol drop-down list, select SDES.
    5. From the Encryption drop-down list, select AES_CM_128.
    6. From the T.38 drop-down list, select Yes.
    7. Click Apply.
  10. Configure parameters that apply to all codecs:
    1. Navigate to Media > Misc.
    2. In the Select Endpoint drop-down list, make sure that Default is selected.
    3. In the DTMF Transport table, from the Transport Method drop-down list, select Out-of-Band using RTP.
    4. In the Payload Type field, enter 96 or 101 as the actual RTP dynamic payload type used.
    5. In the Machine Detection table, from the CNG Tone Detection, CED Tone Detection and V.21 Modulation Detection drop-down lists, select Enable.
    6. From the Behavior On CED Tone Detection drop-down list, select Fax mode.
    7. In the Base Ports table, in the RTP field, enter the default RTP base port 5004.
    8. In the SRTP field, enter the default SRTP base port 5004.
    9. In the T.38 field, enter the default T.38 base port 6004.
    10. Click Apply.
  11. Configure the DTMF maps:
    1. Navigate to Telephony > DTMF Maps.
    2. In the DTMF Map drop-down list, make sure that Allowed is selected.
    3. In the Allowed DTMF Map table, locate the entries for the DTMF Maps *x.T, #x.T and x.T. and from the Enable drop-down list, select Enable.
    4. From the Apply To drop-down list, select Unit.
    5. Click Apply.
  12. Install the RootCA.pem certificate:
    1. Navigate to Management > Certificates.
    2. In the Certificate Import Through Web Browser table, from the drop-down list Type select Other.
    3. Click Browse.
    4. 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.
    5. Click Import.
    6. Click Apply.

      You can see the newly imported certificate added into the Other Certificates table.

    The Mediatrix unit is now configured for OpenScape Cloud and the analog devices connected to the unit can be used with OpenScape Cloud.

Validation

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

  • Navigate to SIP > Servers and check the state of the connection to the OpenScape Cloud SIP Server in the TLS Persistent Connection Status table. The state should be Up.

You can verify that the endpoints are successfully registered to OpenScape Cloud as follows:

  • Navigate to SIP > Registrations and check the registration status of the endpoints you have previously configured in the Endpoints Registration Status table. The status should be Registered.

  • Place a call from and to an analog device connected to the Mediatrix unit and make sure that the call is established.

If the Mediatrix unit or an endpoint is not successfully registered, please check the settings, cabling and network connection.

Tip:

Video calls are not supported.

Further information

The following functionality has been tested:
  • Answer incoming call, reject incoming call, accept call, dial a number, hold and retrieve a call.

  • Send and receive FAX. This applies only to FAX machines.

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