Zoiper 5 and Scribe: editions, push and transcription boundaries

Choose the product and edition before comparing features

The current download page lists Zoiper 5 for Windows, macOS and Linux and separate Android and iOS apps. It identifies the family as the latest available download but does not expose one stable public build number across those platform tracks in the reviewed page. Free, Pro, business and mobile feature boundaries are not interchangeable. Record the installer or store channel, operating system, exact application build and license shown on the device before treating a feature-table row as available.

Zoiper's current feature list also advertises a Banafo AI integration on the desktop product. That does not establish inclusion in every edition or platform. A listed platform or integration does not prove support for a particular PBX, headset, mobile-device policy, recording policy or emergency workflow. Pilot the exact combination that will be deployed.

Distinguish manual setup from managed provisioning

Zoiper documents manual SIP account fields as well as Zoiper 5 desktop XML configuration, provisioning URLs and option restrictions. The provisioning file can define multiple base URLs and authentication behavior. Treat the file and delivery URL as sensitive configuration, and confirm which edition accepts the intended controls.

Do not assume the desktop provisioning procedure applies unchanged to the mobile apps. Record who owns the source configuration, how a device is revoked and what happens when the provisioning service is unavailable.

Verify signaling and media protection separately

The Zoiper 5 configuration reference exposes SIP transport and SRTP settings. Confirm that the selected client edition exposes them, the PBX supports the same modes and the connection validates the intended certificate name and trust chain. Inspect the actual call rather than inferring encrypted media from a TLS registration.

The protected client-to-PBX leg does not prove end-to-end encryption through a PBX or the telephone network. Define whether a call must fail when the required protection cannot negotiate and test that failure behavior with an authorized account.

Review the mobile push registration path

Background ringing on a mobile device can require Zoiper Push. Zoiper's architecture note describes the conventional risk of an intermediary storing SIP credentials in plaintext or reversible form, then says its own design instead routes registrations through the Zoiper server without giving that server plaintext credentials. It uses silent Apple or Google push notifications to wake the client for re-registration. That is a material signaling and trust-path decision, not only a battery-saving toggle.

Confirm whether push is included in the chosen mobile edition, which server handles signaling, what leaves the device, how account access is revoked, and whether media stays on the expected path. Zoiper's audio diagnostic says the push service is normally only in the signaling path; that statement is not proof of the path taken by one call. Test locked-screen delivery, restart, Wi-Fi and cellular transitions, delayed notifications and the no-push fallback on the exact device.

Choose the hosted or on-device transcription path explicitly

Zoiper now documents two different routes from a recording to derived text. The built-in Zoiper 5 integration sends recordings to a Banafo account for hosted transcription and AI processing. The separate Zoiper Scribe desktop application reads finished recording files, runs transcription locally and says audio is not uploaded to a cloud transcription service; licensing and speech-model downloads may still contact servers. Do not collapse those paths into one privacy claim.

Scribe does not register a SIP account, join the call or create the recording. Zoiper says Zoiper 5 Pro must first write a recording on Windows, macOS or Linux; Scribe can then import one file or, with the documented Scribe Pro workflow, watch the recordings folder. Preserve the selected Zoiper edition, Scribe edition, local directories, model and application versions, hosted-service choice, exports and any separately enabled cloud-summary mode in one acceptance record.

Capture diagnostics narrowly and remove them after support

Zoiper documents a desktop debug logger and packet-capture option and separate Android and iOS log procedures. Such artifacts can contain SIP identities, hostnames, numbers, call metadata, messages, SDP, network addresses and potentially authentication material. Reproduce one authorized case, note the exact client build and timestamps, capture only the necessary interval, inspect and redact the artifact, transfer it through the approved support channel and apply a deletion deadline.

Disable the debug logger after the bounded capture. A log file or packet capture shows what the selected client recorded, not the full PBX, provider or far-end path. Keep recording audio, AI uploads, push-proxy state and troubleshooting logs as different data stores with separate owners and retention controls.

Run a bounded acceptance pilot

Test registration, inbound and outbound calls, audio-device changes, hold, transfer, voicemail indication, sleep and wake, network transitions and credential revocation. If transcription is in scope, use an authorized non-sensitive call to verify recording state, participant notice, the actual file path, hosted upload or local processing, transcript access, correction, export, retention and deletion. Zoiper Scribe warns that no speech-to-text system is perfect, particularly with noise or overlapping speech; do not treat a transcript, speaker label, summary or action item as an assured clinical, legal or operational record.

Verify number formatting and caller identity on the PBX leg and keep an alternative route for critical calls while the client is evaluated. Emergency calling, location handling, commercial entitlement, server interoperability, transcription policy and background reliability remain deployment-specific. This record is documentation research and does not claim a Zoiper installation, recording, upload, local transcript, push delivery, diagnostic capture or call test.

Trace a Zoiper background incoming-call failure

When Zoiper rings only while open or stops receiving calls after a few minutes, use the Zoiper background incoming-call diagnostic. It separates application and operating-system state, negotiated registration expiry, NAT reachability, direct registration versus Push Proxy, wake-up and the final INVITE before media.