Build number 1080

  • new feature: self-managed telecom API implemented (working from Android Pie +). CallKit-like feature for Android.
  • new feature: obtain user's GPS location when call is made, or even make GPS location mandatory for making calls
  • new feature: global external provisioning now allows enabling/disabling CS features per user
  • new feature: DFKS (server-side DND and call forwarding)

  • improved Opus codec quality. We found and fixed an issue with Opus codec which added occasional static-like noise into outgoing voice stream.

  • DTMF digits can be sent when call is on hold
  • messaging chat balloons graphics improved. Full theming now possible via theme editor.
  • fixed G729 per-user licensing issue
  • fixed issue with SIP User-Agent header. In some cases, wrong version of the app was sent.
  • fixed jitter calculation, the value shown in GUI was too high. This had no impact on voice quality though.
  • added support for Diversion: SIP header
  • added support for apps which are distributed preinstalled in Android device ROM. Contact us for more details.
  • volume button can now be used to silence the ringtone
  • power button can be used to hang up. This can be configured in Android accessibility settings.
  • improved translations
  • many small GUI, performance and stability improvements

  • implemented RFC 7714 Errata 4938 which change the way how padding should be applied in AES-GCM ciphers. This change makes Cloud Softphone compatible with all libSrtp based apps, but breaks compatibility with older Acrobits apps. The impact should be minimal though, as the affected ciphers are disabled by default.

Note that due to the Google Policy changes, we had to remove PROCESS_OUTGOING_CALLS and WRITE_CALL_LOG permissions from Android app. Apps with this permissions are subject to Google approval and we were not able to get one for Cloud Softphone. This may affect features like writing to native call history or intercepting calls made in native dialer and completing them via the app. These permissions can be enabled in "White Label" configuration step, but you will need to either distribute the app outside of Google Play, or negotiate an exception with Google during their review process.