Config Note 3200 - Avaya



For Octel

Message Servers

Configuration Note 3210 (1/03)

OctelAccess™ Server 4.0 for

Octel® Message Servers

1.0 OctelAccess Overview

Visual desktop messaging solutions and Octel Software Solutions all require an OctelAccess server and software in their architectural configurations. With this architecture, the message server becomes an applications system that can provide Octel messaging capabilities to a personal computer or an Octel Software Solution.

Software that leverages the OctelAccess software is connected to a data network by the OctelAccess Server. Applications can either run on an OctelAccess Server or on a separate Applications Server. These applications take advantage of the functionality and information available on both the message server and the customer’s data network. These applications include Visual Messenger( and messenger( (which make up the Visual Desktop Messaging Suite), and a variety of applications created using the OctelDesigner( Application Development Environment (ADE), called Octel Software Solutions. This includes mobilePath(.

OctelAccess server software creates the path between a message server and a data network, allowing the Windows-based Visual Messenger client application, for example, to have access to the message server’s voice and fax messages from a computer. The communication link between an OctelAccess Server and the message server is TCP. The communication link between the OctelAccess Server software and the client software is TCP/IP, on a specific TCP port.

Additional information regarding OctelAccess license keys, Avaya message server configuration information where Visual Desktop Messaging or any other Octel Software Solution will be installed, please read the OctelAccess technical information, which can be found at:

2.0 OctelAccess Server

All Octel Software Solutions and the Visual Desktop Messaging Suite require a customer-provided Windows 2000 server. This 2000 server must be configured as a standalone server dedicated to Avaya applications. This means that this server can not hold any of the FSMO Roles in Active Directory. It can only be used to execute those functions directly required by the application such as an Octel Software Solution (including mobilePath), and Visual Messenger. No programs or system extensions can be loaded into memory or run on this server other than those components of the Microsoft 2000 Server operating system or those provided by Avaya.

2.1 OctelAccess Server specifications

OCTELACCESS SERVER SOFTWARE RUNS ON MICROSOFT( WINDOWS 2000 SERVER (WITH AT LEAST SERVICE PACK 2). MICROSOFT’S INTERNET INFORMATION SERVER (IIS) 5.0 AND ITS FTP PUBLISHING SERVICE MUST BE INSTALLED AND RUNNING ON THIS SERVER. THESE ARE INCLUDED IN WINDOWS 2000 SERVER WHICH ALSO INCLUDES: SITE SERVER EXPRESS AND POSTING ACCEPTOR. TCP/IP MUST BE INSTALLED AND CONFIGURED ON THIS SERVER.

Verify that the server hardware is certified for use with Microsoft Windows 2000 and is listed on the hardware compatibility list maintained at the following URL: .

The following hardware is the current minimum required specification for the OctelAccess server. The combinations of applications that this server can support are defined in the next section. The server is specified to be able to grow and add additional applications and client access users. Product/application-specific configuration notes may define additional requirements for the OctelAccess server if the application is to be loaded onto this server directly. Multiple processor configurations may be advantageous when using a single Windows 2000 server to host multiple OAS installations. Up to eight OctelAccess Server gateways, each connected to a single Octel Message Server, may be installed on a single Windows 2000 server. However, any multiple message server configuration is subject (in aggregate) to identical limitations of a single message server configuration.

1. Pentium II 450 Mhz processor (Or faster, multiple processor is OK

2. 512 Megabytes SDRAM (Expandable to 2 Gigabytes)

3. 256 Kilobyte L2 cache

4. 4 Gigabyte Free SCSI Hard Drive Space,

5. CD ROM Drive for installation

6. Display standard SVGA resolution 800x600x256 colors

7. V.90 modem preferred, V.34bis Modem minimum and pcAnywhere( 10.5 (for remote support). Direct dial access to the modem is required for support.

OctelAccess Servers should be configured with NTFS (NT File System) instead of FAT (File Allocation Table). NTFS provides faster disk access, security and better disk utilization on 1Gb and larger disk drives. Disk storage requirements are based on the amount of space required to store trace logs during fault isolation and normal status collection.

pcAnywhere Version 10.5 or higher for Windows 2000 must be installed if remote access for support is required.

The optimal and recommended configuration for the OctelAccess Server includes a single NIC (Network Interface Card) configured for 10 MB, half-duplex. Prior to installing Visual Messenger, make sure that you can ping your OA server by name from your user’s desktop PCs. This provides a good troubleshooting test as well.

NOTE: Avaya will not support an OctelAccess Server with the routing information protocol (RIP) enabled.

2.2 Application SERVER

WHILE AN OCTELACCESS SERVER CAN SUPPORT MULTIPLE APPLICATIONS, INCLUDING: OCTEL SOFTWARE SOLUTIONS, MOBILEPATH, VISUAL MESSENGER, THE CUSTOMER REQUIREMENTS FOR THE NUMBER OF CLIENT ACCESS USERS AND THE NUMBER OF APPLICATION LICENSES MAY EXCEED THE PERFORMANCE CAPABILITIES OF THE OCTELACCESS SERVER AT SOME POINT. WHEN AN APPLICATION OR APPLICATIONS REQUIRES A SEPARATE WINDOWS 2000 SERVER ON WHICH TO RUN, THE ADDITIONAL WINDOWS 2000 SERVER(S) IS CALLED AN “APPLICATION SERVER”. IT MAY HAVE THE SAME CONFIGURATION REQUIREMENTS AS AN OCTELACCESS SERVER, OR THEY MAY BE SPECIFIED DIFFERENTLY DEPENDING ON THE APPLICATION. WWW.MESSENGER WILL ALWAYS REQUIRE A SEPARATE, DEDICATED WINDOWS NT 4.0 WEB SERVER. THE CHART IN SECTION 4.3 APPLICATION COEXISTENCE SHOW THE GUIDELINES FOR WHERE THIS WILL OCCUR. IT ALSO SHOWS RECOMMENDATIONS FOR CONFIGURING THE OCTELACCESS SERVER AND WHERE AN “APPLICATION SERVER” NEEDS TO BE USED.

With an Octel message server, Octel Software Solutions (including mobilePath) can be moved to an application server to allow the OctelAccess server to function more efficiently as the gateway for Octel Software Solutions and/or Visual Messenger only. The connectivity from an application server to the OctelAccess server is through the TCP/IP network and is defined in the OctelAccess Online Manual.

2.3 Application coexistence

VISUAL MESSENGER, AND OCTEL SOFTWARE SOLUTIONS CAN COEXIST ON AN OCTELACCESS SERVER, DEPENDING ON THE USERS SUPPORTED AND ON THE NUMBER OF APPLICATION LICENSES REQUIRED, OR AN APPLICATION SERVER MAY BE USED FOR OCTEL SOFTWARE SOLUTIONS. PERFORMANCE SPECIFICATIONS FOR EITHER THE VISUAL MESSAGING DESKTOP SUITE OR OCTEL SOFTWARE SOLUTIONS ALONE MUST BE APPROPRIATELY DE-RATED WHEN BOTH PRODUCTS RUN SIMULTANEOUSLY ON ONE OCTELACCESS SERVER.

Figure 1 below shows recommended guidelines for best acceptable performance when combining applications.

| |Octel 250/350, with A3.1.x |

| |Octel 200/300, with S4.1.x |

| |Visual Desktop Messaging Suite only |Octel Software Solutions only (includes |Visual Desktop Messaging and |

| | |mobilePath) |OSS (including mobilePath) |

|Small Site |OAS running OAS, Visual Messenger |OAS running OAS and Octel Software |OAS running OAS, Visual |

|< 50 clients (total logged | |Solutions |Messenger, and Octel Software |

|on) | | |Solutions |

|< 16 sessions of simple | | | |

|applications | | | |

|Medium Site |OAS running OAS and Visual Messenger |OAS running OAS and Octel Software |OAS running OAS, visual |

|< 500 Clients |WEB SERVER (Windows NT 4.0) running |Solutions |Messenger and Octel Software |

|< 32 sessions of simple |messenger | |Solutions |

|applications |OR | |WEB SERVER (Windows NT 4.0) |

| |OAS running OAS, Visual Messenger | |running messenger |

| | | |APP SERVER required if the |

| | | |application is a large Octel |

| | | |software Solution |

| | | |OR |

| | | |OAS running OAS, Visual |

| | | |Messenger, and Octel Software |

| | | |Solutions |

| | | |APP SERVER required if the |

| | | |application is a large Octel |

| | | |software Solution |

|Large Site |OAS running OAS and Visual Messenger. |OAS running OAS |OAS running OAS and Visual |

|>500 Clients |WEB SERVER (Windows NT 4.0) running |APP SERVER running Octel Software |Messenger |

|>32 sessions of complex |messenger |Solutions |WEB SERVER (Windows NT4.0) |

|applications | | |running messenger |

| | | |APP SERVER running Octel |

| | | |Software Solutions |

Figure 1. Performance Guidelines when running Visual Desktop Messaging Suite with Octel Software Solutions

Notes:

1. Drive space does not seem to be a limiting factor. The total for 2000, OAS, OD and Visual messenger is approximately two gigabytes.

2. RAM is a limiting factor. The RAM specified for OAS may need upgrading for sites supporting a large user population or many complex Octel Software Solutions.

3. The ultimate responsibility for defining the memory and processor requirements for Octel Software Solutions lies with the application developer.

4. The WEB Server for messenger alone must be Windows NT 4.0 with IIS 4.0.

3.0 Software compatability

As shown in the Software dependency matrix below (Figure 2.), there are currently multiple releases of both the OctelAccess Server software and the OctelDesigner Application Development Environment (ADE). OctelDesigner ADE Release 3.0 and OctelAccess Release 4.0 are the current release levels. Avaya recommends that applications be developed and run using the most current ADE and OctelAccess environments whenever possible. However, message server software and OAS releases maintain backward compatibility with previous releases (e.g., S4.1.1 supports OAS 3.0 and OAS 2.1. OAS 3.0 supports VM 3.0, VM 2.1 and 2.2, as well as OD 3.0 and OD 1.x applications).

OctelDesigner ADE 3.0 supports development of applications for both the 200/300 Message Server (Serenade) and the 250/350 Message Server (Aria). Applications developed with ADE 3.0 require Microsoft Visual Basic 6.0 as the development environment. Applications created with ADE 3.0 can run on only OctelAccess Release 3.0. or 4.0 OctelAccess Release 4.0 is compatible with Octel 200/300 Message Servers at Release S4.1.1 or higher and Octel 250/350 Message Servers at Release A3.11.1 or higher.

Please Note:

1. OctelAccess Release 2.1 supports 200/300 Message Servers only.

2. OctelAccess Releases 2.02, 2.2 support 250/350 Message Servers only.

OctelDesigner ADE 1.1 supports development of applications for both the 200/300 Message Server (Serenade) and the 250/350 Message Server (Aria). Applications developed with ADE 1.1 require Microsoft Visual Basic 6.0 as the development environment. Applications created with ADE 1.1 can run on either OctelAccess Release 2.1 or 2.2.

OctelDesigner ADE 1.0 is the previous release level. Applications developed with ADE 1.0 require Microsoft Visual Basic 5.0 as the development environments. It supported only the OctelAccess 2.1 runtime with Octel 200/300 Message Servers.

This information is summarized in the Software Dependency Matrix below (each element in a column is dependent on elements below).

|Applications |VM 2.0 |VM 2.1 |OD 1.1 |VM 2.2 |VM 3.0 and |VM 4.0/OD 3.0 |

| | |OD 1.0 | | |OD 3.0 | |

|OAS Requirements |OAS 2.0 |OAS 2.1 |OAS 2.1 or OAS 2.2|OAS 2.2 | OAS 3.0 |OAS 4.0 |

|Message Server |A2.02 |S3.0 | S3.0 |A3.0 | S4.1 or A3.10 |S.4.1.1 or A3.11.1 |

| | | |A3.0 | | | |

Figure 2. Software Dependency Matrix

f Octelaccess License keys

An OctelAccess License Key must be entered for each OctelAccess gateway on the Windows 2000 server. OctelAccess License Keys encode access for Visual Desktop Messaging Suite communication, Octel Software Solutions session licenses, and Octel Custom Fax Software runtime. OctelAccess Server 4.0 supports installation of up to eight OctelAccess Server gateways on a single Windows 2000 server. OctelAccess Server 2.x can install only one OctelAccess Server gateway on a Windows NT Server 4.0. Each OctelAccess Server gateway works with one Octel message server. The message server(s) serial number must be provided with the order when purchasing OctelAccess software capabilities. The OctelAccess License Key that is generated will enable an OctelAccess Server gateway to work only with the specified Octel message server. Each OctelAccess Server gateway and Octel message server combination is independent (i.e., Applications and application licenses must be purchased separately for each Octel message server. In other words, applications and application session licenses are not shared amongst multiple Octel message servers.)

License keys issued for OAS or VM 2.0 will need to be updated by Avaya Order Assurance for OAS 4.0.

5.0 Considerations

5.1 The OctelAccess Server does not have to be a member of a Domain. It cannot be configured as a Domain Controller and should not hold any of the FSMO roles in the Active Directory. It must be Stand Alone. Visual Desktop Messaging clients communicate with the OctelAccess Server directly via TCP/IP and are not required to be authenticated by Windows 2000.

5.2 Octel message servers require a static TCP/IP address to be programmed. If the customers environment uses DHCP servers to lease IP addresses to workstations, make sure you can PING from the message server to the workstation and Windows 2000 server address range used by the DHCP server.

5.3 When running the administrator client application on a PC other than the OctelAccess Server, you must add the path to the on line help manual. This is done by adding the full UNC (Uniform Naming Convention) of the \OADOCS subdirectory to the path variable in the environment tab of the system tool located in the control panel.

|© 2003 Avaya Inc. | |

|All rights reserved. | |

|Printed in the U.S.A. | |

|2/03 ( P/N 301-0036-002 Rev A | |

-----------------------

Ethernet

TCP/IP

Octel

Voice/Fax

Server

PBX

OctelAccess

Server

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download