| 2WaySMS SMSCRoutename |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through May 20, 2013 ⬆ |
◄ ► |
| Author | Message | |||
| Bill New member Username: Cyberfreak95 Post Number: 1 Registered: 11-2012 |
Hi, I'm trying to setup a 2way command that will reply back to any message it receives with "Received by the server at" the current date and time. My server has multiple SMPP routes. While the command seems to be working it seems to be randomly picking an SMSCRoute, which happens to be the wrong route every time. I even tried to explicitly put the route in the "Command to execute" field like this: http://127.0.0.1:8800/?phonenumber=@@SENDER@@&text=Received+by+myserver+at+@@MSG DATE@@+@@MSGTIME@@&SMSCRoutename=ATT and it STILL sends the message over a different route (not ATT)! How can I tell the 2way command to reply on the same SMPP connection that the message came in on? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4190 Registered: 08-2008 |
Hi Bill, The parameter name is SMSCRoute, not SMSCRouteName. If you put &SMSCRoute=@@SMSCRoute@@ into that command, the message would go back to the same route. (In recent versions of NowSMS, there is also another 2-way command variable that supplies the friendly name of the route, @@SMSCROUTEID@@.) If you are using simple 2-way commands that send their response directly, you can also add 2WayReplySameServer=Yes to the [SMSGW] section of SMSGW.INI to force replies back via the same connection. -- Des NowSMS Support | |||
| Bill New member Username: Cyberfreak95 Post Number: 2 Registered: 11-2012 |
Thanks! I tried the 2WayReplySameServer=Yes which does seem to be sending the message but we have multiple phone numbers associated with our SMPP account. Is there a setting similar to 2WayReplySameServer that also replies on the same phone number that received the SMS? Currently when a text is sent to 5555551212 (sample number) 2Way replies but the message is sent out via our short code 111111 (example) instead, but since the destination isn't valid for that short code, the destination number never receives the message. I would like NowSMS to respond to messages that come from 11111 to be sent back via 11111 and message that come over 5555551212 to be send back via 5555551212. Is this possible? I can successfully send a message via HTTP with this command: http://127.0.0.1:8800/?phonenumber=%2b15001234567&text=test&Sender=5555551212&SM SCRoute=ATT | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4199 Registered: 08-2008 |
Hi Bill, Sorry for the long delay in response. Are you using the direct response of the 2-way command to submit your reply? (Or are you generating a new HTTP request within your 2-way command? In which case the setting I mentioned wouldn't even apply because NowSMS just sees it as a new message submission.) Assuming that you are using the direct response, when NowSMS generates the reply it automatically flips the sender and recipient addresses of the received message. So for example, if a message is received with a recipient address of 5555551212, if NowSMS generate a direct response, it will set the sender as 5555551212 in the response. The only thing that would stop it from going out with that sender address is if the outbound route had a "Default Sender Address" with "Allow Sender Address Override" UNchecked. So I am wondering if the messages you are receiving do not have the expected short code recipient value. Or are you using the literal example that you posted in the first message? In this case, you are causing NowSMS to send a new HTTP request to itself. That is useful for testing, but it requires you set all parameters you require. If that is what you are doing, you need to include a sender address in the request ... like this: http://127.0.0.1:8800/?phonenumber=@@SENDER@@&text=Received+by+myserver+at+@@MSG DATE@@+@@MSGTIME@@&SMSCRoute=@@SMSCRoute@@&sender=@@RECIP@@ In this case, I've added the recipient (@@RECIP@@) of the original message as the sender of the newly generated message. The SMSGW.INI file setting I mentioned does not apply in this scenario, as technically the message generated is not treated as a reply but as a new submitted message. (Not that the distinction means much other than with regard to how defaults are applied to the newly generated message.) -- Des NowSMS Support | |||
