Repository navigation
docs: instance ID on iOS, and which SIP server to run - #11
Merged
Merged
Conversation
- Instance-ID: why +sip.instance matters for a client that reconnects after every wake-up, why pjsua's host-name default cannot be used on iOS, what went wrong in a production client (identifierForVendor and UserDefaults before first unlock, a racing config writer, a random fallback, an SBC refusing the canonical form), and a proposed design: a Keychain-stored device ID written once, hashed per app and account. Links the upstream change, pjsip/pjproject#5313. - Own-SIP-Server: Flexisip first (built-in APNs sender, bindings keyed on the instance ID; certificate-only, no Feature-Caps, AGPL), OpenSIPS second, Kamailio and Asterisk as lab subjects. - Tech-Debt OH-11 (no instance ID of our own) and two Roadmap pointers.
Comment on lines
+157
to
+159
| A VoIP push in that window must still be reported to CallKit. The call can ring, but answering it | ||
| cannot register or accept the INVITE until the device has been unlocked once. The app has to fail | ||
| that answer cleanly and say why, not hang. An outgoing call does not arise there: the app cannot |
Contributor
There was a problem hiding this comment.
🔍 Pre-unlock ringing needs device verification
The proposed CallKit flow assumes iOS launches the app for a VoIP push before first unlock. U4 still lists that behavior as an open device test.
Was this helpful? React with 👍 or 👎 to provide feedback.
Owner
Author
There was a problem hiding this comment.
Fixed in a8ce3d9: §4 and §5.1 now say that a VoIP push launching the app before first unlock is unverified, point at U4 in Push-vs-Active-Socket, and §5.3 lists it as the first thing to verify on a device. The storage design does not depend on it: any background launch in that window has to cope with the failures in §4.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two new research docs and the pointers to them.
docs/Instance-ID.md—+sip.instanceon iOS. Why it matters for a client that reconnects after every wake-up (Kamailio and Flexisip key bindings on it), why pjsua's host-name default is useless on iOS (localhost), and what went wrong in a production iOS client:identifierForVendorandUserDefaultsboth unavailable before first unlock, a racing config writer, a random fallback, and an SBC that refused the canonical UUID form. Proposed design: a device ID written once to the Keychain beside the SIP secrets, hashed per app and per account for the wire (D-INST-1…4), with two decisions left open. Includes the upstream decision behind pjsua: send a configured +sip.instance without SIP outbound too pjsip/pjproject#5313 and why pjsua cannot fix its default.docs/Own-SIP-Server.md— which server to run for push and for a lab: Flexisip first (built-in APNs sender, INVITE parking, bindings keyed on the instance ID; certificate-only APNs auth, noFeature-Caps, AGPL), OpenSIPS second (complete RFC 8599 signalling, our own.p8sender), Kamailio and Asterisk as measurement subjects. How to test push without Apple.docs/Tech-Debt.md— OH-11: no instance ID of our own yet.docs/Roadmap.md— a stored instance ID before push; Flexisip first.Docs only; nothing is built yet.