Closed
Bug 970320
Opened 10 years ago
Closed 10 years ago
[Cost Control] Add configuration to provide top-up & check balance in Movistar Uruguay
Categories
(Firefox OS Graveyard :: Gaia::Cost Control, defect)
Tracking
(blocking-b2g:1.3+, b2g-v1.3 fixed, b2g-v1.3T fixed, b2g-v1.4 fixed)
People
(Reporter: sonmarce, Assigned: mai)
Details
Attachments
(1 file, 1 obsolete file)
This is just to add new configuration in order to provide Cost Control to Movistar Uruguay according to their network characteristics: * Operator short name: 'movistar' * Balance SMS in OB territory is always free: true * Balance SMS in roaming is always free: true * Country currency symbol for display: '$' * Number to send balance SMS to: '222' * Text to be sent in SMS body: 'SALDO' (any text is valid, even blank) * List of possible numbers the balance response SMS may come from: ['222'] * Format of the balance SMS response: 'Saldo:$xxx' (should take any number, including decimals) * Format of the balance SMS response when the user has reached zero balance: 'Saldo:$0' (should be same format as balance) * Required time between two automatic balance enquiries: 3 hours * Number to dial for USSD top-up: '*222*1*1#' * SMS-based top-up: disabled * Amount in local currency that triggers low balance alarm: 0 (operator already sends an SMS in case of low balance, so we could skip notification) It does not require implementation, just adding a new configuration for the MCC/MNC
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → mri
Assignee | ||
Comment 1•10 years ago
|
||
Added config file for movistar Uruguay
Assignee | ||
Comment 2•10 years ago
|
||
Comment on attachment 8373359 [details] [review] patch v1.0 Salva, please, could you review the code?
Attachment #8373359 -
Flags: review?(salva)
Comment 3•10 years ago
|
||
Comment on attachment 8373359 [details] [review] patch v1.0 According to the specification provided by Uruguay, all is ok. It would be great if we are gien some testing SIMs to verify. Thank you.
Attachment #8373359 -
Flags: review?(salva) → review+
Comment 4•10 years ago
|
||
Marina, can you publish the last specification for balance SMSs and update what Marce is saying in c#0?
Comment hidden (obsolete) |
Assignee | ||
Comment 6•10 years ago
|
||
Uruguay configuration: * Operator short name: 'Movistar' * Balance SMS in OB territory is always free: true * Balance SMS in roaming is always free: true * Country currency symbol for display: '$' * Number to send balance SMS to: '222' * Text to be sent in SMS body: 'SALDO' (any text is valid, even blank) * List of possible numbers the balance response SMS may come from: ['222'] * Format of the balance SMS response: 'Recarga $x.xx' or 'Recarga $xxx' (should take any number, including decimals) * Format of the balance SMS response when the user has reached zero balance: 'Su saldo actual es cero' * Required time between two automatic balance enquiries: 3 hours * Number to dial for USSD top-up: '*222*1*1#' * SMS-based top-up: disabled sms samples: * "Recarga $75 vto 12/3 Tenes Movistar, tenes beneficios exclusivos: Recargando 200 pesos o mas hablas por pesos 0.99 iva inc el minuto a todos los Movistar y telefonos fijos del pais a toda hora y la recarga te dura hasta 60 dias. Promo valida recargando desde el 13/1/2014 al 15/2/2014." * "Recarga $72.99 vto 12/3 Tenes Movistar, tenes beneficios exclusivos: Recargando 200 pesos o mas hablas por pesos 0.99 iva inc el minuto a todos los Movistar y telefonos fijos del pais a toda hora y la recarga te dura hasta 60 dias. Promo valida recargando desde el 13/1/2014 al 15/2/2014"
Assignee | ||
Comment 7•10 years ago
|
||
Master: a5099dd1cc3e6761022b979bb58d2d29744a61d8
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 8•10 years ago
|
||
Asking for 1.3, as it is required for Movistar Uruguay, there should be almost no risk as it only adds configuration for the operator, and it will enable operator users to check balance & top-up
blocking-b2g: --- → 1.3?
Comment 9•10 years ago
|
||
We prefer to provide a better and more error-proof regular expression. Back-out: e91e76f5a451b61bdf9be18b012a242dfe72fb05
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 10•10 years ago
|
||
Marina, please, ask for my review again once you replace the regular expression.
Assignee | ||
Comment 11•10 years ago
|
||
Please Salva, could yout test the new patch ?
Attachment #8373359 -
Attachment is obsolete: true
Attachment #8374106 -
Flags: review?(salva)
Comment 12•10 years ago
|
||
Comment on attachment 8374106 [details] [review] pat v1.1 Cool! Less restrictive now but reasonable. Than you Mai!
Attachment #8374106 -
Flags: review?(salva) → review+
Assignee | ||
Comment 13•10 years ago
|
||
Master: 4b928371c9c58a484ae76a73c9f88a39a755a031
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
status-b2g-v1.3:
--- → affected
Target Milestone: --- → 1.4 S1 (14feb)
Comment 15•10 years ago
|
||
Uplifted 4b928371c9c58a484ae76a73c9f88a39a755a031 to: v1.3: 39c0727e66a2f8d5b344f32816929ff2099a903d
Updated•10 years ago
|
status-b2g-v1.3T:
--- → fixed
status-b2g-v1.4:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•