Welcome
Guest
FAQ Forum Developers Sign In

How to configure Gigaset Maxwell Basic, 2, 3 and 4 for use with OpenScape Cloud

Last updated:

Tested models: Gigaset Maxwell Basic, 2, 3 and 4.

The phones have been tested with OpenScape Cloud with the following Software version:
  • Software version 2.22.7

The instructions provided below are likely valid for other software 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 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.

  • It is recommended that you perform a factory reset of your device, if the device has already been used in the past. This way, you can make sure that you have a smooth process of configuring your device without implications.

  • It is recommended that you make the latest available software update prior to any modification of the device configuration.

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. On the phone, press the button with the tick icon and select Settings > Local Network.
    2. Add manually all the information about the registered IP address. You can also see information about Mask, GW and DNS.
  3. Access the main web interface of the phone:
    1. Open a web browser on a computer located in the same network as the phone.
    2. Enter the phone’s IP adress in the browser’s address field: http://phone's_ip_address.

      The device’s web page will open.

    3. Select your preferred language from the Language drop down menu.
    4. Enter the password in the Password field.

      The default password is: admin

    5. Click Login.
  4. If you want to perform a reboot or do a factory reset of the phone via the phone’s web interface, navigate to System > Reboot and Reset and then:
    1. To reboot the phone, click Reboot system now.
    2. To reset the phone to its factory settings, click Reset to Factory Settings.
  5. Navigate to System > Firmware Update to update the phone’s firmware.
    1. Click Browse... next to User defined firmware files and select the Gigaset firmware file from your local computer.
    2. Click Set once you have selected the file to update the phone’s firmware.
  6. Navigate to System > Date and Time to view or edit information about the date and time.
    1. From the drop-down list next to Time Zone, select the UTC time zone for the phone.
    2. In the Automatically adjust clock for daylight saving changes field, select Yes.
    3. Click Set to save the changes.
  7. Navigate to Telephony > VoIP from the menu on the left and make the following settings:
    1. From the Transport Protocol drop-down list, select TCP.
      Note:

      Please note that in the current firmware the Transport Protocol can not be changed to TLS. The only available options are TCP and UDP.

    2. In the SIP Port field, enter the SIP server port you obtained from a Circuit domain administrator.
    3. In the Secure Real Time Protocol (SRTP) field, select Yes.
    4. In the Accept non-SRTP calls field, select No.
    5. From the SIP via TLS drop-don list, select On.
  8. Navigate to Telephony > Connections and make the following settings:
    1. On the Connections page, click the edit icon in the IP1 row.

      The IP1 Connection page opens.

    2. In the Authentication Name field, enter the SIP realm you obtained from a Circuit domain administrator.
    3. In the Authentication Password field, enter the user-specific password for SIP digest authentication you obtained from a Circuit domain administrator.
    4. In the Username field, enter the User ID you obtained from a Circuit domain administrator.
    5. 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.

    6. In the Domain and Registration Server fields, enter the SIP server address you obtained from a Circuit domain administrator.
    7. In the Registration Server Port field, enter the SIP server port you obtained from a Circuit domain administrator.
    8. Leave the Proxy server address and Proxy server port fields blank.
    9. In the Registration Refresh Time field, enter the time interval, in seconds, at which the phone should repeat the registration with the SIP server. You can leave this field to the default value, e.g. 180.
    10. Click Set to the bottom of the page to return to the Connections page.
    11. On the Connections page, when the IP1 connection is activated successfully, there will be a tick displayed in the corresponding Status and Active fields. The domain info will be also visible in the Domain field.
    12. Click Set to save the changes.
  9. Next, navigate to System > Security and do the following to install the RootCA.pem certificate on the phone:
    1. In the Accept all Certificates field, select No.
    2. In the Server Certificates and CA Certificates fields you can see the registered certificates followed by a green tick icon.
    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.

The phone is now configured for use with OpenScape Cloud.

 

Validation

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

  • Navigate to the Status tab on the upper right part of the phone’s web interface.

  • The account should display the indication Registered.

If the phone 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, make call swap, consult transfer, consult transfer on ringing (warm transfer), merge calls/conference, send DTMF tones (SBC allow all types i.e, RFC 2833), hold and resume a call and show SIP display name on the phone.

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

Please understand that some of the features the phone device might offer with other platforms might not be offered with OpenScape Cloud.
Note:

Currently, if you answer a call on the phone while you are signed in to Circuit or if you first answer the call on a Circuit client and then you push it to phone, the call drops. A fix for this will be delivered soon. As a workaround, you can either answer and handle the call entirely on a Circuit client or sign out from Circuit and then answer and handle the call on the phone.

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