| SMS http gateway responce code |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through May 19, 2016 ⬆ |
◄ ► |
| Author | Message | |||
| John Bittner New member Username: Jbittner1002 Post Number: 3 Registered: 10-2015 |
When sending a text with invalid number or a number that does not support SMS, how do we tell in the response if the messages failed? Even with bad numbers we see them as ok in http response. We connect to the carrier via SMPP, since that is near real time, is there away to get error messages to be pushed back to http end users. If there is a list of http errors, please list them. John Bittner | |||
| John Bittner New member Username: Jbittner1002 Post Number: 4 Registered: 10-2015 |
Any way to turn on REST or SOAP based web service? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5531 Registered: 08-2008 |
Hi John, NowSMS provides a store-and-forward service. The HTTP response occurs before any upstream SMSC delivery (SMPP or other) occurs, so it will not report any upstream errors. The HTTP response will generally be OK, unless there is an authentication/credit problem, or an accounting callback rejects the message. The only way to request error feedback is to request delivery notifications . This is done by adding &ReceiptRequested=Yes to the request URL. Delivery reports (or non-delivery reports) are routed back to the 2-way command process (which can be routed to HTTP), and start with a prefix of id: If the upstream SMSC returns an error, a non-delivery report would be generated, and routed to the 2-way command. We do appreciate that some customers would prefer a transaction mode service where the HTTP response is not returned until either an upstream SMPP attempt is made or a timeout occurs. We are evaluating how a transaction mode type of service might be offered in future releases. Currently, delivery reports are the only way to get the feedback you are requesting. -- Des NowSMS Support | |||
