Acrobits 26.1 Autumn Feature Update: Multi-Backend Login, In-App PBX Controls, Android Telecom, Multi-Account Desktop and MMS

The autumn release centers on the Cloud Softphone 26.1 client, with separately deployed updates to the Acrobits Softphone Dashboard and Linkup Messaging. Five changes ship, all against the same assumption: that one app means one SIP account, on one backend, on one device. Each takes a boundary out rather than putting a screen in.

• Signpost multi-backend login. One branded binary routes users to NetSapiens, MetaSwitch, or a direct-login SIP environment.
• Acrobits Softphone Dashboard. Call Park, Answering Rules, and NetSapiens contacts live inside the branded app as a customizable UI.
• Android Telecom integration. VoIP and cellular calls coexist, with a new per-device compatibility test picking the audio strategy.
• Multi-account for desktop. Several SIP accounts in one SIP client for users carrying more than one business identity.
• Linkup Messaging MMS. Images and file attachments on the Sinch and Bandwidth integrations that already carry SMS.

Signpost picks the backend from the login credentials

A provider operating across two backends used to maintain two binaries, two app-store listings, and two release tracks. Signpost collapses that into one branded app: at login it identifies the environment from the credentials and routes the user to the matching cloud configuration.

One build and one update cycle carry the operator through a migration, an acquisition, or a standardization push, with a simpler path to a white-label softphone that works with any SIP switch.

What that frees a carrier to do

• Run several service environments behind one brand and one download.
• Stage a backend migration without teaching every user a new way in.
• Put acquired networks, or separate service populations, behind a common login.
• Offer SSO or password sign-in where the selected platform supports it.

Validated multi-environment login covers NetSapiens and MetaSwitch today, mixed deployments included. Everything else takes the direct path: the operator sets the environment up front with a Cloud Softphone cloud ID and their own External Provisioning, and Signpost passes the login straight through without validating it. BroadSoft deployments carry on unchanged or move to the direct path; automatic backend detection stays NetSapiens and MetaSwitch only.

Softphone Dashboard: Call Park and Answering Rules in the app

The Acrobits Softphone Dashboard is a provider-branded workspace inside Cloud Softphone, with tiles, branding, deep links and web links under provider control.

Without leaving the app, a user can

• Park a call and retrieve it, against live Call Park status showing which slots are taken.
• Edit Answering Rules in place, instead of moving to a separate PBX portal.
• Browse and maintain NetSapiens contacts and favorites, with changes handed back to the app.
• Act on the call in progress: hold, resume, end, park and retrieve.

Dashboard is NetSapiens only and needs its own deployment tied to the applicable cloud ID. Availability is set per cloud and confirmed at runtime for each user, so a provider can pilot with one tenant before enabling a whole cloud.

Contacts and synchronized call history come with the base Marketplace setup. Messaging synchronization is an optional per-domain setting, and setup lives in the NetSapiens Cloud Softphone configuration guide.

On Android, VoIP and cellular calls now coexist

Android call handling is a steady source of audio-routing and missed-call tickets, because Telecom permissions, audio focus, and Bluetooth behavior vary by version and OEM. Cloud Softphone 26.1 integrates with Android Telecom, so VoIP and cellular calls coexist and the app takes proper audio and Bluetooth ownership.

This was the hardest problem in this release, and most of the engineering went into holding the call steady rather than into the integration itself. Four things can change what a call is doing without being asked: Android, the handset vendor, a connected Bluetooth device and the SIP engine, any of them mid-call. The integration absorbs all four, keeping the call up and restoring its state when the system or a device changes course.

An in-app compatibility test picks and saves the right audio-routing strategy per device. If problems surface mid-call, the app falls back to compatibility routing, automatically when auto-switch is on. That means fewer tickets tied to Android fragmentation, especially in BYOD fleets where the operator does not control the handset.

Android only: full Telecom integration needs Android 9 or later, and other devices use compatibility routing.

Several SIP identities in one desktop client

One desktop client now carries several SIP accounts. The user sets a default, and calling, native messaging, voicemail, DND, notifications, callbacks, and headset handling all follow the active identity. Answer, mute, and hang-up land on the right account without manual switching.

For MSPs and multi-tenant operators that cuts client sprawl to one install and one deployment profile per workstation. Desktop only, enabled per deployment in provisioning, which also sets the account limit. Cloud services such as Linkup Messaging still follow the deployment and default-account configuration rather than one tenant per SIP account.

In-app number rewriting on desktop

The desktop client also picks up in-app number rewriting: administrators define rules, test them inside the app, and drag to reorder priority. Dialing behavior adapts per deployment without pushing a new build.

MMS on the Sinch and Bandwidth gateways already in place

MMS now rides on the same Sinch and Bandwidth integrations that already carry SMS. Media handling stays secure and provider-aware, with attachment size limits following each gateway's rules rather than one universal ceiling.

Subscribers send images and file attachments on the contracts and numbers the operator already holds. No new gateway relationship, no re-onboarding the trunk. It assumes Linkup Messaging is enabled with an existing Sinch or Bandwidth gateway account, on numbers and plans that support MMS rather than SMS only. It expands those integrations rather than adding a NetSapiens-Sinch one.

What ships with the client, and what switches on per cloud

Signpost, Android Telecom integration, multi-account desktop and number rewriting all arrive with the 26.1 client. Dashboard and Linkup Messaging switch on per cloud, so those two follow the operator's configuration rather than the release calendar. Each one removes a boundary the operator had been working around.

What providers do with that is the open part. Once the surface a user works in can change without an app release, the app stops being the unit of change: a tile carrying one industry's workflow, a board a dispatcher actually watches, something that sits beside the dialer rather than inside it. None of that is announced. It is just newly reasonable to build.