| SMS Users not getting any Sumbit_sm_Response from their Submit_sm. |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through April 11, 2011 ⬆ |
◄ ► |
| Author | Message | |||
| Tim Williams New member Username: Timw Post Number: 8 Registered: 09-2010 |
Hi, Wondering if you can assist at all here. Most of our SMSC connections are configured via the SMSC configuration page and we actively connect to them, but a new connection that has been created is connecting to us (so they have been setup under SMS users and the SMPP options are set). They can connect fine and send messages to us which then route as configured and we can route messages via the connection as well....But When they send us messages they are apparently not getting any Sumbit_sm_Response from their Submit_sm so the messages still sit in their queue even though they have been sent. Also is there a way to configure the addresses that will route to them without using the very small text area in the SMS Receipent address(es)? Regards Tim Williams | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2741 Registered: 08-2008 |
Hi Tim, Assuming that the submit_sm is valid format, there aren't too many reasons that they would not get a submit_sm_resp. But you say the messages are being accepted and being sent out? That would imply the submit_sm is definitely valid. And there's no way this message would be accepted without NowSMS replying back with submit_sm_resp. My suggestion would be to setup a Wireshark trace to record all packets between that client and the server to get a better idea of what's happening. Since NowSMS is accepting the message and sending it out, I don't think our debug logs would be of any help. If the Wireshark trace clearly shows a submit_sm_resp when you trace it on your end (as I expect it will), then I'd suggest having them do the same on their end to confirm that it is making it back to them (but that their client is not seeing it for some reason).
The only alternative is editing SMSGW.INI. There is a section in this file that stores this information: [Inbound SMS Routing] accountname=abc,def,g* NowSMS periodically looks for changes to this file and reloads this routing information into memory if you change it. It is not necessary to restart the service. -- Des NowSMS Support | |||
| Tim Williams New member Username: Timw Post Number: 10 Registered: 09-2010 |
Hi Des, An update to this in regards to sending messages to this SMSUser, with other messages I believe we can submit them with the route=xxxx option to overide the route it will use to go out, can this be used to specify a SMSUser or only the SMSC routes? Regards Tim | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3067 Registered: 08-2008 |
Hi Tim, I assume there was a resolution to the missing submit_sm_resp issue? I'm just curious if there were any interesting observations that might help with similar issues if they are encountered in the future. The SMSCRoute=routename parameter can be used to specify an outbound route. If you want to route a message to a particular user queue, use a parameter LocalUser=accountname. (Some older versions of NowSMS might also require the parameter InboundMessage=Yes) -- Des NowSMS Support | |||
| Tim Williams New member Username: Timw Post Number: 11 Registered: 09-2010 |
Hi Des, Thanks. Regarding the submit_sm_resp after tracing it and proving we were sending it, they replied when they ran a trace they were receiving it but not getting a delivery receipt, that is related to an issue I raised a while back regarding delivery receipts and delayed SMS which may be due to incorrect delivery receipts from one SMSC - that is still in progress. Regards Tim | |||
