If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

[buri] list of emergency numbers is not correct (066 and 133 not included)

NEW
Unassigned

Status

Firefox OS
Vendcom
4 years ago
3 years ago

People

(Reporter: dpalomino, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [POVB])

(Reporter)

Description

4 years ago
This is a certification blocker issue detected in Chile with buri device. 

device: buri (COM RIL)
version: official build candiate to approval in Chile

STR: 
1. Insert a SIM card from TEF Chile
2. Try to call to any of the emergency numbers that are working in Chile (911, 122, 133)
3. 911 and 112 are working fine
4. 133 is performed as a regular call, not as an emergency call (signalling is not indicating that it's an emergency call). "Emergency call" label isn't shown either. 

This issue has an important user impact, as for instance, it's not possible to perform emergency calls using a pre-paid card without credit. 

We think this could be related with COM RIL, cc'ing mvines. 

FYI, this are the current emergency numbers used in different LatAm countries: 

1. Chile: 133, 911, 112
2. Uruguay: 911, 112
3. Argentina: 911, 112
4. Mexico: 066, 311, 112
5. Guatemala: 122, 911, 112
6. El Salvador: 122, 911, 112
7. Nicaragua: 112, 911
8. Panama: 112, 911
9. Colombia: 112, 123
10. Ecuador: 112, 911
11. Peru: 105, 112, 911
12. Venezuela: 911, 112
13. Costa Rica: 911, 112


Nominated to leo?

We're requesting to testhouse in Chile to collect some logs about this issue. 

Thanks!
David
Note - we're not actively triaging leo? bugs. If you want to raise attention on a 1.1 bug, I'd email b2g-release-drivers@mozilla.org about this.

One thing that could help diagnose this bug is to see if someone can figure out if this issue also reproduces on the Mozilla RIL. If it doesn't, then we'll be able to confirm that this is a Com RIL bug.
Hi Jack -

Could you help to check this one first?

Thanks
Flags: needinfo?(liuyongming)
(In reply to Jason Smith [:jsmith] from comment #1)
> One thing that could help diagnose this bug is to see if someone can figure
> out if this issue also reproduces on the Mozilla RIL. If it doesn't, then
> we'll be able to confirm that this is a Com RIL bug.

We're reading emergency numbers list from system properties "ril.ecclist" or "ro.ril.ecclist" [1] and fall back to "112" and "911" [2].  Since I can't find anything similar in Buri device folder [3], I think we're using the default ones.  If there is no additional commits merged when building images for Chile, then I think this is also reproducible with Mozilla RIL.

[1]: http://mxr.mozilla.org/mozilla-central/source/dom/system/gonk/ril_worker.js#2896
[2]: http://mxr.mozilla.org/mozilla-central/source/dom/system/gonk/ril_worker.js#56
[3]: https://github.com/mozilla-b2g/android-device-hamachi
(In reply to Vicamo Yang [:vicamo][:vyang] (PTO Dec. 21 ~ Jan. 5) from comment #3)
 
> We're reading emergency numbers list from system properties "ril.ecclist" or
> "ro.ril.ecclist" [1] and fall back to "112" and "911" [2].  Since I can't
> find anything similar in Buri device folder [3], I think we're using the
> default ones.  If there is no additional commits merged when building images
> for Chile, then I think this is also reproducible with Mozilla RIL.
> 

One thing I don't understand is, since different regions and different operators will have their own definitions of emergence call code, do we need to cover all the ECC in the fallback? Or we just use default 112/911 in the fallback, and in the meantime also provides a mechanism for partners to expand the ro.ril.ecclist/ril.ecclist(in addition to read the EF-ECC from SIM)?
Let me jump into this discussion as we dealt with something sightly similar in the past. See bug 860844, especially https://bugzilla.mozilla.org/show_bug.cgi?id=860844#c15.

"libril populates the ecc list. If the sim card is present, then it will use values from the EF file. If no sim card is present, then it will rely on hard-coded an NV items. The libril will also block any emergency call that is not listed in ril.ecclist."

If 066 and 133 are not included it means that numbers are not in the EF.

On the other hand, libril will block any emergency call that is not listed in ril.ecclist so having a mechanism for expanding this list cannot work.

Adding pgravel@codeaurora.org to the discussion. Could you shed some light into this issue please?, thanks.
Flags: needinfo?(pgravel)
(Reporter)

Comment 6

4 years ago
Thanks a lot for the clarification. Also ni mvines about this (sorry about that, it's a blocker issue in Chile).
Flags: needinfo?(mvines)
Sounds like the ro.ril.ecclist list simply needs to be updated on this build.
Flags: needinfo?(pgravel)
Flags: needinfo?(mvines)
Whiteboard: [POVB]
(Reporter)

Comment 8

4 years ago
Thanks a lot Michael! These are great news :-)

Updated

4 years ago
Component: General → Vendcom

Comment 9

4 years ago
(In reply to Michael Vines [:m1] [:evilmachines] from comment #7)
> Sounds like the ro.ril.ecclist list simply needs to be updated on this build.

Yes, it's customization issue, those ECC numbers will be customized in new build.
Flags: needinfo?(liuyongming)
Mass-modify - removal of no longer relevant blocking flags.

Updated

3 years ago
blocking-b2g: leo? → ---
You need to log in before you can comment on or make changes to this bug.