| Samba 75 not reinitializing? |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through July 28, 2006 ⬆ |
◄ ► |
| Author | Message | |||
| Darren New New member Username: Dnew Post Number: 1 Registered: 07-2006 |
I have a Falcon Samba 75. I can send MMS from the software that comes with it, and I can send and receive SMS with both the Falcon software and NowSMS. However, I cannot send MMS from NowSMS. (I seem to have managed to receive MMS once or twice, but I can't find those settings again.) Doing the MMS Test button works the first time, but complains the modem isn't responding to GPRS commands the second time. Sometime it'll say it's hammering the modem but the modem isn't responding to the data, but I can't seem to get that to happen again. Are there any known problems with this combination? Anything I might be doing wrong? Even when it looks like it's working, nothing shows up at the destination, so I'm not sure how to debug this. Note that it *does* work as expected with the other software on the same machine, same modem, etc. Any ideas? | |||
| Darren New New member Username: Dnew Post Number: 2 Registered: 07-2006 |
It looks like if I let it run long enough, it eventually hammers the modem into submission. However, having to retry several times over the course of several minutes for each message seems wrong. Is there a known problem with this modem, or a known fix for this? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6262 Registered: 10-2002 |
Hi Darren, It sounds like the modem is not properly terminating the GPRS connection. After you send an MMS message, we need to drop the GPRS connection in order to go back to sending/receiving SMS. When we detect that a modem is not responding we have a routine that we refer to as "hammering the modem". It tries various tricks to wake up a non-responsive modem. From your description, it sounds like this hammering is not succesfully recovering the modem, but the modem recovers itself after some period of time. I'd be curious to see an SMSDEBUG.LOG to see if that helps me understand the pattern any better. But if it is consistent that the "MMS Test" button works the first time, and always complains about the modem not responding to GPRS commands the second time ... then I would suspect that there is a problem with the modem properly terminating the GPRS connection. Normally, the default behaviour for a modem is to drop any active connection when the computer drops the DTR signal. So a Windows modem driver would drop the DTR signal when it wants to terminate a connection. Since that is a USB modem, it is possible that the USB driver is having a problem asserting this signal. Or a problem with the modem cable. Or a problem with the modem itself. (Maybe even a problem with the USB port.) I think it would be a good idea to try some quick tests on another PC as a first test. It is also possible that for some particular reason, this particular modem does not default to using the DTR signal. Normally, the AT&D2 command is used to tell the modem to use the DTR signal in the way that I've described (and AT&D0 tells the modem to ignore DTR). But normally, this is the default setting of the modem. It wouldn't hurt to manually send this AT&D2 command out to the modem, just to make sure that it is using DTR properly. The trick is, when would you send this command? While there are configuration options in NowSMS to send additional AT commands before or after NowSMS performs modem initialisation ... I'm not sure that is the right place. The problem seems to be recovering after an MMS related GPRS connection. And the Windows modem driver performs its own modem initialisation during this process ... and I think it is this initialisation process that should send the AT&D2 command. If you go into the Windows Control Panel, select Phone and Modem Options ... then select your Modem ... and find the area that lets you define "Extra Initialization commands". Put AT&D2 into this setting. It's somewhat of a longshot that this would make a difference. If that doesn't make a difference ... then I'd be curious of the following ... NowSMS creates a Windows dial-up networking profile named "NowSMS - your modem driver". Shut down NowSMS ... and try connecting to this connection manually. Then close the connection ... and try connecting again. Do you receive any error? (If you do, then I think there's a hardware or driver problem, because doing this should not be a problem.) -bn | |||
