Web PhoneManager

bubblesradiographerServers

Dec 4, 2013 (3 years and 11 months ago)

126 views

EN/LZT 108 5828/11 R2A, 3.0: June 2002
Web PhoneManager
OneBox
Introduction ...................................................................................................2
What Is Web PhoneManager? ........................................................................3
How It Works ....................................................................................................................................6
A Word about Secure Sockets Layer (SSL) and Certificates .................................................................7
Before You Install ...........................................................................................9
Installation of Web PhoneManager .............................................................11
Microsoft IIS 5 Instructions ..............................................................................................................13
Microsoft IIS 4 Instructions ..............................................................................................................14
Setting Up Client Workstations to Use Web PhoneManager .......................15
Appendix A: SSL and Certificate Installation ...............................................17
Microsoft Internet Information Server 5 Instructions .......................................................................18
Microsoft Internet Information Server 4 Instructions .......................................................................23
Changing How Web PhoneManager Acts in SSL .............................................................................27
Appendix B: The Server.txt File ....................................................................28
Index .............................................................................................................30
Edition Information ......................................................................................32
ONLINE BOOK:
Web PhoneManager
2
EN/LZT 108 5828/11 R2A, 3.0: June 2002
Introduction
This online book describes how to implement Web PhoneManager in an organization
and assumes that OneBox version 3.0 or higher has been installed and is running
successfully. It contains the following:
•An overview of Web PhoneManager
•Installation requirements for your Internet Information Server (IIS) and
client workstations
•Instructions for installing and configuring Web PhoneManager
•Instructions for installing and configuring SSL Certificates
To successfully implement Web PhoneManager in an organization, the assistance of the
following individuals, who will constitute the implementation team, is required:
•OneBox server administrator
•Microsoft Windows Server domain administrator
•Microsoft IIS administrator
•MIS/IT support staff
IMPORTANT Verify that each member of the implementation team is given
a copy of this online book several days or weeks before the implementation
of Web PhoneManager.
ONLINE BOOK:
Web PhoneManager
3
EN/LZT 108 5828/11 R2A, 3.0: June 2002
What Is Web PhoneManager?
Web PhoneManager allows subscribers to manage their mailboxes through their
preferred Internet browser, whether or not they are in the office. Everything subscribers
currently set through PhoneManager, either through the telephone or Desktop client,
can be set using Web PhoneManager. This includes features such as call blocking, call
screening, message notification, and message presentation. Subscribers can also record
their names and greetings.
Figure 1 shows the Presentation tab in Web PhoneManager. Eight tabs group
PhoneManager feature settings, providing subscribers with quick and easy access.
If a subscriber should have a question about the software, clicking the Help button
launches a browser-based help system in a new browser window.
NOTE The VIM and SMS screens appear only if those features have been
configured by the telephony server administrator. The Session screen is not
available when using Netscape 4.x, Netscape 6.x or Internet Explorer 4.x.
ONLINE BOOK:
Web PhoneManager
4
EN/LZT 108 5828/11 R2A, 3.0: June 2002
Figure 1. The Web PhoneManager Presentation screen
Help button
Logoff button
ONLINE BOOK:
Web PhoneManager
5
EN/LZT 108 5828/11 R2A, 3.0: June 2002
Web PhoneManager has been optimized for Microsoft Internet Explorer (IE) 5.5 and
6.0; however, it also supports IE 5.0 and Netscape Navigator 4.5, 4.6, 4.7, 6.0, and 6.2.
Older browsers are supported but have feature limitations, as outlined in Table 1. The ￿
indicates that the feature is supported.
Table 1. Browser limitations in Web PhoneManager
Browser Version
Localized Times
in Time Fields
Automatic “graying”
of Disabled options
Ability to Record/
Playback Greetings
IE 6.0
X
X
X
IE 5.5
X
X
X
IE 5.0
X
X
Netscape 6.2
X
Netscape 6.0
X
Netscape 4.X
ONLINE BOOK:
Web PhoneManager
6
EN/LZT 108 5828/11 R2A, 3.0: June 2002
How It Works
Web PhoneManager operates as a virtual directory on the Microsoft IIS server and acts
as a liaison between client workstation and the telephony server. Upon client logon,
Web PhoneManager uses a series of Active Server Pages and HTML forms to gather
subscriber mailbox information from the telephony server. This data is then relayed
back to the client and a connection through the IIS server is established. The client can
then modify and save settings on the telephony server.
If security is a priority, these transactions can be encrypted by using Secure Sockets
Layer (SSL) on the IIS server.
Telephony ServerIIS Server
Clients
ONLINE BOOK:
Web PhoneManager
7
EN/LZT 108 5828/11 R2A, 3.0: June 2002
A Word about Secure Sockets Layer (SSL) and Certificates
The Internet has become a vast marketplace for global goods and services, as well as a
vital tool for communication. Because information traveling over the Internet actually
passes through many computers along the way, the opportunity exists for someone to
intercept confidential information.
Microsoft Internet Information Server offers a protocol for providing data security
layered between the service protocols HTTP and TCP/IP. This security protocol, called
Secure Sockets Layer (SSL), was designed by Netscape Communications Corporation to
provide data encryption, server authentication, message integrity, and optional client
authentication for a TCP/IP connection. To access a web page secured by SSL, the
HTTPS protocol is used rather than HTTP.
SSL provides a security “handshake” that is used to initiate the TCP/IP connection. This
handshake results in the client and server agreeing on the level of security they will use
and fulfills any authentication requirements for the connection. Thereafter, SSL’s only
role is to encrypt and decrypt the bit stream of the application protocol being used.
This means that all the information in both the HTTPS request and the HTTPS response
are fully encrypted, including the URL the client is requesting, any submitted form
contents, any HTTPS access authorization information (user names and passwords),
and all the data returned from the server to the client. To complete the handshake, the
web server must have a certificate installed. Web PhoneManager does not include a
certificate.
ONLINE BOOK:
Web PhoneManager
8
EN/LZT 108 5828/11 R2A, 3.0: June 2002
Acquiring a Certificate
To use SSL, a certificate must be purchased from (and renewed annually by) a
Certificate Authority (CA), which is the digital world’s equivalent of a passport office. It
issues digital certificates and validates the holder’s identity and authority. A CA embeds
an individual’s or an organization’s public key along with other identifying information
into each digital certificate and then cryptographically “signs” it as a tamper-proof seal,
verifying the integrity of the data within the certificate and validating its use.
You can purchase certificates from a CA such as VeriSign Inc. (www.verisign.com
),
Thawte Digital Certificate Services (www.thawte.com
), or Baltimore UniCERT
Certificate Authority (www.baltimore.ie/unicert
). For a more complete list of CAs,
follow this link: https://certs.netscape.com/server.html
Instructions for acquiring a certificate and installing it on your server are found in
“Appendix A: SSL and Certificate Installation” on page17.
ONLINE BOOK:
Web PhoneManager
9
EN/LZT 108 5828/11 R2A, 3.0: June 2002
Before You Install
This section lists the installation requirements for successfully installing Web
PhoneManager. Be sure to review and meet these requirements before continuing with
the other procedures discussed in this document.
Server Installation Requirements
Be sure to review the following installation requirements to ensure that the correct files,
versions, and Service Packs are installed.
Microsoft Internet Information Server (IIS) Requirements
•Microsoft IIS 4.0 running on Microsoft Windows NT Server 4.0 with Service Pack 6a
or
•Microsoft IIS 5.0 running on Microsoft Windows 2000 Server with Service Pack 2
•World Wide Web Publishing Server (World Wide Web Service) installed
•Active Server Pages Extension installed
•To ensure web security using SSL, a certificate purchased from a Certificate Authority
OneBox Server Requirements
•OneBox 3.0
•Connection to the local area network (LAN)
•Installation of the correct network protocols to communicate with the IIS server
ONLINE BOOK:
Web PhoneManager
10
EN/LZT 108 5828/11 R2A, 3.0: June 2002
Workstation Installation Requirements
Subscribers should have the following to use Web PhoneManager. If a subscriber uses a
browser other than IE 5.0, 5.5, 6.0, or 6.2, let him know what features may not be
available, as outlined in Table 1. Subscribers also need to be advised of settings in the
“Setting Up Client Workstations to Use Web PhoneManager” section.
Workstation Client
•Microsoft Windows NT Workstation 4.0 (Service Pack 6a) or Microsoft Windows
2000 Professional or Microsoft Windows 95, 98, Me, or XP
•Microsoft Internet Explorer 5.0 or 5.5, or 6.0
•Netscape Navigator 4.5, 4.6, 4.7, 6.0, or 6.2
•Connection to the local area network (LAN) or to the World Wide Web via an
Internet Service Provider (ISP)
The ability to record or review greetings requires either a workstation multimedia
system (speakers, soundcard, and microphone) or a telephone.
IMPORTANT To use a telephone for playback and recording purposes in Web
PhoneManager, subscribers must have an additional line to the one used for
Internet access. That line must be able to receive incoming calls, and its telephone
number must be accessible via the telephony server’s dialing plan.
ONLINE BOOK:
Web PhoneManager
11
EN/LZT 108 5828/11 R2A, 3.0: June 2002
Installation of Web PhoneManager
This section explains how to install Web PhoneManager software on the Microsoft IIS
server.

