| MO SMS failing |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through May 19, 2016 ⬆ |
◄ ► |
| Author | Message | |||
| Pavan C Ramaswamy New member Username: Inmarsatuser Post Number: 1 Registered: 04-2015 |
HI we have our terminating partner (as ESME) binding to NOWSMS (as SMSC) and MO SMS from our network is failing and I get the below error. \ "2015-04-24 12:27:52,51752061,,+13212056786,Error: No SMSC defined to route message -- SYSTEM,SubmitUser=ReRouteReceived-SMPP - 192.168.176.60:2775;SMSCRouteName=SYSTEM;Sender=+15027950501;Text="Hdjhdjh" The same configuration is working on our other production network. I running out of ideas and more importantly time. Your prompt response would be much appreciated. Thanks Pavan Inmarsat (formerly Globe wireless) | |||
| Pavan C Ramaswamy New member Username: Inmarsatuser Post Number: 2 Registered: 04-2015 |
Looks like NOw sms is not forwarding our SMS (Deliver_SM) to our terminating partner. What does it mean by "No SMSC defined to route message" ? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5272 Registered: 08-2008 |
Hi Pavan, The error message means that no SMSC connection exists which has settings defined that allow it to be used to route this message. SMSC routes are decided by either the "Preferred SMSC Connection for" list in the SMSC properties, or by an accounting callback. I seem to recall from past discussions that you are using accounting callbacks (but I may be confusing you with someone else). I would suggest enabling the SMSDEBUG.LOG to look at the accounting callbacks, and verify that they are returning the correct routing response. -- Des NowSMS Support | |||
| Pavan C Ramaswamy New member Username: Inmarsatuser Post Number: 3 Registered: 04-2015 |
hi DEs, Thanks for your response. I think I figured that out, had to change the sms name on the php script! :) My sms can now reach our terminating partner [TP]. Although, I dont' see the SMS sent number increase on the Service tab of Now SMS. MO SMSs are successful but MT SMSs are failing (with our TP) Could you tell me what this 'SMS sent' numbers are please? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5273 Registered: 08-2008 |
Hi Pavan, For the message that you refer to as MO, it appears that the message is originating via an SMSC connection where NowSMS is the ESME. It also appears that this SMSC connection has an SMSGW.INI setting ReRouteReceived=Yes (or =any) to convert from deliver to submit format. An accounting callback then determines which SMSC connection (again with NowSMS as ESME) should get the submit transaction. It is hard for me to understand your references to MO or MT, because there are these transformations. To provide any assistance, I need to understand the path that these messages take through NowSMS. I sort of understand the MO flow based on previous logs, but I do not know what the MT flow is. -- Des NowSMS Support | |||
| Pavan C Ramaswamy New member Username: Inmarsatuser Post Number: 4 Registered: 04-2015 |
Hi Des, As you said, our SMSC is connected to NOwSMS and to TP. you are right about MO SMS. WHen I say MT, it is the SMS coming from outside world through our TP to NowSMS and then to our SMSC. We have the php route script on Now SMS to route SMS based on string match. Hope I am clear this time. So, in this scenario Could you tell me what this 'SMS sent' numbers are please? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5275 Registered: 08-2008 |
Hi Pavan, 'SMS Sent' numbers refer to submit transactions where NowSMS is in the ESME role. For an SMPP NowSMS can be in the ESME or SMSC role If a connection is defined in the SMSC list, NowSMS initiates the transaction and is in the ESME role. If a connection is defined in the SMS Users list, other party initiates the transaction and NowSMS is in the SMSC role. In interconnection scenarios it can get more complex, where some scenarios require both parties in both roles. I'm assuming you have 2 SMSC connections defined in NowSMS, so NowSMS is ESME in both. I am also assuming that in the Advanced Settings for each connection that the "Re-Route Received Messages for Outbound Delivery" setting is enabled. This means that any deliver messages will be converted to submit format for outbound routing. But I have no knowledge what is happening in your MT SMS scenario. Is the message received by NowSMS from TP? What happens next? Does it appear in SMSIN or SMSOUT logs? -- Des NowSMS Support | |||
| raghvendra singh New member Username: Rghvenda_singh Post Number: 1 Registered: 05-2015 |
raghvendra singh | |||
| Globe New member Username: Globeuser Post Number: 33 Registered: 04-2013 |
Hello Des, We have just attempted to migrate our NowSMS platform to a new server and after the migration noticed that all MO SMS's [Our SMSC - NOwSMS (php route script) - Terminating partner] to external network are being routed back to our SMSC by NowSMS instead of forwarding them to our external partner. The configuration & route.php script are the same as the previous NOwSMS platform. Have you seen this weird behaviour in the past? Can you think of anything we might be missing? Its like NowSMS is not going to 'forward to ESME' part of the script at all. If you want to take a look at the script, I can email it to you. Please advise. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5478 Registered: 08-2008 |
Hi Pavan, I've looked over old threads and e-mails, and this does seem to be a common problem for you whenever you make any system changes. I suspect the callback script is not returning the correct routing response. Unfortunately it can be difficult to troubleshoot. The best way is to enable the SMSDEBUG.LOG, where you should see a sequence like this:
NowSMS looks for SMSCRoute= in the callback response to tell it how to route the message. I suspect the callback is not working. Your old logs show you are using a local PHP script....maybe PHP is not installed? The SMSDEBUG.LOG should provide more clues. -- Des NowSMS Support | |||
| Globe New member Username: Globeuser Post Number: 34 Registered: 04-2013 |
Hi Des, I did go through all the mails from the past and nothing looked obvious. Anyway, we did find out something which is probably the reason. On the SMSGW.INI file,the below line was missing which points to php script. SMSAccountingURL=http://nowsmslocal/php/routeme.php As far as I remebered, this line will be written by the application as soon as check the "enable local php script" under 2-Way. Looks like that did not happen in this case even though it was checked. Isnt that right? Or do we need to put that line manually on the file, if yes I dont remember doing that manually the first time. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5479 Registered: 08-2008 |
Hi Pavan, That setting is a manual entry. If it is not present, your routing script is not processed. -- Des NowSMS Support | |||
