Now IMP Server v1.10

Now IMP Server v1.
10
October 14, 2005
© Copyright 2005, Now Wireless Ltd.
Table of Contents
Now IMP Server............................................................................................................... 2
System Requirements.................................................................................................. 3
Basic Configuration...................................................................................................... 4
Basic Configuration Step 1: Define the Server's TCP/IP Ports............................... 5
Basic Configuration Step 2: Start the Now IMP Server..........................................7
Basic Configuration Step 3: Define User Accounts............................................... 8
Basic Configuration Step 4a: Connect with a Mobile IM Client............................ 10
Configuring (Most) SonyEricsson Phones......................................................... 10
Configuring (Most) Nokia Series 60 Phones..................................................... 11
Configuring (Most) Nokia Series 40 Phones..................................................... 11
Configuring (Most) Motorola Phones (V80)....................................................... 12
Basic Configuration Step 4b: Connect with a Desktop IM Client......................... 14
Advanced Configuration............................................................................................. 20
Service Page......................................................................................................... 20
Server Page........................................................................................................... 22
Options Page......................................................................................................... 24
Push Page............................................................................................................. 26
WAP Push over UDP........................................................................................ 27
CIR TCP Push Channel (STCP)........................................................................ 28
WAP Push over SMS........................................................................................ 29
SMTP Page........................................................................................................... 30
Users Page............................................................................................................ 32
SSL/TLS Page....................................................................................................... 34
Serial # Page......................................................................................................... 38
User Account Provisioning via HTTP..................................................................... 39
Automated Agents................................................................................................. 42
OTA Provisioning for IMPS.................................................................................... 45
OTA Provisioning for IMPS: SonyEricsson....................................................... 47
OTA Provisioning for IMPS: Nokia (and other OMA Compliant Devices).........49
Self-User Provisioning via the Web....................................................................... 51
External Transports (AOL, MSN, etc.)............................................................................ 58
MSN Transport........................................................................................................... 59
AIM Transport............................................................................................................ 62
Now IMP Client............................................................................................................... 65
Getting Started with the Now IMP Client.................................................................... 67
Adding a Contact....................................................................................................... 70
To be continued......................................................................................................... 73
Now IMP Server v1.10 – http://www.nowimp.com 1

Now IMP Server
The Now IMP Server is an Instant Messaging and Presence Server that supports both
mobile phones and PC desktop clients. Users can communicate with each other using
instant messaging technology whether they are connected on the same Local Area
Network, or connected through mobile wireless technology.
Mobile phone clients are supported through the Now IMP Server's implementation of
the Open Mobile Alliance (Wireless Village) Instant Messaging and Presence Services
(IMPS) specification. The current release of Now IMP supports the Client Server
Protocol (CSP) version 1.1 or 1.2, with support for both text and binary (WBXML)
protocol variants. As a published standard of the Open Mobile Alliance, many of the
new mobile phone models from major manufacturers include an instant messaging and
presence client that supports this specification.
PC desktop clients are supported through the Now IMP Server's implementation of the
XMPP (Extensible Messaging and Presence Protocol). A Windows based desktop client
supporting XMPP is bundled with the Now IMP Server to enable instant
communications. XMPP is an internet standard, published by the Internet Engineering
Task Force (IETF) in RFC 3920 and RFC 3921.
The Now IMP Server supports the Presence, Instant Messaging (IM) and Group
features of both the IMPS and XMPP specifications, in addition to the fundamental,
common and core features of those specifications.
External connectivity is supported with a built-in e-mail gateway, allowing IM users to

send messages to e-mail recipients, and allowing e-mail users to send messages to IM
recipients. E-mail connectivity provides a simple built-in API for alert management,
allowing automated applications to interface with the Instant Messaging network.
It is also possible to use the Now IMP Server to allow mobile IM clients to connect to
MSN and/or AOL instant messaging networks, via add-on XMPP transport connectors.
The Now IMP Server allow organisations of any size to deploy their own private instant
messaging network, with SSL/TLS encryption, to enable individuals to interact with
each other across the office or around the world with secure instant messaging
technology. The alert management interface allows corporate applications to quickly
disseminate time critical information to employees.
The Now IMP Server provides a web-based administrative interface for user account
maintenance. The administrative interface also supports a programmatic HTTP
interface for user account definition.

System Requirements
The Now IMP Server runs on Windows 2000, Windows XP or Windows 2003. Memory
requirements are minimal, and we recommend that you follow the suggested memory
guidelines for the version of Windows that you are running. Now IMP will consume
approximately 4MB of memory plus 16KB per active user session.
Disk space requirements are not a significant consideration for Now IMP. Each defined
user account will consume approximately 16KB worth of disk space. Allow sufficient
disk space to facilitate log files.
Running the Now IMP Server requires a dedicated IP address, or at minimum an
always connected IP address with a dedicated host name (i.e., dynamic DNS should be
used if you a dedicated IP address is not available).
Mobile phone IM clients will need to be able to make HTTP connections to the Now IMP
Server. The port number for these connections is user configurable. However, there
must be a path to allow mobile phones to make HTTP connections to the configured
port on the Now IMP Server.
Desktop IM clients will need to be able to make a TCP/IP connection to the Now IMP
Server. The port number for these connections is user configurable, however by
default IM clients will expect to connect to the server over TCP/IP port 5222.
The Now IMP Client runs on Windows 98, Windows ME, Windows 2000, Windows XP
or Windows 2003. It requires Internet Explorer v5.5 or later, 5MB of hard disk space,
and 64MB of RAM.

Basic Configuration
To install the Now IMP Server, run the IMPServer.exe program from the distribution
media (CD or web download).
After installing the Now IMP Server software, run the Now IMP Server configuration
utility to configure the software.
For a basic configuration, you will need to perform the following steps:
1.) Define the TCP/IP port number(s) on which the Now IMP server will listen for
connections from IM clients.
2.) Start the Now IMP Server, and optionally configure the server to automatically
startup as a Windows service.
3.) Define user accounts on the Now IMP Server.
4.) Configure IM clients to connect to the Now IMP Server, logging in via defined
user accounts.
(a)If you have any mobile IM clients, these clients will be configured to connect
to the Now IMP Server using the Wireless Village/OMA IMPS Protocols.
(b)If you have any desktop IM clients, these clients will be configure to connect
to the Now IMP Server using the XMPP Protocol. The Now IMP Server
includes licenses to allow user accounts to connect using the Windows
based Now IMP Client.

Basic Configuration Step 1: Define the Server's TCP/IP Ports
The TCP/IP port number, on which the Now IMP Server will listen for HTTP connections
from mobile IM clients, is configured on the Server page of the configuration dialog,
under the setting HTTP Port Number.
To enable the XMPP Server interface, you must define the XMPP Domain Name. This
is normally the host name on which the Now IMP Server is installed. When connecting
to the Now IMP Server, it is customary to login with an XMPP client by specifying a user
name of user@xmppDomain.name, where “xmppDomain.name” is the host name of
the Now IMP Server. (The Now IMP Client can be configured to assume a default
domain name when it is installed, so that users need only supply their user name to

login. This is described in Step 4b.)
Instead of using a host name, a special DNS “SRV” record can be used. It is similar in
concept to DNS “MX” records used by e-mail servers. For XMPP clients to properly
connect to the Now IMP Server using “SRV” records, the “SRV” record needs to be
defined in the format “_xmppclient._tcp.xmppDomain.name” with the port set to 5222,
and the host name set to the specific “A” (host address) record for your server.
Desktop IM clients will connect to the Now IMP Server using the XMPP Protocol, which
by default uses TCP/IP Port 5222. It is easy to override this default port assignment if
you are using “SRV” records in DNS. However, in cases where you are connecting to
the host by its host name, clients will assume port 5222, and the default XMPP Port
Number setting should not be changed.
Please note that the SSL port number assignments are not available until an SSL/TLS
certificate has been generated. This is an advanced topic that is covered later in this
document, and is not necessary for a basic configuration.

Basic Configuration Step 2: Start the Now IMP Server
To start the Now IMP Server, press the Start button on the Service page of the
configuration dialog. Or check the Run as a Service option to install the Now IMP
Server as a service which will automatically start every time the PC is rebooted.

Basic Configuration Step 3: Define User Accounts
IM User accounts are defined on the Users page of the configuration dialog.
To define a new user account, press the Add button.

The User Name and Password fields are required for a user account definition. The
additional user settings are used only as informational settings. These settings are
used primarily to facilitate search functionality, allowing a user to locate another user by
searching on the supplied settings.
For standard user accounts, leave User account is an automated agent unchecked.
Automated agents are IM user accounts where an application program is configured to
send and receive messages for the account, instead of an actual user. Automated
agents are described later in this document on page 42.

Basic Configuration Step 4a: Connect with a Mobile IM Client
The process of configuring a mobile phone IM client to connect to the Now IMP Server
will vary by client. In some cases, it may be possible to send an OTA (Over The Air)
configuration message to automatically send the settings. The Now SMS/MMS
Gateway product supports sending IMPS configuration documents to mobile phones
over SMS, however that process is beyond the scope of this document.
To configure a mobile phone IM client to connect to the Now IMP Server, you must be
familiar with some of the internet and/or WAP configuration settings for the mobile
operator to which your phone is subscribed.
In most cases, you can duplicate the settings that are used by the Web/WAP Browser
on the mobile phone, and simply add the URL for connecting to the Now IMP Server.
The configuration settings that you will usually need to know include the APN (Access
Point Name) that is used for connecting to GPRS/EDGE/UMTS. You may also need to
know the IP address of a WAP proxy/gateway. (Note: For some IM clients, such as
those on SonyEricsson phones, it is advantageous to install the Now IMP Server in
conjunction with a Now.WAP Proxy Server. In this configuration, the Now IMP Server is
able to send WAP push messages through the Now.WAP Proxy to alert the mobile
phone IM client to new IM messages without requiring polling. The Now IMP Server
also directly supports a separate TCP/IP push channel, which is used by Nokia IM
clients. For more information on Push notification support, refer to the Advanced
Configuration section of this document.) Finally, you will need to supply the HTTP URL
for connecting to the HTTP Port on the Now IMP Server, as well as a valid user name
and password for an account on the server.
Configuring (Most) SonyEricsson Phones
In most SonyEricsson phones, the IM Client configuration can be found under the My
Friends application on the mobile phone, under the menu option More/Accounts. The
available configuration settings are:
Username - This setting should contain the name of the user account defined to the
Now IMP Server.
Domain - This setting should be left blank.
Password - This setting should contain the password of the user account defined on
the Now IMP Server.
Server - This setting should contain the HTTP URL for connecting to the Now IMP
Server. For example, http://ip.address:port or http://host.name:port. The :port suffix is
required unless the HTTP Port Number for the Now IMP Server is the default HTTP
port of 80.
Internet Profile - This setting points to an existing internet profile configured on the
mobile phone. Use an appropriate profile that will facilitate connectivity to the HTTP
URL of the Now IMP Server.

