2.3 HTTP (2 requests)
If the client chooses not to connect to the queue manager, the gateway is done via http requests. In this case the customer must set a web server, and communicate to Nvia the URL where he will attend the requests.
The customer chooses the name of the parameters that he needs (except for idrespuesta which is compulsory), for example:
idrespuesta: (ID answer) It identifies univocally to the message. It must be used in the answer.
mobile (optional): mobile number where sms is sent.
host (optional): short number where sms is received.
carrier (optional).
text (optional).
The answer to each request must be "OK" on plain text.
In order to answer each sms, the customer must make a request to our script, accessible at out primary server:
If this server should fail, then use our backup server:
The parameters that the script accepts for text answers are:
idrespuesta: (“IDanswer”) the same one that was received originally.
texto: text to be responded.
The parameters for delivery of binary data are:
idrespuesta: (“IDanswer”) the same one that was received originally.
texto: (text) data in hexadecimal
udh: User Data Header, hexadecimal field
dcs: Data Coding Scheme, integer field.
In order to make WapPush response, the following parameters are to be used:
idrespuesta: (“IDanswer”) the same one that was received originally.
texto: (text) wapppush.
url: the url without "http://"
textowap: (“waptext”) text that will appear before the download of the content.
The client will have to indicate to Nvia the IP addresses from which he will make the requests to ensure authenticity. Nvia, in turn, will make its requests from following IP address 193.219.96.100.
Last updated