PortSIP ONE: PBX-bound desktop and mobile client

Start with the product-generation boundary

PortSIP documents PortSIP ONE for PortSIP PBX 22.0 or later and explicitly says it does not support PBX 16.x. The separate legacy PortSIP Softphone remains the v16.x path. Treat those as different clients rather than using a legacy setup article for a current deployment.

The reviewed release track identifies 10.9.4, dated September 28, 2026, as current. The vendor publishes Windows, macOS, iOS and Android downloads and documents a browser client. This is a PBX-bound unified communications family, not evidence that the app accepts an arbitrary third-party SIP account. Pin the exact PBX, client, platform and installation artifact before rollout.

Read 10.9.4 fixes as version-scoped evidence

PortSIP's 10.9.4 notes include improved desktop network-status handling and fixes for answering after extended computer sleep, saved WebRTC codec changes, Samsung background-call audio and active calls affected by an incoming SIM call. These are vendor change records for one release, not proof that every host, browser, handset or earlier failure is corrected.

The same release adds Windows headset control, Android system-ringtone behavior, optional mobile default-dialer use and caller name-plus-number display. Each adds an operating-system or accessory boundary. Validate resume, reconnect, inbound notification, audio devices, active-call coexistence and call-control state on the deployed build, then retain rollback to the previously approved package.

Choose a controlled sign-in path

First-party guides describe QR-code, Microsoft 365 and manual sign-in. Manual setup distinguishes the tenant SIP domain, PBX or SBC address, transport and extension credentials. A successful sign-in confirms only that account path; it does not establish inbound routing, messaging, recording, CRM or transcription entitlements.

Protect a QR code as a credential-bearing onboarding artifact. Revoke or rotate access when a device is lost, and keep the PBX web password and SIP registration password distinct where the administrator has configured both.

Keep template version gates visible

PortSIP's App Template guide requires PBX 22.4 or later and PortSIP ONE 10.8.6 or later. It distinguishes client-managed app_local.xml from server-enforced app_server.xml, with tenant or extension assignment. Do not describe this as fleet enforcement on earlier versions.

Record the assigned template, app build and regenerated QR code after a change. A documented template mechanism still needs an acceptance test showing that a restricted option cannot be changed or silently retained from an older client configuration. Release 10.9.4 also hides features when their service is absent or the current license excludes them, so a missing control is not automatically a client defect.

Separate controller, signaling endpoint and media device

PortSIP documents a desktop option that can initiate an outbound call while another selected device, such as a desk phone or mobile client, places and receives the call. It also documents Call Flip, where other endpoints ring so an active call can be answered there. These are different PBX-mediated workflows; neither proves that the desktop app owns the audio path.

For acceptance, record the initiating client, selected device, called identity, endpoint that receives media, PBX dialog or bridge evidence and the failure shown when the selected device is offline. Test deselection and recovery. Keep this separate from blind transfer, attended transfer, park and operating-system default-dialer behavior.

Verify transport, media and push separately

The sign-in guide documents UDP, TCP, TLS and WSS connection examples. Selecting TLS does not prove protected media or validate every certificate and SBC policy, so inspect the negotiated signaling and media legs independently. The reviewed app documentation does not establish a universal SRTP policy.

For mobile background calling, PortSIP documents a PBX push path through Apple Push Notification service or Firebase Cloud Messaging. That dependency is not equivalent to a handset maintaining foreground SIP registration. Test locked screen, terminated app, restart, Wi-Fi and mobile data, notification permissions, delayed delivery and revocation on the exact PBX and client build. A 10.9.4 sleep or background-audio fix remains version-scoped release evidence, not a substitute for that matrix. No installation, account, template, transport, media, push, recovery, emergency, availability, price or call-quality behavior was tested for this guide.

Diagnose a missed mobile call after the app closes

Use the PortSIP ONE mobile push diagnostic to separate app and PBX generation, device token, X-Push registration, APNs or FCM delivery, app wake-up, replacement registration and the replacement INVITE.