Change the interface version, Though | Nokia WAP and SMS gateway

		Chapter 5. Setting up a SMS Gateway
Variable	Value	Description
		Change the "interface version"
		parameter sent from Kannel to a
		value other then 0x34 (for SMPP
		v3.4). the value entered here
		should be the hexadecimal
		representation of the interface
		version parameter. for example,
		the default (if not set) is "34"
		which stands for 0x34. for SMPP
interface-version	number	v3.3 set to "33".
		According to the SMPP 3.4 spec
		this is supposed to affect which
		MS’s can send messages to this
		account. Doesn’t seem to work,
address-range (m)	string	though.
		Specicy the outgoing IP address
		for connections from a
		multi-homed machine. If this is
		not deﬁned the default device of
our-host	string	the machine will be used.
		Optional smsc short number.
		Should be set if smsc sends a
my-number	number	different one.
		Optional the time lapse allowed
		between operations after which
		an SMPP entity should
		interrogate whether it’s peer still
		has an active session. The default
enquire-link-interval	number	is 30 seconds.
		Optional the maximum number
		of outstanding (i.e.
		acknowledged) SMPP operations
		between an ESME and SMSC.
		This number is not speciﬁed
		explicity in the SMPP Protocol
		Speciﬁcation and will be
		goverened by the SMPP
		implementation on the SMSC.
		As a guideline it is recommended
		that no more than 10 (default)
		SMPP messages are outstanding
max-pending-submits	number	at any time.

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 Change the interface version, V3.4. the value entered here, V3.3 set to

Models: WAP and SMS gateway

Variable

Change the "interface version"

v3.4). the value entered here

should be the hexadecimal

representation of the interface

version parameter. for example,

the default (if not set) is "34"

v3.3 set to "33".

this is supposed to affect which

though.

for connections from a

multi-homed machine. If this is

not deﬁned the default device of

the machine will be used.

Optional smsc short number.

Should be set if smsc sends a

different one.

between operations after which

an SMPP entity should

is 30 seconds.

Optional the maximum number

of outstanding (i.e.

between an ESME and SMSC.

This number is not speciﬁed

explicity in the SMPP Protocol

Speciﬁcation and will be

goverened by the SMPP

implementation on the SMSC.

that no more than 10 (default)

at any time.

WAP and SMS gateway specifications