Brogan Zumwalt [Inactive] Reporter
	Description • 10 years ago

Description:
When using AT&T SIM to send an SMS to a number using 00+country code+number the message is not sent and user is shown error message "Message not sent. There was a problem sending the message. Please try again." If user uses "+"+country code+number the SMS is sent and received without issue.

Tests were done calling from a US (1) number to a US (1) number.

Repro Steps:
1) Update a Flame to 20140728000238
2) Open Messages app
3) Compose new message to number using format 00+country code+phone number
4) Send message

Actual:
Message does not send and user is shown error message.

Expected:
Message is sent and received as expected.

Environmental Variables:
Device: Flame 2.0 (319mb)
Build ID: 20140728000238
Gaia: 0a864988f5dce7f9f3dea9609e8ef054679c30ff
Gecko: 2da96d621030
Version: 32.0 (2.0) 
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Notes:
Repro frequency: 3/3, 100%
Link to failed test case: Issue does not fail any single test case, but was found while in SMS suite.
See attached: logcat

	Brogan Zumwalt [Inactive] Reporter
	Comment 1 • 10 years ago

Issue DOES reproduce on Flame 2.1 (319mb), Buri 2.1, Flame 2.0 (512mb), Buri 2.0, Flame 1.4 (319mb), and Buri 1.4

Environmental Variables:
Device: Flame Master (319mb)
Build ID: 20140728040209
Gaia: 295967a0b824a355ae9d57fb08f3632ed2ad18dd
Gecko: a4dcfbebcb58
Version: 34.0a1 (Master) 
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Environmental Variables:
Device: Buri Master
Build ID: 20140728073003
Gaia: 295967a0b824a355ae9d57fb08f3632ed2ad18dd
Gecko: d77f6a96ff96
Version: 34.0a1 (Master)
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Environmental Variables:
Device: Flame 2.0 (512mb)
Build ID: 20140728000238
Gaia: 0a864988f5dce7f9f3dea9609e8ef054679c30ff
Gecko: 2da96d621030
Version: 32.0 (2.0)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Environmental Variables:
Device: Buri 2.0
Build ID: 20140726063007
Gaia: 0a864988f5dce7f9f3dea9609e8ef054679c30ff
Gecko: 2da96d621030
Version: 32.0 (2.0)
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Environmental Variables:
Device: Flame 1.4 (319mb)
Build ID: 20140728063001
Gaia: eb3b185325901d4c04e2d43eb58d90835213bea9
Gecko: aae9112f1fc6
Version: 30.0 (1.4) 
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0

Environmental Variables:
Device: Buri 1.4
Build ID: 20140728063001
Gaia: eb3b185325901d4c04e2d43eb58d90835213bea9
Gecko: aae9112f1fc6
Version: 30.0 (1.4) MOZ
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0

Actual Results: Message does not send and user is shown error message.

	Bevis Tseng[:bevis][:btseng](Exited)
	Comment 2 • 10 years ago

According to the attached log, we Got GENERIC_FAILURE in the response of REQUEST_SEND_SMS from modem.
Need vendor's help to check instead.

	Vicamo Yang [:vicamo][:vyang]
	Comment 3 • 10 years ago

You're not even allowed to install MozRIL on Flame. Please stop doing that. This bug belongs to either Vendcom or INVALID.

	Julien Wajsberg [:julienw]
	Comment 4 • 10 years ago

Brogan, on Buri, were you using QCRIL or MozRIL? Can we please have the same logs from the Buri?

I'd like to check if MozRIL is affected too.

	Julien Wajsberg [:julienw]
	Comment 5 • 10 years ago

Can you try using 011 instead of 00 if you're in the US?

	Brogan Zumwalt [Inactive] Reporter
	Comment 6 • 10 years ago

0111+Phone Number sends and is received successfully.

We do not have access to QCRIL on our PVT builds. We have been using only MozRIL for Flame devices.

Attached logcat of issue occurring on Buri 2.0 MozRil

	Brogan Zumwalt [Inactive] Reporter
	Comment 7 • 10 years ago

Clarification to avoid confusion: Number dialed was "011 1 (xxx) xxx-xxxx"

	KTucker [:KTucker][Inactive 3/4/2016]
	Comment 8 • 10 years ago

Closing this as invalid since the exit code for the US is 011 not 00. This is working as expected.

	John Thomas [:Johnt]
	Comment 9 • 10 years ago

This is not a valid test case because the exit code for the US is 011 not 00. This is working as expected.

	KTucker [:KTucker][Inactive 3/4/2016]
	Comment 10 • 10 years ago

No test case needed as this is invalid.