For C.S. networks, there's no ril parcel for call deflection which, however, could be implemented via 3gpp in-call mmi. For IMS, AFAIK, there's neither standardized mmi code nor ril parcel for this, but this could be done via a customized mmi code or a specific vendor IMS solution. As there's no generic way for this feature, it might be more flexible to support this by OEMs. The suggested solution for OEMs is: When user presses "Call deflection" button, the app calls "telephony.dial(_Carrier_specific_string_)" As the customized telephony service detects the customized string _Carrier_specific_string_, the service knows it should treat this string as in-call MMI and behave accordingly. Then, once the request is done, the customized telephony service calls nsITelephonyService.notifyDialMMISuccess* or .notifyDialMMIError*. In this way, there's no new API required. All work is done within OEM implementation. Hi Carol, per our bi-weekly meeting, please provide us more details from carrier partners so that we could review if this solution is feasible or not. Thanks!

Though we are still under discussion about which party, mozilla or partner, the effort of this bug falls into, file this bug for tracking and following-up.

Hi Hsin-Yi, Thanks for opening a bug to track this issue. I think handling this via MMI will work. If no UI is needed, we can handle everything via MMI similar to existing standardized MMI codes: Register (Preset a number used for deflection prior to receiving a call): **SC*SI# Activate (Allows call deflection feature to be turned on): *SC*SI# Deactivate (Allows call deflection feature to be turned off): #SC*SI# Where SC is the customized service code and SI can contain the deflection number. During incoming call, pressing of the "Call deflection" button can then issue the _Carrier_specific_string_ as you've suggested which can be handled by telephony service. What do you think?

(In reply to Carol Yang [:cyang] from comment #2) > Hi Hsin-Yi, > > Thanks for opening a bug to track this issue. I think handling this via MMI > will work. If no UI is needed, we can handle everything via MMI similar to > existing standardized MMI codes: > > Register (Preset a number used for deflection prior to receiving a call): > **SC*SI# > Activate (Allows call deflection feature to be turned on): *SC*SI# > Deactivate (Allows call deflection feature to be turned off): #SC*SI# > > Where SC is the customized service code and SI can contain the deflection > number. > > During incoming call, pressing of the "Call deflection" button can then > issue the _Carrier_specific_string_ as you've suggested which can be handled > by telephony service. > > What do you think? +1 for this, sounds good to me :) Then should I change the component to Vendcom?

> +1 for this, sounds good to me :) > > Then should I change the component to Vendcom? Better yet, we can probably just close this bug as we'll handle this internally :)

Thanks Carol.