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

[B2G][SMS] Unable to send an SMS to an authorized number with FDN enabled

RESOLVED INVALID

Status

Firefox OS
Gaia::SMS
RESOLVED INVALID
3 years ago
3 years ago

People

(Reporter: demerick, Unassigned)

Tracking

unspecified
ARM
Gonk (Firefox OS)
Bug Flags:
in-moztrap +

Firefox Tracking Flags

(b2g-v1.3 affected, b2g-v1.4 affected, b2g-v2.0 affected)

Details

(Whiteboard: [2.0-flame-test-run-1][2.0-woodduck-test-run-1], URL)

Attachments

(3 attachments)

(Reporter)

Description

3 years ago
Created attachment 8435133 [details]
logcat.txt

Description:
With FDN enabled and a phone number added as an authorized number the user will not be able to send an SMS. The user is able to make an outgoing to the authorized number.


Repro Steps:
1) Update a Flame to 20140604040204
2) Launch 'Settings' from the home screen and tap 'Call Settings' 
3) Tap 'Fixed dialing numbers' and enable FDN
4) Tap 'Authorized numbers' then '+' and add a valid phone number
5) Return to the home screen and launch the 'messaging' app
6) Tap the 'notepad' in the top right to create a new message
7) In the 'To:' field add the authorized phone number
8) Type anything in the 'Message' field and tap 'Send'


Actual:
User receives message -
"FDN active
FDN is enabled and the following recipient is not in your FDN list:"

Expected:
The SMS should be sent with no message 

Environmental Variables:
Device: Flame 2.0
Build ID: 20140604040204
Gaia: 1d4f6f7312882e78b57971152de75d1281a26187
Gecko: 668f29cd71b3
Version: 32.0a1 (2.0) 
Firmware Version: v10G-2

User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 


Repro frequency: 100%
Link to failed test case: https://moztrap.mozilla.org/manage/case/11747/
See attached: screenshot, logcat
(Reporter)

Comment 1

3 years ago
Created attachment 8435136 [details]
fdn_sms.png

This issue reproduces on Buri 2.0, Buri 1.4, Flame 1.4, and Buri 1.3.

2.0 Environmental Variables:
Device: Buri 2.0 MOZ
BuildID: 20140604040204
Gaia: 1d4f6f7312882e78b57971152de75d1281a26187
Gecko: 668f29cd71b3
Version: 32.0a1
Firmware Version: v1.2-device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 

1.4F Environmental Variables:
Device: Flame 1.4F
BuildID: 20140604000202
Gaia: 0c16adced7c51f795ef250aebe184f60b6a9b987
Gecko: 04216748e6c1
Version: 30.0
Firmware Version: v10G-2
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0

1.4 Environmental Variables:
Device: Buri 1.4 MOZ
BuildID: 20140604000202
Gaia: 0c16adced7c51f795ef250aebe184f60b6a9b987
Gecko: 04216748e6c1
Version: 30.0
Firmware Version: v1.2-device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0

1.3 Environmental Variables:
Device: Buri 1.3
Build ID: 20140603024001
Gaia: 2408c2238254776b0d3716753b7bf917883c9915
Gecko: 560138f48a17
Version: 28.0 (1.3) 
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:28.0) Gecko/28.0 Firefox/28.0

The user is unable to send an SMS to an authorized number when FDN is enabled.
The SMS Center needs to be in FDN too, can you please check that it is?

But I'm surprised, bug 978130 should have implemented a better error message.

NI me so that I'll check this tomorrow.
Flags: needinfo?(felash)
(Reporter)

Comment 3

3 years ago
Created attachment 8435311 [details]
fdn_smsC.png

In my initial report I did not have the SMS Center number in the FDN. 

When I added the SMS Center number without a '+' I received a different error message. Please see the newly attached screenshot.

When I added a '+' before the SMS Center number I was able to send SMS without issues.

(In reply to Julien Wajsberg [:julienw] from comment #2)
> The SMS Center needs to be in FDN too, can you please check that it is?
> 
> But I'm surprised, bug 978130 should have implemented a better error message.
> 
> NI me so that I'll check this tomorrow.
(In reply to demerick from comment #3)
> Created attachment 8435311 [details]
> fdn_smsC.png
> 
> In my initial report I did not have the SMS Center number in the FDN. 
> 
> When I added the SMS Center number without a '+' I received a different
> error message. Please see the newly attached screenshot.
> 
> When I added a '+' before the SMS Center number I was able to send SMS
> without issues.
> 

Hi,

According to the attached image in comment 3, the SMSC is '+13123149810' in AT&T network.

The '+' has to be provided if the national code of SMSC '1' is provided to 
identify the entire number correctly.

Bevis
Flags: needinfo?(felash)
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → INVALID
Sorry to unexpectedly remove NI request in comment 2.
Flags: needinfo?(felash)
The screenshot from comment 3 shows the message implemented in bug 978130.

And actually, the screenshot from comment 1 does too.

So, demerick, I'll assume that the message copied in comment 0 is from an older version (v1.4 or v1.3), coming from your tests in these older versions.
Flags: needinfo?(felash)

Comment 7

3 years ago
This test case IS valid and the moztrap has already been updated successfully.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Flags: in-moztrap?(rmitchell)
Test case already in moztrap:

https://moztrap.mozilla.org/manage/case/11747/
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Flags: in-moztrap?(rmitchell)
Flags: in-moztrap+
Whiteboard: [2.0-flame-test-run-1] → [2.0-flame-test-run-1][2.0-woodduck-test-run-1]
You need to log in before you can comment on or make changes to this bug.