Auto-Login - Set to Yes if you want the IM Client to automatically startup and connect
to the IM Server when the mobile phone is powered on.
Allow Connection - This setting allows you to specify whether the IM Client can be
used when connected to any network, or if it should only be used when connected to
your home network operator. Specify Home Network in most cases to avoid
unexpected, and often exorbitant, data roaming charges.
Some SonyEricsson phones will have additional settings, such as Check Interval
which specifies an interval in seconds for polling the IMP Server. Refer to the
documentation for your mobile phone for more information.
Configuring (Most) Nokia Series 60 Phones
For Nokia Series 60 (Symbian) phones, IM settings can be configured under the Chat
or Presence applications. Select Options and then Settings to access the Server
Settings configuration for the IM Client.
The Server Settings include the following settings:
Server Name - This is a descriptive name for the server which is used only within the
IM Client for display purposes.
Access Point in Use - This specifies the internet access point (settings profile) that
should be used for IM client connections. Use an appropriate profile that will facilitate
connectivity to the HTTP URL of the Now IMP Server.
Web Address - This setting should contain the HTTP URL for connecting to the Now
IMP Server. For example, http://ip.address:port or http://host.name:port. The :port
suffix is required unless the HTTP Port Number for the Now IMP Server is the default
HTTP port of 80.
User ID - This setting should contain the name of the user account defined to the Now
IMP Server.
the Now IMP Server.
Configuring (Most) Nokia Series 40 Phones
For Nokia Series 40 phones, IM settings can be found under by selecting Messages
from the main menu. Then select Chat and Connect. Settings.
For these devices, it is difficult to select an existing configuration setting that is used by
the mobile phone browser, and adapt it for use by the IM Client. You may need to
manually copy the settings that are used by the WAP browser on the phone by writing
them on paper, and re-entering them into the IM Client settings.
When you edit the active chat and presence settings, the following settings are
included:
Chat and presence service name - This is a descriptive name for the server which is

used only within the IM Client for display purposes.
Homepage - This setting should contain the HTTP URL for connecting to the Now IMP
Server. For example, http://ip.address:port or http://host.name:port. The :port suffix is
required unless the HTTP Port Number for the Now IMP Server is the default HTTP
port of 80.
User ID - This setting should contain the name of the user account defined to the Now
IMP Server. (Note that the phone might automatically add a wv: prefix to the name.
This is not a problem, as it is standard syntax for the IMPS protocol.)
the Now IMP Server.
Connection Settings - This opens another menu to define IP connectivity settings.
Settings' name - This is a descriptive name for the settings which is only used within
the settings menus.
Proxies - This setting specifies whether or not connections will be routed through a
proxy. Enable this setting if you will be connecting to the Now IMP Server via a proxy.
Primary Proxy and Secondary Proxy refer to the address(es) of the WAP or HTTP
proxy server(s) through which you will be connecting. Enter the proxy information if
required for your configuration.
Data Bearer specifies the data bearer that will be used for the connection (e.g., GPRS,
EDGE, UMTS).
Bearer Settings - This opens another menu to define settings specific to the selected
Data Bearer. Typical settings on the sub menu include an Access Point Name (APN),
and settings for a username and password if they are required for connecting to the
APN.
Configuring (Most) Motorola Phones (V80)
The IM Client on the Motorola V80 is not as sophisticated as the clients on the Nokia
and SonyEricsson phones. It is definitely a first generation effort and is likely to
improve in future phones. One consideration to be aware of with the Motorola V80 is
that it uses a text based version of the IM protocol to communicate with the Now IMP
Server. This results in considerable overhead, with typical transactions, including
polling transactions, transmitting ten times as much data. This phone should definitely
only be used as an IM client in environments where you have an unlimited GPRS data
subscription plan.
The configuration settings for the IM Client can be found under the IM option of the
main menu. Select Offline Settings, and ISP Settings to access the configuration
settings.
GPRS APN - This specifies the Access Point Name (APN) on the GPRS network that
should be used for establishing IP connectivity for the IM client.

User name - This setting should contain the name of the user account defined to the
Now IMP Server.
the Now IMP Server.
IM Server - Unlike other phones, where the IMP Server is specified as an HTTP URL,
this setting is split among 3 separate configuration settings on this phone. This setting
should contain the IP address or DNS host name of the Now IMP Server.
IM Port - This setting should contain the HTTP Port Number of the Now IMP Server.
Post URL - This setting is ignored by the Now IMP Server. It is recommended to leave
this setting blank, or specify /.
Secure Login - This setting specifies whether or not the password for the account is
ever transmitted in the clear. Both available settings are supported by the Now IMP
Server.

Basic Configuration Step 4b: Connect with a Desktop IM Client
The Now IMP Client for Windows is included with the Now IMP Server.
The installation program, IMPClient.exe, is run to install the Now IMP Client on a PC
running Windows 98, Windows ME, Windows NT 4.0, Windows 2000, Windows XP, or
Windows 2003.
After installing the Now IMP Client, select its link from the Windows Start menu.
A login screen will be displayed:
In the Address field, specify username@xmppDomain.name, where username is the

user account defined on the Now IMP Server, and xmppDomain.name is the host name
of the Now IMP Server (see Step 1).
The Password field should contain the password for the user accuont as defined on
the Now IMP Server.
Check Remember my password if you would like the client to remember your
password so that you do not need to enter it every time you login with the Now IMP
Client.
Check Automatically log in if you would like the client to automatically login to the
server every time it is started.
Press the Login button to attempt to login with the supplied Address and Password.

After you have logged in, the main screen for the Now IMP Client will be displayed.
The main screen for the Now IMP Client would normally display the status of those
individuals who are on your instant messaging contact list. However, since this is the
first login, your account will not yet have any instant messaging contacts configured.

If you are running Windows XP Service Pack 2, the first time that you run the Now IMP
Client, the following warning screen might be displayed:
This warning is normal. The Now IMP Client uses an internal library which identifies
itself as the Instant Messenger for XMPP. If you select Keep Blocking, this will disable
the ability to perform file transfers via the IM client. If you select Unblock, this will allow
file transfers via the IM client. (Note that file transfers are only available between two
computers that are on the same Local Area Network.)
Now you will want to configure your instant messaging contacts. Either select the link
on the main screen that is labeld Add someone to your contact list, or select
Actions/Add a contact from the menu bar.

Searching for a user via the directory is the default option, so press Next.
It is necessary to supply some information to search for a user. Enter this information,
and press Search.

If any search results are returned, highlight that entry and press Next, or simply click on
the entry.
An authorisation request will be sent to the user, asking if it is permissable for you to
add them to your contact list.

