SMS Deliver Message problem | Search |
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through April 11, 2011 ⬆ |
◄ ► |
Author | Message | ||||
Muhammad Adnan farooq Frequent Contributor Username: Adnan Post Number: 61 Registered: 10-2009 |
Hello, I have a problem with the NowSMS software. It appears that some of our SMPP accounts / Binds are not getting SMS deliver messages.... I have attached pieces of the log files below. Please note that both customer SMPP binds were bound when the deliver messages arrived Please review the TXT file attached and let me know what to do next
| ||||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2989 Registered: 08-2008 |
Hi, The message in question is coming in addressed to a recipient +0364 (0364 with TON=1, indicating that the number is in international format, which is why NowSMS adds a "+"). If you want this message to be routed to a user account, there needs to be a user account defined with a recipient address mask that would match +0364. (I'm referring to a user account defined under "SMS Users", and the "Recipient address(es) to route to this user" parameter has the address mask.) -- Des NowSMS Support | ||||
Muhammad Adnan farooq Frequent Contributor Username: Adnan Post Number: 62 Registered: 10-2009 |
Thank you for the reply. I have attached a screenshot of the user info. This user was connected when the message hit Now SMS. (username and password fields have been covered for security) | ||||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2992 Registered: 08-2008 |
Do all messages addressed to +0364 have this problem? (I assume the answer is Yes, but it would help to know if this is a consistent issue or if it is intermittent.) Is it possible for you to send me the SMSGW.INI file so that I can understand the configuration? (If so, please e-mail to nowsms@nowsms.com with "Attention: Des" in the subject line.) I am doing more research, but the SMSGW.INI file would be most helpful. In particular, the [Inbound Routing Section]. | ||||
Muhammad Adnan farooq Frequent Contributor Username: Adnan Post Number: 63 Registered: 10-2009 |
Correct. All messages have this problem. It has never worked. [Inbound SMS Routing] Username=+0364 | ||||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2993 Registered: 08-2008 |
I'd like to see the full file if possible. My suspicion is that there is an unexpected formatting issue somewhere in the SMSGW.INI file that is causing the problem. | ||||
Muhammad Adnan farooq Frequent Contributor Username: Adnan Post Number: 64 Registered: 10-2009 |
SMSGW file has been emailed to you | ||||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2994 Registered: 08-2008 |
Received and performing further evaluation. | ||||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2995 Registered: 08-2008 |
Everything looks fine in the configuration file. (I've replied back to ask for the file to be resent inside of a ZIP or RAR file to preserve raw formatting. I do not expect to find a problem, but want to check.) As a next step, I would suggest restarting the service. It should not be necessary to restart the service after updating one of these routing definitions. However, as the configuration looks correct, the only reason I could see this not working properly is if the software is not detecting that the SMSGW.INI file has been updated, and reloading this routing table into memory. Restarting the service will definitely force this table to be reloaded. -- Des NowSMS Support | ||||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2996 Registered: 08-2008 |
Follow-up. I've run a series of tests on this, and it appears that NowSMS does not automatically reload this inbound routing table after it is updated. My tests show that it will sometimes automatically reload the inbound routing table after an update, but more often than not, it will not reload the inbound routing table until a restart. This is contrary to the advice that we have offered for years. I am investigating to see if older versions of NowSMS have this same behaviour, or if this is a problem introduced by an update. What version of NowSMS are you currently running? What I have discovered is that the table is only reloaded automatically if the first entry in the [Inbound SMS Routing] section is updated. You might be able to use that as a temporary work-around. Add a dummy user account. Manually edit SMSGW.INI to add this user account as the first entry under [Inbound SMS Routing] (example: dummy=dummy) If you update this account's recipient phone number (even keeping it invalid alphanumeric like in my example) after making any other updates, it should be sufficient to trigger the automatic reload of the table. -- Des NowSMS Support | ||||
Muhammad Adnan farooq Frequent Contributor Username: Adnan Post Number: 65 Registered: 10-2009 |
v2009.07.09 | ||||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3018 Registered: 08-2008 |
This seems to be a longstanding problem that goes back several versions. I was always under the impression that this inbound routing table would automatically get reloaded after any changes without restarting the service, but that does not happen consistently. This will be corrected in a future update. In the meantime, my suggestion above is the only work-around to ensure that this routing table is reloaded after an update. If the first entry in the [Inbound SMS Routing] table of SMSGW.INI changes, this will trigger a reload of the full table without restarting the service. -- Des NowSMS Support |