To install Web PhoneManager on the IIS Server:
1.Log on to the IIS platform with an account that has Administrator privileges on the
Windows Server domain.
2.Insert the OneBox DVD into the DVD drive, and run Setup.exe from the \Unified
Messaging\WPM folder.
As the installation routine begins, you will be asked to accept the Web
PhoneManager license agreement.
3.Please read the agreement and click Yes to move to the next screen.
The installation routine will verify SSL on your IIS server.
4.Choose one, based on your installation.
If…
Then…
You do not have SSL running
At the warning that your data will be
transmitted without security, click Next.
You have a certificate installed
and are running SSL
Select a level of security. Choose “not
using SSL,” “only pages where passwords
are entered are secured,” or “All pages are
secured.” Click Next.
ONLINE BOOK:
Web PhoneManager
12
EN/LZT 108 5828/11 R2A, 3.0: June 2002
5.Choose the location to which your program files will be installed. To accept the
default (C:\Program Files\Web PhoneManager), click Next.
6.Choose the name for the Web PhoneManager virtual directory. This will be the
Internet address for Web PhoneManager. If you choose the default (WPM), the URL
for Web PhoneManager would be http://yourdomainname/wpm. To accept the
default, click Next.
7.Click Yes to finish the installation, or click Back if the information displayed is not
correct.
After you have clicked Yes, the program files will be copied to their destination and
the system will be configured for Web PhoneManager.
8.Click Restart my Computer now.
The installation of Web PhoneManager is complete. There are settings within IIS that
need to be examined and possibly changed, as described next.
ONLINE BOOK:
Web PhoneManager
13
EN/LZT 108 5828/11 R2A, 3.0: June 2002
Microsoft IIS 5 Instructions
These steps will ensure proper operation of Web PhoneManager. Steps 7 and 8 are
optional and are recommended to improve IIS performance.

