Ota-setting. Any string is, Login name | Nokia WAP and SMS gateway

Chapter 5. Setting up a SMS Gateway

phone as a XML document, but this method is perhaps more suitable for continous provisioning.

If you want to send multiple OTA conﬁgurations through the smsbox and you do not want to send XML documents, you will have to declare a ota-idstring to the different ota-settinggroups.

Table 5-13. OTA Setting Group Variables
Variable	Value	Description
group	ota-setting	This is a mandatory variable
		An optional name or id for the
		ota-setting. Any string is
		acceptable, but semicolon ’;’
		may cause problems, so avoid it
		and any other special
ota-id	string	non-alphabet characters.
		The address of the HTTP server
		for your WAP services, i.e.
location	URL	http://wap.company.com
service	string	Description of the service
		IP address of your WAP gateway
ipaddress	IP
		Phone number used to establish
phonenumber	phone-number	the PPP connection
		Connection speed: 9600 or
speed	number	14400. Defaults to 9600.
		Bearer type: data or sms.
bearer	string	Defaults to data.
		Call type: isdn or analog.
calltype	string	Defaults to isdn.
		Connection type: cont or temp.
		Cont uses TCP port 9201 and
		Temp uses UDP port 9200.
connection	string	Defaults to cont.
		Enable CHAP authentication if
pppsecurity	on or off	set to on, PAP otherwise
		normal or secure. Indicates
		wether WTLS should be used or
authentication		not. Defaults to normal.
login	string	Login name.
secret	string	Login password

A sample ’ota-setting’ group:

group = ota-setting

location = http://wap.company.com

service = "Our company’s WAP site"

ipaddress = 10.11.12.13

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 Ota-setting. Any string is, For your WAP services, i.e, PPP connection

Models: WAP and SMS gateway

Variable

An optional name or id for the

ota-setting. Any string is

for your WAP services, i.e.

Description of the service

the PPP connection

Connection speed: 9600 or

Bearer type: data or sms.

Defaults to data.

Call type: isdn or analog.

Defaults to isdn.

Cont uses TCP port 9201 and

Temp uses UDP port 9200.

Enable CHAP authentication if

set to on, PAP otherwise

normal or secure. Indicates

not. Defaults to normal.

Login name.

Login password

A sample ’ota-setting’ group:

WAP and SMS gateway specifications