Telstra 3G MMS Settings

Telstra 3G MMS Settings SearchSearch
Author Message
Oliver Palmer
New member
Username: Opalmer

Post Number: 9
Registered: 12-2003
Posted on Tuesday, July 18, 2006 - 12:04 pm:   

Hey Bryce,

Having issues connecting to Telstra's 3G network (launched Dec 05) for downloading MMS messages. The message arrived in the Q folder but NowSMS is unable to download the message. Note it works perfectly if the SIM is put in a handset.

The Q message is:

[MMSINQ]
To=0448124365/TYPE=PLMN
ModemName=USB Falcom Samba MC75 #2
Notification=8C82983174696436313434383132343336355F376F69372D303130393032008D928 90D8036313432333736393734360086818A808E02830E88058103016D9483687474703A2F2F31373 22E31372E372E31362F6D6D732F776170656E633F6C6F636174696F6E3D363134343831323433363 55F376F69372D30313039303200
ContentLocation=http://172.17.7.16/mms/wapenc?location=61448124365_7oi7-010902
FirstAttemptTime=20060718202130
RetryCount=4
LastRetryTime=20060718202917

Have tried all sorts of settings, including those actually on the handset. Is there any way of tracking what the download issue is through the log files etc.

Cheers
Oliver Palmer
New member
Username: Opalmer

Post Number: 10
Registered: 12-2003
Posted on Tuesday, July 18, 2006 - 12:28 pm:   

Here is the debug log (or the bit of it that looks relevant!)

21:08:44:015 [5] ThreadProcessInboundMMS: Packet Length is 33 bytes
21:08:44:015 [5] ThreadProcessInboundMMS: 48 54 54 50 2F 31 2E 30 20 35 30 30 20 49 6E 76 HTTP/1.0 500 Inv
21:08:44:015 [5] ThreadProcessInboundMMS: 61 6C 69 64 20 52 65 73 70 6F 6E 73 65 0D 0A 0D alid Response
21:08:44:015 [5] ThreadProcessInboundMMS: 0A
21:08:44:015 [5] ThreadProcessInboundMMS: mm1 - got unknown response
21:08:44:015 [5] ThreadProcessInboundMMS: HTTP/1.0 500 Invalid Response


So MM1 - got unknown response and HTTP/1.0 500 Invalid Response would seem to be the problem...
Oliver Palmer
New member
Username: Opalmer

Post Number: 11
Registered: 12-2003
Posted on Thursday, July 27, 2006 - 05:47 am:   

Hi Bryce,

We have been speaking with the Australian carrier on this and this is the reason for the failure above:
___________________________________________
It failed because of Error-no-subscriber-ID – that is the WAP Gateway could not insert an MSISDN in time… The MMSC would have responded with a HTTP 401 Unauthorised, which perhaps could be retried upon if desired…

Perhaps a retry would work if the WAP Gateway obliges by including the MSISDN this time ;-)

_________________________________________________

Any reason why NowSMS would not send through the MSISDN in order to authenticate with the MMSC at the other end?

Many thanks,

Oliver

Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 6253
Registered: 10-2002
Posted on Thursday, July 27, 2006 - 09:43 pm:   

Hi Oliver,

Apologies for the delay in response ... I've been struggling to get caught back up out here after a week's holiday.

Could you please post a longer except of your MMSWAPDEBUG.LOG?

Please note that it is not normal for the mobile phone to identify its MSISDN. If it did, then you could pretend to be any phone number that you wanted.

Instead, it is customary that the WAP proxy identifies the phone number, and inserts an MSISDN to identify the requesting device to other network components, such as the MMSC.

