Keep the distributed binary and source tree as different artifacts
Telephone is a macOS SIP softphone. The current App Store listing still identifies version 1.6, dated June 29, 2022, and requires macOS 10.13 or later; the developer's June 2022 release note says 1.6 added the modern macOS look and Apple Silicon support. Those are the available first-party distributed-release facts, not proof of a later binary, current maintenance commitment or support for every present Mac.
The repository is active source evidence, not an App Store version number. Its current instructions build Opus 1.3.1, LibreSSL 3.1.5 and PJSIP 2.10 with a macOS 15.6 minimum target. That target belongs to those documented source-build commands. It does not retroactively change the App Store listing's macOS 10.13 requirement or establish that repository head has been packaged, signed, notarized, regression-tested or released as Telephone 1.6.
Pin provenance before installation or comparison
For the distributed app, record the storefront, version, receipt, code signature, Mac model and macOS build. For a source build, record the exact commit, Xcode and SDK, architecture, dependency sources and hashes, patches, compiler flags, signing identity and output hash. Do not compare a local repository build with the App Store binary as if they were one artifact.
The repository's PJSIP 2.10 reference is a source-build dependency instruction, not proof that every distributed binary uses the same unmodified library or inherits later PJSIP fixes. Likewise, a recently changed source file is not a release date, security-support promise or compatibility result.
Supply the SIP service and own the account settings
Telephone does not provide phone service. The product, FAQ and App Store pages require an account from a SIP provider or company phone server. Preserve the SIP identity, registrar or proxy, authentication identity, dial format, outbound permissions, number owner and emergency-service responsibility. A successful REGISTER does not prove inbound delivery, outbound authorization, caller identity, DTMF, transfer or public-network calling.
The FAQ says general SIP providers should work, but that is broad guidance rather than tested interoperability with a specific provider, PBX version, proxy, authentication flow or network. Use the exact service's current settings and a bounded pilot.
Treat transport and media protection as coupled policy
The developer's privacy statement, last updated February 8, 2024, says selecting TLS for SIP makes SRTP mandatory for voice, while selecting UDP or TCP leaves connections between Telephone and the configured server in cleartext. Treat this as documented client policy for the selected hop, not proof that a call negotiated the expected transport, certificate identity, cipher or media protection.
Confirm the server name, trust chain, selected transport and actual media profile. Test that an intentionally incompatible server policy fails visibly instead of falling back. A VPN around UDP or TCP changes the network wrapper but does not relabel the SIP or RTP session itself as TLS or SRTP.
Bound codecs, DTMF and workstation behavior
The FAQ lists Opus, G.722, G.711 A-law and G.711 mu-law and describes keyboard DTMF plus remote RFC 2833 or SIP INFO support. These are published capabilities rather than proof of the exact offer, answer, payload mapping, gateway acceptance or decoded audio. Preserve signaling, SDP, RTP and remote application evidence for the affected call.
Exercise first launch, multiple accounts, inbound and outbound calls, hold, transfer, call waiting, DTMF, microphone, speaker and headset changes, sleep and wake, app restart and network transitions. This is a Mac desktop client, not a mobile push client, so do not transfer mobile background-delivery claims to it.
Protect local state, logs and entitlement boundaries
The privacy page says the developer's apps keep their data locally and do not send analytics or usage statistics to its servers. That statement does not cover a selected SIP provider, PBX, operating-system backup, crash tooling or administrator. The FAQ's debug log is overwritten at launch; collect a bounded reproduction, redact credentials and personal identifiers, restrict sharing and reset the log level afterward.
The product page describes Telephone Pro as a subscription unlocking full call history, 30 simultaneous calls and app-development support. Confirm storefront entitlement and keep the app-side allowance separate from PBX, carrier, bandwidth and call-start capacity. No package, build, app, subscription, account, server, certificate, headset, protected path, sleep state, emergency route, availability, price, compatibility, support response, audio result or call was inspected or tested for this guide.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- Telephone product page ↗
- Telephone App Store listing and version history ↗
- Telephone FAQ and diagnostic logging ↗
- 64 Characters privacy policy ↗
- Telephone 1.6 Apple Silicon release note ↗
- Telephone source repository and build instructions ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.