Emergency call processing issue in 10.3.1

Hello!

We have an issue with wrong emergency call processing after update iphone (5/6/6s/6SPlus) to 10.3.1 firmware.

Environment:

Place - Russia, Novosibirsk

Service provider - Vympelkom (Beeline)

Phone numbers:

Emergency Helthcare (production system) - call 103

Emergency(non-production, field trial!) - call 112



What happens:

When we tries to dial 103 we get on 112. It's unacceptable due non-production status of the system.


Could you please provide information what changed in packet (session format) in emergency call processing.


P.S.: Different phones (non-iphone) -all is ok, different service provider - all is ok, different seftware version - all is ok.


Thanks!


Alexey Alexandrov

DevForums isn’t the right place to report this. I think your best option here would be to escalate it via your carrier, but if you want to talk to Apple about it then you need to get in touch with AppleCare.

Share and Enjoy

Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

AppleCare (support) forwarded it to developers due issue is directly connected to the new FW (10.3.1). Carrier stay in position - "problem in phone". I agree that it is wrong position and we are in discussion with carrier and government (to push carrier).

But it's not an issue with button, ringtone, 3rd party application, etc. It's emergency calls and, unfortunately, it can lead to injuries, disabilities and people death.

Please, we just need help to resolve the issue.


Thank you.

Unfortunately this isn’t a code level question and thus is outside of my purview. Have you filed a bug about this already? If not, I recommend you do, so you can at least have a handle on which to hang all of your discussions with Apple on this subject.

Please post your bug number, just for the record.

Share and Enjoy

Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

Ok, thanks, i'll tru bug report.


updated - additional carrier affected (megafon).

Response from developers in Bug reporter team - known issue #31708735. Anybody know how to see details of this issue and possible workaround?


Thanks!

Emergency call processing issue in 10.3.1
 
 
Q