To change Web PhoneManager properties on the IIS 5 server:
1.Log on to the IIS 5 server with an account that has Administrator privileges on the
Windows server domain.
2.From the Start menu, point to Programs, then to Administrative Tools, and click
Internet Services Manager.
3.In the Tree pane, expand yourservername and expand Default Web Site.
4.Right-click WPM and select Properties.
5.Click Configuration and choose the App Debugging tab.
6.Clear the Enable ASP client-side script debugging box. You may clear the
Enable ASP server-side script debugging box as well.
7.Optionally, select Send text error message to client.
8.Optionally, click the Virtual directory tab, and choose Medium (pooled) for
the Application Protection setting.
9.Click Apply, then click OK and OK again.
10.Close Internet Services Manager.
ONLINE BOOK:
Web PhoneManager
14
EN/LZT 108 5828/11 R2A, 3.0: June 2002
Microsoft IIS 4 Instructions
These steps will ensure proper operation of Web PhoneManager. Step 7 is optional and
is recommended to improve IIS performance.

To change Web PhoneManager properties on the IIS 4 server:
1.Log on to the IIS 4 server with an account that has Administrator privileges on the
Windows server domain.
2.From the Start menu, point to Programs, Windows NT 4.0 Option Pack, then to
Microsoft Internet Information Services and click Internet Services Manager.
3.In the Tree pane, expand yourservername and expand Default Web Site.
4.Right-click WPM and select Properties.
5.Select the Virtual directory tab, click Configuration, and choose the App
Debugging tab.
6.Clear the Enable ASP client-side script debugging box. You may clear the
Enable ASP server-side script debugging box as well.
7.Optionally, select Send text error message to client.
8.Click Apply, then click OK and OK again.
9.Close Internet Services Manager.
ONLINE BOOK:
Web PhoneManager
15
EN/LZT 108 5828/11 R2A, 3.0: June 2002
Setting Up Client Workstations to Use Web PhoneManager
Generally, Web PhoneManager requires little setup on client workstations. However,
you should provide your subscribers with the following information to ensure they can
use it successfully.
•Inform subscribers of the web address they should use to access Web PhoneManager
(also called the virtual directory). This is typically http://yourdomainname/wpm.
•Require subscribers to enable the options listed in Table 2.
Table 2. Required browser settings
Browser Version
Settings
IE
•Download signed ActiveX controls
•Run ActiveX controls and plug-ins
•Script ActiveX controls marked safe for scripting
•Allow per-session cookies
•Access data source across domains (if user is in different
domain)
•Active scripting
•Scripting of Java applets
Netscape
•Enable Java
•Enable Java Script for Navigator
•Enable all cookies
ONLINE BOOK:
Web PhoneManager
16
EN/LZT 108 5828/11 R2A, 3.0: June 2002
•Subscribers do not need to have Unified Messaging installed on their workstations to
use Web PhoneManager. They can access it from anywhere, in the office, at home,
and on the road. However, if a subscriber does have Unified Messaging installed on
his workstation, it must be version 3.0 to access Web PhoneManager from that
location.
•On its initial use, Web PhoneManager downloads any necessary components to the
hard drive. If subscribers access Web PhoneManager from a Windows Server
platform, their network logon must have local administrative rights for Web
PhoneManager to execute the required system modifications.
ONLINE BOOK:
Web PhoneManager
17
EN/LZT 108 5828/11 R2A, 3.0: June 2002
Appendix A: SSL and Certificate Installation
A number of tasks must be accomplished to use the Secure Sockets Layer (SSL) with
certificates. You must complete a certificate signing request (CSR), submit the CSR to a
Certificate Signing Authority (CA), apply the certificate to the IIS server, and configure a
directory to require SSL. Steps for those tasks are provided for both IIS 5 and 4.
ONLINE BOOK:
Web PhoneManager
18
EN/LZT 108 5828/11 R2A, 3.0: June 2002
Microsoft Internet Information Server 5 Instructions
CSR Generation
This procedure will create a file that is used to request the certificate.

