Chapter 5. Setting up a SMS Gateway

log-level = 0

Smsbox routing inside bearerbox

The communication link between bearerbox and smsbox has been designed for the purpose of load-balancing via random assignment. Which means, bearerbox holds all smsc connections and passes inbound message to one of the connected smsboxes. So you have a determined route for outbound messages, but no determinated route for inbound messages.

The smsbox routing solves this for the inbound direction. In certain scenarios you want that bearerbox to know to which smsbox instance it should pass messages. I.e. if you implement our own boxes that pass messages to bearerbox and expect to receive messages defined on certain rules, like receiver number or smsc-id. This is the case for EMI/UCP and SMPP proxys that can be written easly using smsbox routing facility.

If you smppbox handles the SMPP specific communication to your EMSEs, and if an client send a submit_sm PDU, smppbox would transform the message into Kannel message representation and inject the message to bearerbox as if it would be an smsbox. As you want to assign your clients shortcuts for certain networks or route any inbound traffic from a certain smsc link connected to bearerbox, you need to seperate in the scope of bearerbox where the inbound message will be going to. An example may look like this:

group = smsbox

...

smsbox-id = mysmsc

...

group = smsbox-route smsbox-id = mysmsc shortcuts = "1111;2222;3333"

which means and inbound message with receiver number 1111, 2222 or 3333 will be delivered to the smsbox instance that has identified itself via the id "mysmsc" to bearerbox. Using this routing the smsbox instance (which may be an EMI/UCP or SMPP proxy) is able to send a deliver_sm PDU

smsbox-route inherits from core the following fields:

Table 5-5. Smsbox-route Group Variables

 

Variable

Value

Description

group (m)

smsbox-route

This is a mandatory variable

 

 

Defines for which smsbox

 

 

instance the routing rules do

smsbox-id (m)

string

apply.

56

Page 63
Image 63
Nokia WAP and SMS gateway Smsbox routing inside bearerbox, Defines for which smsbox, Instance the routing rules do, Apply

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.