Now IMP Server v1.10

8/8/2019 Now IMP Server v1.10

1/73

Now IMP Server v1.10October 14, 2005

Copyright 2005, Now Wireless Ltd.

Table of Contents

Now IMP Server............................................................................................................... 2System Requirements.................................................................................................. 3Basic Configuration...................................................................................................... 4

Basic Configuration Step 1: Define the Server's TCP/IP Ports...............................5Basic Configuration Step 2: Start the Now IMP Server..........................................7Basic Configuration Step 3: Define User Accounts............................................... 8Basic Configuration Step 4a: Connect with a Mobile IM Client............................10

Configuring (Most) SonyEricsson Phones......................................................... 10

Configuring (Most) Nokia Series 60 Phones..................................................... 11Configuring (Most) Nokia Series 40 Phones..................................................... 11Configuring (Most) Motorola Phones (V80)....................................................... 12

Basic Configuration Step 4b: Connect with a Desktop IM Client......................... 14Advanced Configuration............................................................................................. 20

Service Page......................................................................................................... 20Server Page........................................................................................................... 22Options Page......................................................................................................... 24Push Page............................................................................................................. 26

WAP Push over UDP........................................................................................ 27CIR TCP Push Channel (STCP)........................................................................28

WAP Push over SMS........................................................................................ 29SMTP Page........................................................................................................... 30Users Page............................................................................................................ 32SSL/TLS Page....................................................................................................... 34Serial # Page......................................................................................................... 38User Account Provisioning via HTTP..................................................................... 39Automated Agents................................................................................................. 42OTA Provisioning for IMPS.................................................................................... 45

OTA Provisioning for IMPS: SonyEricsson....................................................... 47OTA Provisioning for IMPS: Nokia (and other OMA Compliant Devices).........49

Self-User Provisioning via the Web....................................................................... 51External Transports (AOL, MSN, etc.)............................................................................58

MSN Transport........................................................................................................... 59AIM Transport............................................................................................................ 62

Now IMP Client............................................................................................................... 65Getting Started with the Now IMP Client.................................................................... 67Adding a Contact....................................................................................................... 70To be continued......................................................................................................... 73

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


2/73

Now IMP Server

The Now IMP Server is an Instant Messaging and Presence Server that supports bothmobile phones and PC desktop clients. Users can communicate with each other using

instant messaging technology whether they are connected on the same Local AreaNetwork, or connected through mobile wireless technology.

Mobile phone clients are supported through the Now IMP Server's implementation ofthe Open Mobile Alliance (Wireless Village) Instant Messaging and Presence Services(IMPS) specification. The current release of Now IMP supports the Client ServerProtocol (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 thenew mobile phone models from major manufacturers include an instant messaging andpresence 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 clientsupporting XMPP is bundled with the Now IMP Server to enable instantcommunications. XMPP is an internet standard, published by the Internet EngineeringTask Force (IETF) in RFC 3920 and RFC 3921.

The Now IMP Server supports the Presence, Instant Messaging (IM) and Groupfeatures 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 tosend 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 toMSN 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 instantmessaging network, with SSL/TLS encryption, to enable individuals to interact witheach other across the office or around the world with secure instant messagingtechnology. The alert management interface allows corporate applications to quicklydisseminate time critical information to employees.

The Now IMP Server provides a web-based administrative interface for user accountmaintenance. The administrative interface also supports a programmatic HTTPinterface for user account definition.



3/73

System Requirements

The Now IMP Server runs on Windows 2000, Windows XP or Windows 2003. Memoryrequirements are minimal, and we recommend that you follow the suggested memoryguidelines 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 defineduser account will consume approximately 16KB worth of disk space. Allow sufficientdisk space to facilitate log files.

Running the Now IMP Server requires a dedicated IP address, or at minimum analways connected IP address with a dedicated host name (i.e., dynamic DNS should beused 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 IMPServer. The port number for these connections is user configurable. However, theremust 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 IMPServer. The port number for these connections is user configurable, however bydefault 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 XPor Windows 2003. It requires Internet Explorer v5.5 or later, 5MB of hard disk space,and 64MB of RAM.



4/73

Basic Configuration

To install the Now IMP Server, run the IMPServer.exe program from the distributionmedia (CD or web download).

After installing the Now IMP Server software, run the Now IMP Server configurationutility 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 forconnections from IM clients.

2.) Start the Now IMP Server, and optionally configure the server to automaticallystartup 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 defineduser accounts.

(a)If you have any mobile IM clients, these clients will be configured to connectto 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 connectto the Now IMP Server using the XMPP Protocol. The Now IMP Serverincludes licenses to allow user accounts to connect using the Windowsbased Now IMP Client.



5/73

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 connectionsfrom mobile IM clients, is configured on the Serverpage of the configuration dialog,under the setting HTTP Port Number.

To enable the XMPP Server interface, you must define theXMPP Domain Name. Thisis normally the host name on which the Now IMP Server is installed. When connectingto the Now IMP Server, it is customary to login with an XMPP client by specifying a username [email protected], where xmppDomain.name is the host name ofthe Now IMP Server. (The Now IMP Client can be configured to assume a defaultdomain name when it is installed, so that users need only supply their user name to



6/73

login. This is described in Step 4b.)

Instead of using a host name, a special DNS SRV record can be used. It is similar inconcept to DNS MX records used by e-mail servers. For XMPP clients to properlyconnect to the Now IMP Server using SRV records, the SRV record needs to bedefined 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, whichby default uses TCP/IP Port 5222. It is easy to override this default port assignment ifyou are using SRV records in DNS. However, in cases where you are connecting tothe host by its host name, clients will assume port 5222, and the defaultXMPP PortNumbersetting should not be changed.

