2-Way special case

2-Way special case SearchSearch
Author Message
GSM TEST
New member
Username: Gsmtest

Post Number: 21
Registered: 04-2006
Posted on Wednesday, October 05, 2011 - 09:57 pm:   

Our SMPP connection looks for a key word in the SMS prefix to point messages back to NowSMS. The problem is that NowSMS only looks at the first word also, so I am limited to a single command prefix. Is it possible to configure NowSMS to delete or ignore a specific SMS prefix?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 3506
Registered: 08-2008
Posted on Thursday, October 06, 2011 - 08:31 pm:   

It's probably best if you create your own umbrella script that dispatches to different handlers as needed.

However, I was thinking about this, and I do have a crazy kludge where you have one command that looks for the SMPP prefix, and then reposts the message to NowSMS to be processed without the prefix so that it can be handled by other commands.

Create an "SMS User" account named inbound (or whatever account name you want to use).

Define a 2-way command with an SMS command prefix that matches your SMPP keyword.

Use this command to execute (changing IP and port if necessary):

http://127.0.0.1:8800/?User=inbound&Password=password&Sender=@@SENDER@@&PhoneNum ber=@@RECIP@@&Text=@@SMS@@&InboundMessage=Yes

Make sure "Command returns response text" is NOT checked.

This command basically just resubmits the received message as an inbound message, but the command prefix is removed.

It's a kludge, but it works.

--
Des
NowSMS Support
GSM TEST
New member
Username: Gsmtest

Post Number: 23
Registered: 04-2006
Posted on Friday, October 07, 2011 - 12:33 am:   

I must be missing a step somewhere. The messages arrive and are routed to the "inbound" user. In the smsout log i see the original sms prefix is still there instead of being dropped.Any ideas?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 3509
Registered: 08-2008
Posted on Friday, October 07, 2011 - 12:46 am:   