To generate a CSR:
1.Log on the IIS 5 server with an account that has Administrator privileges on the
Windows server domain.
2.From the Start menu, point to Programs, then to Administrative Tools, and click
Internet Services Manager.
3.In the Tree pane, expand yourservername and locate Default Web Site.
4.Right-click Default Web Site and select Properties.
5.Click the Directory Security tab, then click Server Certificate in the Secure
communications section. The IIS Certificate Wizard starts.
6.Click Next in response to the Welcome message.
7.Select Create a new certificate and click Next.
8.Select Prepare the request now, but send it in later and click Next.
ONLINE BOOK:
Web PhoneManager
19
EN/LZT 108 5828/11 R2A, 3.0: June 2002
9.Type in the Name for your new certificate, select the appropriate bit length, and
click Next.
NOTEYour bit length cannot be larger than 1024 because it will not be
accepted by any browser. If you are outside the US, you may want to
generate a Server Gated Crypto certificate.
10.Type your Organization name and Organizational Unit name, then click Next.
IMPORTANTEnter what appears on your official company domain
registration documents. However, certain characters must be excluded, or
your certificate may not work.
Do not use any of these characters: ! @ # $ % ^ * () ~ ? > < & / \
11.Type the exact name of the host you will secure in Common Name (your registered
domain name, in most cases) and click Next.
12.Specify your site’s location in the Country/region, State/province, and City/locality
boxes. These fields may not contain abbreviations. Click Next.
13.Specify your company’s information in the Full name, E-mail address, and Phone
number boxes, then click Next.
14.Type the path and file name for the certificate request and click Next.
NOTEMake your path easy to remember, as you will open this file later.
ONLINE BOOK:
Web PhoneManager
20
EN/LZT 108 5828/11 R2A, 3.0: June 2002
15.Review your request details.
16.Click Finish.
IMPORTANTThe file you created in the Certificate Wizard is called your private
key. If you lose or cannot access a private key, you cannot use the certificate issued
to you. Back up your private key and make note of the password. If you lose the file
or the password, you will need to buy a new certificate.
17.Open the Certificates snap-in in the MMC and click the Requests folder.
Right-click the file in the details pane, point to All Tasks and select Export. The
Certificate Export Wizard opens.
18.At the welcome message, click Next.
19.Select Yes, export the private key and click Next.
20.Select Enable strong protection in the Personal Information Exchange section
and click Next.
21.Type and confirm your password. Click Next.
If your information is…
Then…
Correct
Click Next.
Incorrect
Click Back until you reach the information that
needs correction.
Fix the information and click Next until you return
to this screen.
ONLINE BOOK:
Web PhoneManager
21
EN/LZT 108 5828/11 R2A, 3.0: June 2002
22.Browse to the path of the private key file you created in the CSR. Select the file and
click Next.
23.Click Finish.
CSR Submission
Start the certificate request process with the CSA of your choice and follow their
instructions. Upon receipt of the certificate, follow the instructions below.
Certificate Installation
Follow this procedure to install the certificate your received from the CA on the IIS 5
server.

