2.1 Sonic MQ

About Sonic MQ

To guarantee message privacy for each client, all clients have their own exclusive reception queue (cola_recepción_cliente), and the forward queue will be common for all users: NviaQ. Once a SMS is received at our platform it is handled by our queue manager –SonicMQ- and sent to the corresponding queue with a unique ID, along with the message’s text and other parameters. Clients that want to handle premium messages must have a connection to the SonicMQ manager, and once the message is proccesed, the response will be sent to the NviaQ queue at our platform. At the moment the SonicQ supports Java class, C client, or a DLL for Visual Basic based solutions. Nvia provides all the necessary modules for clients to integrate via API. The parameters for the API integration are:

Broker’s IP Address
Queue name (one for reception and for forwarding)
Username
Password

When a message from an end user is received at the platform, a text string is sent to the client’s queue with the following parameters in the described order and separated by ‘|’:

IdMensaje (MessageId): Unique Identifier
pais (Country): Numeric Code for the country (See Figure 2.1)
operadora (Carrier): Alphanumeric Carrier Code (See Figure 2.1) Please note that if the syntax doesn’t correspond exactly it will return error.

Figure 2.1 (example for country Spain)

SPAIN - 34

OPERATOR

CODE

Movistar

Vodafone

Nvia

Euskaltel

Yoigo

Telecable

KPN

At this point an event will be thrown on the client as a response to the arrival of the OnMessage message. Once the content has been processed, the client would have to answer the SMS through his forwarding queue with the corresponding method (SendMessage).

The answer is a text with parameters separated by ‘|’. Parameters (in order) are:

IdMensaje (Message ID): unique message identifier
Datos (data): generally the text to send
Udh: User Data Header, hexadecimal code
Dcs: Data Coding Scheme, (Integer)

In case of a WapPush (the data field will have the value “WapPush”), the following parameters will be accepted:

IdMensaje (Message ID): unique message identifier
Datos (data): WAPPUSH
URL: without “http://”
TextoWap (Wap Text): text that appears before the download

About Sonic MQ

Broker’s IP Address

Queue name (one for reception and for forwarding)

Username

Password

When a message from an end user is received at the platform, a text string is sent to the client’s queue with the following parameters in the described order and separated by ‘|’:

IdMensaje (MessageId): Unique Identifier

pais (Country): Numeric Code for the country (See Figure 2.1)

operadora (Carrier): Alphanumeric Carrier Code (See Figure 2.1) Please note that if the syntax doesn’t correspond exactly it will return error.

Figure 2.1 (example for country Spain)

SPAIN - 34

OPERATOR

CODE

Movistar

Vodafone

Nvia

Euskaltel

Yoigo

Telecable

KPN

The answer is a text with parameters separated by ‘|’. Parameters (in order) are:

IdMensaje (Message ID): unique message identifier

Datos (data): generally the text to send

Udh: User Data Header, hexadecimal code

Dcs: Data Coding Scheme, (Integer)

In case of a WapPush (the data field will have the value “WapPush”), the following parameters will be accepted:

IdMensaje (Message ID): unique message identifier

Datos (data): WAPPUSH

URL: without “http://”

TextoWap (Wap Text): text that appears before the download