Page cannot be found when trying to download MMS

Page cannot be found when trying to download MMS SearchSearch
Author Message
altoh
Unregistered guest
Posted on Monday, July 18, 2005 - 04:28 am:   

I have successfully configured NOWSMS to send MMS to another recipient. However the receiving party is unable to receive the incoming MMS. I have received a sms indicating the link to download the MMS but when I tried to download it, it states that the link cannot be found. What could be the problem?
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4656
Registered: 10-2002
Posted on Tuesday, July 26, 2005 - 10:06 pm:   

See http://www.nowsms.com/howmmsworks.htm, it explains how MMS works, and the 2 different ways that NowSMS can be configured to send MMS messages.

The default mode for NowSMS is to act as an MMSC. This means that NowSMS sends out a dynamically generated link for the content of the MMS message, and the receiving phone's MMS client must be able to connect back to the NowSMS server to be able to retrieve it.

If they can't, then this either means that your NowSMS server is not accessible over the internet, or the MMS settings for the mobile operator do not allow external MMSCs. There is explanation of these issues in the link referenced above.

-bn
altoh
Unregistered guest
Posted on Thursday, July 28, 2005 - 04:13 am:   

I tried to follow the steps in configuring Connecting to operator MMSC and this is the problem I received:-

10:38:44:953 [4] ThreadProcessVASPQ: mm1 - got unknown response
10:38:44:953 [4] ThreadProcessVASPQ: HTTP/1.0 502 Bad Gateway
Content-type: application/vnd.wap.xhtml+xml; charset=utf-8
Content-length: 289

<?xml version='1.0'?>
<!DOCTYPE html PUBLIC '-//WAPFORUM//DTD XHTML Mobile 1.0//EN'
'http://www.wapforum.org/DTD/xhtml-mobile10.dtd'>
<html xmlns='http://www.w3.org/1999/xhtml'>
<head>
<title>The request failed.</title>
</head>
<body>
<p><big>The request failed.</big></p>
</body>
</html>

10:38:44:953 [4] ThreadProcessVASPQ: Outbound route Singtel: setting retry for 86E70C55.MMS
10:38:44:953 [4] ThreadProcessVASPQ: Before WSPRasHangUp (#3) - Modem: iTegno GPRS Wireless Modem
10:38:48:640 [4] ThreadProcessVASPQ: After WSPRasHangUp (#3) - Modem: iTegno GPRS Wireless Modem
10:38:48:640 [4] ThreadProcessVASPQ: Before ModemRelease - iTegno GPRS Wireless Modem
10:38:48:640 [4] ThreadProcessVASPQ: After ModemRelease - iTegno GPRS Wireless Modem

I am sure I am using the correct settings - Singapore Singtel. Now I do not understand where does the "Bad Gateway" refers to.

This round, I do not even get the sms notification}
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4683
Registered: 10-2002
Posted on Thursday, July 28, 2005 - 05:37 pm:   

This generally means that you're connecting via the wrong gateway or APN.

Let me see the MMSWAPDEBUG.LOG, and advise what settings you are using for GPRS APN, WAP Gateway IP, and MMS Server URL.

-bn
altoh
Unregistered guest
Posted on Friday, July 29, 2005 - 03:54 am:   

Please see attached for the log.

GPRS APN: e-ideas
WAP Gateway IP: 165.21.42.84
MMS Server URL: http://mms.singtel.com.sg:10021/mmsc

application/octet-streamMMSWAPDEBUG
MMSCDEBUG.LOG (224.6 k)


Thanks for your help!
altoh
Unregistered guest
Posted on Friday, July 29, 2005 - 05:30 am:   

I am attaching another log which is clearer.
application/octet-streamLOG
MMSCDEBUG.LOG (118.4 k)
altoh
Unregistered guest
Posted on Friday, July 29, 2005 - 09:20 am:   

Problem solved. It's a problem of the Server Address. I used the IP address instead of the actual URL.

Thanks!!
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4712
Registered: 10-2002
Posted on Friday, July 29, 2005 - 04:38 pm:   

Ok, great. Glad to see you were able to get it fixed.

I can see that in the logs that it was trying to post to the IP of the WAP gateway, whereas the "Server Address" should be the "MMS Server URL".

-bn