| RAS Error 619 on MMS test connection |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through April 05, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| Jack Stockdale New member Username: Jacks Post Number: 2 Registered: 07-2006 |
Hi, I've been using NowSMS without problem for a number of months but recently the setup has been getting into a state where it is unable to send MMS. We upped the licensed message rate from 5 to 20 MPM but nothing else on the system has changed (even after reverting to the old 5MPM license we still get the error). It appears to work correctly for a time, and then will fail. The logs show COM errors a 797 and then a 619 error. Is there anything obvious which may be happening which we can take action to resolve it? Or any other logs or tests which may narrow down what is happening? I've patched the software 2006.10.31, but still get the error. Thanks for any advice Jack SMSDEBUG: 08:28:26:718 [4] ThreadProcessModem: After ModemAllocate - Siemens AG WM USB Modem - OK 08:28:26:718 [4] ThreadProcessModem: Re-initializing modem: Siemens AG WM USB Modem ... 08:28:26:718 [4] ThreadProcessModem: Before ModemRelease - Siemens AG WM USB Modem 08:28:26:718 [4] ThreadProcessModem: After ModemRelease - Siemens AG WM USB Modem 08:33:26:765 [4] ThreadProcessModem: Before ModemAllocate - Siemens AG WM USB Modem 08:33:32:640 [4] ThreadProcessModem: After ModemAllocate - Siemens AG WM USB Modem - OK 08:33:32:640 [4] ThreadProcessModem: Re-initializing modem: Siemens AG WM USB Modem ... 08:33:32:640 [4] HammerNonResponsiveModem: Begin 08:33:32:640 [4] HammerNonResponsiveModem: Unable to access modem at COM3: -- Error 20 -- The process cannot access the file because it is being used by another process. 08:33:32:640 [4] HammerNonResponsiveModem: FAILED 08:33:32:640 [4] ThreadProcessModem: Before ModemRelease - Siemens AG WM USB Modem 08:33:32:640 [4] ThreadProcessModem: After ModemRelease - Siemens AG WM USB Modem 08:38:32:640 [4] ThreadProcessModem: Before ModemAllocate - Siemens AG WM USB Modem 08:39:37:171 [4] ThreadProcessModem: After ModemAllocate - Siemens AG WM USB Modem - OK 08:39:37:171 [4] ThreadProcessModem: Re-initializing modem: Siemens AG WM USB Modem ... 08:39:37:171 [4] HammerNonResponsiveModem: Begin 08:39:39:453 [4] ReceiveModemCommand: Error - 3E4 08:39:39:703 [4] TestModemSpeed: Initialised modem at 115200 bps 08:39:44:937 [4] HammerNonResponsiveModem: OK 08:39:44:953 [4] ThreadProcessModem: Before ModemRelease - Siemens AG WM USB Modem 08:39:44:953 [4] ThreadProcessModem: After ModemRelease - Siemens AG WM USB Modem 08:44:44:953 [4] ThreadProcessModem: Before ModemAllocate - Siemens AG WM USB Modem 08:45:17:015 [4] ThreadProcessModem: After ModemAllocate - Siemens AG WM USB Modem - OK 08:45:17:015 [4] ThreadProcessModem: Re-initializing modem: Siemens AG WM USB Modem ... 08:45:17:015 [4] HammerNonResponsiveModem: Begin 08:45:18:296 [4] ReceiveModemCommand: Error - 3E4 08:45:19:546 [4] TestModemSpeed: Initialised modem at 115200 bps MMSWAPDEBUG.log 08:27:49:078 [584] InitTAPI: Performing TAPI initialisation 08:27:51:078 [584] WSPRasDial: Before RasDial NowSMS - Siemens AG WM USB Modem 08:27:51:078 [584] WSPRasDial: Error 797 (31D) from RasDial 08:27:51:078 [584] WSPRasDial: Closing connection 08:28:51:140 [584] InitTAPI: Returning cached TAPI session information 08:28:51:156 [584] WSPRasDial: Before RasDial NowSMS - Siemens AG WM USB Modem 08:28:51:156 [584] WSPRasDial: Error 797 (31D) from RasDial 08:28:51:156 [584] WSPRasDial: Closing connection 08:29:36:156 [584] InitTAPI: Returning cached TAPI session information 08:29:36:171 [584] WSPRasDial: Before RasDial NowSMS - Siemens AG WM USB Modem 08:29:36:171 [584] WSPRasDial: Error 797 (31D) from RasDial 08:29:36:171 [584] WSPRasDial: Closing connection 08:30:36:187 [584] InitTAPI: Returning cached TAPI session information 08:30:36:187 [584] WSPRasDial: Before RasDial NowSMS - Siemens AG WM USB Modem 08:30:36:187 [584] WSPRasDial: Error 797 (31D) from RasDial 08:30:36:187 [584] WSPRasDial: Closing connection 08:30:51:218 [584] InitTAPI: Returning cached TAPI session information 08:30:51:218 [584] WSPRasDial: Before RasDial NowSMS - Siemens AG WM USB Modem 08:30:51:218 [584] WSPRasDial: Error 797 (31D) from RasDial 08:30:51:218 [584] WSPRasDial: Closing connection 08:31:56:234 [584] InitTAPI: Returning cached TAPI session information 08:31:56:234 [584] WSPRasDial: Before RasDial NowSMS - Siemens AG WM USB Modem 08:32:33:484 [584] WSPRasDial: Error 619 (26B) from RasDial 08:32:33:484 [584] WSPRasDial: Closing connection 08:33:32:859 [584] InitTAPI: Returning cached TAPI session information 08:33:32:875 [584] WSPRasDial: Before RasDial NowSMS - Siemens AG WM USB Modem 08:34:10:078 [584] WSPRasDial: Error 619 (26B) from RasDial 08:36:02:359 [210] InitTAPI: Returning cached TAPI session information 08:36:04:046 [210] GetCIDForAPN: Siemens AG WM USB Modem 08:36:04:046 [210] GetCIDForAPN: wap.cingular 08:36:04:046 [210] GetCIDForAPN: AT+CGDCONT=? 08:36:04:156 [210] GetCIDForAPN: +CGDCONT: (1-2),"IP",,,(0),(0-1) OK 08:36:04:156 [210] GetCIDForAPN: minCID = 1, maxCID = 2 08:36:04:156 [210] GetCIDForAPN: AT+CGDCONT? 08:36:04:250 [210] GetCIDForAPN: OK 08:36:04:281 [210] InitTAPI: Returning cached TAPI session information 08:36:06:109 [210] GetCIDForAPN: Siemens AG WM USB Modem 08:36:06:109 [210] GetCIDForAPN: wap.cingular 08:36:06:109 [210] GetCIDForAPN: AT+CGDCONT=? 08:36:06:218 [210] GetCIDForAPN: +CGDCONT: (1-2),"IP",,,(0),(0-1) OK 08:36:06:218 [210] GetCIDForAPN: minCID = 1, maxCID = 2 08:36:06:218 [210] GetCIDForAPN: AT+CG08:37:02:312 [584] InitTAPI: Returning cached TAPI session information 08:37:02:312 [584] WSPRasDial: Before RasDial NowSMS - Siemens AG WM USB Modem 08:37:39:546 [584] WSPRasDial: Error 619 (26B) from RasDial 08:37:39:546 [584] WSPRasDial: Closing connection 08:37:44:562 [584] InitTAPI: Returning cached TAPI session information 08:37:44:578 [584] WSPRasDial: Before RasDial NowSMS - Siemens AG WM USB Modem 08:38:21:812 [584] WSPRasDial: Error 619 (26B) from RasDial 08:38:21:812 [584] WSPRasDial: Closing connection 08:38:21:843 [584] InitTAPI: Returning cached TAPI session information 08:38:21:843 [584] WSPRasDial: Before RasDial NowSMS - Siemens AG WM USB Modem 08:38:59:171 [584] WSPRasDial: Error 619 (26B) from RasDial 08:38:59:171 [584] WSPRasDial: Closing connection | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6909 Registered: 10-2002 |
Hi Jack, It appears that for some reason the AT+CGDCONT command is not working properly on the modem. This command is used to specify which APN (e.g., wap.cingular) should be used for the data connection. If you test the MMS settings within NowSMS, do you get a warning message about the modem "not responding to GPRS commands"? I would expect that you would, because based upon what I am seeing in the log, the modem is not saving this setting. Actually ... hmm ... I don't see anywhere in the log where we are setting the value. That is odd. The 797 error indicates that Windows cannot find the modem. That is odd, but maybe you were disconnecting/power cycling the modem? The 619 error indicates that the connection was disconnected unexpectedly. This can be a normal situation when the APN cannot be set properly on the modem. So this error code would be consistent with the issue that I suspect, where the APN is not getting properly set. As I compare an MMSWAPDEBUG.LOG on my system to yours, it looks like the log is scrambled a bit between 8:36:06:218 and 8:37:02:312. That is the part where we would be sending out the command to set the APN. You should see something like this: AT+CGDCONT=1,"IP","wap.cingular" After that, NowSMS would go back and issue AT+CGDCONT? to make sure it gets the following back: +CGDCONT: 1, "IP", "wap.cingular", "", 0, 0 I'd suggest going into HyperTerminal, and trying these commands. Here's what I'd expect to see, so advise of anything you see that does not match my expectations: 1.) AT+CGDCONT? Expect either OK or +CGDCONT: 1, "IP", "wap.cingular", "", 0, 0 2.) AT+CGDCONT=1,"IP","wap.cingular" Expect OK 3.) AT+CGDCONT? Expect +CGDCONT: 1, "IP", "wap.cingular", "", 0, 0 This response would indicate that the setting was successfully applied. 4.) ATZ Expect OK 5.) AT+CGDCONT? Do you still get the same response as in 3? +CGDCONT: 1, "IP", "wap.cingular", "", 0, 0 If you do not get this response, it indicates that the modem loses this setting on a reset. (The NowSMS configuration program would normally try to update your modem driver to fix this problem, but this must not be working.) So if you did not get the expected response, do this: Repeat #2 Issue command AT&W Repeat #3 Repeat #4 Repeat #5 ... does it work this time? If yes, try NowSMS. If you still don't get the expected response for #5, go into "Phone and Modem Options" in the Windows Control Panel. Select "Modems". Highlight your modem and press "Properties". Select "Advanced". In the "Extra Initialization Commands" field, add: AT+CGDCONT=1,"IP","wap.cingular" --- If after all of this, you're still not getting anywhere, test the MMS settings in the NowSMS UI. Note any errors or warnings that you receive ... and post another MMSWAPDEBUG.LOG excerpt. -bn | |||
