| Email to SMS support required |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through July 28, 2014 ⬆ |
◄ ► |
| Author | Message | |||||
| Ansar V M New member Username: Ansarvm Post Number: 1 Registered: 06-2014 |
Hi, Does any one please guide me to configure a shared mailbox configuration for sending email to SMS. I can able to send sms through web interface, but I required to send email to sms feature using external IMAP or POP3 Mailbox. I am using nowsms2014.05.30 version. thanks Ansar | |||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4920 Registered: 08-2008 |
Hi Ansar, For Now SMS/MMS Gateway: http://www.nowsms.com/email-to-sms-mms-gateway-with-nowsms For NowSMS Lite: http://www.nowsms.com/email-to-sms-mms-gateway-with-nowsms-lite If you are confused by any of the steps, reply back and I will clarify. -- Des NowSMS Support | |||||
| Ansar V M New member Username: Ansarvm Post Number: 2 Registered: 06-2014 |
Hi Des, Thanks for your response. Here is my doubt. 1. I have configured my external server imap and smtp account as per the document (Step 1a: (Shared Mailbox Configuration) Connect the E-mail Account). But my imap external account was not getting in, It might be the issue with our external imap account. Then I configured my gmail account with imap.gmail.com and smtp.gmail.com in imap and smtp field respectively. After that configuration was saved but when I try to send mail to sms from my gmail account, nothing is happening. My questions is Do I need to configure anything more to use the shared mailbox configuration for external account other than gmail?, if so do you have any document for that? I have only external imap and smtp server address and need to configure it as per the Step1a (Step 1a: (Shared Mailbox Configuration) Connect the E-mail Account). Could you please guide me to do. then we need to buy the licence too.. regards Ansar | |||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4921 Registered: 08-2008 |
Hi Ansar, Do not use your personal mailbox as the shared mailbox, as NowSMS will delete messages from the inbox as it processes them. This is a mailbox that NowSMS uses to send and receive messages. So you would send to this mailbox (from another mailbox) with a phone number in the subject line. If it is not working, the first thing I'd ask is whether or not you added the sending e-mail address (or appropriate *@domain) to the authorized e-mail sender list? NowSMS will not accept e-mails from users that have not been authorized. Assuming that has been checked, I'd like to see an MMSCDEBUG.LOG. Enable that log from the "Serial #" page. Then restart the NowSMS services and send another e-mail to that mailbox. Send the resulting MMSCDEBUG.LOG to nowsms@nowsms.com, and put Attention: Des in the subject line. Also post a reply here to tell me you've sent the log file. -- Des NowSMS Support | |||||
| Ansar V M New member Username: Ansarvm Post Number: 3 Registered: 06-2014 |
Hi Des, So what i am supposed to do is.. 1. i have to create a new mailbox in my external mail server and configure that in "use external Imap or pop3 mailbox" settings. i need a calrification that reagrding authorized e-mail sender list? is this is the domain where which my mailbox configured or an external domain where the user is having? thanks Ansar | |||||
| Ansar V M New member Username: Ansarvm Post Number: 4 Registered: 06-2014 |
Hi Des, I have created a mail box and when I try to configure in "use external imap or pop mailbox", nowsms is getting hanged and closed. I will send the log files once I configured this. thanks Ansar | |||||
| Ansar V M New member Username: Ansarvm Post Number: 5 Registered: 06-2014 |
Hi Des, i was able to send sms through web interface earlier. now i am getting error message while trying to send sms via web interface. could you please help me asap. i am waiting for your reply. 16:00:28:242 [19] WaitForSocketClose: WinSock reported ioctlsocket complete 16:00:28:243 [18] ProcessRead: End of socket 16:00:28:243 [19] ThreadProcessConnection: Request processing complete 16:00:28:243 [18] WaitForSocketClose: WinSock reported ioctlsocket complete 16:00:28:243 [18] ThreadProcessConnection: Request processing complete 16:00:33:139 [17] SendModemCommand: After CancelIo #2 16:00:33:139 [17] SendModemCommand: Wrote 0 bytes, expected 3 bytes 16:00:33:139 [17] SendModemCommand: AT 16:00:45:001 [17] SendModemCommand: Error - 3E4 - 16:00:45:001 [17] SendModemCommand: CancelIo 16:00:45:012 [17] SendModemCommand: After CancelIo #1 16:00:45:012 [17] SendModemCommand: After CancelIo #1a 16:01:00:013 [17] SendModemCommand: After CancelIo #2 16:01:00:013 [17] SendModemCommand: Wrote 0 bytes, expected 7 bytes 16:01:00:013 [17] SendModemCommand: ATE0V1 16:01:21:021 [17] SendModemCommand: Error - 3E4 - 16:01:21:021 [17] SendModemCommand: CancelIo 16:01:21:032 [17] SendModemCommand: After CancelIo #1 16:01:21:032 [17] SendModemCommand: After CancelIo #1a 16:01:36:023 [17] SendModemCommand: After CancelIo #2 16:01:36:023 [17] SendModemCommand: Wrote 0 bytes, expected 7 bytes 16:01:36:023 [17] SendModemCommand: ATE0V1 16:01:47:017 [17] SendModemCommand: Error - 3E4 - 16:01:47:017 [17] SendModemCommand: CancelIo 16:01:47:017 [17] SendModemCommand: After CancelIo #1 16:01:47:017 [17] SendModemCommand: After CancelIo #1a 16:02:02:008 [17] SendModemCommand: After CancelIo #2 16:02:02:008 [17] SendModemCommand: Wrote 0 bytes, expected 9 bytes 16:02:02:008 [17] SendModemCommand: AT+CFUN? 16:02:02:008 [17] ModemTest: Failed 16:02:02:008 [17] ThreadProcessModem: modem test failed 16:02:13:002 [17] SendModemCommand: Error - 3E4 - 16:02:13:002 [17] SendModemCommand: CancelIo 16:02:13:012 [17] SendModemCommand: After CancelIo #1 16:02:13:012 [17] SendModemCommand: After CancelIo #1a 16:02:28:004 [17] SendModemCommand: After CancelIo #2 16:02:28:004 [17] SendModemCommand: Wrote 0 bytes, expected 10 bytes 16:02:28:004 [17] SendModemCommand: AT+CFUN=? 16:02:29:000 [17] ModemTest: COM3: 16:02:39:994 [17] SendModemCommand: Error - 3E4 - 16:02:39:994 [17] SendModemCommand: CancelIo 16:02:40:005 [17] SendModemCommand: After CancelIo #1 16:02:40:005 [17] SendModemCommand: After CancelIo #1a 16:02:54:996 [17] SendModemCommand: After CancelIo #2 16:02:54:996 [17] SendModemCommand: Wrote 0 bytes, expected 7 bytes 16:02:54:996 [17] SendModemCommand: ATE0V1 16:02:54:996 [17] ThreadProcessModem: OUT: 16:03:05:990 [17] SendModemCommand: Error - 3E4 - 16:03:05:990 [17] SendModemCommand: CancelIo 16:03:06:000 [17] SendModemCommand: After CancelIo #1 16:03:06:000 [17] SendModemCommand: After CancelIo #1a 16:03:20:992 [17] SendModemCommand: After CancelIo #2 16:03:20:992 [17] SendModemCommand: Wrote 0 bytes, expected 1 bytes 16:03:20:992 [17] SendModemCommand: 16:03:21:092 [17] ThreadProcessModem: OUT: \r 16:03:32:086 [17] SendModemCommand: Error - 3E4 - 16:03:32:086 [17] SendModemCommand: CancelIo 16:03:32:097 [17] SendModemCommand: After CancelIo #1 16:03:32:097 [17] SendModemCommand: After CancelIo #1a | |||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4922 Registered: 08-2008 |
Hi Ansar,
It is a "who can send e-mail to SMS through my gateway" list. Let's say the gateway mailbox is sms@company.com. To send out an SMS, a user would send an email to sms@company.com and put the phone number at the start of the subject line. However, you don't want just anyone to be able to use your gateway, so there is an "authorized" list for what email senders are allowed to use the gateway for email to SMS.
NowSMS is trying to connect. There are long timeouts while it tries. It may take 2 minutes before it reports back an error. Try waiting as long as 5 minutes.
The modem has crashed, and NowSMS is trying to reset the modem. After several minutes of these failures, NowSMS will begin taking more aggressive action to try to recover the modem. What model modem is this? If this is a USB modem, especially a Huawei brand modem, it may be necessary to have the software that came with the modem active and running while NowSMS is running. Other modems may require a firmware update from the manufacturer to fix bugs. In 99% of the cases, restarting the NowSMS services will not fix the problem, because the software/firmware inside of the modem has crashed. The only way to recover is to remove power from there modem, then restore power, so the modem can restart. If this is a USB device that draws power from the PC, rebooting the PC will usually fix the problem because rebooting temporarily removes power from the modem so that the modem will restart. For this reason, there is an option in NowSMS under the properties of the modem in the SMSC list to "Reboot System if modem is not accessible". This is only recommended if the system is dedicated for NowSMS. In this case, if the modem fails and NowSMS cannot recover, it will reboot the PC, which will usually reset the modem. (In NowSMS Lite, to enable the automatic reboot if the modem cannot be accessed, edit SMSGW.INI. Locate the [Modem - your modem driver name] section header, and underneath of it, add RebootOnModemError=Yes ) To summarize (an add a few tips): 1.) Try restarting the NowSMS services. If this alone fixes the problem, let us know because this requires more investigation. 2.) If this is a USB stick modem (especially Huawei), try loading the software that ams with the modem and see if this improves reliability. (Some modem software may have features that remove received SMS from the modem. If you have problems receiving SMS, look for config settings in the modem software to keep messages on the SIM). 3.) Try the reboot setting, if you are using a dedicated PC for NowSMS. 4.) Configure alerts in NowSMS to send a email when an error condition occurs. This will tell you when the modem fails. 5.) Try a different modem. If you are not using special developer oriented SMS types, consider using an Android phone as a modem. In most cases, we prefer a quality inexpensive Android phone like the Moto G, to a dedicated modem device. -- Des NowSMS Support | |||||
| Ansar V M New member Username: Ansarvm Post Number: 6 Registered: 06-2014 |
Hi Des, Thanks for your response. Currently i configured and able to send email to sms successfully. But still i had some questions\issues which required help. user is getting same sms again and again 1. When i send an email to sms user is getting sms, but after that outbound sms queue in the service tab showing 1 message is in queued and sending the same sms after certain interval of time. 2. For the time being i have configured a new gmail account for testing. The issue is i am not able to send sms from any other domain other than gmail. say eg: i have a domain name aa.com, i have added this to the authorised sender list. but still not able to send email to sms. 16:51:24:306 [9] ProcessDownloadedEMail: E-Mail sender aaaaa@yyyyy.com not authorised 16:51:24:307 [9] IMAPCheckMessages: UID STORE 11 +FLAGS \Deleted 16:51:24:693 [9] IMAPCheckMessages: * 1 FETCH (FLAGS (\Seen \Deleted) UID 11) * 1 EXPUNGE * 0 EXISTS A0032 OK Success 3. Once a user get received sms, when he replied back the message came in the inbox and deleted. can i get that message in my email id which used to send the message to user. 4. can we have a telephonic/chat/teamviewer support, as this is an urgent requirement for us and need to conclude for a product. We are using wavecom fastrack modem. expecting your early response regards Ansar | |||||
| Ansar V M New member Username: Ansarvm Post Number: 7 Registered: 06-2014 |
Please see the smsdebug log file attached.
| |||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4924 Registered: 08-2008 |
Hi Ansar, 1. Is the SMS retried counter increasing? Does the SMSOUT-yyyymmdd.log report errors? We can look at the SMSDEBUG.LOG, but it sounds like the modem is reporting an error even though the network has accepted the message. If that is the case, it does give me concern about the modem. What does the SMSOUT-yyyymmdd.log report? One idea...there is an "SMS Access" setting, and it may be necessary to try different modes to find what works best for the modem. Try the GSM setting first and see if this removes sending issues. Does the Wavecom Fasttrack modem support 3G or is it only 2G (GPRS/EDGE)? Is it possible it is an old device that was purchased used? I am concerned that it may be failing, 2.) in your example, *@yyyyy.com should be added to the authorised sender list. 3.) The SMS reply can be sent to original email sender ... E.g., aaaaa@yyyyy.com .... But only if “Automatically Route SMS Replies to E-Mail” is checked (Step 4). 4.) If you send an email to nowsms@nowsms.com with Attention: Des in the subject line I will open a direct support incident. I prefer email because usually I need to see logs to understand. But I am happy to connect with TeamViewer to check details if necessary. Note...I will be out for approx the next 1 hour. -- Des NowSMS Support | |||||
| Ansar V M New member Username: Ansarvm Post Number: 8 Registered: 06-2014 |
Hi Des, Thanks for your response. i have sent a mail as you said. please reply back once you get in. Meantime let me check the suggestions what you made. thanks Ansar | |||||
| Ansar V M New member Username: Ansarvm Post Number: 9 Registered: 06-2014 |
Hi Des, yes the sms retrying increasing. please check the log file i have changed the "SMS Access" to default, now getting only one message from webinterface, but i am getting the same message again and again when sending email to sms. This is a new device, i am not sure about it supports 3g (will check and let you know) 2. i have already added this. Thanks Ansar
| |||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4925 Registered: 08-2008 |
Hi Ansar, The modem appears to be failing approximately every 5 minutes with no activity, and more frequently when it is active. What I mean by this is that the modem stops responding to commands, but NowSMS is able to send a “soft reset” command to tell the modem to restart and it becomes accessible again…only for the modem to stop responding again some time later. If there are duplicate messages being sent, it is because the modem stopped responding before reporting that the network had accepted a message for delivery (this would be reported as a “error waiting for response" in SMSOUT-yyyymmdd.LOG), or there are other situations where the modem reports an error when sending a message, which may not be accurate. I see CMS ERROR 21, which means the operator is refusing to accept the message, which usually means an invalid recipient number, or an account with no credit. I also see CMS ERROR 512, which on a Wavecom modem usually means that the modem is busy with something else (such as receiving message), and cannot send the message now. I am going to do some more investigation as we have some old info on Wavecom modems, and I recall a customer that had a modem that kept changing speeds which was causing problems, and they added an init command that made things better. I need to do some searches for that info…but at this point, I am suspecting the modem is failing. What is the exact model number, and is it USB or serial? If it is USB, do you have a different cable you can try…we have seen this type of problem caused by a bad cable (the timeout errors, not the CMS ERRORs). I’m not sure what else to suggest…it is like NowSMS is repeatedly losing connection to the modem…and NowSMS is having to tell the modem to restart so that it is able to talk to the modem again. I will do some searches … but I think the quickest solution is a different modem. Or put the SIM into an Android phone to use as a modem -- Des NowSMS Support | |||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4926 Registered: 08-2008 |
Hi Ansar, Via e-mail you mentioned
This may be an important clue. PL2303H is no a Wavecom chip, but a USB to serial converter chip that is used by many Wavecom modems. Historically, modems have been designed for serial port connections (9-pin connections, or back in the old days, 25-pin connections). Of course, most modern PCs no longer have these connections, and there are chipsets that convert USB to serial. On the PC side, these converters have software drivers that make the USB connection look like a serial port and create a virtual COMx: device. These USB drivers can be notoriously buggy and have issues with different versions of Windows. We have spent the better part of the last 10 years fighting problems with USB modem drivers, which has led to us developing different reset and reboot techniques to recover from a crashed modem. Updated USB drivers can often correct the problem. In this case, I believe you need updated drivers for the PL2303 USB to serial chipset. This is the link on the Prolific (chipset manufacturer) with the latest drivers: http://www.prolific.com.tw/US/ShowProduct.aspx?p_id=225&pcid=41 As a point of reference, I have a USB to serial cable that has this chip. I had to manually update those drivers before I could reliably use the cable. Here is what it looks like in the Windows Device Manager. Right click on the port to access properties, where the driver version can be found. The current version is 3.4.62.293.   If memory serves me correct, i installed the drivers using the installer from the prolific web site, then went into the device manager properties and selected "Update Driver" and pointed to the directory on the computer where the drivers had been installed. Hopefully this is the problem you are encountering, as everything in the logs seems to be pointing to a hardware problem. -- Des NowSMS Support | |||||
| Ansar V M New member Username: Ansarvm Post Number: 10 Registered: 06-2014 |
Hi Des, I have sent an email to nowsms techsupport email id with screenshots. please check. thanks Ansar | |||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4930 Registered: 08-2008 |
A follow-up for others who might be experiencing similar issues. NowSMS and the modem were moved to a different PC and seem to be working better. Problems with e-mail to SMS not being accepted (i.e., "E-Mail sender aaaaa@yyyyy.com not authorised") were a case sensitive issue. The e-mail address of the sender was styled with the first letter as a capital ... for example aaaaa@Yyyyy.com. NowSMS did not consider *@yyyyy.com to be a match, but adding *@Yyyyyy.com to the authorised list resolved this issue. Future versions of NowSMS will do a case insensitive compare for authorised e-mail senders. -- Des NowSMS Support | |||||
