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
  • Definition
  • Paremeters
  1. 1. Sending SMS-MT
  2. 1.1 Interfaces
  3. 1.1.4 SMPP interface

Date time formats for scheduled delivery and validity period

The Nvia platform supports both relative and absolute time stamps for scheduling SMS delivery and for defining the validity period for a message.

Definition

To define a timestamp in one of these parameters, please use the following syntax:

YYMMDDhhmmsstnnp
Copy

Paremeters

With the following time parameters for the delivery:

  • YY: Last two digits of the year (00-99)

  • MM: Month (01-12)

  • DD: Day (01-31)

  • hh: Hours (00-23)

  • mm: Minutes (00-59)

  • ss: Seconds (00-59)

  • t: Tenths of second (0-9)

  • nn: Time difference in quarter hours between local time and UTC time (00-48).

  • p: has 3 possible values:

    • + Local time is in quarter hours advanced in relation to UTC time.

    • - Local time is in quarter hours retarded in relation to UTC time.

    • R Local time is relative to the current SMSC time. In this case, the SMSC interprets the time format as the number of years, months, days, hours, minutes and seconds from the current SMSC time and t and nn should be set to 0 and 00 respectively.

Therefore, to indicate that the message should be sent on the 10th of April 2012 at 10:11:12.4, one can send with the following scheduled delivery parameter 120410101112300+