| Sending DLR to client |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through June 21, 2007 ⬆ |
◄ ► |
| Author | Message | ||||||
| Zuhair E. New member Username: Zuhair Post Number: 5 Registered: 04-2006 |
Hi, We are using NowSMS as a SMPP Server and receive messages from clients, which we forward to a SMS Center by HTTP. We are able to receive the delivery receipts from the SMS Center via HTTP POST. We want to know how to route these delivery receipts back to the clients by SMPP? Thanks, Zuhair | ||||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7072 Registered: 10-2002 |
Hi Zuhair, If you can write an application to process those HTTP POST requests and convert them into an HTTP GET request for NowSMS, then it is possible. The following thread discusses this: http://support.nowsms.com/discus/messages/1/15186.html Note that it is not necessary to download any updates referenced by that thread, as changes discussed there have been incorporated in current releases. Essentially, the way that it works is that when NowSMS submits a message to the SMSC via HTTP, it looks for a configurable keyword in the response to parse the message id assigned by the upstream SMSC. NowSMS will then accept an HTTP GET request with that message id to send back a delivery receipt confirmation or failure. -bn | ||||||
| Zuhair E. New member Username: Zuhair Post Number: 6 Registered: 04-2006 |
Hi Bryce, I have read all that discussion. It is talking all about sending delivery report. What if we need some other data to the client? If a client is connected to us as transiver mode means he can send we recv , or reverse. So how we can send him data as well? not necessary delivery report. Zuhair | ||||||
| Zuhair E. New member Username: Zuhair Post Number: 7 Registered: 04-2006 |
Another question is, Can you give me the complete correct url format for submitting smsid & delivery report to now sms? Is it correct: http://ip:8800?username=&password=&phone=&receiptmessageid=&receiptdelivered=yes Which username and password we should use? And what is phone=? Zuhair | ||||||
| Zuhair E. New member Username: Zuhair Post Number: 8 Registered: 04-2006 |
Ant the third question is: How we can pass the username/password which client used to connect to our smpp server , to our http url? | ||||||
| Malathy New member Username: Malathy Post Number: 4 Registered: 04-2007 |
Hi Bryce, I tested with the configuration mentioned in this thread. I'm using NowSMS(client) to connect to NowSMS(as SMPP server) and submitted a message.After I received the NowSMS MessageId, I sent the messageID sent as HTTP Response to NowSMS as receiptmessageId using http://ip:8800?user=&password=&receiptmessageid=&receiptdelivered=yes . I've also set TrackHttpReceipts=yes and MessageIDResponsePrefix=xxxx in the HTTP SMSC section of SMSGW.INI. But nothing seems to happen. Where should i look for the delivery receipt( on the client as well as Server) ? Malathy | ||||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7099 Registered: 10-2002 |
Hi Zuhair, The quick answer is that is all we support at this time. The longer answer is that this capability has been on our development list for quite some time. So I did a little digging, and I found that it has actually been implemented ... but it has not gone through testing yet, which is why it is not in the changes log. I ran a few quick tests, and it seemed to work for me. Basically, if you issue an HTTP request and include "&LocalUser=xxxx", then the message gets routed to the message queue for SMPP client "xxxx" instead of the outbound message queue. It looks like all other HTTP parameters are supported (http://www.nowsms.com/documentation/ProductDocumentation/sending_messages/url_pa rameters_for_sending_messages.htm), except for the ones related to sending MMS messages. Only SMS types are supported. -bn | ||||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7100 Registered: 10-2002 |
You need to define a username and password under "SMS Users". Note that it is "&user=username" in the URL, not "&username=username" (i.e., only "&user="). That other thread is wrong in this regard. "&Phone=" is the same as "&PhoneNumber=", it indicates the recipient phone number (both parameters are treated the same way). Although, this is now ignored for a delivery receipt submission, as we always route the receipt back to the sender address associated with the original message submission. When you submit a message with a "&ReceiptMessageID=xxx" parameter, NowSMS will look to see if it has a message id "xxx" in its tracking database. If it does not, it will return an error. If it does, then it will generate a delivery receipt back to the sender of that original message. The message id is only in the tracking database if you do the following: 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 (;). (Note: "<" and ">" are also interpreted as terminating characters, in case the message id in the response is in an XML format.) -bn | ||||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7101 Registered: 10-2002 |
That is not supported. If you need to restrict some accounts to particular outbound SMSC connections, there are "AllowedUser" settings described in the following link: http://support.nowsms.com/discus/messages/485/17220.html But that does not give you the same level of control. | ||||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7102 Registered: 10-2002 |
Follow-up ... regarding the "&LocalUser=" support. I am not sure when this feature was added, since it is not in our changes log. I tried it with the update at http://www.nowsms.com/download/20070412.zip. -bn | ||||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7103 Registered: 10-2002 |
The original submitting client should receive it via SMPP deliver (if they are bound as a receiver or transceiver). It would be queued under USERS\username\Q Probably the best thing to do is enable the SMSDEBUG.LOG, try again ... and let's take a closer look at that. | ||||||
| Malathy New member Username: Malathy Post Number: 5 Registered: 04-2007 |
Hi Bryce, I installed the update. I tried submitting using http://ip:8800?user=&password=&receiptmessageid=&receiptdelivered=yes and also using localUser as a parameter as in http://ip:8800?text=yes&localuser=xxxxx. Both were not received by the SMPP client, either as delivery receipt or a recd message. I've done all the reqd. settings in the SMSGW.ini file as mentioned in the previous post. Where & in what form the delivery Receipt or message will be received on the SMPP client? There is nothing under USERS\xxx\Q on the SMPP Server also. I can't find any info from the documentation also regarding these points. I've enabled debug and the debug file SMSDEBUG.LOG on Server shows entry about the submitted HTTP request and says 'Request Processing complete'- for both requests. Malathy. | ||||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7114 Registered: 10-2002 |
Can you upload an SMSDEBUG.LOG that shows you submitting these messages. Hopefully that will help me see what configuration is missing. | ||||||
| Malathy New member Username: Malathy Post Number: 6 Registered: 04-2007 |
Hi, These are the debug/configuration files on the SMPP Server. Malathy
| ||||||
| Malathy New member Username: Malathy Post Number: 7 Registered: 04-2007 |
These are the debug/config files on the client. Malathy
| ||||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7118 Registered: 10-2002 |
Hi Malathy, Ok. I see the problem, actually two related problems. For the delivery receipt, I thought that the recipient phone number parameter was not required, but it is. So you must include the "&PhoneNumber=" parameter, even though it will actually be ignored when "&ReceiptMessageId=" is present. Regarding the routing of the message to a local user account, this function also requires a recipient phone number to be included (&PhoneNumber=). Of course, the message won't actually be sent to that recipient, but this value will appear as the destination address when the SMPP client receives the message. -bn | ||||||
smsdebug
