Chapter 5. Setting up a SMS Gateway

Variable

Value

Description

 

 

Port number in which Kannel

 

 

listens to (MO) messages from

port (m)

port-number

other gateway

 

 

IPs allowed to use this interface.

 

 

If not set, "127.0.0.1" (localhost)

 

 

is the only host allowed to

connect-allow-ip

IP-list

connect.

 

 

Username associated to

 

 

connection, if needed. ’kannel’

 

 

requires this, and it is the same as

smsc-username

string

send-sms username at other end.

 

 

Password for username, if

smsc-password

string

needed.

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-idand denied-smsc-idto set up the routing to your taste. See also SMS PUSH settings (’sendsms-user’ groups), below.

Feature checklist

Not all of Kannel’s SMSC drivers support the same set of features. This is because they were written at different times, and new features are often only added to drivers that the feature author can test.

The table in this section is an attempt to show exactly what features to expect from a driver, and to help identify areas where drivers need to be updated. Currently most of the entries are marked as "not tested" because the table is still new.

Table 5-2. SMSC driver features

 

 

 

 

 

 

 

 

Featurecimd

 

emi

 

emi2

 

sema

ois

at

at2

http

fake

 

cimd2

 

emi_ip

 

smpp

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Can use DLR

 

 

 

 

 

 

 

 

 

 

 

n

y?

n

n

y

y?

n

n

n

n

n

n

Can set DCSa

 

 

 

 

 

 

 

 

 

 

 

?

?

?

?

y

?

?

?

?

y

?

?

Can set Alt-DCS

50

Page 56 Page 58
Page 57
Image 57
Nokia WAP and SMS gateway Using multiple SMS centers, Feature checklist, Featurecimd, Sema Ois At2 Http, Cimd2 Emiip Smpp
Page 56 Page 58

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