Optional. If given, kannel will, Center | Nokia WAP and SMS gateway

		Chapter 5. Setting up a SMS Gateway
		Optional. If given, kannel will
		inform SMS Center that it should
		only try to send the message for
		this many minutes. If the
		destination mobile is off other
		situation that it cannot receive
		the sms, the smsc discards the
		message. Note: you must have
		your kannel box time
		syncronized with the SMS
validity	number (minutes)	Center.
		Optional. If given, the SMS
		center will postpone the message
		to be delivered at now plus this
		many minutes. Note: you must
		have your kannel box time
		syncronized with the SMS
deferred	number (minutes)	Center.
		Optional. Request for delivery
		reports with the state of the sent
		message. The value is a bit mask
		composed of: 1: Delivered to
		phone, 2: Non-Delivered to
		Phone, 4: Queued on SMSC, 8:
		Delivered to SMSC, 16:
		Non-Delivered to SMSC. Must
		set dlr-url on sendsms-user
		group or use the dlrurl CGI
dlrmask	number (bit mask)	variable.
		Optional. If dlrmask is given,
		this is the url to be fetched.
dlrurl	string (url)	(Must be urlencoded)
		Optional. Sets the PID value.
		(See ETSI Documentation). Ex:
		SIM Toolkit messages would use
		something like
		&pid=127&coding=2&alt-dcs=1&mclass=3
pid	byte
		Optional. If unset, kannel uses
		the alt-dcs deﬁned on smsc
		conﬁguration, or 0X per default.
		If equals to 1, uses FX. If equals
alt-dcs	number	to 2, force 0X.
		Optional. Sets the Return Path
		Indicator (RPI) value. (See ETSI
rpi	number	Documentation).

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.

Chapter 5. Setting up a SMS Gateway

Optional. If given, kannel will

inform SMS Center that it should

only try to send the message for

this many minutes. If the

destination mobile is off other

situation that it cannot receive

the sms, the smsc discards the

message. Note: you must have

your kannel box time

syncronized with the SMS

Center.

Optional. If given, the SMS

center will postpone the message

to be delivered at now plus this

many minutes. Note: you must

have your kannel box time

Optional. Request for delivery

reports with the state of the sent

message. The value is a bit mask

composed of: 1: Delivered to

phone, 2: Non-Delivered to

Phone, 4: Queued on SMSC, 8:

Delivered to SMSC, 16:

Non-Delivered to SMSC. Must

group or use the dlrurl CGI

variable.

Optional. If dlrmask is given,

this is the url to be fetched.

(Must be urlencoded)

Optional. Sets the PID value.

(See ETSI Documentation). Ex:

SIM Toolkit messages would use

something like

Optional. If unset, kannel uses

the alt-dcs deﬁned on smsc

conﬁguration, or 0X per default.

If equals to 1, uses FX. If equals

to 2, force 0X.

Optional. Sets the Return Path

Indicator (RPI) value. (See ETSI

Documentation).

WAP and SMS gateway specifications