(CDMA handsets do frequently insert their own MSISDN header. We frequently see this with CDMA devices that are used in test labs, where the phone sends an X-VzW-MSISDN header, which appears to be specific to Verizon Wireless. However, I can't believe that a mobile operator would have a trust model relying on the handset to identify itself in this way, as it would be too easy to spoof.)

Anyway, I'd like to see more detail from the MMSWAPDEBUG.LOG, so that I can see what proxy you are talking to, and compare that against MMS settings that would normally be used in a phone on that network.

I'm wondering if perhaps the issue is that the WAP gateway IP that we are using (10.1.1.155), might not be able to properly receive MSISDN for a connection coming from a 3G device on that network.

In your working 3G phone, what are the MMS settings configured in that device? Specifically, what proxy (and what port on the proxy) is it using?

It is possible that the 3G devices need to go through a different proxy, as most 3G devices use WAP2/HTTP instead of WAP/WSP.

To configure NowSMS to use a WAP2/HTTP proxy, use the following syntax in the "WAP Gateway IP Address" field:

http://ip.address:port

-bn
Oliver Palmer
New member
Username: Opalmer

Post Number: 12
Registered: 12-2003
Posted on Thursday, July 27, 2006 - 09:53 pm:   

Hey Bryce,

Thanks for your reply. All the details have been confirmed by the telco company here. Below are the comments from the technical team:

___________________________________

I would suggest setting your HTTP user-agent: string to “NokiaN70-1/5.0609.2.0.1 Series60/2.8 Profile/MIDP-2.0 Configuration/CLDC-1.1 UP.Link/6.3.0.0.0” (without the quotes) as this is a provisioned handset when you do a HTTP GET to download the MMS message.



As Anna mentioned, upon further investigation you seem to be getting this MSISDN Insertion Issue way more often than you should which points towards some kind of malformation in the MM1 (HTTP GET used to retrieve the MMS message).



Perhaps you can provide an example of a HTTP GET you use to download an MMS and we can have a look at it…

___________________________________________

I have a Siemens UMTS modem that we are using, this works perfectly for Optus here in Australia but does not work with another carrier. So the problem is carrier specific. Is there anyway of simulating a handset using the UAProfile as has been suggested above? I have more correspondence which I am looking in to.

Happy to send the logs through to you, can I email them to you directly?

Regards,

Oliver
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 6259
Registered: 10-2002
Posted on Friday, July 28, 2006 - 08:27 pm:   

Hi Oliver,

I'm still a bit suspicious about the explanations that you're getting.

Is it possible for you to check the proxy settings that would be used in an actual mobile phone on that network. For example, the Nokia N70 whose user-agent string you quote above, does not support WAP/WSP connections ... it only supports WAP2/HTTP. So that's why I'm thinking that the problem here is that when the connection comes in from a 3G APN, the carrier's network is not forwarding the MSISDN information to the WAP/WSP gateway ... because they expect that all 3G devices will be using the WAP2/HTTP gateway only.

So I think it would be a good idea to try this. I've done some searching on the internet, and I just can't seem to locate these settings ... but if you have a working phone on that network, you should be able to find them by going through the configuration settings on the phone.

It is possible to set the "User-Agent:" header. The following thread provides an example of the settings: http://support.nowsms.com/discus/messages/485/13063.html

Please feel free to send me any logs. Send them to nowsms@now.co.uk, and put "Attention: Bryce" in the subject line. In the text of the e-mail, remind me of why you're sending me the logs (a link to this thread would be helpful).

-bn
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 6275
Registered: 10-2002
Posted on Monday, July 31, 2006 - 07:24 pm:   

Oliver,

Thanks for sending that log file via e-mail. I'm also posting parts of my reply here, in case this problem affects others who are using NowSMS with Telstra 3G.

The behaviour in the log file is definitely strange. Basically, we are downloading the complete MMS message successfully ... but failing to recognise it as a successful download.

It appears that there is a logic problem in our WSP handling (well, technically at the WTP level) ... and we are getting confused by an optional parameter that is being included in the header by Telstra's WAP gateway.

I've posted an update that will correct this problem to http://www.nowsms.com/download/20060731.zip.

I'd appreciate it if you could try this update to see if it resolves the problem, as we haven't been able to test this fix live (as we don't see any other WAP gateways inserting this particular header).

You should also be able to quickly resolve the issue by changing the "WAP Gateway IP Address" setting to be http://10.1.1.180:80 (this will route it via the WAP2/HTTP proxy instead of the WAP/WSP proxy). Based upon the information that you forwarded me in your e-mail, this would appear to the be the correct address. It will also most likely be faster if you go this route. However, that said, if you have more than one modem connected to the same mobile operator (I see from your log that you have multiple modems, but it appears they might be connected to different operators), then it may be more reliable to stick with the existing WAP/WSP proxy. If the multiple modems all connect to different operators, then the WAP2/HTTP proxy setting will likely offer better performance.

-bn