Has there been any new issues with the push notification service for the Sangoma Talk app on iOS? It was working this weekend, and not today. We have not made any changes on our end and the calls work with the app open but not with the app close. A coworker is theorizing that it may be an issue on Sangoma’s end with their push notification certificate, as it works with Android.
Wanted to ask here before I open a ticket and see if anyone else is facing the same issues.
I came to make a post about the same issue. I have reports from 2 separate users on different instances with the same issue and I just reproduced it on a 3rd. I haven’t tested Groundwire on an iPhone yet to see if that is working (to narrow down between Sangoma and Acrobits). But I’ll try to test that soon since I’ll probably get a faster response from Acrobits support if I can repro the problem there too.
Ok, I can confirm that the problem does not seem to be present when using push notifications via Groundwire (which is Acrobits mobile softphone). That seems to point to an issue with the Sangoma integration. I’ll be opening a support ticket.
If we could get some eyes on it here, it would be a big help since I’ve had issues with Sangoma support taking a while in the past. I hesitate to do this, but @mwhite or @penguinpbx could you bring this to the attention of whoever is in charge of Sangoma Talk on mobile? I suspect this is impacting a lot of people.
Glad to hear I am not the only one!
Here is my case number if any Sangoma staff are able to escalate this issue: 02155889
I also am reproducing the issue…
iPhone 17, running iOS 26.4.2
187299 [2026-05-04 11:38:02] VERBOSE[12585][C-00007528] app_dial.c: Called PJSIP/1019/sip:[email protected]:23839;transport=TLS;rinstance=2F55E985;x-ast-orig-host=10.65.8.1:23839
187300 [2026-05-04 11:38:02] VERBOSE[12585][C-00007528] app_dial.c: PJSIP/1019-00050b28 is ringing
187301 [2026-05-04 11:38:02] VERBOSE[12585][C-00007528] app_dial.c: No one is available to answer at this time (1:0/0/0)
yet
Endpoint: 1019/1019 Not in use 0 of inf
InAuth: 1019-auth/1019
Aor: 1019 6
Contact: 1019/sip:[email protected]:23839;transpor 4f75565de9 Avail 12.804
For 2 out of 3 systems I tested I’m getting a’ ‘480 Temporarily Unavailable’ sip response from the acrobits push server. With these relevant headers:
X-Sipis-Reason: Push-Notification-Failure
User-Agent: Acrobits SIPIS
The other system seemed to have the same effective issue but the response from the acrobits push server was actually ‘ringing’ and I believe, though I didn’t save it, the X-Sipis-Reason was something akin to ‘alerting device’. But the wakeup never occurred either.
Just adding to the list as well, all of our iPhone users are having the same issue. Sangoma Talk only works if they have the app open. When it is in push side, they do not wake up.
I agree this is likely an Acrobits issue. Not sure where to check on their website, in case that company has an outage.
Chris
...
SIP/2.0 480 Temporarily Unavailable
...
...
X-Sipis-Reason: Push-Notification-Failure
User-Agent: Acrobits SIPIS
Content-Length: 0
yup seeing the same thing in debug logs
It may be an Acrobits issue, and I even reached out to their support since I still haven’t heard back on my Sangoma ticket, but I don’t seem to be having this issue on the Groundwire mobile app (which is released by acrobits and seems to use their same push system). So I think it’s likely an issue with the way Sangoma and Acrobits are interfacing. I’ll update here if I hear back from Acrobits.
I was just getting ready to open a ticket with Sangoma. Did you just open a ticket or did you call in? I may call into Sangoma if you haven’t already.
Here to help - DM the ticket# when open.
@christrati @matthewljensen - I’ve shared this thread with ENFG as well. FYI
Thank you. I just DMed the ticket number too.
I’ve also DMed you the ticket number that I opened.
Broken for me too across all systems.
It only works when the iphone is unlocked and app is open.
I ended up calling, since I hadn’t heard back on my ticket, and waited on hold for a long time and finally reached someone telling me I could view the status of the issue here: https://trust.sangoma.com/
It looks like they recently confirmed the issue’s existence and are saying it’s due to a 3rd party (I suspect Acrobits).
Latest update:
Monitoring - A fix has been implemented and we are monitoring the results.
May 04, 2026 - 14:38 EDT
I did one test and it worked. Will have to do more but looks good so far!