To install the certificate on the IIS 5 server:
1.From the Start menu, point to Programs, then to Administrative Tools, and click
Internet Services Manager.
2.In the Tree pane, expand yourservername and locate Default Web Site.
3.Right-click Default Web Site and select Properties.
4.Click the Directory Security tab, and click Server Certificate in the Secure
communications section. The IIS Certificate Wizard starts.
5.At the welcome message, click Next.
6.Select Process the pending request and install the certificate and click
Next.
ONLINE BOOK:
Web PhoneManager
22
EN/LZT 108 5828/11 R2A, 3.0: June 2002
7.Browse to the location of the certificate file sent from the CSA. Select the file and
click Next.
8.Confirm the details of the certificate and click Next.
9.Click Finish. The wizard closes.
10.Select the Web Site tab.
11.Enter the SSL Port you will be using.
12.Click Apply and OK.
You can now use SSL on Web PhoneManager.
ONLINE BOOK:
Web PhoneManager
23
EN/LZT 108 5828/11 R2A, 3.0: June 2002
Microsoft Internet Information Server 4 Instructions
CSR Generation
This procedure will create a file that is used to request the certificate.

To generate the CSR:
1.Log on the IIS 4 server with an account that has Administrator privileges on the
Windows server domain.
2.From the Start menu, point to Programs, Windows NT 4.0 Option Pack, then to
Microsoft Internet Information Server and click Internet Service Manager.
3.In the Tree pane, expand yourservername and locate Default Web Site.
4.Right-click Default Web Site and select Properties.
5.Click the Directory Security tab, and click Key Manager in the Secure
communications section.
6.Select WWW.
7.From the Key menu, select Create New Key.
8.Select Put the request in a file that you will send to an authority.
9.Enter the path and filename for the certificate request and click Next.
10.Type the Name for your new certificate.
ONLINE BOOK:
Web PhoneManager
24
EN/LZT 108 5828/11 R2A, 3.0: June 2002
11.Type and confirm your password.
IMPORTANTMake note of this password, as it is required to use the
certificate. If you lose this password, you will be required to purchase a
new certificate.
12.Select the appropriate bit length, and click Next.
NOTEYour bit length cannot be larger than 1024 because it will not be
accepted by any browser. If you are outside the US, you may want to
generate a Server Gated Crypto certificate.
13.Type your Organization name and Organizational Unit name.
IMPORTANTEnter what appears on your official company domain registration
documents. However, certain characters must be excluded, or your
certificate may not work.
Do not use any of these characters: ! @ # $ % ^ * ( ) ~ ? > < & / \
14.Type the exact name of the host you will use to secure in Common Name. In most
cases, this will be your registered domain name. Click Next.
15.Specify your site’s location in the Country/Region, State/Province, and City/Locality
boxes. These fields may not contain abbreviations. Click Next.
16.Specify your company’s information in the Name, E-mail address, and Phone
number boxes, then click Next.
ONLINE BOOK:
Web PhoneManager
25
EN/LZT 108 5828/11 R2A, 3.0: June 2002
17.Click Finish.
IMPORTANT The file you created in the Certificate Wizard is called your private
key. If you lose or cannot access a private key, you cannot use the certificate issued
to you. Back up your private key and make a note of the password. If you lose the
file or the password, you will need to buy a new certificate.
CSR Submission
Start the certificate request process with the CA of your choice and follow their
instructions. Upon receipt of the certificate, follow the instructions below.
Certificate Installation
Follow this procedure to install the certificate your received from the CA on the IIS 4
server.