The server will not display presence information for another user unless that user has
authorised it. (Note that some mobile IM clients do not accept presence authorisation
requests. Instead, affected clients have configuration parameters that specify whether
authorisation is granted to anyone who asks, or if it is granted only to those that have
been added to the mobile's contact list.)
Press Finish to send the authorisation request.
Please note that the contact will not appear in your contact list until:
• They have authorised your presence request, or it is automatically authorised based
upon settings defined in the mobile IM client.
• The user must be on-line. Contacts will not display in your contact list unless they
are connected to the IM server. (A user's status can be busy or away, and they will
appear in the contact list. However, if they are not connected, they will not appear.)
Additional information on using the Now IMP Client can be found elsewhere in this
document, beginning on page 65

Advanced Configuration
This section describes the advanced configuration settings available for the Now IMP
Server.
Service Page
This page is used to start and stop the Now IMP Server. It is also used to install Now
IMP as a Windows service, so that it is automatically started every time the PC is
rebooted. The following settings are available on this page:
Run as a Service - Check this setting to install Now IMP as a Windows service.
Remove the check to remove Now IMP from running as a Windows Service.
Start - This button is enabled if the Now IMP Server is not running. Press this button to
start the Now IMP Server.
Stop - This button is enabled if the Now IMP Server is currently running. Press this
button to stop the Now IMP Server.
Service Information - This box contains information about the running service.

Server Page
This page contains general server configuration settings for the Now IMP Server.
IP Address – This box contains a list of the of the IP Addresses available on the
computer. For configurations where multiple IP addresses are configured on the
computer, it is possible to configure the Now IMP Server to listen for HTTP connections
on the specified port for only a specific IP address. Select one of the listed IP
addresses, or select all available to have the Now IMP Server listen for connections on
any IP address bound to the computer.
HTTP Port Number - This specifies the TCP/IP Port Number on which the Now IMP
Server should listen for connections from mobile IM Clients (Wireless Village / OMA
IMPS Protocol).
HTTPS Port Number - This specifies the TCP/IP Port Number on which the Now IMP
Server should listen for SSL/TLS connections from mobile IM Clients (Wireless Village /
OMA IMPS Protocol). This option is only enabled if an SSL/TLS certificate has been
generated on the SSL/TLS page of the configuration dialog.
To enable the XMPP Server interface, you must define the XMPP Domain Name. This

is normally the host name on which the Now IMP Server is installed. When connecting
to the Now IMP Server, it is customary to login with an XMPP client by specifying a user
name of user@xmppDomain.name, where “xmppDomain.name” is the host name of
the Now IMP Server. (The Now IMP Client can be configured to assume a default
domain name when it is installed, so that users need only supply their user name to
login. This is described in Step 4b.)
Instead of using a host name, a special DNS “SRV” record can be used. It is similar in
concept to DNS “MX” records used by e-mail servers. For XMPP clients to properly
connect to the Now IMP Server using “SRV” records, the “SRV” record needs to be
defined in the format “_xmppclient._tcp.xmppDomain.name” with the port set to 5222,
and the host name set to the specific “A” (host address) record for your server.
Desktop IM clients will connect to the Now IMP Server using the XMPP Protocol, which
by default uses TCP/IP Port 5222. It is easy to override this default port assignment if
you are using “SRV” records in DNS. However, in cases where you are connecting to
the host by its host name, clients will assume port 5222, and the default XMPP Port
Number setting should not be changed.
SSL/TLS can also be used for XMPP Protocol connections. Many IM clients, including
the Now IMP Client, can negotiate an SSL/TLS connection over the standard XMPP
port (using the STARTTLS protocol option). However, some XMPP clients expect to
use a separate port for SSL/TLS connections. For those clients, the XMPP SSL Port
Number field specifies a port on which the server will listen for XMPP connections
using SSL. Clients that use a separate port for XMPP SSL/TLS connections will
assume the default port assignment of 5223.
Web Admin User Name and Web Admin Password - If these settings are non-blank,
an administrative interface is available via the web, which allows for an administrative
user to define user accounts on the Now IMP Server.
When the web administrative interface is enabled, it is possible to connect to this
interface by connecting to the HTTP port of the Now IMP Server, and including /ADMIN
in the URL (e.g., http://ip.address:port/ADMIN). Web administration functionality can be
limited to a specified list of IP addresses by entering one or more IP addresses in the
Web Admin IP Address Restrictions field. The IP address restrictions field can
contain a comma-delimited list of IP addresses, with the ability for wild cards to be
specified (e.g., 192.168.1.*,127.0.0.1).

Options Page
This page contains general configuration settings for the Now IMP Server.
Session Timeout - This specifies the number of seconds of inactivity before which a
client session is considered inactive. (Note: Even though a session may become
inactive, provisions are in place to allow a session to automatically reconnect without
user intervention.)
Keep Alive Time for Clients - This specifies a time interval, in seconds, that is
broadcast by the server to connected IM Clients. The server informs clients that it
expects to receive a request within this time interval before it may consider a session
inactive. (Note that while this is similar in concept to Session Timeout, that setting
refers to the actual session timeout used by the server, while this is the setting that is
broadcast to IM clients.) Some IM clients will use this is a suggestion for clients as to
the amount of time between polling requests issued by the client.
Minimum Server Poll Interval – This is the minimum amount of time that is required to
elapse between client polling requests of the server. This setting does not control how
often the client polls the server, but rather if the client needs to make multiple requests

of the server, it will impose a delay between requests.
Idle Polling Response Delay – When the server receives a polling request from a
client, and there is no updated information to send to the client, the server can display
the response by a number of seconds in order to slow down requests from the client.
Setting this value larger than 15 seconds is not recommend, as it may cause clients to
report errors.
Force disconnect of idle polling clients – In some public server configurations, it may
be advantageous to forcibly disconnect idle users who are actively polling the server,
but not sending or receiving messages. If this option is enabled, and a client is only
sending polling and keep-alive requests to the server, without sending or receiving any
messages within the "Idle Session Timeout" period, the server will force the client to
disconnect from the server.
Created groups are temporary (deleted after participants leave) – By default, when
a user creates a group (conference room) using the Wireless Village protocol, the group
is considered to be permanent, in that it is not deleted until the group creator deletes
the group. This is different from the XMPP protocol, in which conference rooms are
considered temporary by default. When a group is temporary, it is automatically
deleted when all participants leave the discussion. Checking this option causes the
server to consider groups created by Wireless Village protocol users to be temporary.
This setting can help avoid cluttering up the server with groups.
Allow all users to create public groups – If checked, this option indicates that any
user is allowed to create a public group (chat room) on the server. A public group can
appear in search lists, allowing other users to find and join the group. A non-public
group can only be accessed if you receive an invite or manually enter the group name
(subject to member access restrictions which can also limit access to groups). If this
option is unchecked, then users cannot create public groups unless their user name is
listed in the “Users allowed to create public groups” field, which can contain a
comma delimited list of users allowed to create public groups. If a user attempts to
create a public group, but their account is not allowed to do so, the group is created, but
the group will be created as a private group only.
Delete group if no activity for x days – If a group has not seen any activity (no
members joining, no messages posted) for a configurable number of days, the server
can be configured to automatically delete the group. This setting can help avoid
cluttering up the server with inactive groups.

Push Page
Most mobile phone IM clients will connect to the Now IMP Server via a WAP Proxy
server. The typical mode of operation is for an IM client to establish an IP connection
(GPRS/EDGE/UMTS), and poll the server for new messages.
For some IM clients, such as those on SonyEricsson phones, it is advantageous to
install the Now IMP Server in conjunction with a Now.WAP Proxy Server. In this
configuration, the Now IMP Server is able to send WAP push messages through the
Now.WAP Proxy to alert the mobile phone IM client to new IM messages without
requiring polling.
The Now IMP Server also directly supports a separate TCP/IP push channel, which is
used by Nokia IM clients.
The Now IMP Server supports three types of WAP Push notification for IM events:
1.) WAP Push over UDP
2.) CIR TCP Push Channel (STCP)
3.) WAP Push over SMS

WAP Push over UDP
WAP Push over UDP is used when a mobile phone connects to Now IMP Server via a
WAP proxy. This type of connection is commonly used in the IM clients built into
SonyEricsson phones.
To support WAP Push over UDP, the Now IMP Server needs to be able to identify the
IP address of the IM client. In a typical configuration, the Now IMP Server will only see
the IP address of the WAP proxy.
To identify the IP address of the IM client, Now IMP must receive the IP address via an
HTTP header that is forwarded by the WAP proxy. The Now IMP Server automatically
looks for X-WAP-Client-IP: and X-Network-Info: headers that are generated by the
Now.WAP Proxy. If the Now IMP Server needs to be configured to look at additional
headers, these headers can be specified as a comma delimited list under the HTTP
Headers for IP Address setting.
Note that in most configurations of a Now IMP Server residing outside of an operator
network, having the IP address of the IM Client is not sufficient for allowing WAP Push
over UDP. This is because in most operator configurations, the mobile phones are
assigned a private IP address on the operator network, and connect to the external
world via a Network Address Translation (NAT) router. This private IP address is not
accessible to the outside world.
For the reason detailed above, the Now IMP Server has special hooks to integrate with
the Now.WAP Proxy Server v2.55 or later. When Now IMP connections are proxied via
the WAP protocols by a Now.WAP server, the Now IMP Server and Now.WAP Proxy
can cooperate to ensure that WAP Push messages over UDP can be delivered, even
when the mobile phone is connected to a private IP address. The Now IMP Server and
Now.WAP Proxy will detect each other automatically to facilitate this cooperation.
However, it is necessary that in the Now.WAP Proxy, the Forward X-MSISDN: header
in content server requests setting is enabled, and that the domain name and/or IP
address of the Now IMP Server be listed in the Content Domains to receive X-MSISDN:
header. This is required even if the Now.WAP Proxy is not able to actually
receive MSISDN information via RADIUS, as these settings will also enable the
enhanced cooperation between the two servers. (Note: The Now.WAP Proxy
server can be installed outside of the operator network.)

CIR TCP Push Channel (STCP)
CIR is an acronym for Communications Initiation Request.

When an IM client connects to an IM Server using HTTP over TCP (with or without a
proxy), it is possible for the client to establish a persistent CIR connection to the Now
IMP Server.
The Now IMP Server will send a notification over this connection whenever an IM event
has occurred (presence notification, new message, invitation, etc.).
The Now IMP Server uses the same port for this CIR TCP Push Channel as is used for
standard IM client connections. However, the Now IMP Server needs to be able to
advertise this capability to IM clients in order for them to be able to take advantage of
this capability.
To do this, the Now IMP Server needs to publish the external IP address and port
number that should be used for connecting to the Now IMP Server. This is required
because it is common for the Now IMP Server to be sitting on a private IP address that
is routed via a firewall and/or NAT router. The public IP address for the Now IMP
Server should be specified in the Advertised IP Address field, and the external port
number for connecting to the HTTP Port Number of the Now IMP Server should be
specified in the Advertised Port field.

