How Sms-Service Interprets The Http Response - Kannel WAP and SMS gateway User Manual

%P
%q
%Q
%i
%d
%A
%n
%c
%C
%u
Some sample 'sms-service' groups:
group = sms-service
keyword = nop
text = "You asked nothing and I did it!"
catch-all = true
group = sms-service
keyword = complex
get-url = "http://host/service?sender=%p&text=%r"
accept-x-kannel-headers = true
max-messages = 3
concatenation = true
group = sms-service
keyword = default
text = "No action specified"

How sms-service interprets the HTTP response

When an
sms-service
text/plain
requests a document via HTTP, it will accept one of four types of content types:
Chapter 5. Setting up a SMS Gateway
the phone number of the receiver of the SMS
message
like %p, but a leading '00' is replaced with '+'
like %P, but a leading '00' is replaced with '+'
the smsc-id of the connection that received the
message
the delivery report value
the delivery report SMSC reply, if any
the sendsms-user or sms-service name
message coding: 0 (default, 7 bits), 1 (7 bits), 2 (8
bits) or 3 (unicode)
message charset: for a "normal" message, it will be
"gsm" (coding=1), "binary" (coding=2) or
"UTF16-BE" (coding=3). If the message was
sucessfully recoded from unicode, it will be
"ISO-8859-1"
of incoming message
udh
Blanks are squeezed into one, rest is chopped to fit
an SMS message.
63