To Install the SSL Certificate on the IIS 4 server:
1.From the Start menu, point to Programs, Windows NT 4.0 Option Pack, then to
Microsoft Internet Information Services and click Internet Services Manager.
2.In the Tree pane, expand yourservername and locate Default Web Site.
3.Right-click Default Web Site and select Properties.
ONLINE BOOK:
Web PhoneManager
26
EN/LZT 108 5828/11 R2A, 3.0: June 2002
4.Click the Directory Security tab, and click Key Manager in the Secure
communications section.
5.Click the key created in the CSR.
6.From the Key menu, select Install Key Certificate.
7.Browse to the location of the certificate sent from the CA and select it.
8.Type the certificate password in the Password box and click OK.
9.At the Server Bindings dialog box, click OK.
You can now use SSL on Web PhoneManager.
ONLINE BOOK:
Web PhoneManager
27
EN/LZT 108 5828/11 R2A, 3.0: June 2002
Changing How Web PhoneManager Acts in SSL
If needed, the Web PhoneManager SSL mode can be modified after Web
PhoneManager’s installation. Follow the instructions below.

To modify the SSL mode:
1.Locate the SSLMode.inc file and open it in Notepad
.
2.Save your changes.
3.Close Notepad.
If you want to change the SSL mode to…
Then change the “SSL_mode =” to…
No SSL
SSL_mode = 0
SSL for only pages containing passwords
SSL_mode = 1
SSL for all pages
SSL_mode = 2
ONLINE BOOK:
Web PhoneManager
28
EN/LZT 108 5828/11 R2A, 3.0: June 2002
Appendix B: The Server.txt File
It’s 3 A.M. and a subscriber is in a Frankfurt hotel room trying desperately to log on the
telephony server via Web PhoneManager. She forgot to record new mailbox greetings for
the trip—not to mention changing notification options and daily reminders—and is looking
forward to using the new tool. Your Web PhoneManager Logon screen has been reached
and the mailbox and password entered with surprisingly little difficulty for the weary
traveler. But there looms the empty Server Name field. Thinking she is more likely to
remember your extension number than the server name, you receive “what’s-our-server-
name” call number forty-eight.
To avoid this and similar situations, Web PhoneManager has the ability to provide a list
of server names in the Logon screen. Simply follow the instructions below to activate
this helpful option.