Please note that the SSL port number assignments are not available until an SSL/TLScertificate has been generated. This is an advanced topic that is covered later in thisdocument, and is not necessary for a basic configuration.



7/73

Basic Configuration Step 2: Start the Now IMP Server

To start the Now IMP Server, press the Startbutton on the Service page of theconfiguration dialog. Or check the Run as a Service option to install the Now IMPServer as a service which will automatically start every time the PC is rebooted.



8/73

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 theAddbutton.



9/73

The User Name and Passwordfields are required for a user account definition. Theadditional user settings are used only as informational settings. These settings areused primarily to facilitate search functionality, allowing a user to locate another user bysearching on the supplied settings.

For standard user accounts, leave User account is an automated agentunchecked.

Automated agents are IM user accounts where an application program is configured tosend and receive messages for the account, instead of an actual user. Automatedagents are described later in this document on page 42.



10/73

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 Serverwill 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 phonesover 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 befamiliar with some of the internet and/or WAP configuration settings for the mobileoperator to which your phone is subscribed.

In most cases, you can duplicate the settings that are used by the Web/WAP Browseron 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 (AccessPoint Name) that is used for connecting to GPRS/EDGE/UMTS. You may also need toknow 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 inconjunction with a Now.WAP Proxy Server. In this configuration, the Now IMP Server isable to send WAP push messages through the Now.WAP Proxy to alert the mobilephone IM client to new IM messages without requiring polling. The Now IMP Serveralso directly supports a separate TCP/IP push channel, which is used by Nokia IMclients. For more information on Push notification support, refer to the AdvancedConfiguration section of this document.) Finally, you will need to supply the HTTP URLfor connecting to the HTTP Port on the Now IMP Server, as well as a valid user nameand password for an account on the server.

Configuring (Most) SonyEricsson Phones

In most SonyEricsson phones, the IM Client configuration can be found under the MyFriends application on the mobile phone, under the menu option More/Accounts. Theavailable configuration settings are:

Username - This setting should contain the name of the user account defined to theNow IMP Server.

Domain - This setting should be left blank.

Password- This setting should contain the password of the user account defined onthe 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 isrequired unless the HTTP Port Number for the Now IMP Server is the default HTTPport of 80.

Internet Profile - This setting points to an existing internet profile configured on themobile phone. Use an appropriate profile that will facilitate connectivity to the HTTPURL of the Now IMP Server.



11/73

Auto-Login - Set to Yes if you want the IM Client to automatically startup and connectto the IM Server when the mobile phone is powered on.

Allow Connection - This setting allows you to specify whether the IM Client can beused when connected to any network, or if it should only be used when connected toyour 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 Intervalwhich specifies an interval in seconds for polling the IMP Server. Refer to thedocumentation 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 Chator Presence applications. Select Options and then Settings to access the ServerSettings 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 theIM Client for display purposes.

Access Point in Use - This specifies the internet access point (settings profile) thatshould be used for IM client connections. Use an appropriate profile that will facilitateconnectivity to the HTTP URL of the Now IMP Server.

Web Address - This setting should contain the HTTP URL for connecting to the NowIMP Server. For example, http://ip.address:port or http://host.name:port. The :portsuffix is required unless the HTTP Port Number for the Now IMP Server is the defaultHTTP port of 80.

User ID - This setting should contain the name of the user account defined to the NowIMP Server.


Configuring (Most) Nokia Series 40 Phones

For Nokia Series 40 phones, IM settings can be found under by selecting Messagesfrom 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 tomanually copy the settings that are used by the WAP browser on the phone by writingthem on paper, and re-entering them into the IM Client settings.

When you edit the active chat and presence settings, the following settings areincluded:

Chat and presence service name - This is a descriptive name for the server which is



12/73

used only within the IM Client for display purposes.

Homepage - This setting should contain the HTTP URL for connecting to the Now IMPServer. For example, http://ip.address:port or http://host.name:port. The :port suffix isrequired unless the HTTP Port Number for the Now IMP Server is the default HTTPport of 80.

User ID - This setting should contain the name of the user account defined to the NowIMP 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.)


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 withinthe 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 Proxyand Secondary Proxyrefer to the address(es) of the WAP or HTTPproxy server(s) through which you will be connecting. Enter the proxy information ifrequired for your configuration.

Data Bearerspecifies 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 selectedData 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 theAPN.

Configuring (Most) Motorola Phones (V80)

The IM Client on the Motorola V80 is not as sophisticated as the clients on the Nokiaand SonyEricsson phones. It is definitely a first generation effort and is likely toimprove in future phones. One consideration to be aware of with the Motorola V80 isthat it uses a text based version of the IM protocol to communicate with the Now IMPServer. This results in considerable overhead, with typical transactions, includingpolling transactions, transmitting ten times as much data. This phone should definitelyonly be used as an IM client in environments where you have an unlimited GPRS datasubscription plan.

The configuration settings for the IM Client can be found under the IM option of themain menu. Select Offline Settings, and ISP Settings to access the configurationsettings.

GPRS APN- This specifies the Access Point Name (APN) on the GPRS network thatshould be used for establishing IP connectivity for the IM client.



13/73

User name - This setting should contain the name of the user account defined to theNow 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 settingshould 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 leavethis setting blank, or specify /.

Secure Login - This setting specifies whether or not the password for the account isever transmitted in the clear. Both available settings are supported by the Now IMPServer.



14/73

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 PCrunning 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 theAddress field, specify [email protected], where username is theuser account defined on the Now IMP Server, and xmppDomain.name is the host nameof the Now IMP Server (see Step 1).

The Passwordfield should contain the password for the user accuont as defined onthe Now IMP Server.

