Chapter 5. Setting up a SMS Gateway

SMSBox inherits from core the following fields:

smsbox-port

http-proxy-port

http-proxy-host

http-proxy-username

http-proxy-password

http-proxy-exceptions

ssl-certkey-file

Table 5-4. Smsbox Group Variables

 

Variable

Value

Description

group (m)

smsbox

This is a mandatory variable

 

 

The machine in which the

bearerbox-host (m)

hostname

bearerbox is.

 

 

Optional smsbox instance

 

 

identifier. This is used to identify

 

 

an smsbox connected to an

 

 

bearerbox for the purpose of

 

 

having smsbox specific routing

 

 

inside bearerbox. So if you you

 

 

own boxes that do pass messages

 

 

into bearerbox for delivery you

 

 

may want that answers to those

 

 

are routed back to your specific

 

 

smsbox instance, i.e. SMPP or

smsbox-id (o)

string

EMI proxying boxes.

 

 

The port in which any sendsms

 

 

HTTP requests are done. As with

 

 

other ports in Kannel, can be set

sendsms-port (c)

port-number

as anything desired.

 

 

If set to true, the sendsms HTTP

 

 

interface will use a SSL-enabled

 

 

HTTP server with the specified

 

 

ssl-server-cert-file and

 

 

ssl-server-key-file from the core

sendsms-port-ssl (o)

bool

group. Defaults to "no".

 

 

URL locating the sendsms

 

 

service. Defaults to

sendsms-url (o)

url

/cgi-bin/sendsms.

 

 

URL locating the sendota

 

 

service. Defaults to

sendota-url (o)

url

/cgi-bin/sendota.

53

Page 59 Page 61
Page 60
Image 60
Nokia WAP and SMS gateway Smsbox Group Variables, Optional smsbox instance, An smsbox connected to an, Ssl-server-cert-file
Page 59 Page 61

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