| DLR via HTTP |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through November 14, 2013 ⬆ |
◄ ► |
| Author | Message | |||
| SMSCOMM New member Username: Smstext Post Number: 5 Registered: 07-2007 |
After submitting a messages via HTTP, how can I route the DLR to the client that submit the message? this is all that is displayed; MessageID=51681E73.req, Recipient=+XXXXXXXXXX I would want to see the below displayed; ext="id:57302-1381326787996+XXXXXXXXXXX sub:001 dlvrd:001 submit date:1310091553 done date:1310091553 stat:DELIVRD err:0000 | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4682 Registered: 08-2008 |
Hi, I assume clients are submitting via HTTP and your system is submitting via another protocol such as SMPP. NowSMS is a store-and-forward system. And your upstream SMPP server is also most likely a store-and-forward system (unless it is a specialised First Delivery Attempt system). So when you submit a message, neither system waits for the message to be delivered before acknowledging acceptance back to the client. In other words, an HTTP or SMPP response only means the message has been accepted at the server that you submitted to, and it is awaiting processing. You can request a delivery report when you send a message, and if supported, a delivery report will be sent back. Unfortunately, we do not have a solution for routing these delivery reports back to an HTTP client. You can process them via HTTP using either the 2-way command interface, or through accounting callbacks ... but this is at a system level, not a scenario where you need to route reports to different submitting HTTP clients. -- Des NowSMS Support | |||
