MMS Receiving problem with Sierra 750 card

MMS Receiving problem with Sierra 750 card SearchSearch
Author Message
Derek Liu
Unregistered guest
Posted on Friday, April 16, 2004 - 11:18 am:   

Hi,

Please help. If this is not the right place to post following question, please do let me know.

I am developing a MMS application based on NowSMS. I have had a few problems, but i found work arounds. Now the problem at hand is simply receiving MMS. I am using a Sierra 750 card that just bought. The SIM card is provisioned OK and worked for sending MMS from a SE T610 phone/modem. What i am trying to do is to send MMS to itself through Sierra 750 card and make sure the MMS is received in mms-in directory.

I attached the smsdebug.log and mmswapdebug.log for the whole process. It seems sending part is ok, but receiving part failed, but i don't know why.

I have followed the instruction to setup 750 card. It works (got IP address) and the Watcher program was down.

I also attached the operator's (Hong Kong, Sundays) configuration parameters. One thing might be noticeable is that there are two APNs(sgprs, smms). I used smms for the 750 Watcher, otherwise, i am getting 403 forbidden error when sending MMS.

Please let me know what other information can be provided.

Regards,

Derek
text/plainsmsdebug.log
smsdebug.log.report (8.7 k)
text/plainmmswapdebug.log
mmswapdebug.log.report (42.8 k)
application/pdfOperator's GPRS/MMS setting
Sunday_Generic_Settings.pdf (56.8 k)
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2304
Registered: 10-2002
Posted on Monday, April 19, 2004 - 02:47 pm:   

Hi Derek,

I think you have used different parameters when defining the connection for the sending ("MMSC Routing" page) and receiving ("Receive MMS Messages"/"MMS Settings" under "Properties" for SMSC connection).

The sending setup appears to be configured to use the "Network" driver connection on the Aircard, while the receiving setup appears to be trying to dial it as a modem.

In the "Network Connection" parameter, the sending side is setup for "Network: GPRS - AirCard 710/750". But the receiving side setup is for "Modem: Sierra Wireless AirCard GPRS Modem", and it should be set for "Network: GPRS - AirCard 710/750". If you make that change, it should work for you.

You were correct in configuring the watcher for the APN that is used for MMS. That configures the network driver to connect to that APN (which is why the sending is working).

-bn
Derek Liu
Unregistered guest
Posted on Tuesday, April 20, 2004 - 04:28 am:   

Thanks Bruce. It worked after the change. However, it seems only working on XP box and doesn't work on my Win2K box. I am happy to stick with XP, but just curious if OS had made difference before?

Thanks again.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2370
Registered: 10-2002
Posted on Thursday, April 22, 2004 - 07:29 pm:   

Hi Derek,

I've primarily used the Sierra Aircard installed on a Win2K box. So I don't think the OS should make a difference.

What happens on Win2K?

-bn
Derek Liu
Unregistered guest
Posted on Saturday, April 24, 2004 - 09:56 am:   

I don't remember exactly what happend, but roughtly the NowSMS received the SMS notice and failed to process it and left a .SAR file in the SMS-IN directory. I will have to move things back to my win2k to capture exactly what happend. It might be just configuration error as it worked on xp.

thanks

Derek
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2412
Registered: 10-2002
Posted on Wednesday, April 28, 2004 - 06:46 pm:   

Derek,

You're left with ".SAR" files in the SMS-IN directory if NowSMS does not receive all parts of a multipart message.

I've noticed on one of my test systems (with an Aircard), this this will happen unless I configure "SMS Message Storage" in NowSMS to be "Direct to Modem". (This setting was added in v5.50 under "Properties" for the modem under the "SMSC" page. This was the default behaviour in v5.0/v5.01 ... however, we found that some modems were not behaving properly with that setting.)

-bn