Trouble receiving MMS trough MC35

Trouble receiving MMS trough MC35 SearchSearch
Author Message
Anonymous
 
Posted on Tuesday, August 17, 2004 - 10:48 am:   

Please describe in details how sould I setup NOWSMS and MC35 (siemens GPRS modem) in order to receive MMS.
Anonymous
 
Posted on Tuesday, August 17, 2004 - 11:16 am:   

I setup the modem as a SMSC connection and entered appropriate settings (MMS settings, etc).

MC35 receives MMS Notification (SMS) and tries to connect using DialUp connection to GPRS but fails. My guess is that this fails because modem port is already opened by NowSms, so Windows can't access it.

So, now I stopped NowSms and connected to DialUp connection manually and then started NowSms. So now, NowSms downloaded the MMS, but as soon as it finised it disconnected DialUp connection.

And now, if I want to receive another MMS, I have to do this process all over.

There has got to be easier way to do receive MMS.

Please help!
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 3286
Registered: 10-2002
Posted on Tuesday, August 17, 2004 - 09:57 pm:   

I think it would probably help most if you would explain exactly how you have things configured.

Did you test the connection (MMS Receive Settings) in NowSMS before saving them?

Did you create a separate dial-up networking profile for this, or did you let NowSMS create it automatically?

Normally, this "contention" between NowSMS and Windows dial-up is all taken care of automatically if:

1.) You select a "Modem:" entry in the "Network Connection" field. (This means that NowSMS dynamically generates the dial-up networking profile.)

2.) You specify in the "Modem Used" field the modem name which matches the one that you have listed in the "SMSC" page. (This way, NowSMS knows to release that modem from SMS usage when it needs to make a GPRS access.)

More information on the configuration can be found at:

http://www.nowsms.com/documentation/ProductDocumentation/mms_notifications_and_c ontent/Connecting_to_operator_MMSC.htm
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 3290
Registered: 10-2002
Posted on Wednesday, August 18, 2004 - 03:14 pm:   

Follow-up. If you need more assistance, please enable the debug logs in NowSMS so that we can better troubleshoot the problem.

Edit SMSGW.INI, and add Debug=Yes under the [SMSGW] header. Edit MMSC.INI, and add Debug=Yes under the [MMSC] header. Also, in that same directory, create a file named MMSWAP.INI, and add Debug=Yes under an [MMSWAP] header. Then restart the services.

Send a message, and then reply back including a ZIP file with the SMSDEBUG.LOG, MMSCDEBUG.LOG and MMSWAPDEBUG.LOG files from your system.

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

Post Number: 3294
Registered: 10-2002
Posted on Wednesday, August 18, 2004 - 03:43 pm:   

I think I received a forwarded e-mail that had more details about this particular incident.

In the "SMSC" list, the GSM modem was defined as "COM4:".

In the "MMS Receive Settings", the "Network Connection" was defined as "Modem: Standard Modem", and "Modem Used" was defined as "Standard Modem".

In this type of configuration, NowSMS does not know that "COM4:" and "Standard Modem" are the same device.

So, the SMS process is allocating "COM4:" for sending/receiving SMS. When the time comes to retrieve an MMS message (or to send an MMS message over GPRS via an operator MMSC), NowSMS tries to allocate "Standard Modem". This will fail because the port behind that modem driver, "COM4:" is already in use by NowSMS.

But NowSMS doesn't know that. Instead, you need to tell NowSMS.

The solution is either of the following:

1.) Change the GSM modem definition in the "SMSC" list to point to "Standard Modem" instead of "COM4:".

When the MMS process needs the "Standard Modem", it asks the SMS process to release it.

2.) Change the "Modem Used:" setting in the MMS Receive Settings to specify "COM4:" instead of "Standard Modem". This way, when the MMS process needs to use the modem, it will tell the SMS process to release "COM4:".

While either of these solutions will work, I would recommend #1, as it is less confusing.

-bn
Anonymous
 
Posted on Thursday, August 19, 2004 - 01:02 pm:   

Above explanation doesn not describe my case.

* In SMSC list I have "MC35(GPRS)".
* In MMS Settings I have "Network Connection: Modem: MC35(GPRS)" and "Modem Used: MC35(GPRS)".

This settings does not work for me (problem is described in my previous message).

Here is how I solved this:
* I made a exact copy of NowSMS DialUp connection (named it VodafoneMMS).
* In MMS Settings I changed "Network Connection: Dial-Up: VodafoneMMS" (other settings as in prevoius case).

Now receiving MMS works fine. NowSMS receives MMS with no problem and everything works fine.

Any idea on what was the problem?

Thanks.
Anonymous
 
Posted on Thursday, August 19, 2004 - 01:14 pm:   

It seems to me that SMS process releases the modem when using custom DialUp Network Connection, but fails to release it when using Modem (NowSMS DialUp) Network Connection.

It does sound a bit strange, but I have no other idea.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 3304
Registered: 10-2002
Posted on Thursday, August 19, 2004 - 03:57 pm:   

Beware that creating your own dial-up connection relies on the PDP context being initialised correctly on the modem.

For example, if you copy the dial-up profile created by NowSMS, it will be configured to dial *99#. This assumes that the PDP context id for the MMS APN is initialised and set to 1.

When NowSMS is configured with a Network Connection of "Modem: xxx", it checks the context id before each connection, initialises it if necessary, and may change the dial-up number before initiating the connection.

(If you do end up using your own dial-up profile, I would recommend that you include AT+CGDCONT=1,"IP","apn.name" in the extra commands for the initialisation of the modem driver. This ensures that the correct APN is set with a context id of 1.)

I don't have an explanation of why it is not working properly for you when you use the "Modem: name" connection. I would have to see debug logs from your system in order to analyse and understand what is occurring.

Edit SMSGW.INI, and add Debug=Yes under the [SMSGW] header. Edit MMSC.INI, and add Debug=Yes under the [MMSC] header. Also, in that same directory, create a file named MMSWAP.INI, and add Debug=Yes under an [MMSWAP] header. Then restart the services.

Send an MMS message, or receive an MMS message over the modem (whichever action you are having problems with), and then either post those log files in reply here as a ZIP attachment. Or e-mail the log files to nowsms@now.co.uk and reference this problem.

-bn