| Connecting 2 NowSMS |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through April 05, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| AlexGuttmann New member Username: Alegh Post Number: 1 Registered: 10-2006 |
I looking for connect 2 NowSMS servers in differents cities. I probably also use 2-way sms to mantain a realtime sql database with the messages I receive (in the first server) but also want that some of this messages to be routed to the other NowSMS server (maybe by the recip number). If I route using SMPP user routing options I found that the 2 way sms do not execute. Is anyway I could route some messages and also execute 2-way sms in the first server? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6652 Registered: 10-2002 |
Hi Alex, The 2-way commands only get triggered when an SMS message is received via a connection that is listed in the "SMSC" list. It basically wasn't designed so much for accounting or logging, as for taking an action based upon receiving a message. I'm wondering if maybe the SMS accounting callbacks might work better for you. I just realised that the document that describes these callbacks is very out of date: http://www.nowsms.com/support/bulletins/tb-nowsms-001.htm Although not described in that document, we do pass along all of the details about the message in the "SMSSend" accounting callback (which would make more sense if it was called "SMSSubmit" instead), similar to what you see in the NowSMS log files. This might do what you want. Parameters included in this callback are: Type, From, To, MessageID, SubmitIP, Sender, Binary=1 (if binary), PID (if non-zero), DCS (if non-zero), UDH (if present), and Data or Text depending on whether or not the message is binary. The only "catch" is that long text messages, or messages with EMS, or Unicode messages, are going to appear in binary format here, whereas they would be text in the 2-way SMS callback. We seem to get lots of questions from people who would like to use 2-way SMS in different ways than we had originally intended. So I'd be interested in more info on what changes you'd like to see. One change that I think a lot of people would like would be to have 2-way SMS triggered by message submissions to NowSMS (perhaps on a per-user account basis), in addition to just functioning on messages received from an SMSC connection. If we were to implement such an option (I haven't studied it to see how involved this would be to implement), it sounds like there is also a desire to have an option that would do both. But as I think through this, I'm not even sure if this would address what you're trying to do. It sounds like you're receiving an SMS message via an "SMSC" connection ... and that you would like to have the message routed to a 2-way command and to an "SMS Users" account via SMPP. That might be more difficult. But if this is what you're trying to accomplish, then maybe I have another idea that I touched on in another recent thread: http://support.nowsms.com/discus/messages/1/17827.html Basically, instead of routing to an "SMS Users" SMPP account via recipient phone number, you would have the messages routed to the 2-way command. The 2-way command then would either use a redirect response or generate a new HTTP request back to NowSMS that essentially submits the same message back to NowSMS but with "&LocalUser=accountname" in the URL which forces the message to be routed to that account. -bn | |||
| AlexGuttmann New member Username: Alegh Post Number: 2 Registered: 10-2006 |
Hi Bryce, Thanks for your answer. As I am testing NowSMS I understand that maybe I don't have yet a complete picture of all the possiblities I could have. Every option that you described might be a solution for what I need, but I think that the last (using "LocalUser") is what I will try. The only thing is that will be a two step process: I will receive and exec a 2 way command from an SMSC connection and in this command I will send the same SMS to the SMPP logged user. I will be using 2-way command to add every SMS to a database and dispatch and process the messages in different applications. In reference to: "One change that I think a lot of people would like would be to have 2-way SMS triggered by message submissions to NowSMS (perhaps on a per-user account basis), in addition to just functioning on messages received from an SMSC connection." This also is a very interesting option. I will post another message after my tests. Thanks. | |||
