| Control send sms over multiple short codes usint smpp |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through December 09, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| elma |
Dear Sir I try to use you product as a trail version , and i have some problem with the configuration , i have a frame relay connection to the operator and i have 4 large account to thier SMSC , and i try to configure nowsms with two large accounts and it's working but how can i distinguish between the two smpp account when i send the message( with 2 short codes) from the URL. For Example: I have these two short codes are working now on nowsms : 5555 & 6666 and I want to send some msg's from 5555 and others from 6666 , how can i control that? as i understand from the help file i try that but it didn't work, and every time send from only one account. http://xxxxxx:8800/?PhoneNumber=0101829970&text=hello&sender=5555 must send the message from shortcoda 5555 http://xxxxxx:8800/?PhoneNumber=0101829970&text=hello&sender=6666 must send the message from shortcoda 6666 and how can i do that on the configuration menu? this issue are related with the routing configuration ? another thing: about the error handling, if the application server that deal with the http request send by nowsms is offline . what happened? can i configure nowsms to try to send the http request again ? BR; elma | |||
| Bryce Norwood - NowSMS Support |
Hi elma, When you configure the SMPP accounts in NowSMS, highlight the account definition in the "SMSC" list and press "Properties". Configure the "Sender Address" for each SMSC as "5555" and "6666" as appropriate. When you make that configuration, if you submit a message with a URL that includes "&sender=5555" (as shown in the example in your message), the message will always be sent out via the SMSC definition that has "5555" as its sender address. I hope this answers your question. Regarding your other question:
I believe you are referring to the use of the "2-way" command table. Is this correct? If yes, then when NowSMS processes received SMS messages, if the configured server is off-line, NowSMS will retry indefinitely until the application server is again available. Received messages will be queued in the SMS-IN directory of the NowSMS server until the application server is again on-line. -bn | |||
| elma |
Thax Bryce for ur reply But i want to know if nowsms can support this senario As gateway( i know i need a third party application to fetch the DB and find the ring tone) : When the user sends the word RING NOKIA 23456 to an operator short code (A). The system (nowsms and third party application) will respond to the user by a confirmation msg sent from another short code (B). If the user replies with an approval (RING YES), the application requests the ringtone number 23456 for NOKIA handset from the database and sends it to the user. BR; elma | |||
| Bryce Norwood - NowSMS Support |
Hi elma, Yes, that is possible. Your application would require some logic to track the outstanding requests, but you could certainly do it. The flow would be something like this: User sends "RING NOKIA 23456" to operator short code A. NowSMS receives this message, and makes an HTTP request to your script, passing the parameters "RING NOKIA 23456", along with the phone number of the sender, and the short code to which the message was addressed. Your HTTP script generates a URL request back to the NowSMS server (one easy way to send this URL request back is with a redirect response, as described in this document: http://www.nowsms.com/support/bulletins/tb-nowsms-003.htm). So your script could return back a redirect that looks something like this: http://username:password@127.0.0.1:8800/?PhoneNumber=insert.sender.here&text=Ple ase+reply+to+this+message+with+RING+YES+to+receive+the+requested+ring+tone.&SEND ER=short.code.b (The above example assumes that the HTTP port configured for the NowSMS web interface is "8800". "username" and "password" refer to an account created in NowSMS on the "SMS Users" page. Your script would replace "insert.sender.here" with the phone number of the sender that was passed into your script, and it would replace "short.code.b" with the appropriate value.) This causes NowSMS to send a message back out via the other short code. Your script would need to interface with a database to remember the ring tone number that this particular sender phone number had requested. That way, when you receive back a reply on the other short code, you will know which ring tone was requested. So now, user sends "RING YES" to operator short code B. NowSMS receives this message, and makes an HTTP request to your script, passing the parameters "RING YES", along with the phone number of the sender, and the short code to which the message was addressed. Your script sees that the message was addressed to short code B, so it checks its database to see what ring tone that sender requested, and it issues a redirect command back to the gateway that includes the necessary codes to send the requested ring tone. (Or instead of using this redirect approach, your script can generate its own connection back to the gateway without using redirect.) -bn | |||
