Bug 757235 (b2g-voicemail)

[meta] B2G Voicemail

RESOLVED FIXED

Status

defect
RESOLVED FIXED
7 years ago
5 years ago

People

(Reporter: philikon, Assigned: marshall)

Tracking

unspecified
ARM
Gonk (Firefox OS)
Dependency tree / graph

Firefox Tracking Flags

(blocking-basecamp:-)

Details

Attachments

(1 obsolete attachment)

For now this is mostly a placeholder so we can identify individual work items and then track them here. In order to do that, it'd be good to understand which features are possible and which are requested by our partners, and then triage that list into bugs.

Fernando, Jose Antonio: can you give any input on how the voicemail system is expected to work in the initial launch markets?
AFAIK, the only certification requirements from our side is retrieving the VM access short and long number. 

Also answering your post on b2g-dev mailing list:
> 1) Voicemail notifications (supporting some kind of visual notification in the phone's status bar)

AFAIK, voicemail notifications, at least from TEF side, are already done via SMS. Do you know about any other notification done by the RIL?

> 2) Possibly retrieving voicemail # from SIM / network (usually this is the same as the mobile # itself -- but does anyone know if that is always the case?)
>
> Not always the case. Also, I don't think voicemail gets stored on the SIM. 

Usually, those numbers are stored in the SIM, but it´s a similar case as the MSISDN number. I mean, this numbers could not be available on the SIM. I´ve just made a simple test with an Android phone (long press on dialer #1 key) with two SIM cards, one from TEF and other from Vodafone. The TEF one had the voicemail number stored in the SIM, the Vodafone one, hadn´t.
Posted patch [WIP] Patch to get MBDN (obsolete) — Splinter Review
Hi, Marshall
  I did a little investigation, so far I think voice mail is the EF_MBDN in TS 31.102, and I did a WIP for you to get MBDN. 
You could try to get getMBDN() in ril_worker.js to get the number of voice mail.
 
  Sorry I don't have a Vodafone SIM at hand, but I got a T-mobile SIM and can get the voice mail number. Also I don't know the short and long number ferjm mentioned, I'll check if I can help to provide some details to you. 

Thanks
  
thanks
(In reply to Yoshi Huang[:yoshi] from comment #2)
Sorry I forgot to mention in this patch I use some code in Bug 754018, which is still being reviewed.
(In reply to Yoshi Huang[:yoshi] from comment #2)
Thanks Yoshi!

> Also I don't know the short and long number
> ferjm mentioned, I'll check if I can help to provide some details to you. 
Short numbers (i.e.: 123) are the ones dialed while you are on your carrier´s network.
Long numbers (i.e.: +34666111222) are the ones dialed using a network different from your carrier. For example, using a different SIM or while roaming.
Hi, my name is Ignacio Barandalla. I am working on Open Web Device from Telefonica side. Just wanted to add some more information on this topic.

About the SIM storage of voicemail number, as Yoshi says, the SIM file for that is EF_MBDN, as defined in 3GPP TS 31.102, section 4.2.60. 

This is the latest version of the Release 7, which should be enough for us:

http://www.3gpp.org/ftp/specs/archive/31_series/31.102/31102-7f0.zip

For some operators, the voicemail number will be stored in this file, and for others it will be included the variant. Another option combining both is that the variant has the value "From SIM", which references to the SIM EF (EF = Elementary File). I think that this EF_MBDN is widely used among operators.

Another SIM file related with voicemail is EF_MWIS (Message Waiting Indication Status). I think this file is not being used by operators or current phones.

Coming back to Philipp initial question on the features needed for the voicemail service to work, it is very simple: it just needs voice calls (including short numbes, international numbers and DTMF) and SMS for the service daily use, and the management of the Call Forwarding services for setting up the situations when the call is diverted to the voicemail. These situations can be:

- CFB: Busy (the user is talking to someone else)
- CFNRy: No Reply (the receiver's phone has been ringing but the user didn't answer)
- CFNRc: Not Reachable (the receiver is out of coverage or switched off)
- CFU: Call Forwarding Unconditional (divert in all cases)

These call diverts should be configured from the settings menu and also using the string codes like *21*6123456#. 

This is for the normal voicemail to work. If we want "visual voicemail" (which is really nice in my opinion) as in the iPhones, that requires a specific development in the operator side so that the operator voicemail servers offer this interface. A protocol would have to be defined to do this, but the integration times in the operator side would be of several months, so this probably wouldn't be ready for a first version of the device.
Yoshi, thanks for the patch.. I'll try to incorporate this into my implementation :)
Comment on attachment 625959 [details] [diff] [review]
[WIP] Patch to get MBDN

Guys, this is a meta bug. Please add and discuss patches in individual bugs blocking this bug.
Attachment #625959 - Attachment is obsolete: true
(In reply to Ignacio Barandalla from comment #5)
> Another SIM file related with voicemail is EF_MWIS (Message Waiting
> Indication Status). I think this file is not being used by operators or
> current phones.

Interesting. There's also the message waiting flag in an SMS itself (bug 736710). Isn't that used for voicemail indication? I know Android displays a little icon when you have voicemail. But again, we probably want to punt on that for v1.

> Coming back to Philipp initial question on the features needed for the
> voicemail service to work, it is very simple: it just needs voice calls
> (including short numbes, international numbers and DTMF) and SMS for the
> service daily use,

That's what I suspected. You simply get an SMS and you call a special number (e.g. MBDN) to listen to your answering machine.

> and the management of the Call Forwarding services for
> setting up the situations when the call is diverted to the voicemail. These
> situations can be:
> 
> - CFB: Busy (the user is talking to someone else)
> - CFNRy: No Reply (the receiver's phone has been ringing but the user didn't
> answer)
> - CFNRc: Not Reachable (the receiver is out of coverage or switched off)
> - CFU: Call Forwarding Unconditional (divert in all cases)
> 
> These call diverts should be configured from the settings menu and also
> using the string codes like *21*6123456#. 

Those are USSD messages, though, right? Those are not dialed but dispatched separately, ferjm is working on a patch (bug 734145).

> This is for the normal voicemail to work. If we want "visual voicemail"
> (which is really nice in my opinion) as in the iPhones, that requires a
> specific development in the operator side so that the operator voicemail
> servers offer this interface. A protocol would have to be defined to do
> this, but the integration times in the operator side would be of several
> months, so this probably wouldn't be ready for a first version of the device.

s/probably/definitely absolutely with 100% certainty/ :)
Sounds like this is viable via USSD and can be done in Gaia land. Marking as a non-blocker. Re-nominate for blocking if a voicemail WebAPI is actually required.
No longer blocks: b2g-ril
blocking-basecamp: --- → -
Depends on: 736710
(In reply to Philipp von Weitershausen [:philikon] from comment #8)
> (In reply to Ignacio Barandalla from comment #5)
> > Another SIM file related with voicemail is EF_MWIS (Message Waiting
> > Indication Status). I think this file is not being used by operators or
> > current phones.
> 
> Interesting. There's also the message waiting flag in an SMS itself (bug
> 736710). Isn't that used for voicemail indication? I know Android displays a
> little icon when you have voicemail. But again, we probably want to punt on
> that for v1.
> 
We've received confirmation from Brazil OB about this. They notify the user with an SMS with the MW indicator.
Depends on: 773068
Component: DOM: Device Interfaces → RIL
Product: Core → Firefox OS
Version: Trunk → unspecified
All dependent bugs are fixed.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.