| HTTP Short Code Connection |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through October 16, 2008 ⬆ |
◄ ► |
| Author | Message | |||
| DJXLoRd |
Hi , We have been assigned various short Codes Recently that are only active Via HTTP , yet we were searching for possible scenarios to receive incoming Messages to NOWSMS so we are able to route it to Users or apply a 2-way SMS command for incoming Messages. Any advice on how that can be possible , especially that for HTTP SMSCs , it is not possible to route incoming messages as per the NOWSMS Interface. Is there an HTTP API or URL Parameter where NOWSMS can receive SMS Via HTTP or any other possible methods. Thanks | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 130 Registered: 08-2008 |
Hi, Yes, there is a feature that was introduced in NowSMS 2007. You can deliver a message to NowSMS using the same URL parameters as you would to submit a message for outbound delivery. However, if you include "&InboundMessage=Yes" in the URL request, then the message will be treated as a message being delivered, so that it could be routed to the 2-way command processor. Note that if "SMS Users" accounts are enabled, it is necessary to include an "&User=xxxx&Password=yyyy" parameter to authenticate as an "SMS Users" account, even though the messages are to be processed as received messages instead of outbound message submissions. To prevent the possibility of a received message being routed for outbound delivery, we recommend creating a separate "SMS Users" account for this type of message delivery. Check "Enable Credit Balance" for the account, and leave the credit balance at 0. This will allow the account to deliver received SMS messages (i.e., "&InboundMessage=Yes"), but will disallow any attempts to submit a message for outbound delivery. There are also some additional parameters that can be used for delivering delivery receipts via the HTTP interface, which is a little more complicated. The way that delivery receipts work in this type of environment is that NowSMS expects the HTTP SMSC to return a "message id" somewhere in the response when NowSMS submits a message via HTTP. NowSMS expects to later receive back a delivery or non-delivery receipt via HTTP, also referencing that same "message id". Under the SMSGW.INI section that defines the HTTP SMSC connection, you need to add TrackHTTPReceipts=Yes. You also need to define MessageIDResponsePrefix=xxxxxx setting, where "xxxxxx" is some text for NowSMS to look for in the HTTP SMSC response. It is expected that the message id is the first non-blank text following this text string. The id is assumed terminated by a space, line break, period (.), comma (,) or semi-colon (;). For the SMSC to send back a receipt, it connects back to the NowSMS web interface as described above, including the "&InboundMessage=Yes" URL parameter. It must include a "&PhoneNumber=" parameter to indicate who should receive the receipt (original sender). Then it should include "&ReceiptMessageId=" to indicate the message id (should match what was returned in the HTTP response), and either "&ReceiptDelivered=Yes" or "&ReceiptFailed=Yes" to indicate the receipt type. NowSMS will look up the message id, and route an SMPP format receipt to the appropriate submitter account (and although you must include a Phone= parameter in the request, NowSMS will remember the original sender and recipient and insert them into the receipt as appropriate). -- Des NowSMS Support | |||
| DJXLoRd New member Username: Djxlord Post Number: 2 Registered: 01-2004 |
Hi , We have tried the above Method , yet when we try to add &LocalUser=XXXXX to route the message back to a certain user , it generates no effect on the incoming SMS and the Route to Local user remains "~SMSIN" , while we need to route it back to a certain User. regards | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 139 Registered: 08-2008 |
"&InboundMessage=Yes" will override "&LocalUser=". If you want to route the message to a local user, you can leave off "&InboundMessage=Yes". However, if you do this ... the submitting account requires credit for submitting the message. (You can't use the "Enable Credit Balance" with a credit balance of 0 trick that I mentioned above.) Should it work like this? I don't think so. 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. -- Des NowSMS Support | |||
