The installation program for Now.WAP will copy the Now.WAP program files to the PC. For basic operation, no further configuration is required, except for configuring a port to be used for the HTTP Proxy interface.

For automatic operation, Now.WAP is best installed as a service. Services are automatically started by Windows when the machine is started. When Now.WAP is configured to run as a service, it will always be available, as long as the machine running Now.WAP is powered on and connected to the network.

The “Service” tab of the configuration dialog provides setup options for installing Now.WAP as a service.

Check “Run as a service” to install and start the Now.WAP service.
The “Start” and “Stop” buttons can be used to start and stop the service.

To remove the Now.WAP service from the Windows services registry, uncheck “Run as a service”. The “Service” tab of the configuration dialog also displays information about the status of the currently running service, indicating how long the service has been running, the number of currently active users, and the number of requests processed by the gateway.

The “Options” tab of the configuration dialog is used for setting some of the more commonly used configuration options for the gateway.

Check the “Use HTTP Proxy Server” checkbox if the gateway should forward all HTTP requests through an HTTP proxy server. Provide the IP address of the HTTP proxy server in the “HTTP Proxy Server” field. If a port number other than 80 is used by the proxy server, add a colon (:) and the port number to the proxy server IP address (e.g., 192.168.1.1:2080). If the HTTP Proxy Server requires a username and password for access, supply these settings in the “HTTP Proxy User Name” and “HTTP Proxy Password” fields.

Older versions of the OpenWave/Phone.com browser installed on some phone models do not allow the home page to be set on the phone. For these legacy browsers, a default home page can be specified in the “Default home page for legacy browsers” field. Please specify a complete URL such as http://wap.mydomain.com/home.wml.

The “IP Address Restrictions” settings can be used to restrict access to the gateway to a pre-defined set of IP addresses. If “Restrict access to the Gateway” is checked, then only the IP addresses listed in the “Addresses Allowed to Use Gateway” table will be allowed to access the gateway. If “Restrict access to the Gateway” is not checked, then any device can connect to the gateway.

When adding IP Address restrictions, both an IP address and mask are specified. For example, to restrict access to only the IP address of 192.168.1.101, specify that address and a mask of 255.255.255.255. To restrict access to all IP addresses in the range 192.168.1.1 thru 192.168.1.254, specify any address within that range, and a mask of 255.255.255.0.

After entering an IP address and mask, click “Add” to add the entry to the list.

To remove an address from the allowed list, highlight the entry and click “Remove”.

Note that after making any configuration changes in this dialog, it is necessary to click “Apply” or “OK” for the changes to be saved.

The Now.WAP Proxy includes an HTTP Proxy Server interface that can be utilised by WAP 2.0 clients which support Wireless Profiled HTTP and TCP (W-HTTP and W-TCP). This interface can also be used as an HTTP proxy to provide speed enhancements for web browsing via a PC over a GPRS modem or other wireless connection.

The HTTP (WAP2) Proxy server interface is enabled by checking “Enable HTTP (WAP2) Proxy”, and specifying an available port number on the local PC to be used as the “ HTTP Proxy Port”. HTTP and WAP2 clients must then be configured to connect to the Now.WAP Proxy on this port to use the proxy services.

When the “Enable Compression” setting is enabled, the Now.WAP Proxy will automatically compress requested files before transmitting them to the receiving client (when compression is supported by the receiving client).

When the “Enable WTCP Extensions” setting is enabled, the Now.WAP Proxy will enable certain Wireless Profile TCP extensions to provide optimum performance for wireless clients.

Both the “Enable Compression” and “Enable WTCP Extensions” settings are enabled by default. It is recommended that these settings only be changed for troubleshooting purposes.

The Now.WAP Proxy supports SSL/TLS tunneling, to support end-to-end encryption between WAP2 and HTTP clients and content servers. By default, the Now.WAP Proxy only supports SSL/TLS tunneling to content servers via the standard HTTP SSL/TLS port of 443. If you wish to enable SSL/TLS tunneling to other ports, check the “Allow SSL/TLS Tunnel to non-standard ports” setting.

To help achieve optimum performance, the Now.WAP Proxy uses HTTP “Keep-Alive” connections whenever possible. By default, Now.WAP will allow a client device to maintain a “Keep-Alive” connection to the proxy for up to 300 seconds. This means that a connected device can remain connected to the proxy for up to 300 seconds without making a request, eliminating the need to re-connect for each request. This value can be changed by entering a new value in the “Max Keep-Alive for Client Connections” field. A value of “0” can be used to disable all “Keep-Alive” connections to client devices.

Similarly, the Now.WAP Proxy will maintain “Keep-Alive” connections to content servers whenever possible. By default, after issuing a request to a content server that supports “Keep-Alive”, Now.WAP will keep that connection alive for up to 90 seconds, and will re-use the connection for any additional requests. This value can be changed by entering a new value in the “Max Keep-Alive for Server Connections” field. A value of “0” can be used to disable all “Keep-Alive” connections to content servers.

