Content Comparison

...

Send SMS

This provides the capability to send a text message of up to 160 characters to a list of 1 or more mobile phones. A documentId is returned which can then be used to query the status of the submitted SMS.

Query SMS Status

This provides the capability to query the status of previously submitted SMS. A query is made using the documentId returned from above. An list of phone numbers and current status is returned

Receive SMS

Amethon is able to host a dedicated number on which to receive SMS. All SMS messages received on this number can be forwarded in one of the following ways. Initially this will need to be configured by Amethon. For each received message we know the following:

• sender: the number of the person who sent the message
• recipients: the number to which the message was sent (this is the hosted number)
• text: the SMS message text

Email

an email is sent to a preconfigured email address. The email will appear to come from phoneNumber@amethon.net (eg 6142154353@amethon.net). It's subject will be "SMS Message Received" and the email body will contain the SMS text.

HTTP GET

A remote URL can be called passing as parameters the sender, recipient and SMS text details. Eg
http://www.company.com/receive.asp?sender=61450123123&recipient=61414414414&message=Hello+World

Web Service

A remote Web Service can be called passing as parameters the sender, recipient and SMS text details.

Send Document

This provides the capability to send advanced SMS messages. The Document structure provides a powerful but complex interface. Multiple messages can be submitted in a single document.  Each message can be addresses to one or more recipients. A reply address can be set for each individual message destination. 8-Bit or binary SMS is supported enabling ringtone, logos & picture messages to be sent.  Messages can be individually scheduled and also be given an expiry time.

Document, Message & Destination Options include: (default values in bold).

• Destination options take precedence over Message options which in turn take precedence over Document options.
• Addresses will be serialised into Strings
• A unique documentId will be generated by MessageCore.

Document

Class Document{
    String username;
    String password;

    Message[] message;
    Option[]  option;
}

Message

Class Message{
    String        subject;
    Destination[] destination;
    String        referenceId;
    Body          body;
    Option[]      option;
}

Destination

Class Destination{
    Address   destinationAddress;
    Address   fromAddress;
    String    referenceId;
    Option[]  option;
}

Address

Class Address{
    String type;
    String value;
}

Type: EMAIL | SMS | URL | WEBSERVICE

Note: Type is automatically determined when Value is set to one of the following:

Body

Class Body{
    String     type;
    Payload[]  payload;
}

Type: TEXT | RINGTONE | LOGO | PICTURE

Payload

Class Payload{
    String   type;
    String   encoding;
    String   content;
    Option[] option;
}

Payload Options include:

Option

Class Option{
    String  name;
    String  value;
}