Maybe you inserted an extra step somewhere? (I can't think of any that were left out.)

Enable the SMSDEBUG.LOG. Is this 2-way command being triggered?

It is not clear to me why the messages would be routed to the "inbound" user, as this user is only submitting messages. Did you select this user in the SMSC definition as "Route SMS to local user"? (If so, remove this setting as that would be the cause of the problem.)

Do other 2-way commands for other prefixes work properly?

I set this up on a test system before I replied, and I just went back and reviewed it all, and it looks correct.

I just can't see why any messages would be routed to this "inbound" user at all, unless a rule was defined to do so. The purpose of this user is only to allow it to resubmit the messages.

--
Des
NowSMS Support
GSM TEST
New member
Username: Gsmtest

Post Number: 25
Registered: 04-2006
Posted on Friday, October 07, 2011 - 07:20 am:   

The regular 2-way command works. Here is the log for the working regular command and the failing special config.

message 1: The SMPP keyword "SMS" is sent and it triggers a standard 2way command to send an SMS. The message is sent and the log is easy to follow.

message 2: I sent "SMS go". The keyword "SMS" points to the redirect command you provided and "go" points to the test sending command. I can not figure out what is happening in the log file.



application/octet-stream
SMSDEBUG.LOG (10.6 k)
sam
New member
Username: Samdsouza

Post Number: 17
Registered: 08-2006
Posted on Friday, October 07, 2011 - 10:32 am:   

Hi Des

Regret to get into somebody else's thread but have seen similar problem.

This doesnt work and inbound messages get stuck in the SMSIN folder and dont get routed to user account:

http://127.0.0.1:8800/?User=inbound&Password=password&Sender=@@SENDER@@&PhoneNum ber=@@RECIP@@&Text=@@SMS@@&InboundMessage=Yes

This works:

http://127.0.0.1:8800/?User=inbound&Password=password&Sender=@@SENDER@@&PhoneNum ber=@@RECIP@@&Text=@@SMS@@&LocalUser=inbound

In short LocalUser parameter is working. InboundMessage is not working.

Sam
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 3511
Registered: 08-2008
Posted on Friday, October 07, 2011 - 02:49 pm:   

The discussion board software inserted a line break in my 2-way command example above.

Where it says:


http://127.0.0.1:8800/?User=inbound&Password=password&Sender=@@SENDER@@&PhoneNum ber=@@RECIP@@&Text=@@SMS@@&InboundMessage=Yes

This should all be on one line, with no break between "PhoneNum" and "ber".

I think if you fix that, it will resolve your problem ... essentially the SMSDEBUG.LOG shows that the message is not being resubmitted because the URL is truncated.

--
Des
NowSMS Support
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 3512
Registered: 08-2008
Posted on Friday, October 07, 2011 - 03:25 pm:   

Hi Sam,

I need further clarification to understand the problem you are describing.

&InboundMessage=Yes should not route to a local user account unless there is a match on a recipient address mask. The intent of this parameter is primarily to route a message to a 2-way command.

Maybe there is a scenario that we are missing?

--
Des
NowSMS Support
sam
New member
Username: Samdsouza

Post Number: 21
Registered: 08-2006
Posted on Friday, October 07, 2011 - 05:51 pm:   

Hi Des

My apologies. I got confused between localuser and inboundmessage parameters.

Searched for inboundmessage keyword and went through all the discussions but am still not clear on the different between the two.

You had mentioned in one of the discussions:


Personally, I think it should be changed so that "&LocalUser=" implies "&InboundMessage=Yes", and so that there is no conflict between these two parameters. But I need to discuss this further with my colleagues, as maybe there is a reason for this distinction which I do not understand.

Can you kindly point me some refrence link which would exlpain this 2 paramters clearly?

Thanks once again

Sam
sam
New member
Username: Samdsouza

Post Number: 22
Registered: 08-2006
Posted on Friday, October 07, 2011 - 06:29 pm:   

Hi Des

I guess the InboundMessage=Yes will process the message and put it back in the SMSIN folder of NowSMS

and LocalUser will get that SMS in the SMS User account.

Is this correct?

Kindly let me know

Thanks
Sam
GSM TEST
New member
Username: Gsmtest

Post Number: 26
Registered: 04-2006
Posted on Saturday, October 08, 2011 - 05:19 am:   

Thanks Des, it works great.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 3517
Registered: 08-2008
Posted on Monday, October 10, 2011 - 04:38 pm:   

Hi Sam,

The description of the "LocalUser" and "InboundMessage" parameters appears to be correct here:

http://www.nowsms.com/doc/submitting-sms-messages/url-parameters


quote:

LocalUser - Indicates that the message should be routed to a local “SMS Users” account supplied as the parameter value. The account must have SMPP or SMTP Login enabled to support receiving messages.

InboundMessage - Set to “Yes” to indicate that this is an inbound/received message that should be routed to the 2-way command processor instead of being routed to an outbound SMSC connection.




The confusion that you are referring to is that the original implementation of the "LocalUser" parameter (in earlier versions of NowSMS) had an issue that it did not work as designed unless "InboundMessage=Yes" was also specified as a parameter. That requirement is no longer necessary.

--
Des
NowSMS Support
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 3518
Registered: 08-2008
Posted on Monday, October 10, 2011 - 04:38 pm:   

Hi Sam,

The description of the "LocalUser" and "InboundMessage" parameters appears to be correct here:

http://www.nowsms.com/doc/submitting-sms-messages/url-parameters


quote:

LocalUser - Indicates that the message should be routed to a local “SMS Users” account supplied as the parameter value. The account must have SMPP or SMTP Login enabled to support receiving messages.

InboundMessage - Set to “Yes” to indicate that this is an inbound/received message that should be routed to the 2-way command processor instead of being routed to an outbound SMSC connection.




The confusion that you are referring to is that the original implementation of the "LocalUser" parameter (in earlier versions of NowSMS) had an issue that it did not work as designed unless "InboundMessage=Yes" was also specified as a parameter. That requirement is no longer necessary.

--
Des
NowSMS Support
sam
New member
Username: Samdsouza

Post Number: 24
Registered: 08-2006
Posted on Monday, October 10, 2011 - 05:03 pm:   

Many thanks Des...Highly appreciated...Last had seen 2008 version and 2011 is far more superior..in a nutshell NowSMS Rocks!!!

Thanks once again
Sam