Documentation
 Discord
 Login
Cloudonix Logo
  
Sales
 Signup
  
Cloudonix Logo
Knowledge Center
Cubed Mobile™
An enterprise BYOD communications mobile application for hybrid workforce.
Knowledge Center
Cubed Mobile™
An enterprise BYOD communications mobile application for hybrid workforce.
Knowledge Center
Cubed Mobile™
An enterprise BYOD communications mobile application for hybrid workforce.

Cubed Mobile

Company Overview

Company Name: Cubed Mobile Ltd
Location: Global
Website: https://cubedmobile.com/
Product Name: Cubed Mobile

Product Description

With Cubed Mobile, your employees will not need a second device or SIM card, and their personal and work spaces will be kept separate and safe.

The Challenge

Key Issues

Cubed Mobile needed a platform that was clear, simple, private, and safe so they could meet their cutting edge communication needs. After looking at a number of service platforms, such as Twilio®, Plivo®, and SignalWire®, Cubed Mobile chose Cloudonix as the best solution for its global communications network.

  • Power Consumption
    The device required the communications solution to be power efficient and not battery consuming.
  • Network Utilization
    The devices required the communications solution to be network efficient. Data usage needed to be controlled and contained.
  • Privacy and Security
    Cubed Mobile required a mobile SIP SDK that will be operational within its proprietary secured mobile execution container. Cubed Mobile's container provides similar capabilities to "Android Work Mode" - however, includes additional capabilities and is available for iOS as well.
  • Device Support
    The solution needed to the support a wide range of mobile devices, including multiple operating systems and platforms.

Impact of Challenges

Standard mobile VoIP SDKs could not be used with Cubed Mobile’s app because of the issues listed above. Also, the different enterprise security and privacy rules made it hard to manage platform users and subscribers and hide these things and how they were used.

The Solution

Why Cloudonix?

Cloudonix equipped Cubed Mobile with all the technologies they needed to create their solution. While Cloudonix’s mobile SDK worked great for communicating with mobile devices, Cubed Mobiles’ secured container presented some interesting problems.

  • Operating System Restrictions
    Unlike a normal operating system, the secured execution container introduced some challenging memory and resource allocation and usage challenges.
  • Variable Topologies
    As a BYOD solution, Cubed Mobile had no knowledge of the device network and connectivity topology. This introduced some significant challenges, where the Cloudonix mobile SDK needed to "learn" new topologies independently.
  • CPU Considerations
    The secured container was unable to provide a full "CPU Experience" to the Cloudonix SDK, and thus, the SDK needed to work with reduced resources - while still "believing" it was working with the actual device CPU.
Eric Klein

Eric Klein

COO/CISO, Cloudonix

For its novel approach to bring-your-own-device (BYOD) services, Cubed Mobiles’ solution piqued Cloudonix’s interest. Built from the bottom up to be an extremely secure communications infrastructure, Cloudonix does not use traditional SIP credentials but rather relies on ephemeral authorization techniques. Providing a more secure and private communications platform was the original goal of Cloudonix, and Cubed Mobile embodies that.

Implementation

The Cubed Mobile execution container was “given” its own profile by the Cloudonix Mobile Fragmentation Engine. After that, a number of new features were added to the engine that let it handle the “quirks” and challenges of the container’s resources.