| No SMSC defined to route message after upgrade. |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through July 28, 2014 ⬆ |
◄ ► |
| Author | Message | |||
| Compass Communications New member Username: Compass Post Number: 1 Registered: 06-2014 |
Hi There, we are experiencing an issue where after we upgraded our NowSMS software from v2009.07.09 to v2014.05.30. We get an error message: Warning: SMS message could not be sent to +64xxxxxxx, Error: No SMSC defined to route messages. As far as I know we do not have any specific routes configured. We have reverted back to the old version v2009.07.09 for now to be able to send sms'. Are you able to assist on this issue? Thanks Dom | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4934 Registered: 08-2008 |
Hi, How many SMSC connections defined? In the properties for the connections, is "Support any outbound" checked? Are there entries in the preferred for list? -- Des NowSMS Support | |||
| Compass Communications New member Username: Compass Post Number: 2 Registered: 06-2014 |
Hi Des, Our current config (v2009.07.09) has nothing checked in the "Support any outbound message traffic". From memory when I did the upgrade (v2012.05.30) it did not have that checked as well. Thanks Dom | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4935 Registered: 08-2008 |
Hi Dom, I'm wondering why it was working before. I'm assuming the "Preferred SMSC Connection for" list was also empty? The error you describe occurs if NowSMS can't find a route where the recipient matched an entry in the preferred list, or, failing that, if there is no route with "Support any outbound message traffic" checked. (there is also sender based routing...more detail here http://www.nowsms.com/doc/configuring-smsc-connections/routing-options) I'd like to understand why it is working in your current config. Can you send me your SMSGW.INI file, so that I can better understand your configuration? Email to nowsms@nowsms.com, and put Attention: Des in the subject line. -- Des NowSMS Support | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4936 Registered: 08-2008 |
Some follow-up information for anyone who might encounter a similar problem, or be concerned about the possibility of encountering a similar problem... We try to avoid making any changes that trigger unexpected behavior when upgrading, but sometimes there are unexpected issues. In this case, reviewing the logs and INI files, it was observed that there was an accounting callback configured which was returning an SMSCRoute= response, but there was no matching route name in NowSMS. Older versions of NowSMS ignored the invalid route and let the message be routed to the default route (one of the routes had "Support any outbound message traffic"). Newer versions of NowSMS will reject the message as having no valid route (Error: No SMSC defined to route messages). Adding a RouteName to one of the routes using the name referenced by the accounting callback is the preferred solution. (Alternatively, the accounting callback could be modified to remove the invalid SMSCRoute response.) -- Des NowSMS Support | |||
