A cross-platform softphone built by a Bulgarian team. It only does the client, which keeps it neutral towards every SIP provider.
# Both put your logo on the client. SDK and branding are completely different roads, with very different investment and freedom.
Vendors building communications equipment, door-entry systems or industry terminals run into the same request: the customer wants the softphone to be ours. There are two routes — build one on an SDK, or use an off-the-shelf branding service.
The SDK exposes the low-level calling interfaces: registration, call control, media control, state callbacks. The vendor writes the interface, the interactions and the business flow themselves.
The advantage is freedom: calling can be woven deep into the business logic, such as a doorbell automatically calling the resident, or one-touch group calls in a dispatch system. The disadvantage is workload, plus keeping a team that understands communications on staff long term.
An SDK does not sell code. It sells the fact that you do not have to reinvent the SIP stack.
Branding takes an existing client and changes the identity, the colours and the preset server configuration. Fast to launch, cheap to maintain, and right for the case where you simply want users to have an entry point under your brand.
The cost is limited freedom: interface structure, feature entry points and interaction flow stay as they are. What you can change is the surface.
First, somebody must own the server side. The client is only the entry point; registration, routing, trunks and recording all live on servers, and no SDK removes that.
Second, plan licensing and distribution early. App store review, enterprise distribution signing and the licence terms of underlying components all affect launch timing.
Many teams assume a new logo equals white label, then discover after launch that users complain the phone does not ring or Bluetooth audio disappears. Those issues have nothing to do with the logo — they are mobile background policy. When selecting an approach, the first question should be how push and background keep-alive are handled, not whether the interface can be changed.