To use the Now.WAP Proxy to provide increased speed for connections from a web browser running on a PC, it is necessary to configure the web browser to use the Now.WAP Proxy as an HTTP 1.1 proxy for HTTP (and optionally HTTPS) connections. To configure these settings in Internet Explorer, follow these steps:

Under Tools/Internet Options/Advanced, find the entry "Use HTTP 1.1 through proxy connections" and make sure this setting is checked. (Compression of content is only supported in the HTTP 1.1 interface.)

Next, it is necessary to define the address of the proxy server to the web browser. This definition is applied under Tools/Internet Options/Connections.

The “MSISDN” tab of the configuration dialog allows the gateway to interface with a Radius accounting server that is integrated with the service provider's data network. This allows the gateway to determine the MSISDN (phone number) of a connected user.

Note that this configuration is typically used only inside of a service provider's data network, requiring that the WAP gateway be able to receive a Radius accounting feed from the provider's dial-in server and/or GPRS network.

Check “Activate Radius Accounting for MSISDN Collection” to enable a Radius accounting server that is built into the Now.WAP Proxy, and specify the port number on the local PC to be utilised. The default port number is 1813, although some older Radius services expect Radius accounting to listen to port 1646. You will also need to configure a “Shared Secret” that is common to the Radius server.

Once the “Radius accounting server” is enabled, the Radius servers on the service provider's network should be configured to forward Radius Accounting packets to the Now.WAP Proxy on the specified port.

Check “Activate Simple Radius Authentication Server” to enable a simple Radius authentication server built into the Now.WAP Proxy. By default, this Radius authentication server accepts all logins, regardless of user name and password, although it is possible to configure this server to authenticate against the user name and password list defined on the “Users” page of the Now.WAP Proxy configuration. This interface is provided primarily for environments where a Radius proxy is unable to separate the Radius accounting and Radius authentication feeds. By default, Radius authentication services listen to port 1812, although some older Radius services expect Radius authentication services to listen to port 1645.

Check “Require MSISDN for all gateway connections” if you wish to only accept WAP connections where the MSISDN (phone number) of the device can be reliably determined. Note that this setting would normally only be used in an environment where the Now.WAP Proxy is tightly integrated with the service provider network.

The gateway can forward the MSISDN of the WAP device to content servers via the “X-MSISDN:” HTTP header. Check “Forward ‘X-MSISDN:' Header in content server requests” to enable this capability. For privacy reasons, it is possible to explicitly list the content servers and/or domains that will receive the “X-MSISDN:” header. When a content domain is added to the list, a host name that exactly matches the content domain, as well as any host names within the content domain will receive the “X-MSISDN:” header. For example, if “now.co.uk” is added to the content domain list, the “X-MSISDN:” header would be forwarded to a host named “now.co.uk” as well as for “www.now.co.uk” and “mms.now.co.uk”. If you wish to have the “X-MSISDN” header forwarded to all content servers, define a content domain named “*”.

In smaller configurations, it may be desirable to configure user accounts, so that a username and password are required for access to the Now.WAP Proxy.

User accounts are defined on the “Users” page of the configuration dialog.

A single user account list is supported. This user account list can be used to restrict access to the HTTP Proxy functions, the WAP/WSP Proxy functions, or it can be used for user account/password validation for the built-in RADIUS Authentication Server (the RADIUS Authentication Server is defined on the “MSISDN” page of the configuration).

The user account list is stored as a text file in the Now.WAP Proxy gateway directory under a file name of USERS.TXT. This file can be edited outside of the Now.WAP Proxy. Each line of the text file should consist of a user name, followed by a comma, followed by the password for the account.

The Now.WAP Proxy is licensed by active (or concurrent) users.

When the Now.WAP Proxy is purchased, you will be provided with a serial number, user count and authorization code that must be entered into the “Serial #” tab of the configuration dialog. Enter this information and press “Add” to serialise the Now.WAP product.

Several additional configuration options may be applied by directly editing the WAPGW.INI file, located in the Now.WAP program directory.The configuration settings described in this section may be entered into the WAPGW.INI file under the [WAPGW] section header.

[ Charset ]
us- ascii = 1252
iso-8859-1= 1252
iso-8859-2= 1250
iso-8859-4= 1257
iso-8859-5= 1251
iso-8859-6= 1256
iso-8859-7= 1253
iso-8859-8= 1255
iso-8859-9= 1254
big5=950 big-5= 950
gbk = 936
gb2312=936
gb2312-80= 936
shift- jis = 932
shift_jis =932
iso-2022-kr= 949
korean = 949
ks_c_5601=949
KSC_5601=949
KSC5601=949
KSC-5601=949

The Now.WAP Proxy is available in two versions, with or without WTLS.

The WTLS version provides support for WTLS Class 1 and Class 2.

The evaluation version that is available for download from this web site does not include WTLS support. Please contact us if you wish to evaluate Now.WAP with WTLS support.

To implement WAP Push and MMS services in conjunction with Now.WAP, we recommend the use of the Now SMS/MMS Gateway. More information regarding the Now SMS/MMS Gateway can be found at http://www.nowsms.com .