Help us to improve our website!

We want to inspire you for our UCC solution! To do this, we use cookies to provide you with an optimal and personalised website experience. Clicking on "Accept all" allows us to process this data and share it with third-party providers in accordance with our privacy policy. Here you can also adjust the cookie settings at any time.
Technically necessary cookies
Statistics
Comfort
Accept all
Save selection

How do I configure Softphone Mobile?

 
 


This article is intended for partners who have already performed a project-specific release together with support.


Before the steps mentioned below can be carried out, an entry must be set in atlas.xml, which you currently only receive as part of the project-specific release.

Information on project-specific release can be found in the partner portal.



Before Softphone Mobile is activated, the basic function (device selection and AnyDevice calls) of the mobile app should ideally be available in V9.

If a message regarding missing devices appears in the Mobile Client, please check the points from the following article: https://www.c4b.com/en/knowledgebase/mobile-app/no-devices-mobile-app.php


Enabling the feature for sites and configuration groups

By default, the use of the Softphone Mobile feature is deactivated. The item can be enabled per configuration group or location. For example, open a location, navigate to Settings > Telephony and set the following check mark:

softphonemobile


Setting up the STUN server

In order to use Softphone Mobile, it is mandatory to configure a STUN server. We recommend the Sipgate STUN server, but any other STUN can also be used. Proceed as follows:

  1. Navigate to Telephony & Meetings > Network
  2. Click on "Add..." for the STUN server.
  3. Set the name, FQDN/IP and port e.g.:
STUN

4. click Apply, and then click Save on the Network page.
5. open the SIP gateway under Telephony & Meetings > Telephony > SIP
6. check the box "Use STUN Server" and save the setting (Attention: triggers a SIP gateway reboot)

stun


If required: Configuration of the ACL's (white and black list).

If you or your customer should work e.g. via VPN or if there should be other special features in the network, the ACL's must be adapted. We distinguish two areas here:


Private IP address ranges (whitelist)

It is mandatory to enter the private address range (trusted network) configured in the company here. This configuration is used to detect which communication subscribers are located in the internal network (LAN, VPN). This ensures that for softphone calls of all types, the audio-media connection remains within the company network.

What must be entered?

  • Local client IP address ranges of the company network
  • Loopback address 127.0.0.1 (if the XCC is not outsourced)
  • VPN address (if no payload separation is planned)


Access control via IP address ranges (blacklist)

The networks listed here are not used for media communication. IP addresses from these ranges are not considered when negotiating the possible RTP connection candidates. List networks here that are not or should not be VoIP-capable.

Note: The whitelist entries prick the blacklist entries.


When all the above steps have been performed, the Mobile Client can be restarted and the function tested.

Subscribe to our Newsletter

 
 
 
 
 
 
 

Thank you for subscribing. To confirm your subscription, please click the link in your registration email.

 
 

An error occured. Please try again.