Check Remember my passwordif you would like the client to remember yourpassword so that you do not need to enter it every time you login with the Now IMPClient.

CheckAutomatically log in if you would like the client to automatically login to theserver every time it is started.

Press the Login button to attempt to login with the suppliedAddress and Password.



15/73

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 thoseindividuals who are on your instant messaging contact list. However, since this is thefirst login, your account will not yet have any instant messaging contacts configured.



16/73

If you are running Windows XP Service Pack 2, the first time that you run the Now IMPClient, the following warning screen might be displayed:

This warning is normal. The Now IMP Client uses an internal library which identifiesitself as the Instant Messenger for XMPP. If you select Keep Blocking, this will disablethe ability to perform file transfers via the IM client. If you select Unblock, this will allowfile transfers via the IM client. (Note that file transfers are only available between twocomputers that are on the same Local Area Network.)

Now you will want to configure your instant messaging contacts. Either select the linkon the main screen that is labeldAdd someone to your contact list, or select

Actions/Add a contactfrom the menu bar.



17/73

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.



18/73

If any search results are returned, highlight that entry and press Next, or simply click onthe entry.

An authorisation request will be sent to the user, asking if it is permissable for you toadd them to your contact list.



19/73

The server will not display presence information for another user unless that user hasauthorised it. (Note that some mobile IM clients do not accept presence authorisationrequests. Instead, affected clients have configuration parameters that specify whetherauthorisation is granted to anyone who asks, or if it is granted only to those that havebeen 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 basedupon settings defined in the mobile IM client.

The user must be on-line. Contacts will not display in your contact list unless theyare connected to the IM server. (A user's status can be busy or away, and they willappear 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



20/73

Advanced Configuration

This section describes the advanced configuration settings available for the Now IMPServer.

Service Page

This page is used to start and stop the Now IMP Server. It is also used to install NowIMP as a Windows service, so that it is automatically started every time the PC isrebooted. 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 tostart 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.



21/73



22/73

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 thecomputer. For configurations where multiple IP addresses are configured on thecomputer, it is possible to configure the Now IMP Server to listen for HTTP connectionson the specified port for only a specific IP address. Select one of the listed IPaddresses, or select all available to have the Now IMP Server listen for connections onany IP address bound to the computer.

HTTP Port Number - This specifies the TCP/IP Port Number on which the Now IMPServer should listen for connections from mobile IM Clients (Wireless Village / OMAIMPS Protocol).

HTTPS Port Number - This specifies the TCP/IP Port Number on which the Now IMPServer 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 beengenerated on the SSL/TLS page of the configuration dialog.

To enable the XMPP Server interface, you must define theXMPP Domain Name. This



23/73

is normally the host name on which the Now IMP Server is installed. When connectingto the Now IMP Server, it is customary to login with an XMPP client by specifying a username [email protected], where xmppDomain.name is the host name ofthe Now IMP Server. (The Now IMP Client can be configured to assume a defaultdomain name when it is installed, so that users need only supply their user name tologin. This is described in Step 4b.)

Instead of using a host name, a special DNS SRV record can be used. It is similar inconcept to DNS MX records used by e-mail servers. For XMPP clients to properlyconnect to the Now IMP Server using SRV records, the SRV record needs to bedefined 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, whichby default uses TCP/IP Port 5222. It is easy to override this default port assignment ifyou are using SRV records in DNS. However, in cases where you are connecting tothe host by its host name, clients will assume port 5222, and the defaultXMPP PortNumbersetting should not be changed.

SSL/TLS can also be used for XMPP Protocol connections. Many IM clients, includingthe Now IMP Client, can negotiate an SSL/TLS connection over the standard XMPPport (using the STARTTLS protocol option). However, some XMPP clients expect touse a separate port for SSL/TLS connections. For those clients, theXMPP SSL PortNumberfield specifies a port on which the server will listen for XMPP connectionsusing SSL. Clients that use a separate port for XMPP SSL/TLS connections willassume 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 administrativeuser to define user accounts on the Now IMP Server.

When the web administrative interface is enabled, it is possible to connect to thisinterface by connecting to the HTTP port of the Now IMP Server, and including /ADMINin the URL (e.g., http://ip.address:port/ADMIN). Web administration functionality can belimited to a specified list of IP addresses by entering one or more IP addresses in theWeb Admin IP Address Restrictions field. The IP address restrictions field cancontain a comma-delimited list of IP addresses, with the ability for wild cards to bespecified (e.g., 192.168.1.*,127.0.0.1).



24/73

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 aclient session is considered inactive. (Note: Even though a session may becomeinactive, provisions are in place to allow a session to automatically reconnect withoutuser intervention.)

Keep Alive Time for Clients - This specifies a time interval, in seconds, that isbroadcast by the server to connected IM Clients. The server informs clients that itexpects to receive a request within this time interval before it may consider a sessioninactive. (Note that while this is similar in concept to Session Timeout, that settingrefers 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 tothe amount of time between polling requests issued by the client.

Minimum Server Poll IntervalThis is the minimum amount of time that is required toelapse between client polling requests of the server. This setting does not control howoften the client polls the server, but rather if the client needs to make multiple requests



25/73

of the server, it will impose a delay between requests.

Idle Polling Response Delay When the server receives a polling request from aclient, and there is no updated information to send to the client, the server can displaythe 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 maybe 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 onlysending polling and keep-alive requests to the server, without sending or receiving anymessages within the "Idle Session Timeout"period, the server will force the client todisconnect from the server.

Created groups are temporary (deleted after participants leave) By default, whena user creates a group (conference room) using the Wireless Village protocol, the groupis 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 areconsidered temporary by default. When a group is temporary, it is automaticallydeleted when all participants leave the discussion. Checking this option causes theserver 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 anyuser is allowed to create a public group (chat room) on the server. A public group canappear in search lists, allowing other users to find and join the group. A non-publicgroup 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 thisoption is unchecked, then users cannot create public groups unless their user name is

listed in the Users allowed to create public groupsfield, which can contain acomma delimited list of users allowed to create public groups. If a user attempts tocreate a public group, but their account is not allowed to do so, the group is created, butthe 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 (nomembers joining, no messages posted) for a configurable number of days, the servercan be configured to automatically delete the group. This setting can help avoidcluttering up the server with inactive groups.



26/73

Push Page

Most mobile phone IM clients will connect to the Now IMP Server via a WAP Proxyserver. 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 toinstall the Now IMP Server in conjunction with a Now.WAP Proxy Server. In thisconfiguration, the Now IMP Server is able to send WAP push messages through theNow.WAP Proxy to alert the mobile phone IM client to new IM messages withoutrequiring polling.

The Now IMP Server also directly supports a separate TCP/IP push channel, which isused 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



27/73

WAP Push over UDP

WAP Push over UDP is used when a mobile phone connects to Now IMP Server via aWAP proxy. This type of connection is commonly used in the IM clients built intoSonyEricsson phones.

To support WAP Push over UDP, the Now IMP Server needs to be able to identify theIP address of the IM client. In a typical configuration, the Now IMP Server will only seethe IP address of the WAP proxy.

To identify the IP address of the IM client, Now IMP must receive the IP address via anHTTP header that is forwarded by the WAP proxy. The Now IMP Server automaticallylooks for X-WAP-Client-IP: and X-Network-Info: headers that are generated by theNow.WAP Proxy. If the Now IMP Server needs to be configured to look at additionalheaders, these headers can be specified as a comma delimited list under the HTTPHeaders for IP Address setting.

Note that in most configurations of a Now IMP Server residing outside of an operatornetwork, having the IP address of the IM Client is not sufficient for allowing WAP Pushover UDP. This is because in most operator configurations, the mobile phones areassigned a private IP address on the operator network, and connect to the externalworld via a Network Address Translation (NAT) router. This private IP address is notaccessible to the outside world.

For the reason detailed above, the Now IMP Server has special hooks to integrate withthe Now.WAP Proxy Server v2.55 or later. When Now IMP connections are proxied viathe WAP protocols by a Now.WAP server, the Now IMP Server and Now.WAP Proxycan cooperate to ensure that WAP Push messages over UDP can be delivered, evenwhen 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: headerin content server requests setting is enabled, and that the domain name and/or IPaddress 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 actuallyreceive MSISDN information via RADIUS, as these settings will also enable theenhanced cooperation between the two servers. (Note: The Now.WAP Proxyserver can be installed outside of the operator network.)



28/73

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 NowIMP Server.

The Now IMP Server will send a notification over this connection whenever an IM eventhas occurred (presence notification, new message, invitation, etc.).

The Now IMP Server uses the same port for this CIR TCP Push Channel as is used forstandard IM client connections. However, the Now IMP Server needs to be able toadvertise this capability to IM clients in order for them to be able to take advantage ofthis capability.

To do this, the Now IMP Server needs to publish the external IP address and portnumber 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 thatis routed via a firewall and/or NAT router. The public IP address for the Now IMPServer should be specified in theAdvertised IP Address field, and the external portnumber for connecting to the HTTP Port Number of the Now IMP Server should bespecified in theAdvertised Portfield.



29/73

WAP Push over SMS

The Now IMP Server can use WAP Push notifications over SMS by routing them via aWAP Push Proxy Gateway (PPG), such as the Now SMS/MMS Gateway. WAP Pushrequests are delivered to the PPG using the Push Access Protocol (PAP).

To send WAP Push notifications via a WAP Push Proxy Gateway, check Enable SMSPush via WAP Push Proxy Gateway (PPG), and supply the settings to connect to theWAP Push Proxy Gateway.

The PPG Server URL is an HTTP URL for connecting to the Push Proxy Gateway. Forthe NowSMS PPG, this URL is generally of the format http://ip.address:port/PAP, whereip.address is the IP address or DNS host name of the NowSMS server, and port is theport number for the web interface. /PAP is a path in the URL that tells NowSMS thatthe request is using the Push Access Protocol (PAP).

User Name and Passwordare 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. WhenNow IMP generates a PAP push request, if a PPG Push Domain value is present, it willbe included in the destination push address. For example, if no PPG Push Domainvalue is present, the destination push address will be of the formatWAPPUSH=99999999/TYPE=PLMN. If a PPG Push Domain of operator.net ispresent, the destination push address will be of the formatWAPPUSH=99999999/[email protected]. Whether or not a PPG PushDomain is required depends on the PPG, and you will need to check with theadministrator 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 foraccounts 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 alsogenerate WAP Push over SMS for presence updates, you must manually add aconfiguration setting to NOWIMPS.INI. Under the [NOWIMPS] header, addPushMessagesOnly=No. When this setting is present, Now IMP will generate WAPPush over SMS messages for both notification of new messages and for updatedpresence information.

IfEnable Direct WAP Push over UDP"is also enabled, and the server has an IPaddress to which to attempt to send a WAP Push over UDP, the server will first attemptto send the WAP Push over UDP. If the client does not respond to the push within atimeout period, a WAP Push over SMS will then be attempted. (The default timeout forWAP Push over UDP is 12 seconds, and can be configured by editing NOWIMPS.INI,and placing UDPPushTimeout=### under the [NOWIMPS] header.)



30/73

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 tosend messages to IM recipients.

To enable this capability, you must configure settings for the SMTP server that is builtinto the Now IMP Server. These settings are configured on the SMTPpage of theconfiguration dialog.

To enable SMTP e-mail connectivity, check Enable SMTP Server. You should thenconfigure a host and domain name for the SMTP server. The Host Name should be ahost name for the server which has been configured for internet DNS. When initiatingoutbound 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-mailmessages to IM user (e.g., user@domain). Internet DNS should be configured with amail exchange (MX) record to route e-mail for this domain to the Now IMP Server (or toanother SMTP server that relays the mail to the Now IMP Server).

The SMTP Port Numberis the port number on which the server will listen for inbound



31/73

SMTP e-mail deliveries. The standard port number for SMTP e-mail is 25. Thisstandard port number should be used unless you are using a specialised SMTP relaythat relays messages to a non-standard port.

IP Address This box contains a list of the of the IP Addresses available on thecomputer. For configurations where multiple IP addresses are configured on the

computer, it is possible to configure the Now IMP Server to listen for SMTP connectionson the specified port for only a specific IP address. Select one of the listed IPaddresses, or select all available to have the Now IMP Server listen for connections onany IP address bound to the computer.

For delivering SMTP e-mail messages sent by IM users to SMTP users, the Now IMPServer will attempt to act as a smart mailer, connecting directly to recipient e-mailservers. If you prefer to use an SMTP relay host in your environment, check the UseSMTP Relay Hostsetting, and specify an IP address or host name for the relay host inthe SMTP Relay Hostfield.

The E-Mail Character Limitsetting specifies the maximum number of characters that

will be extracted from an e-mail message when routing the message from SMTP e-mailto an IM user.



32/73

Users Page

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

To define a new user account, press theAddbutton.



33/73

The User Name and Passwordfields are required for a user account definition. Theadditional user settings are used only as informational settings. These settings areused primarily to facilitate search functionality, allowing a user to locate another user bysearching on the supplied settings.

For standard user accounts, leave User account is an automated agentunchecked.

Automated agents are IM user accounts where an application program is configured tosend and receive messages for the account, instead of an actual user. Automatedagents are described later in this document on page 42.



34/73

SSL/TLS Page

The SSL/TLS page allows you to configure setting related to the use of secureprotocols 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 servercertificate.



35/73

Host Name This should be the host name of the server. XMPP clients will expect thisto match the XMPP Domain Name setting. Wireless Village/OMA IMPS clients willexpect 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 anadministrative 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 thecompany to which this server belongs.

City Name and State or Province Name These provide location information to whichthe server certificate is registered for the company or organisation.

Country Name (2 letter code) This provides additional location information to whichthe server certificate is registered for the company or organisation. Example countrycodes are US for the United States and GB for Great Britain.

Challenge Passwordand Re-enter Password This password provides security forprotecting 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 mostbasic SSL/TLS connections.



36/73

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 Serverpage of theconfiguration dialog.

However, the certificate is only self-signed. This only enables SSL/TLS to be used forencryption purposes, so that a client can connect to the server over an encryptedchannel. A self-signed certificate does not provide any authentication, or verificationthat 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 willsign a certificate to indicate that they trust it. Web browsers are usually configured witha 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 acertificate authority that is trusted by the browser, and a security warning message istypically displayed to the end user. The end user must then decide whether or not toaccept the connection.

The Now IMP Client does not validate certificates, and will simply use the channel forencryption, without presenting a warning.



37/73

However, some IM clients may require that the certificate be signed by a trustedcertificate authority. More information on certificate authorities can be found at theindependent web site, http://www.sslreview.com.

To have your certificate signed by a certificate authority (CA), press the Request orInstall 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 theNowIMP program directory which contains the CSR. This file is in text format and canbe opened with a simple text editor, such as Notepad.

When you receive a signed certificate back from the authority, that certificate should besaved 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.



38/73

Serial # Page

The serial number page is used to enter serialisation information for a purchased copyof the Now IMP Server product.



39/73

User Account Provisioning via HTTP

A web interface is available for provisioning Now IMP user accounts. To enable thisinterface, the Web Admin User Name and Web Admin Passwordsettings on theOptions 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 IPaddresses in theAdmin IP Address Restrictions field. The IP address restrictionsfield can contain a comma-delimited list of IP addresses, with the ability for wild cards tobe specified (e.g., 192.168.1.*,127.0.0.1).

When the web administrative interface is enabled, it is possible to connect to thisinterface by connecting to the HTTP port of the Now IMP Server, and including /ADMINin the URL (e.g., http://ip.address:port/ADMIN).

Additionally, an HTTP-based interface has been added to allow for account provisioningby external applications. This interface is accessed with a URL of "/provision" followedby a series of "HTTP GET" parameters. (The admin username and password must besupplied 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 (validusername/password, and supported IP address for originating the request), the serverwill return a normal HTTP response code of 200 with a MIME content type oftext/plain. The response will start with OK if the request was successful, or ERRORif the request failed.

An example URL for defining a new user is provided below:

http://server:port/provision?AdminAction=Add&UserName=accountname&Password=password&Firstname=First&Lastname=Last&PhoneNumber=%2B447777777777&[email protected]

(Note: In the above example notice that some characters must be URL escaped forHTTP. This includes the space character as %20 and the + character as %2B.)



40/73

If the AgentURL parameter is non-blank when provisioning a user, the user account isprovisioned as an automated agent (see page 42).

AdminAction=Queryis a special case which allows an application to retrieveinformation about defined users.

When the AdminAction=Query command is issued, the server will search for useraccounts that match the supplied parameters. For example, the following command willsearch for any user accounts that have the e-mail address [email protected] with them:

http://server:port/provision?AdminAction=Query&[email protected]

If multiple search parameters are supplied, the server will look for a match on all supliedparameters.

Search parameters can include wildcard characters * (match zero or more characters)and/or ? (match exactly one character). For example, the following command willsearch for all accounts that have an e-mail address associated with them from aparticular 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:

bryce

[email protected]

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 willbe included in UserInfo section of the response:

TRUEhttp://www.now.co.uk/echo.asp



41/73

Additional parameters are available for AdminAction=Query to allow for searches ofactive users and active conference rooms. Including the parameterActiveUsers=Yeswill cause a list of currently active uses to be returned, whileActiveRooms=Yes willcause 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:

bryceXMPPNow IMP

kentIMPS/test.conference.roombrycekent

ActiveUsers=Yes causes the element list to be returned. Each activeuser will be represented by a element. At a minimum, this user informationwill 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 becauseXMPP allows a user to connect simultaneously under multiple resources.)

ActiveRooms=Yes causes the element list to bereturned. Each active conference room will be represented by a element. At a minimum, this conference room information willcontain the ConferenceRoomID, and a list of active users in the conference room.



42/73

Automated Agents

Automated agents are IM user accounts where an application program is configured tosend 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 anautomated agentshould be checked.

Every time the Now IMP server receives an instant message for the agent, it willconnect to an HTTP script to allow the agent to process the message. The URL for thescript that you want to associate with the agent should be defined in theAgent URLparameter of the account.

Now IMP will pass information about the received message to the URL using standardHTTP GET (CGI style) parameters. The from= parameter will contain the sender's IMaddress. 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 abovethat space characters have been replaced with %20.



43/73

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 anHTTP response of the content type text/plain, with the text of the response in the bodyof the HTTP response. (If the response is blank, or returns a different content type, noresponse 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 returnthis HTTP 200 OK response automatically, but if you need to do this manually, thefollowing is a valid empty response (no response sent back to the sender).

HTTP/1.0 200 OKContent-Type: text/plainContent-Length: 0

A good example of a simple interactive agent is an echo agent, which simply echosback any text received from a user.

If you wish to test your system, you can specify an agent URL ofhttp://www.now.co.uk/echo.asp, which is a simple echo agent installed on one ofNow's web servers.

The source forecho.asp is included below:

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

While extremely simplistic, both of the above examples illustrate how an agent scriptcan process received URL parameters, and generate a reply.



44/73

It may also be desirable for an agent to send a message that is not in direct response toa received message. For example, the agent may wish to broadcast information tosubscribers.

To send such a message, the agent must make an HTTP request to the server's HTTPPort Number, as configured on the Serverpage of the configuration dialog.

The request should be an HTTP GET request to http://server:port/agent with thefollowing 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 accountname(s) of the intended recipient(s). If more than onerecipient is desired, separate recipients with either a comma(,) or semicolon (;).

Broadcast Set to allonline to send a message to all instant messagingusers 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 arecurrently connected to the server.Set to alldefinedto send a message to all user accounts

that are defined to the server.This setting can only be used ifAgent can broadcast to allusers is enabled for an account.

Examples:

http://server:port/agent?User=agent&password=agent&text=This+is+a+broadcast+message+to+all+who+have+added+the+agent+to+their+contact+list.&broadcast=allonline

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+message+to+all+connected+users.&systembroadcast=allonline



45/73

OTA Provisioning for IMPS

Most mobile phones that support IMPS have the ability to receive settings for the IMPSclient over-the-air (OTA). This means that the IMPS settings can be sent to the mobilephone 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 Specificationv7.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 issignificantly 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/MMSGateway product.

From the Send XML Settings option of the NowSMS web interface, it is possible tosend an XML document containing IMPS settings to a mobile phone.

Programatically, it is possible to post the XML settings document to the NowSMS serverto request that it be sent out via SMS.

An example HTTP POST of an XML settings document to a NowSMS server looks likethis:

POST /?PhoneNumber=xxxxxxxx&OTA=POST HTTP/1.0Content-Length: yyyyyy(*blank line*)

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 toauthenticate to the NowSMS server:

POST /?PhoneNumber=xxxxxxxx&user=username&password=password&OTA=POST HTTP/1.0Content-Length: yyyyyy(*blank line*)

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



46/73

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 wishto be associated with the message.

For full documentation on the format of the XML settings documents, please refer to theNokia/SonyEricsson OTA Settings Specification v7.1, available for download from theSonyEricsson developer web site (http://www.sonyericsson.com/developer), and theOMA Provisioning Content v1.1 specification, available for download from the OpenMobile Alliance web site (http://www.openmobilealliance.org ). Nokia also has OTAsettings information specific to their mobile phones available from the Nokia developerweb site (http://www.forum.nokia.com).

To help get you started, we have provided basic examples for settings documents foreach of these protocols in the following sections.



47/73

OTA Provisioning for IMPS: SonyEricsson

The following document is an example OTA document for provisioning the IM client ona SonyEricsson phone.

1.0

NowIMP

Internet Profile

1.0

1.1

username

password

http://server:port/

T

Note that in the above settings that there are five fields that you will need to replacewith your settings.

WVSettingsName This text contains a descriptive name for the settings. (Note thatcurrent SonyEricsson phones seem to ignore this value.)

WVRefName This text should contain the name of an existing Internet Profile that hasbeen configured in the mobile phone. Note that it is not possible to provision a newinternet profile at the same time as sending IM settings. If you also need to configurean internet profile to be used with the settings, a separate configuration message mustbe sent with the internet profile settings first. It is possible to remove this statementfrom 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 theserver.

WVSAPURI This text should contain the HTTP URL for connecting to the Now IMPServer.



48/73

If it is necessary to send internet profile settings to the phone, a simple example ispresented below:

To adapt the above example to your environment, several changes are required.

The PARM NAME=PROXYvalue should be changed to reference the IP address ofthe WAP proxy to be used. (We recommend using a conventional WAP proxy via theWSP stack instead of the HTTP stack, as this is the only way to support pushnotifications over IP to these devices.)

The PARM NAME=GPRS_ACCESSPOINTNAMEvalue should be changed toreference the GPRS Access Point Name (APN) of the subscriber's mobile operator.

The lines containing PARM NAME=PPP_AUTHUSERand PPP_AUTHSECRETcan be removed if no username and password is required for connecting to the GPRSAPN. If a username and/or password is required, the values should be edited asappropriate for the connection.

The CHARACTERISTIC TYPE=URLvalue will contain the home page associatedwith the internet profile being created. Although there is not strictly a home pageassociated with this connection, it is a good idea to specify a valid WAP portal entrypage here.

The PARM NAME=NAME value should be changed to contain a descriptive name forthe settings. Note that the value here will correspond to the WVRefName value in anIM Settings message.



49/73

OTA Provisioning for IMPS: Nokia (and other OMA Compliant Devices)

The following document is an example OTA document for provisioning the IM clientusing OMA (Open Mobile Alliance) Provisioning Content, as deployed on Nokia phones.



50/73

To adapt the above example to your environment, a number of changes are required.

There are several places in the settings document whereparm name=NAMEvalue=NowIMPappears. In these cases, NowIMP is a descriptive name that isbeing associated with the settings. This name is displayed in the user interface of themobile 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 appearsas a prefix in the value parameter. This is done to indicate that portions of the settingsare related. While these settings are not displayed anywhere in the phone's userinterface, you may want to change the prefix to one that is specific to your environment.

Theparm name=NAP-ADDRESSvalue should be changed to reference the GPRSAccess Point Name (APN) of the subscriber's mobile operator.

The lines containingparm name=AUTHUSERand AUTHSECRETshould beremoved if no username and password is required for connecting to the GPRS APN. Ifa username and/or password is required, the values should be edited as appropriate for

the connection.Theparm name=PXADDRvalue should be changed to reference the IP address ofthe WAP/HTTP proxy to be used. Note that all Nokia phones that support theseconfiguration parameters are expecting to connect to an HTTP/WAP2 proxy server.Theparm name=PORTNBRvalue should be changed to reference the port numberto be used on the WAP/HTTP proxy.

Theparm name=ADDRvalue should contain the HTTP URL for connecting to theNow IMP Server.

Theparm name=AAUTHNAMEvalue should contain the username of the accounton the Now IMP Server, and theparm name=AAUTHSECRETvalue should contain

the password for that same account.



51/73

Self-User Provisioning via the Web

The Now IMP Server includes an interface for allowing users to self-register with theIMP Server via the web. This interface is designed primarily to help simplify theprocess 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 connectingto 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-upauthorisation code to that e-mail address, and require that the user supply thisauthorisation code in order to complete the registration process.

To enable this interface, it is necessary to manually edit the NOWIMPS.INI file (locatedin the NowIMP program directory), and under the [NOWIMPS] header, addEmailSignupSupported=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 theWEB\SIGNUP subdirectory of the NowIMP installation.

The index.htm template file is used to construct the initial screen that is displayedwhen connecting to the /SIGNUP URL, as displayed below:



52/73

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 totheir e-mail address.



53/73

Thepassword.htm template file is used to generate the Recover Password screen.

After the password has been sent to the e-mail address, thepasswordsent.htmtemplate file is used to generate the confirmation screen.

Under normal conditions, when the e-mail address being entered is not alreadyassociated with a user account on the Now IMP Server, the server will send an e-mailmessage containing 4 character authorisation code. The web interface will display ascreen (authcode.htm template) that prompts for that authorisation code before theuser can complete the registration process.

After entering the authorisation code that was received via e-mail, the user is presentedwith a screen (account.htm template) that allows them to define an account on theNow IMP Server.

7



54/73

The User ID, Password and Confirm Password fields are required. The other fieldsare 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 generatea confirmation message.

The Server URL in the template is read from an entry in the NOWIMPS.INI file. Under



55/73

the [NOWIMPS] header, the setting IMPSServerURL=http://server:port/ is used toconstruct the URL that is displayed.

When the OK or Close (X) button is pressed, the interface will redirect the user to aconfigurable 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 webinterface 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 promptfor 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\USERsubdirectory.

Note that it is not possible for the user to change the e-mail address associated with anaccount. This can only be changed through the administrative interface.



56/73

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



57/73

The text of the e-mail messages generated by the self-user provisioning interface canbe modified through the following settings in the NOWIMPS.INI file, with all settingslocated in the [NOWIMPS] section of the file.

[email protected]

This setting specifies the From address that is used when sending out e-mailmessages 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 anauthorisation code. The default subject is displayed above.

EmailAuthTemplate=Your authorisation code for registering an account with the IMPService is @@AUTHCODE@@

This setting specifies the message text of the e-mail message that is sent out with anauthorisation code. The default text is displayed above. Note that the@@AUTHCODE@@ placeholder will be replaced with the appropriate authorisation

[email protected]

This setting specifies the From address that is used when sending out e-mailmessages 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 alost 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\nThis setting specifies the message text of the e-mail message that is sent out to recovera 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, andthe @@IMPSServerURL@@ placeholder will be replaced with the IMPSServerURLsetting from the NOWIMPS.INI file. \r\n are used to indicate a line break.



58/73

External Transports (AOL, MSN, etc.)

Adding an external transport connector to Now IMP allows users to connect to externalInstant 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 manyexternal transport connectors that were written to work with Jabber, can work with NowIMP. This section of the documentation describes some experience and advice inconfiguring popular connectors.

Please note that each user that wishes to connect to an external Instant Messagingsystem MUST HAVE AN ACCOUNT with the external system.

When using Now IMP, the user can specify their account details with the external IMsystem, so that Now IMP can proxy to the external IM system via an installed externaltransport connector. When the user logs in to Now IMP, Now IMP will also log the userinto the external IM system. The user can then exchange messages with local NowIMP 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 IMPdesktop client.

Once a transport has been registered, Now IMP will automatically connect to theaccount 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 servicethat connects to a public IM network, and we encourage you to review the terms of useof any public IM networks with which you wish to interconnect.



59/73

MSN Transport

An MSN transport that is compatible with Now IMP is PyMSNt (Python based MSNTransport 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) andPyCrypto (http://www.amk.ca/python/code/crypto.html).

Because web site links can change, we have copied all of the necessary modules into asingle download, http://www.nowimp.com/download/msntransport.zip. This downloadcontains 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 theconfiguration dialog. Specify a "Transport Port Number" upon which Now IMP will listenfor 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 anyvalue that you choose.

Under "Domains routed via Transport", enter "hotmail.com" and press "Add". Thenenter "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 willchange 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 theZIP download. The default installation settings are sufficient.

3.) If it is not already installed, install Twisted 2.0 for Python 2.3 by runningTwisted_NoDocs-2.0.1.win32-py2.3.exe from the ZIP download. The defaultinstallation settings are sufficient.

4.) Install PyOpenSSL 0.6 for Python 2.3 by running pyOpenSSL-0.6.win32-py2.3.exefrom 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 theZIP download. The default installation settings are sufficient.



60/73

6.) Install PyMSNt 0.9.3 by opening PyMSNt-0.9.3.zip from the ZIP download. Use aZIP utility to extract all of the files from this ZIP to a directory on your PC. Be sure thatthe 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 thatNotepad will not display this file properly, so instead of Notepad, use Wordpad, whichcan be accessed from the command line by typing WRITE CONFIG.XML).

Edit the following sections of CONFIG.XML:

a.) The value should be msn.xmpp.domain.name, where "xmpp.Domain.Name" isthe "XMPP Domain Name" value defined on the "Server" page of the Now IMPconfiguration dialog. ***IMPORTANT*** The value should be all lower case, evenif you have used mixed or upper case in the NowIMP configuration.

b.) The 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 value should match the "Transport Port Value" defined in Step #1.

d.) The value should match the "Password" value defined in Step #1.

8.) Change your current directory to the "src" subdirectory of the PyMSNt-0.9.3directory.