To provide a list of server names:
1.With write access to the Web PhoneManager virtual directory, create a new text file
named SERVERS.TXT.
2.Open SERVERS.TXT in a text editor such as Notepad.
3.Enter the server name or IP address, then exit and save your changes.
If multiple servers exist, enter each on a separate line.
NOTEThe server names depend upon your protocols. Entries of different
protocol types such as DNS, TCP/IP, and Named Pipes can exist in the same file.
ONLINE BOOK:
Web PhoneManager
29
EN/LZT 108 5828/11 R2A, 3.0: June 2002
With SERVERS.TXT in place, Web PhoneManager will present the following Server
Name options.
If SERVERS.TXT...
Then the Server Name field will display...
Contains one server name or address
A read-only field containing this entry
Contains multiple server names or
addresses
A drop-down menu containing all entries
Does not exist or is empty
A blank text box
ONLINE BOOK:
Web PhoneManager
30
EN/LZT 108 5828/11 R2A, 3.0: June 2002
Index
A
Active Server Page (ASP) 6
C
Certificate Authority (CA) 8, 21, 25
Certificate signing request (CSR)
generating under IIS 4 23–25
generating under IIS 5 18–21
installing under IIS 4 25–26
installing under IIS 5 21–22
submitting for IIS 4 25
submitting for IIS 5 21
Certificate, SSL 7, 11
bit length 19, 24
installing 17–26
obtaining 8
reserved characters 19, 24
G
Generating a certificate signing request (CSR)
Internet Information Server 4 23–25
Internet Information Server 5 18–21
I
Implementation team members 2
Installing a certificate signing request (CSR)
Internet Information Server 4 25–26
Internet Information Server 5 21–22
Internet Explorer
compatibility with Web
PhoneManager 5
required settings 15
Internet Information Server (IIS) 6
installing Web PhoneManager on server platform 11–14
See also Requirements
Internet Information Server 4
generating a certificate signing request (CSR) 23–25
installing a certificate signing request (CSR) 25–26
installing Web PhoneManager 14
submitting a certificate signing request (CSR) 25
Internet Information Server 5
generating a certificate signing
request (CSR) 18–21
installing a certificate signing request (CSR) 21–22
installing Web PhoneManager 13
submitting a certificate signing
request (CSR) 21
M
Microsoft Internet Explorer
compatibility with Web
PhoneManager 5
required settings 15
N
Netscape Navigator
compatibility with Web
PhoneManager 5
required settings 15
P
Presentation screen 4
Private key 20, 25
Protocols
HTTP 7
HTTPS 7
TCP/IP 7
ONLINE BOOK:
Web PhoneManager
31
EN/LZT 108 5828/11 R2A, 3.0: June 2002
R
Requirements
browser settings 15
client workstation 15–16
IIS 9
OneBox 9
Reserved characters 19, 24 S
Secure Sockets Layer (SSL) 6
certificate 11
changing mode for Web
PhoneManager 27
described 7
installing 17–26
obtaining certificate 8
Server Name field, populating 28–29
Servers.txt file, creating 28–29
Submitting a certificate signing request (CSR)
Internet Information Server 4 25
Internet Information Server 5 21
T
Transmission Control Protocol / Internet Protocol (TCP/IP) 7 W
Web PhoneManager 3
changing SSL mode 27
described 6
implementation team members 2
installing on IIS server 11–14
populating Server Name field 28–29
Presentation screen 4
virtual directory 12, 15
ONLINE BOOK:
Web PhoneManager
32
EN/LZT 108 5828/11 R2A, 3.0: June 2002
Edition Information
This is the first edition of the Web PhoneManager Online Book.
Copyright
Copyright © Ericsson Enterprise AB 1998-2002
All rights reserved.
Disclaimer
Ericsson Enterprise AB, reserves the right to revise this publication and to make changes from time to time in the
content hereof without obligation of Ericsson Enterprise AB, to notify any person of such revisions or changes.
Trademarks
Ericsson and OneBox are registered trademarks of Ericsson Enterprise AB. Web PhoneManager is a licensed trademark
of Captaris, Inc. Microsoft and Windows are registered trademarks, and Windows 95, Windows 98, Windows Me,
Windows NT, and Windows 2000 are trademarks of Microsoft Corporation.
All other products, brand names, or companies mentioned in this document may be trademarks or registered
trademarks of their respective companies.
Ericsson Enterprise AB
S-131 89 Stockholm, Sweden
Telephone +46 8 422 0000, Telefax +46 8 422 1010
http://www.ericsson.com