WAP Push over SMS
The Now IMP Server can use WAP Push notifications over SMS by routing them via a
WAP Push Proxy Gateway (PPG), such as the Now SMS/MMS Gateway. WAP Push
requests are delivered to the PPG using the Push Access Protocol (PAP).
To send WAP Push notifications via a WAP Push Proxy Gateway, check Enable SMS
Push via WAP Push Proxy Gateway (PPG), and supply the settings to connect to the
WAP Push Proxy Gateway.
The PPG Server URL is an HTTP URL for connecting to the Push Proxy Gateway. For
the NowSMS PPG, this URL is generally of the format http://ip.address:port/PAP, where
ip.address is the IP address or DNS host name of the NowSMS server, and port is the
port number for the web interface. “/PAP” is a path in the URL that tells NowSMS that
the request is using the Push Access Protocol (PAP).
User Name and Password are optional parameters, that if present, are used to build a
basic authentication (“Authorization:”) header in the PAP request. In most situations,
this is how the Now IMP Server will authenticate to the PPG.
PPG Push Domain is a configuration setting that is required by some PPGs. When
Now IMP generates a PAP push request, if a PPG Push Domain value is present, it will
be included in the destination push address. For example, if no PPG Push Domain
value is present, the destination push address will be of the format
WAPPUSH=99999999/TYPE=PLMN. If a PPG Push Domain of operator.net is
present, the destination push address will be of the format
WAPPUSH=99999999/TYPE=PLMN@operator.net. Whether or not a PPG Push
Domain is required depends on the PPG, and you will need to check with the
administrator of the PPG. (For NowSMS, the PPG Push Domain field can be left
blank.)
If WAP Push over SMS is enabled, Now IMP will only use WAP Push over SMS for
accounts that have a phone number defined.
By default, WAP Push over SMS will only be used to notify the client of new messages,
and not for updated presence information. If you wish to have the Now IMP Server also
generate WAP Push over SMS for presence updates, you must manually add a
configuration setting to NOWIMPS.INI. Under the [NOWIMPS] header, add
PushMessagesOnly=No. When this setting is present, Now IMP will generate WAP
Push over SMS messages for both notification of new messages and for updated
presence information.
If “Enable Direct WAP Push over UDP" is also enabled, and the server has an IP
address to which to attempt to send a WAP Push over UDP, the server will first attempt
to send the WAP Push over UDP. If the client does not respond to the push within a
timeout period, a WAP Push over SMS will then be attempted. (The default timeout for
WAP Push over UDP is 12 seconds, and can be configured by editing NOWIMPS.INI,
and placing UDPPushTimeout=### under the [NOWIMPS] header.)

SMTP Page
The Now IMP Server supports external connectivity via a built-in e-mail gateway,
allowing IM users to send messages to e-mail recipients, and allowing e-mail users to
send messages to IM recipients.
To enable this capability, you must configure settings for the SMTP server that is built
into the Now IMP Server. These settings are configured on the SMTP page of the
configuration dialog.
To enable SMTP e-mail connectivity, check Enable SMTP Server. You should then
configure a host and domain name for the SMTP server. The Host Name should be a
host name for the server which has been configured for internet DNS. When initiating
outbound SMTP connections, the SMTP server will identify itself with this host name.
The Domain Name will be used as the e-mail domain name for routing SMTP e-mail
messages to IM user (e.g., user@domain). Internet DNS should be configured with a
mail exchange (MX) record to route e-mail for this domain to the Now IMP Server (or to
another SMTP server that relays the mail to the Now IMP Server).
The SMTP Port Number is the port number on which the server will listen for inbound

SMTP e-mail deliveries. The standard port number for SMTP e-mail is 25. This
standard port number should be used unless you are using a specialised SMTP relay
that relays messages to a non-standard port.
IP Address – This box contains a list of the of the IP Addresses available on the
computer. For configurations where multiple IP addresses are configured on the
computer, it is possible to configure the Now IMP Server to listen for SMTP connections
on the specified port for only a specific IP address. Select one of the listed IP
addresses, or select all available to have the Now IMP Server listen for connections on
any IP address bound to the computer.
For delivering SMTP e-mail messages sent by IM users to SMTP users, the Now IMP
Server will attempt to act as a smart mailer, connecting directly to recipient e-mail
servers. If you prefer to use an SMTP relay host in your environment, check the Use
SMTP Relay Host setting, and specify an IP address or host name for the relay host in
the SMTP Relay Host field.
The E-Mail Character Limit setting specifies the maximum number of characters that
will be extracted from an e-mail message when routing the message from SMTP e-mail
to an IM user.

Users Page
IM User accounts are defined on the Users page of the configuration dialog.
To define a new user account, press the Add button.

The User Name and Password fields are required for a user account definition. The
additional user settings are used only as informational settings. These settings are
used primarily to facilitate search functionality, allowing a user to locate another user by
searching on the supplied settings.
For standard user accounts, leave User account is an automated agent unchecked.
send and receive messages for the account, instead of an actual user. Automated
agents are described later in this document on page 42.

SSL/TLS Page
The SSL/TLS page allows you to configure setting related to the use of secure
protocols for client connections to the Now IMP Server.
When Now IMP is initially installed, you must generate an SSL/TLS server certificate
before any secure connections will be allowed.
Press Generate Server Certificate to start the process of generating an SSL/TLS server
certificate.

Host Name – This should be the host name of the server. XMPP clients will expect this
to match the XMPP Domain Name setting. Wireless Village/OMA IMPS clients will
expect this to match the host name that they use for connecting to the server (not
configured in Now IMP, but configured in DNS.)
Administrator E-Mail Address – This should be a valid e-mail address for an
administrative user that can receive e-mail regarding the server.
Company or Organization Name – This is the company or organisation's legal name.
Department Name – This is an optional setting, reflecting the department of the
company to which this server belongs.
City Name and State or Province Name – These provide location information to which
the server certificate is registered for the company or organisation.
Country Name (2 letter code) – This provides additional location information to which
the server certificate is registered for the company or organisation. Example country
codes are US for the United States and GB for Great Britain.
Challenge Password and Re-enter Password – This password provides security for
protecting the server certificate.
Press Generate Server Certificate to create the server certificate.
Now IMP Server generates a self-signed server certificate, which is sufficient for most
basic SSL/TLS connections.

After you generate the server certificate, Now IMP will explain that SSL/TLS (HTTPS)
support has been enabled for this server to accept connections, and instruct that you
now review the SSL/TLS related port number assignments on the Server page of the
configuration dialog.
However, the certificate is only self-signed. This only enables SSL/TLS to be used for
encryption purposes, so that a client can connect to the server over an encrypted
channel. A self-signed certificate does not provide any authentication, or verification
that the information presented in the certificate is valid.
In the SSL/TLS model, independent trusted parties, known as certificate authorities,
validate that the information presented in a certificate is valid. And these authorities will
sign a certificate to indicate that they trust it. Web browsers are usually configured with
a predefined list of known trusted certificate authorities. If a web browser connects to a
server via SSL/TLS, and is presented with a certificate that has not been signed by a
certificate authority that is trusted by the browser, and a security warning message is
typically displayed to the end user. The end user must then decide whether or not to
accept the connection.
The Now IMP Client does not validate certificates, and will simply use the channel for
encryption, without presenting a warning.

However, some IM clients may require that the certificate be signed by a trusted
certificate authority. More information on certificate authorities can be found at the
independent web site, http://www.sslreview.com.
To have your certificate signed by a certificate authority (CA), press the Request or
Install Certificate from CA button. This will cause the Now IMP Server to display
additional information.
To request a certificate from a certificate authority, you will need to deliver a certificate
sign request (CSR) to the authority. Now IMP has created a file named SSL.CSR in the
NowIMP program directory which contains the CSR. This file is in text format and can
be opened with a simple text editor, such as Notepad.
When you receive a signed certificate back from the authority, that certificate should be
saved in a text file named SSL.CA, and located in the NowIMP Directory.
You must restart the Now IMP Server in order to recognise any certificate changes.

Serial # Page
The serial number page is used to enter serialisation information for a purchased copy
of the Now IMP Server product.

User Account Provisioning via HTTP
A web interface is available for provisioning Now IMP user accounts. To enable this
interface, the Web Admin User Name and Web Admin Password settings on the
Options page of the configuration dialog must be non-blank. Web administration
functionality can be limited to a specified list of IP addresses by entering one or more IP
addresses in the Admin IP Address Restrictions field. The IP address restrictions
field can contain a comma-delimited list of IP addresses, with the ability for wild cards to
be specified (e.g., 192.168.1.*,127.0.0.1).
When the web administrative interface is enabled, it is possible to connect to this
interface by connecting to the HTTP port of the Now IMP Server, and including /ADMIN
in the URL (e.g., http://ip.address:port/ADMIN).
Additionally, an HTTP-based interface has been added to allow for account provisioning
by external applications. This interface is accessed with a URL of "/provision" followed
by a series of "HTTP GET" parameters. (The admin username and password must be
supplied in the HTTP GET request within an "Authorization:" header.)
The following parameters are supported in this interface:
• AdminAction=Add, Modify, Delete, or Query
• UserName=
• Password=
• Firstname=
• Lastname=
• Alias=
• PhoneNumber=
• EmailAddress=
• AgentURL=
Assuming that the user is authorized to issue a provisioning command (valid

username/password, and supported IP address for originating the request), the server
will return a normal HTTP response code of 200 with a MIME content type of
“text/plain”. The response will start with “OK” if the request was successful, or “ERROR”
if the request failed.
An example URL for defining a new user is provided below:
http://server:port/provision?AdminAction=Add&UserName=accountname&Password=pa
ssword&Firstname=First&Lastname=Last&PhoneNumber=%
2B447777777777&EMailAddress=user@domain.com
(Note: In the above example notice that some characters must be URL escaped for
HTTP. This includes the space character as %20 and the + character as %2B.)

If the AgentURL parameter is non-blank when provisioning a user, the user account is
provisioned as an automated agent (see page 42).
AdminAction=Query is a special case which allows an application to retrieve
information about defined users.
When the AdminAction=Query command is issued, the server will search for user
accounts that match the supplied parameters. For example, the following command will
search for any user accounts that have the e-mail address user@domain.com
associated with them:
http://server:port/provision?AdminAction=Query&EMailAddress=user@domain.com
If multiple search parameters are supplied, the server will look for a match on all suplied
parameters.
Search parameters can include wildcard characters “*” (match zero or more characters)
and/or “?” (match exactly one character). For example, the following command will
search for all accounts that have an e-mail address associated with them from a
particular domain:
http://server:port/provision?AdminAction=Query&EMailAddress=*@domain.com
Or the following command could be used to return a list of all defined users:
http://server:port/provision?AdminAction=Query&UserName=*
The search results will be returned in an XML document using the following format:
<NowIMPInfo>
<UserList>
<UserInfo>
<UserName>bryce</UserName>
<FirstName>Bryce</FirstName>
<LastName>Norwood</LastName>
<Alias>bryce</Alias>
<PhoneNumber>123</PhoneNumber>
<EMailAddress>nowsms@now.co.uk</EMailAddress>
</UserInfo>
</UserList>
</NowIMPInfo>
If multiple users match the query, the “UserInfo” element will be repeated for each user.
Fields that are not defined for a user, or are left blank (e.g., Alias, PhoneNumber,
EmailAddress), will not be included in the XML response.
For user accounts that are Automated Agents (see page 42), two additional fields will
be included in UserInfo section of the response:
<IsAgent>TRUE</IsAgent>
<AgentURL>http://www.now.co.uk/echo.asp</AgentURL>

Additional parameters are available for AdminAction=Query to allow for searches of
active users and active conference rooms. Including the parameter ActiveUsers=Yes
will cause a list of currently active uses to be returned, while ActiveRooms=Yes will
cause a list of currently active conference rooms to be returned.
For example, the following command:
http://server:port/provision?AdminAction=Query&ActiveUsers=Yes&ActiveRooms=Yes
would return a response similar to the following:
<NowIMPInfo>
<ActiveUserList>
<UserInfo>
<Protocol>XMPP</Protocol>
<Resource>Now IMP</Resource>
</UserInfo>
<UserInfo>
<UserName>kent</UserName>
<Protocol>IMPS</Protocol>
</UserInfo>
</ActiveUserList>
<ActiveConferenceRoomList>
<ConferenceRoomInfo>
<ConferenceRoomID>/test.conference.room</ConferenceRoomID>
<ConferenceRoomActiveUserList>
<UserName>kent</UserName>
</ConferenceRoomActiveUserList>
</ConferenceRoomInfo>
</ActiveConferenceRoomList>
</NowIMPInfo>
ActiveUsers=Yes causes the <ActiveUserList> element list to be returned. Each active

user will be represented by a <UserInfo> element. At a minimum, this user information
will contain their UserName and the Protocol that is being used to connect to the server.
(XMPP users will also have a Resource name associated with the user. This is because
XMPP allows a user to connect simultaneously under multiple resources.)
ActiveRooms=Yes causes the <ActiveConferenceRoomList> element list to be

returned. Each active conference room will be represented by a
<ConferenceRoomInfo> element. At a minimum, this conference room information will
contain the ConferenceRoomID, and a list of active users in the conference room.

Automated Agents

send and receive messages for the account, instead of an actual user.
Automated agents are defined similar to standard IM user accounts, using the Users
Page of the configuration dialog.
When adding an automated agent user account, the setting User account is an
automated agent should be checked.
Every time the Now IMP server receives an instant message for the agent, it will
connect to an HTTP script to allow the agent to process the message. The URL for the
script that you want to associate with the agent should be defined in the Agent URL
parameter of the account.
Now IMP will pass information about the received message to the URL using standard
HTTP GET (CGI style) parameters. The “from=” parameter will contain the sender's IM
address. The “to=” parameter will contain the agent's IM address. The “text=”
parameter will contain the text of the received message.
For example:
http://www.now.co.uk/echo.asp?from=bryce&to=agent&text=this%20is%20a%20test
Parameters are escaped using standard URL escaping. Notice in the example above
that space characters have been replaced with “%20”.

Please note that all message text will be encoded in the UTF-8 character set.
If an agent wishes to reply back to the sender, it is possible for the agent to return an
HTTP response of the content type “text/plain”, with the text of the response in the body
of the HTTP response. (If the response is blank, or returns a different content type, no
response will be sent.)
Please note that the agent must respond with a standard HTTP 200 OK response,
otherwise the server will retry the request. Most web server environments will return
this HTTP 200 OK response automatically, but if you need to do this manually, the
following is a valid empty response (no response sent back to the sender).
HTTP/1.0 200 OK
Content-Type: text/plain
Content-Length: 0
<blank line>
A good example of a simple interactive agent is an “echo” agent, which simply echos
back any text received from a user.
If you wish to test your system, you can specify an agent URL of
http://www.now.co.uk/echo.asp, which is a simple “echo” agent installed on one of
Now's web servers.
The source for echo.asp is included below:
<%
Response.ContentType = "text/plain"
If (Request.QueryString("text") = "") Then
Response.Write (" ")
Else
Response.Write ("ECHO : ")
Response.Write (Request.QueryString("text"))
End If
%>
Alternative, a PHP version, echo.php, is presented below:
<?
header ("Content-Type: text/plain");
if (isset($_REQUEST['text'])) {
echo "ECHO : " . $_REQUEST['text'];
}
?>
While extremely simplistic, both of the above examples illustrate how an agent script
can process received URL parameters, and generate a reply.

It may also be desirable for an agent to send a message that is not in direct response to
a received message. For example, the agent may wish to broadcast information to
subscribers.
To send such a message, the agent must make an HTTP request to the server's HTTP
Port Number, as configured on the Server page of the configuration dialog.
The request should be an HTTP GET request to http://server:port/agent with the
following parameters specified as standard HTTP GET (CGI style) parameters.
Required parameters:
User User account defined for agent
Password Password associated with agent user account
Text Text of the message to be sent
Plus one of the following parameters:

To One or more message recipients, usually the user account
name(s) of the intended recipient(s). If more than one
recipient is desired, separate recipients with either a comma
(,) or semicolon (;).
Broadcast Set to allonline to send a message to all instant messaging
users that have added the agent to their contact list (i.e.,
subscribed to the agent's presence information).
SystemBroadcast Set to allonline to send a message to all users that are
currently connected to the server.
Set to alldefined to send a message to all user accounts
that are defined to the server.
This setting can only be used if Agent can broadcast to all
users is enabled for an account.
Examples:
http://server:port/agent?User=agent&password=agent&text=This+is+a+broadcast+m
essage+to+all+who+have+added+the+agent+to+their+contact+list.&broadcast=allon
line
http://server:port/agent?User=agent&password=agent&text=This+is+a+message+to+
2+user+accounts.&to=bryce,kent
http://server:port/agent?User=agent&password=agent&text=This+is+a+message+to+
2+user+accounts.&to=bryce%2Ckent
http://server:port/agent?User=agent&password=agent&text=This+is+a+broadcast+m
essage+to+all+connected+users.&systembroadcast=allonline

OTA Provisioning for IMPS
Most mobile phones that support IMPS have the ability to receive settings for the IMPS
client over-the-air (OTA). This means that the IMPS settings can be sent to the mobile
phone in an SMS message (actually a series of SMS messages are sent that are
treated as a single message by the receiver).
Currently there are two different formats for these OTA messages.
SonyEricsson utilises the format defined by the Nokia/SonyEricsson OTA Specification
v7.1.
Nokia (and other vendors) use the format defined by the Open Mobile Alliance (OMA)
Provisioning Content specification.
Both of these OTA formats use XML based documents, however the XML schema is
significantly different between the two formats.
When the documents are sent out via SMS, they are encoded in a wireless binary XML
(WBXML) format.
One way of sending out these settings documents is using the Now SMS/MMS
Gateway product.
From the Send XML Settings option of the NowSMS web interface, it is possible to
send an XML document containing IMPS settings to a mobile phone.
Programatically, it is possible to post the XML settings document to the NowSMS server
to request that it be sent out via SMS.
An example HTTP POST of an XML settings document to a NowSMS server looks like
this:
POST /?PhoneNumber=xxxxxxxx&OTA=POST HTTP/1.0
Content-Length: yyyyyy
(*blank line*)
<xml settings document>
The “Content-Length:” header specifies the length of the XML document that follows.
(This tells the server how much data to expect in the XML document.)
Optionally, the POST line can be modified to include a username and password to
authenticate to the NowSMS server:
POST /?PhoneNumber=xxxxxxxx&user=username&password=password&OTA=POST HTTP/1.0
Content-Length: yyyyyy
(*blank line*)
<xml settings document>
Note that some Nokia phones require that OTA settings be signed with a PIN code.
The receiving user is then prompted to enter that PIN code when opening the message

that contains the settings.
To include a PIN code when posting settings to a NowSMS server, include
“&OTAPIN=1234” in the POST URL, where “1234” is the 4 digit PIN code that you wish
to be associated with the message.
For full documentation on the format of the XML settings documents, please refer to the
Nokia/SonyEricsson OTA Settings Specification v7.1, available for download from the
SonyEricsson developer web site (http://www.sonyericsson.com/developer), and the
OMA Provisioning Content v1.1 specification, available for download from the Open
Mobile Alliance web site (http://www.openmobilealliance.org). Nokia also has OTA
settings information specific to their mobile phones available from the Nokia developer
web site (http://www.forum.nokia.com).
To help get you started, we have provided basic examples for settings documents for
each of these protocols in the following sections.

OTA Provisioning for IMPS: SonyEricsson
The following document is an example OTA document for provisioning the IM client on
a SonyEricsson phone.
<WVSettings>
<WVOTAVersion>1.0</WVOTAVersion>
<WVCommon>
<WVSettingsName>NowIMP</WVSettingsName>
<WVRefName>Internet Profile</WVRefName>
<WVSupportedVersion>1.0</WVSupportedVersion>
<WVSupportedVersion>1.1</WVSupportedVersion>
<WVUserID>username</WVUserID>
<WVPassword>password</WVPassword>
<WVPreferredProtocol></WVPreferredProtocol>
</WVCommon>
<WVHTTP>
<WVSAPURI>http://server:port/</WVSAPURI>
<WVSAPFourWaySupported>T</WVSAPFourWaySupported>
</WVHTTP>
</WVSettings>
Note that in the above settings that there are five fields that you will need to replace
with your settings.
WVSettingsName – This text contains a descriptive name for the settings. (Note that
current SonyEricsson phones seem to ignore this value.)
WVRefName – This text should contain the name of an existing Internet Profile that has
been configured in the mobile phone. Note that it is not possible to provision a new
internet profile at the same time as sending IM settings. If you also need to configure
an internet profile to be used with the settings, a separate configuration message must
be sent with the internet profile settings first. It is possible to remove this statement
from the settings message, in which case the IM client will prompt to select a profile.
WVUserID – This text should contain the name of the user account on the server.
WVPassword – This text should contain the password of the user account on the
server.
WVSAPURI – This text should contain the HTTP URL for connecting to the Now IMP
Server.

If it is necessary to send internet profile settings to the phone, a simple example is
presented below:
<CHARACTERISTIC-LIST>
<CHARACTERISTIC TYPE="ADDRESS">
<PARM NAME="BEARER" VALUE="GPRS"/>
<PARM NAME="PROXY" VALUE="1.2.3.4"/>
<PARM NAME="GPRS_ACCESSPOINTNAME" VALUE="gprs.apn"/>
<PARM NAME="PPP_AUTHTYPE" VALUE="PAP"/>
<PARM NAME="PPP_AUTHUSER" VALUE="GPRSusername"/>
<PARM NAME="PPP_AUTHSECRET" VALUE="GPRSpassword"/>
</CHARACTERISTIC>
<CHARACTERISTIC TYPE="URL" VALUE="http://homepage"/>
<CHARACTERISTIC TYPE="NAME">
<PARM NAME="NAME" VALUE="Internet Profile"/>
</CHARACTERISTIC>
</CHARACTERISTIC-LIST>
To adapt the above example to your environment, several changes are required.
The PARM NAME=”PROXY” value should be changed to reference the IP address of
the WAP proxy to be used. (We recommend using a conventional WAP proxy via the
WSP stack instead of the HTTP stack, as this is the only way to support push
notifications over IP to these devices.)
The PARM NAME=”GPRS_ACCESSPOINTNAME” value should be changed to
reference the GPRS Access Point Name (APN) of the subscriber's mobile operator.
The lines containing PARM NAME=”PPP_AUTHUSER” and “PPP_AUTHSECRET”
can be removed if no username and password is required for connecting to the GPRS
APN. If a username and/or password is required, the values should be edited as
appropriate for the connection.
The CHARACTERISTIC TYPE=”URL” value will contain the home page associated
with the internet profile being created. Although there is not strictly a home page
associated with this connection, it is a good idea to specify a valid WAP portal entry
page here.
The PARM NAME=”NAME” value should be changed to contain a descriptive name for
the settings. Note that the value here will correspond to the WVRefName value in an
IM Settings message.

OTA Provisioning for IMPS: Nokia (and other OMA Compliant Devices)
The following document is an example OTA document for provisioning the IM client
using OMA (Open Mobile Alliance) Provisioning Content, as deployed on Nokia phones.
<wap-provisioningdoc>
<characteristic type="BOOTSTRAP">
<parm name="NAME" value="NowIMP"/>
</characteristic>
<characteristic type="NAPDEF">
<parm name="NAPID" value="NowIMP_NAPID"/>
<parm name="BEARER" value="GSM-GPRS"/>
<parm name="NAP-ADDRESS" value="grps.apn"/>
<parm name="NAP-ADDRTYPE" value="APN"/>
<characteristic type="NAPAUTHINFO">
<parm name="AUTHTYPE" value="PAP"/>
<parm name="AUTHNAME" value="GPRSusername"/>
<parm name="AUTHSECRET" value="GPRSpassword"/>
</characteristic>
</characteristic>
<characteristic type="PXLOGICAL">
<parm name="PROXY-ID" value="NowIMP_Proxy"/>
<characteristic type="PXPHYSICAL">
<parm name="PHYSICAL-PROXY-ID" value="NowIMP_PhProxy"/>
<parm name="PXADDR" value="1.2.3.4"/>
<parm name="PXADDRTYPE" value="IPV4"/>
<parm name="TO-NAPID" value="NowIMP_NAPID"/>
<characteristic type="PORT">
<parm name="PORTNBR" value="8080"/>
</characteristic>
</characteristic>
</characteristic>
<characteristic type="APPLICATION">
<parm name="APPID" value="wA"/>
<parm name="TO-PROXY" value="NowIMP_Proxy"/>

<parm name="ADDR" value="http://server:port/"/>
<characteristic type="APPAUTH">
<parm name="AAUTHNAME" value="username"/>
<parm name="AAUTHSECRET" value="password"/>
</characteristic>
</characteristic>
</wap-provisioningdoc>
To adapt the above example to your environment, a number of changes are required.
There are several places in the settings document where parm name=”NAME”
value=”NowIMP” appears. In these cases, “NowIMP” is a descriptive name that is
being associated with the settings. This name is displayed in the user interface of the
mobile phone as a name associated with the IM server and settings, and you should set
this to a name to an appropriate descriptive name for your environment.
You will notice that there are also a number of other places where “NowIMP” appears
as a prefix in the value parameter. This is done to indicate that portions of the settings
are related. While these settings are not displayed anywhere in the phone's user
interface, you may want to change the prefix to one that is specific to your environment.
The parm name=”NAP-ADDRESS” value should be changed to reference the GPRS
Access Point Name (APN) of the subscriber's mobile operator.
The lines containing parm name=”AUTHUSER” and “AUTHSECRET” should be
removed if no username and password is required for connecting to the GPRS APN. If
a username and/or password is required, the values should be edited as appropriate for
the connection.
The parm name=”PXADDR” value should be changed to reference the IP address of
the WAP/HTTP proxy to be used. Note that all Nokia phones that support these
configuration parameters are expecting to connect to an HTTP/WAP2 proxy server.
The parm name=”PORTNBR” value should be changed to reference the port number
to be used on the WAP/HTTP proxy.
The parm name=”ADDR” value should contain the HTTP URL for connecting to the
Now IMP Server.
The parm name=”AAUTHNAME” value should contain the username of the account
on the Now IMP Server, and the parm name=”AAUTHSECRET” value should contain
the password for that same account.

Self-User Provisioning via the Web
The Now IMP Server includes an interface for allowing users to self-register with the
IMP Server via the web. This interface is designed primarily to help simplify the
process of evaluating the product, and allowing product evaluators an easy way to
create accounts.
When this interface is enabled, it is possible to connect to this interface by connecting
to the HTTP port of the Now IMP Server, and including /SIGNUP in the URL (e.g.,
http://ip.address:port/SIGNUP).
The interface will prompt for a valid e-mail address. It will then send a sign-up
authorisation code to that e-mail address, and require that the user supply this
authorisation code in order to complete the registration process.
To enable this interface, it is necessary to manually edit the NOWIMPS.INI file (located
in the NowIMP program directory), and under the [NOWIMPS] header, add
EmailSignupSupported=Yes. It is also necessary to enable the SMTP e-mail server
that is built into the Now IMP Server.
The self-user provisioning interface uses HTML template files that are located in the
WEB\SIGNUP subdirectory of the NowIMP installation.
The index.htm template file is used to construct the initial screen that is displayed
when connecting to the /SIGNUP URL, as displayed below:

If the e-mail address is already registered with a user account on the Now IMP Server,
the server will indicate that the e-mail address is already registered to the system.
The user can select the “Recover Lost Password” link to have their password sent to
their e-mail address.

The password.htm template file is used to generate the “Recover Password” screen.
After the password has been sent to the e-mail address, the passwordsent.htm
template file is used to generate the confirmation screen.
Under normal conditions, when the e-mail address being entered is not already
associated with a user account on the Now IMP Server, the server will send an e-mail
message containing 4 character authorisation code. The web interface will display a
screen (authcode.htm template) that prompts for that authorisation code before the
user can complete the registration process.
After entering the authorisation code that was received via e-mail, the user is presented
with a screen (account.htm template) that allows them to define an account on the
Now IMP Server.
7

The “User ID”, “Password” and “Confirm Password” fields are required. The other fields
are optional, and are used primarily to facilitate user searches on the server.
Assuming that the account is created, the succes.htm template will be used to generate
a confirmation message.
The Server URL in the template is read from an entry in the NOWIMPS.INI file. Under

the [NOWIMPS] header, the setting IMPSServerURL=http://server:port/ is used to
construct the URL that is displayed.
When the OK or Close (“X”) button is pressed, the interface will redirect the user to a
configurable web address. To specify this web address, in the NOWIMPS.INI file,
under the [NOWIMPS] header, include CancelRedirectURL=http://server/path.
After creating an account, it is also possible for a user to connect back to the web
interface to change their user information, or to delete their account.
This is done by connecting to the HTTP port of the Now IMP Server, and including /
USER in the URL (e.g., http://ip.address:port/USER). The Now IMP Server will prompt
for the username and password of the account. If this information is provided correctly,
the following display is generated from the index.htm template file in the WEB\USER
subdirectory.
Note that it is not possible for the user to change the e-mail address associated with an
account. This can only be changed through the administrative interface.

If the user selects “Edit Account”, the editaccount.htm template (WEB\USER
directory) will be used to generate the display:

The text of the e-mail messages generated by the self-user provisioning interface can
be modified through the following settings in the NOWIMPS.INI file, with all settings
located in the [NOWIMPS] section of the file.
EmailAuthSender=sender@domain.com
This setting specifies the “From” address that is used when sending out e-mail
messages that contain an authorisation code.
EmailAuthSubject=IMPS Authorisation Code
This setting specifies the subject line of the e-mail message that is sent out with an
authorisation code. The default subject is displayed above.
EmailAuthTemplate=Your authorisation code for registering an account with the IMP
Service is @@AUTHCODE@@
This setting specifies the message text of the e-mail message that is sent out with an
authorisation code. The default text is displayed above. Note that the
@@AUTHCODE@@ placeholder will be replaced with the appropriate authorisation
code.
EmailPasswordSender=sender@domain.com
This setting specifies the “From” address that is used when sending out e-mail
messages to recover a lost password.
EmailPasswordSubject=IMPS User Account Information
This setting specifies the subject line of the e-mail message that is sent out to recover a
lost password. The default subject is displayed above.
EmailPasswordTemplate=Your IMPS User Account Information:\r\n\r\nUser ID:
@@UserName@@\r\nPassword: @@Password@@\r\nServer URL:
@@IMPSServerURL@@\r\n
This setting specifies the message text of the e-mail message that is sent out to recover
a lost password. The default text is displayed above. Note that the
@@UserName@@ placeholder will be replaced with the user account name, the
@@Password@@ placeholder will be replaced with the password for the account, and
the @@IMPSServerURL@@ placeholder will be replaced with the IMPSServerURL
setting from the NOWIMPS.INI file. \r\n are used to indicate a line break.

External Transports (AOL, MSN, etc.)
Adding an external transport connector to Now IMP allows users to connect to external
Instant Messaging systems such as MSN and AIM (AOL Instant Messenger).
Now IMP does not provide external transports to connect to these external IM systems.
However, Now IMP does support the XMPP (Jabber) gateway protocol, so that many
external transport connectors that were written to work with Jabber, can work with Now
IMP. This section of the documentation describes some experience and advice in
configuring popular connectors.
Please note that each user that wishes to connect to an external Instant Messaging
system MUST HAVE AN ACCOUNT with the external system.
When using Now IMP, the user can specify their account details with the external IM
system, so that Now IMP can proxy to the external IM system via an installed external
transport connector. When the user logs in to Now IMP, Now IMP will also log the user
into the external IM system. The user can then exchange messages with local Now
IMP users, or with users defined to the external IM system.
External IM account attributes can be defined via the Now IMP server admin interface,
or users can register their details using the Tools/Transports option in the Now IMP
desktop client.
Once a transport has been registered, Now IMP will automatically connect to the
account on the external transport each time the user logs in to the Now IMP Server.
Please note that there may be legal issues involved in providing a commercial service
that connects to a public IM network, and we encourage you to review the terms of use
of any public IM networks with which you wish to interconnect.

MSN Transport
An MSN transport that is compatible with Now IMP is PyMSNt (Python based MSN
Transport for Jabber).
The web site for PyMSNt is http://msn-transport.jabberstudio.org/
The latest version of PyMSNt that has been tested with Now IMP is v0.9.3.
This version of PyMSNt requires Python v2.3 (http://www.python.org), Twisted v2.0
(http://www.twistedmatrix.com), PyOpenSSL (http://pyopenssl.sourceforge.net) and
PyCrypto (http://www.amk.ca/python/code/crypto.html).
Because web site links can change, we have copied all of the necessary modules into a
single download, http://www.nowimp.com/download/msntransport.zip. This download
contains all of the necessary requirements to install PyMSNt on a Windows PC
(Windows 2000, XP, 2003).
PyMSNt can be installed on the same machine as the Now IMP server, or it can be
installed on a separate machine.
We recommend following these steps to install PyMSNt:
1.) Define the MSN transport to Now IMP. Go to the "Transports" page of the
configuration dialog. Specify a "Transport Port Number" upon which Now IMP will listen
for connections from external transports. Many transports default to using port 5347,
which is usually a good choice. Enter this value, and press "Apply".
Next click, "Add". Specify "MSN" as the "Transport Name". "Password" can be any
value that you choose.
Under "Domains routed via Transport", enter "hotmail.com" and press "Add". Then
enter "msn.com" and press "Add" again.
Check "Replace '@' with '%' (transport handles multiple domains)".
Press "OK".
The "Transports" list should now show "MSN - NOT connected". (The status will
change to "MSN - connected" once you complete this installation process.)
2.) If it is not already installed, install Python 2.3 by running Python-2.3.5.exe from the
ZIP download. The default installation settings are sufficient.
3.) If it is not already installed, install Twisted 2.0 for Python 2.3 by running
Twisted_NoDocs-2.0.1.win32-py2.3.exe from the ZIP download. The default
installation settings are sufficient.
4.) Install PyOpenSSL 0.6 for Python 2.3 by running pyOpenSSL-0.6.win32-py2.3.exe
from the ZIP download. The default installation settings are sufficient.
5.) Install PyCrypto 2.0 for Python 2.3 by running pycrypto-2.0.win32-py2.3.exe from the

6.) Install PyMSNt 0.9.3 by opening PyMSNt-0.9.3.zip from the ZIP download. Use a
ZIP utility to extract all of the files from this ZIP to a directory on your PC. Be sure that
the ZIP utility is configured to preserve folder names when extracting (with WinZIP, the
"Use folder names" button should be checked when extracting).
7.) Go to the directory that PyMSNt was extracted to. You will find the PyMSNt files in a
subdirectory beneath that directory named PyMSNt-0.9.3. Copy CONFIG-
EXAMPLE.XML over as CONFIG.XML. Edit CONFIG.XML with a text editor (note that
Notepad will not display this file properly, so instead of Notepad, use Wordpad, which
can be accessed from the command line by typing WRITE CONFIG.XML).
Edit the following sections of CONFIG.XML:
a.) The <jid> value should be msn.xmpp.domain.name, where "xmpp.Domain.Name" is
the "XMPP Domain Name" value defined on the "Server" page of the Now IMP
configuration dialog. ***IMPORTANT*** The <jid> value should be all lower case, even
if you have used mixed or upper case in the NowIMP configuration.
b.) The <mainServer> value should contain the IP address of the Now IMP server. If
the Now IMP server is running on the same machine, specify 127.0.0.1.
c.) The <port> value should match the "Transport Port Value" defined in Step #1.
d.) The <secret> value should match the "Password" value defined in Step #1.
8.) Change your current directory to the "src" subdirectory of the PyMSNt-0.9.3
directory.
Type "c:\python23\python main.py" to start the external transport. (Do not include
quotes, those are just for highlighting in this document.)
9.) The "Transports" list should in Now IMP should now show "MSN - Connected",
indicating that the transport has successfully connected to the Now IMP server.
You can now configure a user account to register with the transport. The easiest way to
do this for an initial test is using the Tools/Transports option in the Now IMP desktop
client.
Be sure to include "@msn.com" or "@hotmail.com" in your MSN user id, as
appropriate.
Internally, Now IMP will represent MSN contacts with an address of "user%
msn.com@msn.xmpp.domain.name" or "user%
hotmail.com@msn.xmpp.domain.name". However, you can also address these
contacts in short form as as "user@msn.com" or "user@hotmail.com".
10.) If the transport is installed on the same PC as Now IMP, it is possible to configure
Now IMP to automatically load the transport in the background, so that the transport is
automatically started every time the PC running the Now IMP Server is restarted.
This configuration should be attempted only after you have confirmed that the transport
is properly installed and working.
Begin by stopping the currently running transport. This can be done by pressing CTRL-

