Update - We are continuing to work on a fix for this issue.
Jul 07, 2025 - 10:22 AEST
Jul 07, 2025 - 10:22 AEST
Identified - Overview
We are currently investigating an issue affecting audio functionality on VoIP calls made using the 2talk and SIPcity Android mobile apps on certain Samsung devices running Android 14 and 15.
⸻
📱 Affected Devices
• Samsung Galaxy A16 (Android 14)
• Samsung Galaxy A73 (Android 15)
• Other Samsung devices running Android 14 or 15 may also be impacted.
⸻
🛠️ Identified Issue
On these devices:
• Calls connect, but neither party can hear audio.
• The issue appears to be caused by changes in microphone permissions and audio handling introduced in Samsung’s Android 14/15 software.
✅ This issue does not affect:
• iPhone (iOS) devices
• Google Pixel or other non-Samsung Android devices
• Samsung devices running Android 13 or earlier
⸻
🔍 What We’ve Found So Far
• Samsung Android 14/15 devices may deny microphone access at runtime, even when permissions are granted.
• As a result, VoIP media streams fail to initialize, leading to one-way or no-way audio.
• This issue appears specific to Samsung’s system configuration and is not related to push notifications or account registration.
⸻
👷♂️ What We’re Doing
• We’re implementing a Samsung-specific fix to work around these permission and routing issues.
• A patch update is being tested that forces microphone access and adjusts the way audio streams are initiated on Samsung Android 14/15.
• We are also reaching out to Samsung for support.
⸻
Temporary Workarounds
If you are affected:
1. Bluetooth or external appear to resolve the the mic issue on most Android
⸻
📅 ETA for Resolution
We expect to deploy an app update with a Samsung compatibility patch within the next 5–7 days.
Jul 07, 2025 - 10:16 AEST
We are currently investigating an issue affecting audio functionality on VoIP calls made using the 2talk and SIPcity Android mobile apps on certain Samsung devices running Android 14 and 15.
⸻
📱 Affected Devices
• Samsung Galaxy A16 (Android 14)
• Samsung Galaxy A73 (Android 15)
• Other Samsung devices running Android 14 or 15 may also be impacted.
⸻
🛠️ Identified Issue
On these devices:
• Calls connect, but neither party can hear audio.
• The issue appears to be caused by changes in microphone permissions and audio handling introduced in Samsung’s Android 14/15 software.
✅ This issue does not affect:
• iPhone (iOS) devices
• Google Pixel or other non-Samsung Android devices
• Samsung devices running Android 13 or earlier
⸻
🔍 What We’ve Found So Far
• Samsung Android 14/15 devices may deny microphone access at runtime, even when permissions are granted.
• As a result, VoIP media streams fail to initialize, leading to one-way or no-way audio.
• This issue appears specific to Samsung’s system configuration and is not related to push notifications or account registration.
⸻
👷♂️ What We’re Doing
• We’re implementing a Samsung-specific fix to work around these permission and routing issues.
• A patch update is being tested that forces microphone access and adjusts the way audio streams are initiated on Samsung Android 14/15.
• We are also reaching out to Samsung for support.
⸻
Temporary Workarounds
If you are affected:
1. Bluetooth or external appear to resolve the the mic issue on most Android
⸻
📅 ETA for Resolution
We expect to deploy an app update with a Samsung compatibility patch within the next 5–7 days.
Jul 07, 2025 - 10:16 AEST
About This Site
Learn more about status and outage updates from SIPcity.
SIPcity Calling Platform (Network)
Operational
SIPcity Cloud PBX
Operational
MySIPcity app
Degraded Performance
Desktop app
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.