| 2nd MMS always fails with PT-2 |  Search
|
|
NowSMS Support Forums ⬆ Now.WAP Proxy Support ⬆ Archive through September 22, 2005 ⬆ |
◄ ► |
| Author | Message | |||||
| Matt Allie New member Username: Matt Post Number: 12 Registered: 02-2004 |
Hello, I'm using Nokia PT-2 phones (Observation Camera)to send VGA snapshots via MMS at regular intervals. The first MMS is always successful, but the 2nd one seems to hang towards the end of the UL transfer. It works this way: PT-2 takes a snaphots, then GPRS attaches, then activates a PDP and then sends the MMS containing one jpeg attachment. I dont know why the 2d one fails: it hangs and stay there forever until I reset the phone. The MMS size is around 50kbytes. I'm using nowSMS WAP gateway and MMSC. SGSN is 10.176.99.100 PT-2 gets IP@ 10.176.98.0 (GSN has NAT enabled). WAP and MMSC run on same WinXP laptop: 10.176.99.40. PT-2 sends MMS using a VASP account: received MMS is stored in MMS-IN directory. No MMS limit is set for the VASP account! Attached are the WAP debug files: it contains 2 MMS: the first one is successful and the second failed. Looks like the WAP session is still hanging...it the WAP expecting more data? Thanks for your help! -Matthieu
| |||||
| Matt Allie New member Username: Matt Post Number: 14 Registered: 02-2004 |
It seems that if after each MMS from the PT-2 I stop/restart the WAP service, then it is fine. If i dont, then the 2nd MMS fails... thanks | |||||
| Matt Allie New member Username: Matt Post Number: 15 Registered: 02-2004 |
One more (important) thing: if i restart the WAP service in between MMS, then it is fine! Also, if PT-2 gets a different IP@ at each GPRS PDP activation, it seems fine as well. This is quite surprising since the originating IP@ that reached the WAP is the GSN (because of NAT). The port might be different though... With a P800, I can send as many MMS is row as I want with no pb... Thanks! | |||||
| Kent Williams Moderator Username: Kent Post Number: 45 Registered: 10-2003 |
Hi Matt, This is a tough one to explain. But the problem does have to do with the facts that: 1.) The device gets assigned the same IP address on each connection, and connects from the same port on each connection. 2.) The device starts its transaction id counter at 1 for each connection, so the MMS transaction has the same id each time. We maintain some state information about SAR transactions, even after they have been completed, so that the gateway can respond intelligently to lost packets that arrive out of sequence. But that state information should be cleared by a connect/disconnect and it is not. As Bryce mentions in the other discussion thread (http://support.nowsms.com/discus/messages/485/3394.html), it is automatically cleared after 5 minutes ... and there is a config setting to adjust this, but I don't think it is worth going into. The better solution is to fix the problem so that the state information is properly cleared. I've uploaded an update to http://www.nowwap.com/download/update.zip. Stop the Now.WAP service. Use the file in the ZIP to update the existing file of the same name. Then restart the service, and this should take care of the problem. -- Kent Williams Now Wireless Support | |||||
