Skip to content

Fix runtime cleanup and VoIP push lifecycle #31

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
PetrShtuka merged 1 commit into from
Sep 7, 2026
Merged

Fix runtime cleanup and VoIP push lifecycle #31

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,16 @@ bump may contain breaking changes, and each one is listed below.

### Fixed

- Runtime ownership now uses a separate identity token that survives ARC weak
zeroing during deallocation, so releasing a client also destroys its PJSUA
runtime and releases an initialization-stage claim.
- Registration checks, refresh, unregister, logout and account updates validate
ownership and operate in the same SIP queue turn as stop. Queue identity is
specific to each client, and account state is published before leaving it.
- Managed CallKit handling reports cancellation, duplicate and stale VoIP
payloads before completing them. Cancelled calls are immediately ended;
duplicate reports reuse the UUID. Host-owned CallKit handling is unchanged.

- PJSUA runtime ownership is claimed for the whole initialization window, not
only after `isRunning` becomes true, so two clients cannot initialize the
process-global stack concurrently on different queues. Start/stop state is
Expand Down
Loading