| SMPP Notifications |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through December 23, 2009 ⬆ |
◄ ► |
| Author | Message | |||
| spinnerudi New member Username: Spinnerudi Post Number: 6 Registered: 02-2009 |
Hi, I have a question about SMPP Notifications. We use NowSMS as SMPP Server. In the "SMS Users" Tab for all users the "Enable SMPP Login" option is checked. In the "SMSC" Tab I have my HTTP SMSC Connections. The routing (which user which connection) i configured in the smsgw.ini file. (AllowedUserOnly=Yes, AllowedUser1=customer1) ...That works fine. Our SMSC (HTTP Connection) supports sending notification, if a sms was delivered. Now my Question: How can i configure, that NowSMS sends SMPP notifications?? Otherwise the customer does not know, if a sms was delivered or not. Thanks for your help! | |||
| spinnerudi New member Username: Spinnerudi Post Number: 9 Registered: 02-2009 |
for your information: we use NowSMS V2006.10.31 | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1340 Registered: 08-2008 |
Hi, It's possible, but it would take some scripting on your end. (And it might require an update to NowSMS ... I don't think so, based upon my notes, but it might.) Here's why it's so difficult ... Every HTTP interface is different. So this notification coming back from the HTTP SMSC connection is very specific to the provider that you are using. You *might* be able to write a script that receives the notification from the HTTP SMSC and translates it into a format that NowSMS can understand. Here's how it works from a NowSMS perspective: When NowSMS submits a message to the HTTP SMSC, it can parse the HTTP response that comes back and look for an SMSC assigned message id. It is then possible for a subsequent HTTP transaction to be sent to NowSMS to signal a delivery receipt (or failure) for that 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 NowSMS to receive a receipt, it expects to receive an HTTP connection, very similar to a URL connection for submitting an SMS message to NowSMS. This HTTP delivery receipt request needs to include a username and password in the request (User= and Password= parameters matching a defined "SMS Users" account). Some versions of NowSMS require 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 your version of NowSMS might require a PhoneNumber= parameter in the request, NowSMS will remember the original sender and recipient and insert them into the receipt as appropriate). To give you an example ... Let's say that when you submit a message to the HTTP SMSC, it returns a response like this: OK - ID=xxxxxxxxxx You'd edit SMSGW.INI, and under the [HTTP - smsc:port] section header, add: TrackHTTPReceipts=Yes MessageIDResponsePrefix=ID= The URL request to send back a delivery receipt through NowSMS would look like this: http://ip:port/?user=username&password=password&ReceiptMessageId=xxxxxxxxxx&Rece iptDelivered=Yes&PhoneNumber=zzzzzzz (Note: The "PhoneNumber=" parameter might not be required in your version. Some time during 2006, we removed that requirement when ReceiptMessageId= is present.) So, it's technically possible ... but it relies on NowSMS being able to parse the SMSC assigned message ID from the HTTP response when the message is submitted. And it relies on you being able to convert/translate the HTTP notification from the SMSC into a format that NowSMS can understand. -- Des NowSMS Support | |||
