Nokia WAP and SMS gateway manual Using the Http interface to send OTA configuration messages

		Chapter 5. Setting up a SMS Gateway
		Account name or number to
		carry forward for billing
		purposes. This field is logged as
		ACT in the log file so it allows
		you to do some accounting on it
		if your front end uses the same
		username for all services but
		wants to distinguish them in the
		log. In the case of a HTTP
		SMSC type the account name is
		prepended with the servicename
		(username) and a colon (:) and
		forwarded to the next insta ce of
		kannel. This allows hierarchical
account	string	accounting.

Notes:

a.To set number of messages, use mwi=[1-4]&coding=1&udh=%04%01%02%<XX>%<YY>, where YY are the number of messages, in HEX, and XX are mwi-1plus 0xC0 if text field is not empty.

Using the HTTP interface to send OTA configuration messages

OTA messages can be sent to mobile phones or devices to auto-configure the settings for WAP. They are actually complex SMS messages with UDH and sent as concatenated messages if too long (and compiled if necessary).

You may either pass an HTTP request as GET method or POST method to the HTTP interface.

If you want to send a configuration that is defined within Kannel’s configuration file itself you have to pass a valid ota-idvalue otherwise the content of the request will be compiled to as OTA message.

GET method for the OTA HTTP interface

An example URL (OTA configuration defined in the Kannel configuration file):

http://smsbox.host.name:13013/cgi-bin/sendota?

otaid=myconfig&username=foo&password=bar&to=0123456

URL containing XML document looks like this (you must URL encode it before sending it over HTTP):

http://smsbox.host.name:13013/cgi-bin/sendota?

username=foo&password=bar&to=0123456&

text=MyURLEncodedXMLdocument&type=settings

80