SMS-service conﬁgurations

		Chapter 5. Setting up a SMS Gateway
Variable	Value	Description
		If set, speciﬁes from which
		smsc-ids all inbound messages
		should be routed to this smsbox
		instance. List contains smsc-ids
		seperated by semilon (";"). This
		rule may be used to pull any
		smsc speciﬁc message stream to
smsc-ids	word-list	an smsbox instance.
		If set, speciﬁes which receiver
		numbers for inbound messages
		should be routed to this smsbox
		instance. List contains numbers
		seperated by semilon (";"). This
		rule may be used to pull receiver
		number speciﬁc message streams
shortcuts	number-list	to an smsbox instance.

Now that you have an SMS center connection to send and receive SMS messages you need to deﬁne services for incoming messages. This is done via ’sms-service’ conﬁguration groups.

These groups deﬁne SMS services in the smsbox, so they are only used by the smsbox. Each service is recognized from the ﬁrst word in an SMS message and by the number of arguments accepted by the service conﬁguration (unless catch-allconﬁguration variable is used). By adding a username and password in the URL in the following manner "http://luser:password@host.domain:port/path?query" we can perform HTTP Basic authentication.

The simplest service group looks like this:

group = sms-service

keyword = www

get-url = "http://%S"

This service grabs any SMS with two words and ’www’ as the ﬁrst word, and then does an HTTP request to an URL which is taken from the rest of the message. Any result is sent back to the phone (or requester), but is truncated to the 160 characters that will ﬁt into an SMS message, naturally.

Service group default has a special meaning: if the incoming message is not routed to any other service, default ’sms-service’ group is used. You should always deﬁne default service.

Service group black-listhas a special meaning: if the incoming message is in service’s black-list, this service is used to reply to user. If unset, message will be discarded.

Table 5-6. SMS-Service Group Variables
Variable	Value	Description
group (m)	sms-service	This is a mandatory variable

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.

Nokia WAP and SMS gateway manual SMS-service conﬁgurations

Models: WAP and SMS gateway

Variable

If set, speciﬁes from which