Nokia WAP and SMS gateway manual How sms-service interprets the Http response

Models: WAP and SMS gateway

1 116
Download 116 pages 31.95 Kb
Page 70
Image 70

 

Chapter 5. Setting up a SMS Gateway

%P

the phone number of the receiver of the SMS

 

message

%q

like %p, but a leading ‘00’ is replaced with ‘+’

%Q

like %P, but a leading ‘00’ is replaced with ‘+’

%i

the smsc-id of the connection that received the

 

message

%d

the delivery report value

%A

the delivery report SMSC reply, if any

%n

the sendsms-user or sms-service name

%c

message coding: 0 (default, 7 bits), 1 (7 bits), 2 (8

 

bits) or 3 (unicode)

%C

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"

%u

udh of incoming message

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-servicerequests a document via HTTP, it will accept one of four types of content types:

text/plain

Blanks are squeezed into one, rest is chopped to fit

 

an SMS message.

63

Page 70
Image 70
Nokia WAP and SMS gateway manual How sms-service interprets the Http response