| Does Now SMS always have to have a permanent BIND? |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through January 22, 2009 ⬆ |
◄ ► |
| Author | Message | |||
| Douglas Drury |
We have an SMSC that creates a 'just in time' SMPP BIND to send an SMS, then disconnects until the next time. When setting up an SMSC in Now SMS, it only seems that I can setup an SMSC entry if I can get an permanent BIND. I have looked through the advanced settings and can't find any settings to set the SMSC entry to a 'LISTEN' type mode. Any help would be appreciated! | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 168 Registered: 08-2008 |
Hi Douglas, When configuring an outbound SMSC connection, NowSMS does assume that the SMPP connection will always be active (i.e., permanent bind). There is no option that will configure it as an on-demand bind. However, if you want NowSMS to "listen" for SMPP connections (accept connections from others), that is possible. The "Web" tab of the configuration dialog has a checkbox for enabling the SMPP Server component of NowSMS. And you can then specify what port number NowSMS should listen on for SMPP connections. For an SMPP client to authenticate to NowSMS in this manner, they need to login with the credentials of an account defined in the "SMS Users" list. -- Des NowSMS Support | |||
| Douglas Drury New member Username: Dougdrury Post Number: 2 Registered: 02-2006 |
Thank you Des! I will check it out... | |||
| Douglas Drury New member Username: Dougdrury Post Number: 3 Registered: 02-2006 |
One last question. With the setup on the web tab, if an SMS comes in, will the 2-way rules kick in to start an external script just like a permanent bind does? Thanks, Doug | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 176 Registered: 08-2008 |
Hi Doug, Apologies for the delay in reply. Unfortunately, no. Anything that comes in from an "SMS Users" account is put into the outbound message queue. 2-way commands are processed against the inbound message queue. I wish we had an option to configure messages from the account to go into the inbound message queue instead. However, that said, in NowSMS there is usually enough flexibility to accomplish most tasks one way or another ... even if the configuration gets a little confusing in the process. What you can do is define an "HTTP SMSC" in the outbound SMSC list. NowSMS will connect to the URL that you configure for the HTTP SMSC similar to the way that it would process a 2-way command. If all you are doing is connecting the SMPP client through NowSMS to convert to an HTTP request, and you are not using NowSMS for any other SMS message routing tasks, then all you need to do is define this HTTP SMSC. Any messages that NowSMS receives for outbound routing will be posted to the URL configured in the HTTP SMSC definition. Where it gets trickier ... is if you are using NowSMS for other SMS message routing. You obviously would not want other outbound message traffic to go to the pseudo HTTP SMSC. The easiest way to configure this is to use sender based routing. If the sender address in the SMPP message is not important to your application, then you can use the approach that does not involve manual editing of the INI files. In this case, define a "forced sender address" for the account defined in "SMS Users". Then in the "SMSC" dialog, define an HTTP SMSC connection that points to a script that you write. Make the "Sender address" for this SMSC definition match your "forced sender address" for the "SMS Users" account. This way, when NowSMS has an outbound message to route from this sender address, it will always route it via this "SMSC" connection instead of the GSM modem because of the match on sender address. If you don't want to lose the sender address, then perhaps recipient address routing could also be used ... if the SMPP client is always submitting to certain recipients. More information about NowSMS routing logic can be found here: http://blog.nowsms.com/2008/07/routing-sms-messages-to-specifc-smsc.html -- Des NowSMS Support | |||
| Douglas Drury New member Username: Dougdrury Post Number: 4 Registered: 02-2006 |
Des, Thank you. I will try this out!! doug | |||
| Douglas Drury New member Username: Dougdrury Post Number: 5 Registered: 02-2006 |
Des, I have Now SMS gateway version 2006.10.31. I can't find an outbound smsc list. I tried to add a new HTTP SMSC under the SMSC tab, but it kept trying to do some kind of connect to the URL I put in there and kept failing. Bottom line is, yes, all I want to do is upon an SMPP Message coming in, convert that to an HTTP request with the info using the @@xxxx@@ in the get string so that I can write some PHP scripts to handle incoming messages. I can do my filtering and routing in my PHP scripts, so I don't have to get crazy with the message routing.  Do I need to upgrade to a newer version of Now SMS to do this? Thanks, Doug | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 183 Registered: 08-2008 |
Doug, It sounds like you're doing the right thing. The configuration program only checks to make sure that it can make a TCP connection to the web server that you are running the script on. (It doesn't validate the URL itself.) So just make sure the "host name" is a valid DNS name or IP address (e.g., 192.168.1.100 ... NOT http://192.168.1.100). And unless your web server is on a special port, specify port number 80. The URL template strings are the URL without the host name (e.g., everything after "http://192.168.1.100"). -- Des | |||
