Deﬁnes what kind of action, Received | Nokia WAP and SMS gateway

		Chapter 5. Setting up a SMS Gateway
Variable	Value	Description
		Deﬁnes what kind of action
		should be taken if the the ack of
		a message expires. The options
		for this value are: 0x00 -
		disconnect/reconnect, (default)
		0x01 - as is now, requeue, but
		this could potentially result in the
		msg arriving twice 0x02 - just
		carry on waiting (given that the
		wait-ack should never expire this
wait-ack-expire	number	is the mst accurate)
		This SMSC can support two
		types of ﬂow control. The ﬁrst
		type of ﬂow control is a
		stop-and-wait protocol, when
		this parameter equals to ’1’.
		During the handling of
		commands, no other commands
		shall be sent before the a
		response is received. Any
		command that is sent before the
		reception of the response will be
		discarded. The second type of
		ﬂow control is windowing,
		when this parameter is unset or
		equals ’0’. In this case a
		maximum of n commands can be
		sent before a response is
flow-control	number	received.
		When using flow-control=0,
		emi works in windowed ﬂow
		control mode. This variable
		deﬁnes the size of the window
		used to send messages. (optional,
window	number (messages)	defaults to the maximum - 100)
		If SMSC requires that kannel
		limits the number of messages
		per second, use this variable.
throughput	number (messages/sec)	(optional)
		Assuming that kannel is well
		conﬁgured and we had one
		sucessful connection, if retry is
		true, kannel will always retry the
		connection even if some related
retry	boolean	error ocur.

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 Deﬁnes what kind of action, For this value are, Is the mst accurate

Models: WAP and SMS gateway

Variable

Deﬁnes what kind of action

for this value are: 0x00 -

disconnect/reconnect, (default)

0x01 - as is now, requeue, but

msg arriving twice 0x02 - just

carry on waiting (given that the

is the mst accurate)

This SMSC can support two

types of ﬂow control. The ﬁrst

type of ﬂow control is a

this parameter equals to ’1’.

During the handling of

shall be sent before the a

response is received. Any

discarded. The second type of

ﬂow control is windowing,

when this parameter is unset or

equals ’0’. In this case a

sent before a response is

received.

emi works in windowed ﬂow

control mode. This variable

deﬁnes the size of the window

defaults to the maximum - 100)

If SMSC requires that kannel

limits the number of messages

per second, use this variable.

(optional)

Assuming that kannel is well

conﬁgured and we had one

sucessful connection, if retry is

connection even if some related

error ocur.

WAP and SMS gateway specifications