Nvia Technical Guides
SMS API Wiki 1.0
SMS API Wiki 1.0VMS API Wiki 3.0Number Lookup Services Wiki 1.0
SMS API Wiki 1.0
SMS API Wiki 1.0VMS API Wiki 3.0Number Lookup Services Wiki 1.0
  • Basics
    • Glossary
  • 1. Sending SMS-MT
    • 1.1 Interfaces
      • 1.1.1 HTTP Request
        • Sending text, flash and binary messages
        • Sending WAP push messages
      • 1.1.2 JSON Request
        • Sending text, flash and binary messages
        • Sending WAP push messages
      • 1.1.3 Webservices
        • Sending text, flash and binary messages
        • Sending WAP push messages
      • 1.1.4 SMPP interface
        • About the SMPP interface
        • Date time formats for scheduled delivery and validity period
    • 1.2 Date time formats
    • 1.3 Error Codes
    • 1.4 Delivery Report Callback
  • 2. SMS - 2 Ways
    • 2.1 Sonic MQ
    • 2.2 HTTP with Content-Reply (Synchronous)
    • 2.3 HTTP (2 requests)
    • 2.4 Unanswered messages
    • 2.5 Delivery reports (DLR)
  • 3. SMS Certified by Blockchain
    • 3.1 SMS Certified by Blockchain
    • 3.2 Sending a SMS certified by blockchain
  • EXAMPLES
    • GitHub sendMtSms
Powered by GitBook
On this page
  1. 2. SMS - 2 Ways

2.4 Unanswered messages

Operators require that for every originated message (MO) there is an answer (MT) within 2 hours or less (depending on the Carrier Service Provider). If the circle isn’t closed on time, the message won’t be charged to the final user and therefore no money will be retrieved.

Nvia provides a webtool where unanswered MOs can be tracked in real time and resent where the login data is the the client username and password:

https://www.panelsms.com/reenviosms
Copy

Clicking on “reenviar” (resend) resends MOs with the same method as they were sent the first time (Sonic, or HTTP), and keeping the same identifier.

Last updated 1 year ago