| Cant send sms |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through June 24, 2009 ⬆ |
◄ ► |
| Author | Message | |||
| wong New member Username: Warpig Post Number: 1 Registered: 03-2009 |
i am using nowsms trial version, i noticed that i could receive sms and mms but cannot send sms. i tried send using web interface but the message appeared in Q folder. [SMS] SubmittedBy=127.0.0.1 PhoneNumber=+XXXXXXXXXXX Data=hello pid=00 dcs=00 Binary=0 [ErrorDetail] RetryCount=12 LastRetryTime=20090311164423 | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 568 Registered: 08-2008 |
Hi, What is the error message in the SMSOUT-yyyymmdd.LOG file? That will tell us what error is being reported by the modem. -- Des NowSMS Support | |||
| wong New member Username: Warpig Post Number: 2 Registered: 03-2009 |
2009-03-11 18:02:08,49B77358.req,127.0.0.1,+XXXXXXXXXX,ERROR - Modem Response (2): ERROR -- Standard 56000 bps Modem,Text="hello" | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 576 Registered: 08-2008 |
Hmm...what brand/model modem is this? When we try sending the message, NowSMS is getting back a response that simply says "ERROR". The trick is figuring out why. What we have observed is that there are some USB and card modems which expose multiple virtual COM port devices to the PC. When this is the case, usually only one of the ports is actually allowed to send messages. This is frequently the case with Sierra Wireless modems, and you can go into the Windows Control Panel / System / Device Manager to view the COM & LPT ports where you can get a clue as to which ports the modem is using. There was also an issue with some Nokia phones where NowSMS was sending commands too quickly for the modem. The modem would report errors but actually send the message. For this issue, it may be worth updating to the NowSMS 2009 release candidate version at http://www.nowsms.com/download/nowsms2009rc.zip to see if it works any better with this particular modem. -- Des NowSMS Support | |||
| tunde New member Username: Tundeemma Post Number: 1 Registered: 03-2009 |
Hello All, i am developing an application to work as a GSM service provider. For demo i am using Sierra Wireless modems for test but i am not getting error. Not sending or receiving any message. could anyone help. Thanks | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 581 Registered: 08-2008 |
Hi Tunde, Recent Sierra Wireless modems are a little bit tricky. I recently wrote up some instructions regarding the Sierra Wireless 881U...although other models should be quite similar. This info should help... The Sierra Wireless 881 USB Modem (881U) is a good modem to use with NowSMS. However, it can be a frustrating modem to get properly configured. The reason for this is because the primary market for this modem (and other USB modems) is to provide internet connectivity. If you're looking at using this modem (or a similar modem) with NowSMS, it's probably best not to purchase the modem from the mobile operator with a data plan. When you do this, they are assuming that the primary use of the modem is internet connectivity, and NowSMS will not use the modem for that purpose. Often these data plans don't even have SMS or MMS services enabled. When you attempt to add the Sierra Wireless 881 USB Modem to NowSMS, you will most likely encounter the error message "Modem does not properly support command for sending SMS (AT+CMGS)". Or, with older versions of NowSMS, the modem will add correctly, however any attempt at sending SMS messages will result in the error "ERROR -Modem Response (1): OK". These errors happen because the driver software for the Sierra Wireless modems actually installs several virtual COM ports for communicating with the modem. One of these ports can be used for sending/receiving SMS messages, while the other port can only support data/internet connectivity. Older Sierra Wireless modems would install two Windows modem drivers, one for each port. The modem driver "Sierra Wireless AirCard HSDPA Modem" would work with NowSMS and provide support for sending/receiving SMS mesasges. However the modem driver "Sierra Wireless AirCard 3G Modem" did not work with NowSMS, and could only be used for data/internet connectivity. With the 881U modem, multiple virtual COM ports are installed by the Sierra Wireless software. However, a Windows modem driver is installed for only one of these COM ports, so when you select "Sierra Wireless AirCard 881U HSDPA Modem", you are connecting to a COM port that only supports data/internet connectivity. To be able to send/receive SMS messages, it is necessary to identify the other COM port. To identify the COM port, go into the System applet in the Windows Control Panel, and access "Device Manager". In the "Ports (COM & LPT)" section, you will find a port labeled "Sierra Wireless AT Command Port (UMTS)", followed by a COM port number such as COM8. Once you have identified the COM port number, it is possible to add the modem to NowSMS by referencing the COM port number directly. However, if you use the COM port directly in NowSMS, you won't be allowed to configure the modem for sending and receiving MMS. It will support SMS only. The simple way to enable support for sending/receiving MMS is to manually install a Windows Modem driver for this COM port. This can be done through the "Phone & Modem Options" applet in the Windows Control Panel. We recommend that you manually select the modem driver, rather than having Windows detect the modem. For best results, use the "Standard 33600 bps Modem" driver. After installing this Windows modem driver, configure NowSMS to use the "Standard 33600 bps Modem" to connect with the Sierra Wireless 881U, instead of using the direct COM port reference. -- Des NowSMS Support | |||
| tunde New member Username: Tundeemma Post Number: 2 Registered: 03-2009 |
Hello, Thanks very much for your quick response and good information given.I am using the 3g 580 got from the operator but before this time i do send and receive sms through the card. but now i can only receive the card will not send. However, what i am looking for specifically is to build an sms,mms gateway, or say be a sms service provider that will be very cheap or almost free to the people in my country and others arround us. My company is ready to partner with any other company on this project who is ready to help us achive this goal. I will appreciate if you can give me more information on how we can go about this project. Regards | |||
| tunde New member Username: Tundeemma Post Number: 3 Registered: 03-2009 |
Hi Des, I have tried your suggestion to register a new modem but my system did not give me list of COM ports to select from as the port to which the new modem "Standard 33600 bps Modem" driver is communication. Pls any help. tunde | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 584 Registered: 08-2008 |
Hi Tunde, Is this a Sierra Wireless 580? That model is a CDMA device, which would probably not work with NowSMS at all. However, I did think of one other common issue for situations where you are receiving SMS messages with no problem, but cannot send SMS messages. In the "Properties" for the modem in the "SMSC" list of NowSMS, try changing "SMS Access" to be GSM. Many mobile operators do not enable SMS over their packet network, and sometimes modems get confused and do not fall back to trying over the circuit switched network. -- Des NowSMS Support | |||
| jorge luis florez New member Username: George8504 Post Number: 1 Registered: 03-2009 |
Hi, I'm using nowsms v2008.06.03, The software works well, but the messages are sent every exact one minute, how can I change this? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 610 Registered: 08-2008 |
Hi, The best solution is to purchase a licensed copy of the software. To contact us, please see http://www.nowsms.com/contact.htm. -- Des NowSMS Support | |||
| tunde New member Username: Tundeemma Post Number: 4 Registered: 03-2009 |
Hi buying this software, what is least amount i can send sms through it and can give me list of the modems that work perfectly ( on commercial base) with this software. I will like to know what type developer support you provide. Thanks | |||
| wong New member Username: Warpig Post Number: 3 Registered: 03-2009 |
still not working des. i am using wavecom fastrack 10 and connecting it to my pc using COM1. before that i did try sms api from other resources. will it affected the sending process? and is it nowsms only using one service to send and receive mms/sms or need more services started? | |||
| wong New member Username: Warpig Post Number: 4 Registered: 03-2009 |
2009-03-19 15:44:09,49C1F452.req,127.0.0.1,+XXXXXX,OK -- Standard 56000 bps Modem,Text="abc def ghi" 2009-03-19 16:52:28,49C1F458.req,127.0.0.1,+XXXXXXXXXX,Retry Pending - ERROR - Modem Response (2): ERROR -- Standard 56000 bps Modem 2009-03-19 16:52:30,49C1F458.req,127.0.0.1,+XXXXXXX,Retry Pending - ERROR - Modem Response (2): ERROR -- Standard 56000 bps Modem help!! i noticed that i could send the message again once i restart the modem. but after the modem receiving mms i cant send sms again... | |||
| wong New member Username: Warpig Post Number: 5 Registered: 03-2009 |
Retry Pending - ERROR - Modem Response (2): +CMS ERROR: 69 -- Standard 56000 bps Modem this is the latest error after i install nowsms2009 | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 615 Registered: 08-2008 |
Wong, CMS ERROR 69 is very puzzling. According to the Wavecom documentation, this is what it means:
I've only seen this before when SMS services were not enabled for a SIM card ... not as a sporadic error. Are you saying this only happens after you receive an MMS message with the modem? I'd suggest enabling the SMSDEBUG.LOG. Repeat this sequence (where it is working at start, and then stops working) and post the SMSDEBUG.LOG so that I can take a closer look at it. -- Des NowSMS Support | |||
| wong New member Username: Warpig Post Number: 6 Registered: 03-2009 |
14:04:49:707 [13] ThreadProcessConnection: Processing connection from 127.0.0.1... 14:04:49:707 [13] ThreadProcessConnection: Processing request / 14:04:49:707 [13] WaitForSocketClose: WinSock reported ioctlsocket complete 14:04:49:707 [13] ThreadProcessConnection: Request processing complete 14:04:49:832 [13] ThreadProcessConnection: Processing connection from 127.0.0.1... 14:04:49:832 [13] ThreadProcessConnection: Processing request /TOCFrame.htm 14:04:49:847 [14] ThreadProcessConnection: Processing connection from 127.0.0.1... 14:04:49:847 [14] ThreadProcessConnection: Processing request /Send%20Text%20Message.htm 14:04:49:847 [13] WaitForSocketClose: WinSock reported ioctlsocket complete 14:04:49:847 [13] ThreadProcessConnection: Request processing complete 14:04:49:863 [14] WaitForSocketClose: WinSock reported ioctlsocket complete 14:04:49:863 [14] ThreadProcessConnection: Request processing complete 14:04:49:910 [13] ThreadProcessConnection: Processing connection from 127.0.0.1... 14:04:49:910 [13] ThreadProcessConnection: Processing request /background.gif 14:04:49:910 [14] ThreadProcessConnection: Processing connection from 127.0.0.1... 14:04:49:910 [14] ThreadProcessConnection: Processing request /logo.gif 14:04:49:926 [13] WaitForSocketClose: WinSock reported ioctlsocket complete 14:04:49:926 [13] ThreadProcessConnection: Request processing complete 14:04:49:926 [14] WaitForSocketClose: WinSock reported ioctlsocket complete 14:04:49:926 [14] ThreadProcessConnection: Request processing complete 14:04:50:066 [13] ThreadProcessConnection: Processing connection from 127.0.0.1... 14:04:50:066 [13] ThreadProcessConnection: Processing request /favicon.ico 14:04:50:066 [13] WaitForSocketClose: WinSock reported ioctlsocket complete 14:04:50:066 [13] ThreadProcessConnection: Request processing complete 14:04:52:910 [13] ThreadProcessConnection: Processing connection from 127.0.0.1... 14:04:52:910 [13] ThreadProcessConnection: Processing request /favicon.ico 14:04:52:910 [13] WaitForSocketClose: WinSock reported ioctlsocket complete 14:04:52:910 [13] ThreadProcessConnection: Request processing complete 14:04:59:894 [13] ThreadProcessConnection: Processing connection from 127.0.0.1... 14:04:59:894 [13] ThreadProcessConnection: Processing request /Send%20Text%20Message.htm?PhoneNumber=%2B60176105331&Text=help+desperate&InfoCh arCounter=&PID=&DCS=&DestPort=&DelayUntil=&Submit=Submit 14:04:59:894 [13] Debug: 1 recipient entries 14:04:59:894 [13] ThreadProcessConnection: Before message loop 14:04:59:894 [13] ThreadProcessConnection: Before message loop 14:04:59:894 [13] ThreadProcessConnection: Begin message loop 14:04:59:941 [13] ThreadProcessConnection: End message loop 14:04:59:941 [13] WaitForSocketClose: WinSock reported ioctlsocket complete 14:04:59:941 [13] ThreadProcessConnection: Request processing complete 14:05:00:926 [4] ThreadProcessModem: Processing 49C21B87.req... 14:05:00:926 [4] ThreadProcessModem: OUT: AT+CMGS=26 14:05:00:988 [4] ThreadProcessModem: IN: > 14:05:00:988 [4] ThreadProcessModem: OUT: 0001010B910671165033F100000EE8321B0E2297E7F0B23C4C2F03 14:05:02:848 [4] ThreadProcessModem: ERROR - Modem Response (2): +CMS ERROR: 69 14:05:02:848 [4] ThreadProcessModem: OUT: 14:05:02:941 [4] ThreadProcessModem: OUT: \r 14:05:02:941 [4] ThreadProcessModem: OUT: AT 14:05:03:004 [4] ThreadProcessModem: IN: OK 14:05:05:004 [4] ThreadProcessModem: Error: ERROR - Modem Response (2): +CMS ERROR: 69 14:05:08:066 [4] ThreadProcessModem: Processing 49C21B87.req... 14:05:08:066 [4] ThreadProcessModem: OUT: AT+CMGS=26 14:05:08:129 [4] ThreadProcessModem: IN: > 14:05:08:129 [4] ThreadProcessModem: OUT: 0001020B910671165033F100000EE8321B0E2297E7F0B23C4C2F03 14:05:08:957 [4] ThreadProcessModem: ERROR - Modem Response (2): +CMS ERROR: 69 14:05:08:957 [4] ThreadProcessModem: OUT: 14:05:09:051 [4] ThreadProcessModem: OUT: \r 14:05:09:051 [4] ThreadProcessModem: OUT: AT 14:05:09:113 [4] ThreadProcessModem: IN: OK 14:05:11:113 [4] ThreadProcessModem: Error: ERROR - Modem Response (2): +CMS ERROR: 69 this is the log i get | |||
| wong New member Username: Warpig Post Number: 7 Registered: 03-2009 |
is there any AT command to clear gprs modem memory? | |||
| wong New member Username: Warpig Post Number: 8 Registered: 03-2009 |
or is it after receiving mms in gprs mode, the network still connected in gprs? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 622 Registered: 08-2008 |
It shouldn't be ... unless the configuration is unusual. Normally, in a modem configuration, the SMS process of NowSMS releases the modem when there is an MMS message to be sent. It then activates Windows dial-up networking to make an IP connection over the modem. After that is finished, it terminates dial-up networking and opens a connection back up with the modem for SMS processing. I was hoping to see a log that had this whole sequence so that I could look for anything unusual. Ideally, it would start with the modem working ok, then you sending an MMS, then the error condition. I did just have a thought ... however. Have you tried going into properties for the modem in the NowSMS SMSC list, and setting "SMS Access" to "GSM"? Many mobile operators do not enable SMS sending over GPRS/EDGE/packet networks. Perhaps the modem is ok defaulting to GSM for sending SMS until it sees that we made a GPRS connection ... then it gets confused.
Not really. But potentially helpful could be a reset ... AT+CFUN=1,1 will perform a reset with many modems. But not all modems support the second parameter which is what triggers the reset. For others ... AT+CFUN=0 ... this sets the modem to "minimum functionality", which often turns off its radio. AT+CFUN=1 ... this sets the modem back to "full functionality". This sequence might work as a reset. However, AT+CFUN=0 has a bad effect on some modems ... it disables all communications until the modem is power cycled. | |||
| wong New member Username: Warpig Post Number: 9 Registered: 03-2009 |
could i know where i could get the wavecom AT command set for wavecom supreme 10? can i use AT+WRST to reset too? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 626 Registered: 08-2008 |
It can be tricky to find manuals for particular Wavecom models ... the web site is somewhat limited with information. But there's not a whole lot if difference. For Wavecom modems I usually refer people to the Multitech GPRS manual which uses the Wavecom chipset. The EDGE version uses Siemens so make sure to get the GPRS version manual. www.multitech.com | |||
| wong New member Username: Warpig Post Number: 10 Registered: 03-2009 |
it works now after i changed sms setting to gsm network only. Thank you very much des. Actually where u from man? | |||
| Royston Netto New member Username: Roystonnetto Post Number: 1 Registered: 04-2009 |
Hi, I am using nowsms trial version, i noticed that i could receive sms, but unable to send sms, the error message in the smsout is as follows: 2009-04-18 15:10:13,49E99FB5.req,192.168.1.5,9894993792,Retry Pending - ERROR - Modem Response (2): +CMS ERROR: 512 -- COM4: 2009-04-18 15:11:28,49E99FB5.req,192.168.1.5,9894993792,Retry Pending - ERROR - Modem Response (2): +CMS ERROR: 512 -- COM4: 2009-04-18 15:12:43,49E99FB6.req,192.168.1.5,9841088182,Retry Pending - ERROR - Modem Response (2): +CMS ERROR: 512 -- COM4: 2009-04-18 15:13:12,49E99FB5.req,192.168.1.5,9894993792,Retry Pending - ERROR - Error waiting for response from modem (2) -- COM4: 2009-04-18 15:13:24,System,,COM4:,Modem Failure -- Unable to access modem, ensure that it is powered on and passes diagnostic tests. 2009-04-18 15:13:44,System,,COM4:,Modem Failure -- Unable to access modem, ensure that it is powered on and passes diagnostic tests. 2009-04-18 15:14:24,System,,COM4:,Modem Failure -- Unable to access modem, ensure that it is powered on and passes diagnostic tests. 2009-04-18 15:17:27,49E99FB5.req,192.168.1.5,9894993792,Retry Pending - ERROR - Error waiting for response from modem (1) -- COM4: 2009-04-18 15:21:14,49E99FB6.req,192.168.1.5,9841088182,Retry Pending - ERROR - Error waiting for response from modem (2) -- COM4: 2009-04-18 15:24:40,49E99FB5.req,192.168.1.5,9894993792,Retry Pending - ERROR - Error waiting for response from modem (2) -- COM4: 2009-04-18 15:26:08,49E99FB6.req,192.168.1.5,9841088182,Retry Pending - ERROR - Error waiting for response from modem (2) -- COM4: 2009-04-18 15:29:06,49E99FB5.req,192.168.1.5,9894993792,Retry Pending - ERROR - Error waiting for response from modem (2) -- COM4: 2009-04-18 15:31:15,49E99FB6.req,192.168.1.5,9841088182,Retry Pending - ERROR - Modem Response (2): +CMS ERROR: 512 -- COM4: 2009-04-18 15:37:08,49E99FB5.req,192.168.1.5,9894993792,Retry Pending - ERROR - Error waiting for response from modem (2) -- COM4: 2009-04-18 15:45:20,49E99FB9.req,192.168.1.5,9841088182,Retry Pending - ERROR - Error waiting for response from modem (2) -- COM4: 2009-04-18 15:53:42,49E99FB9.req,192.168.1.5,9841088182,Retry Pending - ERROR - Modem Response (2): +CMS ERROR: 512 -- COM4: 2009-04-18 16:01:45,49E99FBA.req,192.168.1.5,9894993792,Retry Pending - ERROR - Error waiting for response from modem (2) -- COM4: 2009-04-18 16:04:39,49E99FB9.req,192.168.1.5,9841088182,Retry Pending - ERROR - Error waiting for response from modem (2) -- COM4: 2009-04-18 16:08:32,49E99FB9.req,192.168.1.5,9841088182,Retry Pending - ERROR - Modem Response (2): +CMS ERROR: 512 -- COM4: 2009-04-18 16:15:58,49E99FBA.req,192.168.1.5,9894993792,Retry Pending - ERROR - Modem Response (2): +CMS ERROR: 512 -- COM4: 2009-04-18 16:19:34,49E99FB9.req,192.168.1.5,9841088182,Retry Pending - ERROR - Error waiting for response from modem (2) -- COM4: 2009-04-18 16:27:55,49E99FBA.req,192.168.1.5,9894993792,Retry Pending - ERROR - Modem Response (2): +CMS ERROR: 512 -- COM4: 2009-04-18 16:35:23,49E99FB9.req,192.168.1.5,9841088182,Retry Pending - ERROR - Modem Response (2): +CMS ERROR: 512 -- COM4: 2009-04-18 16:38:56,49E99FBA.req,192.168.1.5,9894993792,Retry Pending - ERROR - Error waiting for response from modem (2) -- COM4: help me please | |||
| wong New member Username: Warpig Post Number: 11 Registered: 03-2009 |
CMS ERROR: 512 indicate 'MM establishment failure'. This error occurs when you try to send a message and the module is receiving another one at the same time. This causes a collision in the message transfer protocol resulting in failure in sending the SMS and hence, +CMS ERROR: 512. Sometimes, +CMS ERROR: 512 may also occur when the module is receiving weak signal and is loosing connection. I receive the +CMS ERROR 512 when I send a SMS from my modem to another one Sending and receiving SMS at the same time. The outgoing SMS could be rejected. | |||
| Royston Netto New member Username: Roystonnetto Post Number: 2 Registered: 04-2009 |
is there any checks that i can perform to over come this error? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 697 Registered: 08-2008 |
Hi, Sorry for the delay in response. What is the modem that you are trying to use? Some modems expose multiple COM ports to the computer, where only one of these ports actually supports sending/receiving SMS. I'm wondering if that is what you are seeing. -- Des NowSMS Support | |||