C or CTRL-BREAK in the console window where the transport is running.
Next, manually edit the NOWIMPS.INI file, and add the following section to this file:
[TransportAutostart-MSN]
Directory=c:\PyMSNt-0.9.3\src
CommandLine=c:\python23\python main.py
The above assumes that "MSN" was specified as the "Transport Name" in Step #1.
Change the "Directory=" parameter to reference the "src" subdirectory in which you
installed the MSN transport.
Change the "CommandLine=" parameter to reference the directory in which Python is
installed (this directory should contain python.exe).
After you save this change to the NOWIMPS.INI file, the Now IMP Server will attempt to
launch the transport in the background within the next 60 seconds. Once the transport
has been launched, the "Transports" list should in the Now IMP configuration should
now show "MSN - Connected", indicating that the transport has successfully connected
to the Now IMP server.

AIM Transport
An AIM transport that is compatible with Now IMP is PyAIMt (Python based AIM
Transport for Jabber).
The web site for PyAIMt is http://pyaim-t.blathersource.org/
The latest version of PyAIMt that has been tested with Now IMP is v0.5.
This version of PyAIMt requires Python v2.3 (http://www.python.org), and Twisted v2.0
(http://www.twistedmatrix.com). These requirements are similar to those of the PyMSNt
transport, and it is not necessary to re-install those components if they are already
installed.
Because web site links can change, we have copied all of the necessary modules into a
single download, http://www.nowimp.com/download/aimtransport.zip. This download
contains all of the necessary requirements to install PyAIMt on a Windows PC
(Windows 2000, XP, 2003).
PyAIMt can be installed on the same machine as the Now IMP server, or it can be
installed on a separate machine.
We recommend following these steps to install PyAIMt:
1.) Define the AIM transport to Now IMP. Go to the "Transports" page of the
configuration dialog. Specify a "Transport Port Number" upon which Now IMP will listen
for connections from external transports. Many transports default to using port 5347,
which is usually a good choice. Enter this value, and press "Apply".
Next click, "Add". Specify "AIM" as the "Transport Name". "Password" can be any
value that you choose.
Under "Domains routed via Transport", enter "aim.com" and press "Add".
"Replace '@' with '%' (transport handles multiple domains)" should NOT be checked.
Press "OK".
The "Transports" list should now show "AIM - NOT connected". (The status will change
to "AIM - connected" once you complete this installation process.)
2.) If it is not already installed, install Python 2.3 by running Python-2.3.5.exe from the
3.) If it is not already installed, install Twisted 2.0 for Python 2.3 by running
Twisted_NoDocs-2.0.1.win32-py2.3.exe from the ZIP download. The default
installation settings are sufficient.
4.) The PyAIMt transport has a bug where the server may end up running at 100%
utilisation after installing the AIM transport, and when this occurs, the only solution to
this problem is to reboot the server.
The version of PyAIMt included in the aimtransport.zip distribution includes a patch to
fix this problem. However, to prevent the possibility of this problem occurring if you

