995925 - [Sora]MMS User Agent sent by the device is incorrect

Status: RESOLVED INVALID

(Firefox OS Graveyard :: RIL, defect, P1)

Description

[sync-1]

Dears,
 
 Telefonica has tested this problem in V124 and at their servers they still see that the phone is sending this user Agent for MMS:
 
 Mozilla/5.0 Gecko/28.0 Firefox/28.0
 
 BUT, we use tcpdump to get the http head package, open it with wireshark
 It shows :
 
 AS per the attached pcap.log I can see that it is using this for MMS:
 POST http://mms.movistar.com/ HTTP/1.1
 
 Host: mms.movistar.com
 User-Agent: Mozilla/5.0 (Mobile; ALCATELOneTouch4019X; rv:28.0) Gecko/28.0 Firefox/28.0
 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
 Accept-Language: es,es-ES;q=0.8,es;q=0.6,en-US;q=0.4,en;q=0.2
 Accept-Encoding: gzip, deflate
 Content-Type: application/vnd.wap.mms-message
 Content-Length: 552
 x-wap-profile: http://www-ccpp.tcl-ta.com/files/ALCATELOneTouch4019X.xml
 Connection: keep-alive
 Pragma: no-cache
 Cache-Control: no-cache
 ----------
 
 My suspicious is that we are not looking propoerly at the logs, or maybe the MMS protocol is defined at another layer. Please help to fix this issue as it is blocker for Telefonica

Comment 1

[sync-1]

Attachment: LOG

Comment 2

[sync-1]

Attachment: LOG file in plain text

Comment 3

[sync-1]

Attachment: V124_log2_MMS.pcap

Comment 4

[Jack Liu]

Hi Vance,

Please help on this issue, how to confirm UA string properly customized?

Could you please help verify on Sora device with the same build as sent to Telefonica?

Thanks a lot.

Comment 5

[Jack Liu]

Comment from customer:

The operator is not using TCPDUMP they are getting the user agent by network
log at the Telefonica MMS server.

I have the suspicious that probably the MMS client at phone is causing this
problem.

Comment 6

[Vance Chen [:vchen][skype:vance.lucida][[e-mail]]]

Hi Jack -

I think we need to check with TEF first to see what is the desired user agent they want. 

According to the log "V124_log2_MMS.pcap", the device post a request to MMSC:

 POST http://mms.movistar.com/ HTTP/1.1

So the above is not a user agent, but a HTTP Post request.

And following that is the user agent and some other headers:

Host: mms.movistar.com
 User-Agent: Mozilla/5.0 (Mobile; ALCATELOneTouch4019X; rv:28.0) Gecko/28.0 Firefox/28.0
 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
 Accept-Language: es,es-ES;q=0.8,es;q=0.6,en-US;q=0.4,en;q=0.2
 Accept-Encoding: gzip, deflate
 Content-Type: application/vnd.wap.mms-message
 Content-Length: 552
 x-wap-profile: http://www-ccpp.tcl-ta.com/files/ALCATELOneTouch4019X.xml
 Connection: keep-alive
 Pragma: no-cache
 Cache-Control: no-cache

However, i am not sure if the user agent can be modified since this is defined by Mozilla, so could you help to check with TEF again? Also it would be best if we can have Buri log as well

Thanks

Vance

Comment 7

[Beatriz Rodríguez [:brg]]

The UA including device model:
 User-Agent: Mozilla/5.0 (Mobile; ALCATELOneTouch4019X; rv:28.0) Gecko/28.0 Firefox/28.0

It is enough to pass certification. Please check with your local team. It seems to be an issue in the TEF server side that it is ignoring these () symbols...

Comment 8

[Viga]

(In reply to Beatriz Rodríguez [:brg] from comment #7)
> The UA including device model:
>  User-Agent: Mozilla/5.0 (Mobile; ALCATELOneTouch4019X; rv:28.0) Gecko/28.0
> Firefox/28.0
> 
> It is enough to pass certification. Please check with your local team. It
> seems to be an issue in the TEF server side that it is ignoring these ()
> symbols...

Thanks for your comments

Comment 9

[sync-1]

Dears it looks like that the Telefonica server is not getting the information from the user agent between brackets.
 
 Please leave this issue opened to Monitor until Telefonica confirms that this is a problem in their server.

Comment 10

[Julien Wajsberg [:julienw]]

(In reply to Jack Liu from comment #5)

> I have the suspicious that probably the MMS client at phone is causing this
> problem.

If tcpdump is showing the right user-agent, then that's what's being sent to the network and the client is correct.

Now, I really don't like that we have the phone model in the user-agent.. is this happening for MMS only, or is it happening on the Web?

Comment 11

[Viga]

Both, It's the operator's certification request.

Comment 12

[Jack Liu]

(In reply to Vance Chen [:vchen][[e-mail]] from comment #6)
> Hi Jack -
> 
> I think we need to check with TEF first to see what is the desired user
> agent they want. 
> 
> According to the log "V124_log2_MMS.pcap", the device post a request to MMSC:
> 
>  POST http://mms.movistar.com/ HTTP/1.1
> 
> So the above is not a user agent, but a HTTP Post request.
> 
> And following that is the user agent and some other headers:
> 
> Host: mms.movistar.com
>  User-Agent: Mozilla/5.0 (Mobile; ALCATELOneTouch4019X; rv:28.0) Gecko/28.0
> Firefox/28.0
>  Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
>  Accept-Language: es,es-ES;q=0.8,es;q=0.6,en-US;q=0.4,en;q=0.2
>  Accept-Encoding: gzip, deflate
>  Content-Type: application/vnd.wap.mms-message
>  Content-Length: 552
>  x-wap-profile: http://www-ccpp.tcl-ta.com/files/ALCATELOneTouch4019X.xml
>  Connection: keep-alive
>  Pragma: no-cache
>  Cache-Control: no-cache
> 
> However, i am not sure if the user agent can be modified since this is
> defined by Mozilla, so could you help to check with TEF again? Also it would
> be best if we can have Buri log as well
> 
> Thanks
> 
> Vance

Hi Vance,

Thanks for you help and we are waiting local team feedback to confirm.

Comment 13

[Beatriz Rodríguez [:brg]]

2014, May, someone from TEF testing house wrote: "This issue could be caused by a server problem. This bug is invalid. Bug closed"

Comment 14

[Julien Wajsberg [:julienw]]

So let's do that :) Thansk Beatriz !