Chapter 5. Setting up a SMS Gateway

Variable

Value

Description

 

 

If client does not set

 

 

Content-Type for reply, it is

 

 

normally

 

 

application/octet-stream which is

 

 

then handled as data in kannel.

 

 

This can be forced to be

 

 

plain/text to allow backward

 

 

compatibility, when data was not

assume-plain-text

bool

expected.

 

 

Long messages can be sent as

 

 

independent SMS messages with

 

 

concatenation = false or

 

 

as concatenated messages with

 

 

concatenation = true.

 

 

Concatenated messages are

 

 

reassembled into one long

 

 

message by the receiving device.

concatenation

bool

 

 

 

Allowed characters to split the

 

 

message into several messages.

 

 

So, with "#!" the message is split

 

 

from last ’#’ or ’!’, which is

split-chars

string

included in the previous part.

 

 

If the message is split into

 

 

several ones, this string is

 

 

appended to each message except

split-suffix

string

the last one.

 

 

Normally, Kannel sends a

 

 

warning to the user if there was

 

 

an empty reply from the service

 

 

provider. If omit-emptyis set to

 

 

’true’, Kannel will send nothing

omit-empty

bool

at all in such a case.

 

 

If specified, this string is

 

 

automatically added to each

 

 

SMS sent with this service. If the

 

 

message is split, it is added to

header

string

each part.

 

 

As header, but not inserted into

footer

string

head but appended to end.

 

 

Stuff in answer that is cut away,

 

 

only things between prefix and

 

string

suffix is left. Not case sensitive.

prefix

Matches the first prefix and then

 

 

the first suffix. These are only

 

 

used for url type services, and

 

 

only if both are specified.

61

Page 67 Page 69
Page 68
Image 68
Nokia WAP and SMS gateway If client does not set, Content-Type for reply, it is, Normally, Then handled as data in kannel
Page 67 Page 69

WAP and SMS gateway specifications

Nokia has long been a pivotal player in the telecommunications industry, and its contributions to mobile communication technology are numerous. Among these contributions, the Nokia WAP and SMS Gateway stand out as essential elements in enabling mobile internet access and messaging services in the early days of wireless communication.

The Nokia WAP (Wireless Application Protocol) gateway was introduced to facilitate mobile access to the internet and to allow users to interact with web services through their mobile devices. Built on a client-server architecture, the WAP gateway acted as a bridge between the mobile network and the internet, translating traditional web content into a format that mobile devices could effectively render. This conversion was crucial, given the limitations of early mobile devices regarding screen size, processing power, and network bandwidth.

One of the main features of the Nokia WAP gateway was its ability to provide users with real-time access to information such as weather updates, news, and stock prices. By using a lightweight markup language called WML (Wireless Markup Language), the gateway allowed developers to create mobile-friendly websites that could be accessed via WAP-enabled devices. This marked a significant step toward the mobile internet we know today, creating a new realm of possibilities for developers and users alike.

Another critical aspect of Nokia's offering was the SMS (Short Message Service) gateway. The SMS gateway provided a robust platform for sending and receiving text messages across various mobile networks. It enabled seamless communication between devices, regardless of the underlying technology. This feature made SMS a popular choice for both personal communication and business applications, such as marketing campaigns and customer service notifications.

The Nokia SMS gateway utilized established protocols, such as SMPP (Short Message Peer-to-Peer), to ensure reliable message delivery and efficient interaction between SMS applications and mobile networks. Its characteristics included scalability, allowing service providers to handle large volumes of messages, and flexibility to integrate with existing applications and systems.

In summary, the Nokia WAP and SMS gateway played a vital role in the evolution of mobile communication. With features that enabled mobile internet access and streamlined messaging capabilities, these technologies laid the groundwork for the mobile-centric world we live in today. Their legacy continues to influence mobile application development and the broader telecommunications landscape. As the industry progresses, the innovations introduced by Nokia serve as a reminder of the foundational technologies that paved the way for modern mobile experiences.
Top Page Image Contents