Type "c:\python23\python main.py" to start the external transport. (Do not includequotes, 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 todo this for an initial test is using the Tools/Transports option in the Now IMP desktopclient.

Be sure to include "@msn.com" or "@hotmail.com" in your MSN user id, asappropriate.

Internally, Now IMP will represent MSN contacts with an address of "user%[email protected]" or "user%[email protected]". However, you can also address thesecontacts in short form as as "[email protected]" or "[email protected]".

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 isautomatically started every time the PC running the Now IMP Server is restarted.

This configuration should be attempted only after you have confirmed that the transportis properly installed and working.

Begin by stopping the currently running transport. This can be done by pressing CTRL-



61/73

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\srcCommandLine=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 youinstalled the MSN transport.

Change the "CommandLine=" parameter to reference the directory in which Python isinstalled (this directory should contain python.exe).

After you save this change to the NOWIMPS.INI file, the Now IMP Server will attempt tolaunch the transport in the background within the next 60 seconds. Once the transporthas been launched, the "Transports" list should in the Now IMP configuration shouldnow show "MSN - Connected", indicating that the transport has successfully connected

to the Now IMP server.



62/73

AIM Transport

An AIM transport that is compatible with Now IMP is PyAIMt (Python based AIMTransport 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 PyMSNttransport, and it is not necessary to re-install those components if they are alreadyinstalled.

Because web site links can change, we have copied all of the necessary modules into asingle download, http://www.nowimp.com/download/aimtransport.zip. This downloadcontains 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 beinstalled 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 theconfiguration dialog. Specify a "Transport Port Number" upon which Now IMP will listenfor 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 anyvalue 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 changeto "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 theZIP download. The default installation settings are sufficient.

3.) If it is not already installed, install Twisted 2.0 for Python 2.3 by runningTwisted_NoDocs-2.0.1.win32-py2.3.exe from the ZIP download. The defaultinstallation 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 tothis problem is to reboot the server.

The version of PyAIMt included in the aimtransport.zip distribution includes a patch tofix this problem. However, to prevent the possibility of this problem occurring if you



63/73

should install an updated version of the PyAIMt transport, we recommed adding thePython directory to your search path, which will prevent the 100% utilisation problemfrom occurring. To add the Python directory to your path, go into the Windows ControlPanel, then select System/Advanced/Environment Variables, and edit the Path variableto 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 ZIPutility to extract all of the files from this ZIP to a directory on your PC. Be sure that theZIP 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 asubdirectory beneath that directory named PyAIM-t-0.5. CopyCONFIG_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, useWordpad, which can be accessed from the command line by typing WRITECONFIG.XML).

Edit the following sections of CONFIG.XML:

a.) The value should be aim.xmpp.domain.name, where "xmpp.domain.name" isthe "XMPP Domain Name" value defined on the "Se

Now IMP Server v1.10

Documents

Transcript of Now IMP Server v1.10