should install an updated version of the PyAIMt transport, we recommed adding the
Python directory to your search path, which will prevent the 100% utilisation problem
from occurring. To add the Python directory to your path, go into the Windows Control
Panel, then select System/Advanced/Environment Variables, and edit the Path variable
to add c:\python23 (or the directory in which Python is installed) to the end of your path.
5.) Install PyAIMt 0.5 by opening PyAIM-t-0.5.zip from the ZIP download. Use a ZIP
utility to extract all of the files from this ZIP to a directory on your PC. Be sure that the
ZIP utility is configured to preserve folder names when extracting (with WinZIP, the
"Use folder names" button should be checked when extracting).
6.) Go to the directory that PyAIMt was extracted to. You will find the PyAIMt files in a
subdirectory beneath that directory named PyAIM-t-0.5. Copy
CONFIG_EXAMPLE.XML over as CONFIG.XML. Edit CONFIG.XML with a text editor
(note that Notepad will not display this file properly, so instead of Notepad, use
Wordpad, which can be accessed from the command line by typing WRITE
CONFIG.XML).
Edit the following sections of CONFIG.XML:
a.) The <jid> value should be aim.xmpp.domain.name, where "xmpp.domain.name" is
the "XMPP Domain Name" value defined on the "Server" page of the Now IMP
configuration dialog. ***IMPORTANT*** The <jid> value should be all lower case, even
if you have used mixed or upper case in the NowIMP configuration.
b.) The <mainServer> value should contain the IP address of the Now IMP server. If
the Now IMP server is running on the same machine, specify 127.0.0.1.
c.) The <port> value should match the "Transport Port Value" defined in Step #1.
d.) The <secret> value should match the "Password" value defined in Step #1.
7.) Change your current directory to the "src" subdirectory of the PyAIM-t-0.5 directory.
Type "c:\python23\python main.py" to start the external transport. (Do not include
quotes, those are just for highlighting in this document.)
Please note that some warning messages will be displayed, specifically "Deprecation
warnings". This is because PyAIMt was written to be compatible with earlier versions
of the Twisted framework. However, our testing shows that it works ok with Twisted
2.0, and we recommend using Twisted 2.0, because that is the version of the Twisted
framework required by the latest version of the MSN transport.
8.) The "Transports" list should in Now IMP should now show "AIM - Connected",
indicating that the transport has successfully connected to the Now IMP server.
You can now configure a user account to register with the transport. The easiest way to
do this for an initial test is using the Tools/Transports option in the Now IMP desktop
client.
Internally, Now IMP will represent AIM contacts with an address of
"user@aim.xmpp.domain.name". However, you can also address these contacts in
short form as as "user@aim.com".

