Repository navigation
Sipral 1.3.1
A push whose call screen iOS refuses now says why, a removed account takes its subscriptions with it, and the .NET package targets .NET 10.
At C ABI 1.13, unchanged: an application built on any earlier 1.x release works unchanged.
Added
- A push whose call screen iOS refuses says so, and why. Under a Focus (
filteredByDoNotDisturb) or for a blocked caller CallKit refuses the report;PushKitBridge.receivenow answersPushOutcome.refused(VoipPush?, Error)with CallKit's error instead ofunusable,PushKitAdapter.refusedis told the same, and the binding is refreshed (RFC 8599 §4.1.3), so the INVITE still arrives for the application to refuse, busy (486) under a Focus, rather than the PBX waiting out its timer with no answer. AswitchoverPushOutcomethat lists every case needs the new one.
Fixed
- A removed account's subscriptions go with it.
remove_account(sipral_account_remove) dropped the account's registration and publications but kept its subscriptions, which went on firing their refreshes with no account to send from and ended, one by one, asunreachablewith no status, long after the application had removed the account; an application that removes and adds its account on every configuration change saw its presence and dialog subscriptions die that way. They are now dropped with the account, with no event, and lapse at the notifier.
Changed
- The
SipralNuGet package targets .NET 10. .NET 8 and .NET 9 left Microsoft's support on 10 November 2026, so the package moves fromnet8.0tonet10.0, the one runtime still receiving security fixes; an application on .NET 8 or 9 keeps 1.3.0.