Appendix C. Setting up a test environment for Push Proxy Gateway

second one pap control document. (For command line options, see Table C.1.). For example doing one push(you can simplify push url by setting a ppg configuration variable, see "Setting up push proxy gateway"; q flag here prevents dumping of test_ppg program debugging information):

test/test_ppg -q http://ppg-host-name:ppg-port/ppg-url [content_file]

[control_file]

This presumes that you have set trusted-pi true.

If you want use authentication in a test environment, you can pass username and password either using headers (setting flag -b) or url (you must have set trusted-pi false and added wap-push-user configuration group):

test/test_ppg -q http://ppg-host-name:ppg-port?username=ppg-username’&’

password=ppg-password [content_file] [control_file]

Table C-1. Test_ppg’s command line options

 

Switch

Value

Description

 

 

Use content qualifier string

 

 

instead of default si (service

 

 

indication). Allowed values are

 

 

wml, si, sl, sia, multipart, nil and

 

 

scrap. Nil and scrap are used for

 

 

debugging purposes. Wml does

 

 

work with some older phone

-c

string

simulators.

 

 

Use application id string instead

 

 

of default any. Application

 

 

identifies the application in the

 

 

phone that should handle the

 

 

push request. Sia, ua, mms, nil

 

 

and scrap are accepted. Nil and

 

 

scrap are used for debugging

-a

string

purposes.

 

 

Use tranfer encoding when

 

 

sending a push content. Only

-e

string

base64 is currently supported.

 

 

Use headers for authentication,

-b

boolean

instead of url. Default off.

 

 

Wait interval number instead of

-i

number

default 0 between pushes.

 

 

Do number requests instead of

-r

number

default 1.

 

 

Use number threads instead of

-t

number

default 1.

100

Page 107
Image 107
Nokia WAP and SMS gateway manual Table C-1. Testppg’s command line options, Use content qualifier string, String Simulators

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.