9.) If the transport is installed on the same PC as Now IMP, it is possible to configure
Now IMP to automatically load the transport in the background, so that the transport is
automatically started every time the PC running the Now IMP Server is restarted.
This configuration should be attempted only after you have confirmed that the transport
is properly installed and working.
Begin by stopping the currently running transport. This can be done by pressing CTRL-
C or CTRL-BREAK in the console window where the transport is running.
Next, manually edit the NOWIMPS.INI file, and add the following section to this file:
[TransportAutostart-AIM]
Directory=c:\PyAIM-t-0.5\src
CommandLine=c:\python23\python main.py
The above assumes that "AIM" was specified as the "Transport Name" in Step #1.
Change the "Directory=" parameter to reference the "src" subdirectory in which you
installed the AIM transport.
Change the "CommandLine=" parameter to reference the directory in which Python is
installed (this directory should contain python.exe).
After you save this change to the NOWIMPS.INI file, the Now IMP Server will attempt to
launch the transport in the background within the next 60 seconds. Once the transport
has been launched, the "Transports" list should in the Now IMP configuration should
now show "AIM - Connected", indicating that the transport has successfully connected
to the Now IMP server.

Now IMP Client
The Now IMP Client is an instant messaging desktop client for Windows.
The Now IMP Client runs on Windows 98, Windows ME, Windows 2000, Windows XP
or Windows 2003. It requires Internet Explorer v5.5 or later, 5MB of hard disk space,
and 64MB of RAM.
The installation program, IMPClient.exe, is run to install the Now IMP Client on a PC.
Before using the Now IMP Client, you will need to install the Now IMP Server and
create one or more user accounts on the server.
When the Now IMP Client is run on a workstation, it will login to a user account on the
Now IMP Server.
In most installations, it is desirable to pre-configure the Now IMP Client so that it will
connect to a specific server. Normally, when logging in to the server, a user of the Now
IMP Client needs to specify a user name of username@xmppDomain.name, where
xmppDomain.name is the host name of the Now IMP Server. To avoid user confusion,
it is possible to pre-configure the Now IMP Client for a specific server. To do this,
create a text file named override.xml, and place the following content in that file:
<?xml version="1.0" encoding="UTF-8" ?>
<override>

