| Increasing the timeout response for MMS content retrieval |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through April 05, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| Aidan Cope New member Username: Acope Post Number: 7 Registered: 09-2006 |
I am getting a timeout when I am retrieving an MMS from Cingular's MMSC. I looked through the optional parameters that you can set in NowSMS, and there didn't seem to be any way to increase this wait time. It eventually ends up connecting usually on the second try, but it would be nice to give it a bit more time to connect, rather than having to wait another cycle. The log file produces: 13:53:32:139 [4] ThreadProcessInboundMMS: After WSPRasDial - OK 13:53:33:420 [4] ThreadProcessInboundMMS: GET http://66.102.171.150/RQ8HFUJmq5QAAFUnAAAAAgABgtMAAAAA HTTP/1.1 Accept: application/vnd.wap.mms-message Host: 66.102.171.150 13:54:36:233 [4] ThreadProcessInboundMMS: mm1 - timeout waiting for response 13:54:36:233 [4] ThreadProcessInboundMMS: Before WSPRasHangUp (#3) - Modem: Standard 33600 bps Modem 13:54:40:748 [4] ThreadProcessInboundMMS: After WSPRasHangUp (#3) - Modem: Standard 33600 bps Modem Thanks in advance! | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6551 Registered: 10-2002 |
Hi Aidan, Hmm ... I guess what is unusual is that in such a delayed response scenario, there should be an ACK returned to indicate that the WAP proxy received the request. We'll wait for 2 minutes of idle time after getting an ACK. But we'll only wait about 60 seconds for the ACK. (In fact, since we are not getting this ACK, we are resending the request several times ... the WAP proxy should recognise these as duplicate requests, but I'm surprised we're not getting an ACK!) I'll look to see if we can change this timeout (it appears hardcoded), but in the meantime, here's a suggestion ... try changing the WAP Gateway IP address from: 66.209.11.61 to http://66.209.11.32:8080 (It may seem counter-intuitive, but leave the "http://" prefix in there like I have above.) Does this work better for you? -bn | |||
| Aidan Cope New member Username: Acope Post Number: 8 Registered: 09-2006 |
I tried using the WAP gateway from above, but it's saying that it can not connect to it. WSPConnect: Proxy Connection failed: http:66.209.11.32:8080 WSPRasDial: Unable to connect to WAP gateway at http:66.209.11.32:8080 | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6553 Registered: 10-2002 |
Hmm ... I guess you can't believe everything that you read on the internet.  I found multiple sites that seemed to reference that as a setting for certain mobile phones on Cingular. But I also see some where instead of "8080", it is "80" ... and others where it is "9201". I don't have access to a device on Cingular for testing right now. But it may be worth your trying ":80" and ":9201" in place of ":8080" to see if you get anywhere. If not, go back to the other setting. Meanwhile, I'll see about getting that timeout increased. -bn | |||
| Jesse S New member Username: Jesse59672 Post Number: 1 Registered: 11-2006 |
I dont know where to post this, but i have a cheap motorolla (my razer broke) and anyways today I received 3 text messages. They all say &application/vnd.wap.mms-message from number 1111301000. I'm wondering why i received them. By the way my phone isnt internet capable and I only use it for calls/text messaging. | |||
| Malcolm - Now Support New member Username: Malcolm Post Number: 6 Registered: 12-2006 |
This isn't the right place for this type of question. This is the suppot forum for the Now SMS/MMS Gateway product. But ... short answer ... somebody tried to send you an MMS message. Your mobile service provider thinks you have a phone that supports MMS (your RAZR), and is trying to deliver the MMS message to you. A specially formatted binary SMS message is sent to trigger the MMS delivery process, but your phone does not understand it. | |||
