kannel sms gateway(Mo ,Mt)

Mo

 MO Messages Meta Data coming from MO messages comes urlencoded into the %D parameter. Only TLV parameters defined on the configuration file are honored. 

Example http://localhost/myscript?...&meta-data=%D&...

MT 

 MT Messages To send into an MT messages the meta-data parameter should be used.

 The format used to pass the data has 2 parts: The ?smsc-type? (surrounded by question marks), which specify the kind of smsc receiving the data (at the moment only smpp is implemented) and then a set of key/value pairs with the data to be transmitted. Extra smsc-types can be added surrounded by question marks and followed by the key/value pairs.

 In other words, the data should be coded using the following format, where URLENCODE() implies that the data between parentheses should be urlencoded: 

?URLENCODE(<smsc-type1)? URLENCODE(key1)=URLENCODE(value1)&URLENCODE(key2)=URLENCODE(value2?URLENCODE(<smsc-type2)?URLENCODE(key1)=URLENCODE(value1)&..

Only the parameters defined on the configuration file are honored.

 Important: For the sendsms interface, you must URLENCODE the resulting string again to pass it as a single parameter on the URL.

 Examples If we want to send the parameter "my-data" with value "Hello World" to an SMSC over SMPP, we’d use: sendsms get-url: 

http://localhost:13013/cgi-bin/sendsms?...&meta-data=%3Fsmpp%3Fmy-data%3DHello%2BWorld

 sendsms post: Send ?smpp?my-data=Hello+World on the X-Kannel-Meta-Data header 

XML:

<meta-data>?smpp?my-data=Hello+World</meta data>

Loopback SMSC (MT to MO direction switching) 

This special "SMSC" type can be used to route MT messages in bearerbox internally as MO input messages again. Therefore this tyoe is the MT wise counterpart of the ’reroute’ functionality of the smsc group when MOs are re-routed as MTs.

 group = smsc

 smsc = loopback 

smsc-id = loop1

 reroute-smsc-id = my_id 

Variable                                                                      Value                                            Description reroute-smsc-id (o)                                                   string                     Tag the rerouted MO with the                                                                                                                      given value for smsc-id instead of                                                                                                                the canonical smsc-id value of the                                                                                                                 smsc group itself

Using multiple SMS centers 

If you have several SMS center connections (multiple operators or a number of GSM modems) you need to configure one smsc group per SMS center (or GSM modem). When doing this, you might want to use routing systems to rout messages to specific centers - for example, you have 2 operator SMS centers, and the other is much faster and cheaper to use.

 To set up routing systems, first give an unique ID for each SMS center - or if you want to treat multiple ones completely identical, give them identical ID. Then use preferred-smsc-id and denied-smsc-id to set up the routing to your taste. See also SMS PUSH settings (’sendsms-user’ groups), below.