<fixedserver>xmppDomain.name</fixedserver>
</override>
Place override.xml in the same directory as the IMPClient.exe installation program.

If you are distributing the installation program to your users electronically, we
recommend renaming IMPClient.exe to setup.exe, and then placing setup.exe and
override.xml in a ZIP archive. ZIP archive utilities will then present an install option
which extracts the files from the archive into a temporary directory before running
setup.exe. In this way, setup.exe can find the override.xml file that was included with it
in the ZIP archive.

Another useful option for override.xml is if you want to add a “Sign Up” button to the
client login screen, where this “Sign Up” button links to a URL on your web site for user
registration. To enable this functionality, include the following within the override
section of override.xml:
The following settings will enable a "Sign Up" button on the login screen, where clicking
on the "Sign Up" button loads up a web page:
<showsignup>yes</showsignup>
<websignup>http://your.signup.url/path/here</websignup>
If you want to use the built-in User Self Provisioning, specify a websignup URL of
http://server:port/signup.

Getting Started with the Now IMP Client
After installing the Now IMP Client, select its link from the Windows Start menu.
A login screen will be displayed:
In the Address field, specify username@xmppDomain.name, where username is the

user account defined on the Now IMP Server, and xmppDomain.name is the host name
of the Now IMP Server (see Step 1). (Note if you have pre-configured the Now IMP
Client to connect to a specific server using the override.xml file, it is only necessary to
specify the user account name in this field, e.g., username.)
The Password field should contain the password for the user accuont as defined on
the Now IMP Server.
Check Remember my password if you would like the client to remember your
password so that you do not need to enter it every time you login with the Now IMP
Client.
Check Automatically log in if you would like the client to automatically login to the
server every time it is started.
Press the Login button to attempt to login with the supplied Address and Password.
After you have logged in, the main screen for the Now IMP Client will be displayed.

The main screen for the Now IMP Client would normally display the status of those
individuals who are on your instant messaging contact list. However, since this is the
first login, your account will not yet have any instant messaging contacts configured.

If you are running Windows XP Service Pack 2, the first time that you run the Now IMP
Client, the following warning screen might be displayed:
This warning is normal. The Now IMP Client uses an internal library which identifies
itself as the Instant Messenger for XMPP. If you select Keep Blocking, this will disable
the ability to perform file transfers via the IM client. If you select Unblock, this will allow
file transfers via the IM client. (Note that file transfers are only available between two
computers that are on the same Local Area Network.)
Now you will want to configure your instant messaging contacts. Either select the link
on the main screen that is labeld Add someone to your contact list, or select
Actions/Add a contact from the menu bar.

Adding a Contact
To add a contact, select Actions/Add a contact from the menu bar. The easiest way
to add a contact is to search for another user via the directory.
Searching for a user via the directory is the default option, so press Next.

It is necessary to supply some information to search for a user. Enter this information,
and press Search.

If any search results are returned, highlight that entry and press Next, or simply click on
the entry.
An authorisation request will be sent to the user, asking if it is permissable for you to
add them to your contact list.
The server will not display presence information for another user unless that user has
authorised it. (Note that some mobile IM clients do not accept presence authorisation
requests. Instead, affected clients have configuration parameters that specify whether
authorisation is granted to anyone who asks, or if it is granted only to those that have
been added to the mobile's contact list.)
Press Finish to send the authorisation request.
Please note that the contact will not appear in your contact list until:
• They have authorised your presence request, or it is automatically authorised based
upon settings defined in the mobile IM client.
• The user must be on-line. Contacts will not display in your contact list unless they
are connected to the IM server. (A user's status can be busy or away, and they will
appear in the contact list. However, if they are not connected, they will not appear.)

To be continued...
Additional documentation on the Now IMP Client will be added in future product
releases.
Most of the core functionality of the Now IMP Client is self-explanatory.

Now IMP Server v1.10

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Now IMP Server v1.10

Caricato da

Copyright:

Formati disponibili

Now IMP Server v1.

Now IMP Server v1.10 – http://www.nowimp.com 1

External connectivity is supported with a built-in e-mail gateway, allowing IM users to

Now IMP Server v1.10 – http://www.nowimp.com 2

Now IMP Server v1.10 – http://www.nowimp.com 3

Now IMP Server v1.10 – http://www.nowimp.com 4

Now IMP Server v1.10 – http://www.nowimp.com 5

Now IMP Server v1.10 – http://www.nowimp.com 6

Now IMP Server v1.10 – http://www.nowimp.com 7

To define a new user account, press the Add button.

Now IMP Server v1.10 – http://www.nowimp.com 8

Now IMP Server v1.10 – http://www.nowimp.com 9

Configuring (Most) SonyEricsson Phones

Now IMP Server v1.10 – http://www.nowimp.com 10

Configuring (Most) Nokia Series 60 Phones

Configuring (Most) Nokia Series 40 Phones

Now IMP Server v1.10 – http://www.nowimp.com 11

Configuring (Most) Motorola Phones (V80)

Now IMP Server v1.10 – http://www.nowimp.com 12

Now IMP Server v1.10 – http://www.nowimp.com 13

In the Address field, specify username@xmppDomain.name, where username is the

Now IMP Server v1.10 – http://www.nowimp.com 14

Now IMP Server v1.10 – http://www.nowimp.com 15

Now IMP Server v1.10 – http://www.nowimp.com 16

Now IMP Server v1.10 – http://www.nowimp.com 17

Now IMP Server v1.10 – http://www.nowimp.com 18

Now IMP Server v1.10 – http://www.nowimp.com 19

Now IMP Server v1.10 – http://www.nowimp.com 20

Now IMP Server v1.10 – http://www.nowimp.com 22

Now IMP Server v1.10 – http://www.nowimp.com 23

Now IMP Server v1.10 – http://www.nowimp.com 24

Now IMP Server v1.10 – http://www.nowimp.com 25

Now IMP Server v1.10 – http://www.nowimp.com 26

Now IMP Server v1.10 – http://www.nowimp.com 27

CIR is an acronym for Communications Initiation Request.

Now IMP Server v1.10 – http://www.nowimp.com 28

Now IMP Server v1.10 – http://www.nowimp.com 29

Now IMP Server v1.10 – http://www.nowimp.com 30

Now IMP Server v1.10 – http://www.nowimp.com 31

To define a new user account, press the Add button.

Now IMP Server v1.10 – http://www.nowimp.com 32

Now IMP Server v1.10 – http://www.nowimp.com 33

Now IMP Server v1.10 – http://www.nowimp.com 34

Now IMP Server v1.10 – http://www.nowimp.com 35

Now IMP Server v1.10 – http://www.nowimp.com 36

Now IMP Server v1.10 – http://www.nowimp.com 37

Now IMP Server v1.10 – http://www.nowimp.com 38

Assuming that the user is authorized to issue a provisioning command (valid

Now IMP Server v1.10 – http://www.nowimp.com 39

Now IMP Server v1.10 – http://www.nowimp.com 40

ActiveUsers=Yes causes the <ActiveUserList> element list to be returned. Each active

ActiveRooms=Yes causes the <ActiveConferenceRoomList> element list to be

Now IMP Server v1.10 – http://www.nowimp.com 41

Automated agents are IM user accounts where an application program is configured to

Now IMP Server v1.10 – http://www.nowimp.com 42

Alternative, a PHP version, echo.php, is presented below:

Now IMP Server v1.10 – http://www.nowimp.com 43

Plus one of the following parameters:

Now IMP Server v1.10 – http://www.nowimp.com 44

Now IMP Server v1.10 – http://www.nowimp.com 45

Now IMP Server v1.10 – http://www.nowimp.com 46

Now IMP Server v1.10 – http://www.nowimp.com 47

Now IMP Server v1.10 – http://www.nowimp.com 48

Now IMP Server v1.10 – http://www.nowimp.com 49