Avaya IP Telephony User Manual download pdf (Page 27)

KW Avaya IP Telephony Implementation Guide

3 Guidelines for Avaya Servers and Gateways

This section gives guidelines for Avaya servers and gateways, and covers most of the IP-telephony-

related configurations. Refer back to section 1 for an overview of IP telephony components and Avaya

architectures.

Avaya Communication Manager is the call processing software that runs on Avaya servers, and it is

configured via the Switch Administration Terminal (SAT) interface. Although the server platforms

themselves may be configured in various ways, SAT is the universal interface for Communication

Manager.

The Avaya Site Administrator (SA) is a client software application used to access the SAT interface on all

Avaya servers. Additionally, on all but the DEFINITY servers, SAT can also be accessed by telnet-ing to

the server.

3.1 S87xx/S8500 Servers

The S87xx and S8500 are 19-inch rack-mountable Red Hat Linux server platforms. S87xx servers

operate in a redundant pair, whereas the S8500 is a simplex server. Each server is configured and

managed via a variety of web interfaces, with the Maintenance Web Interface being the most

comprehensive. The web interfaces are designed to facilitate all anticipated configuration and

management requirements, and there is little or no need for a customer to access the Linux shell.

In an S87xx pair one of the servers is active and the other is standby. SAT administration is performed on

the active server, and it is automatically carried over to the standby server. Either of the servers could be

active or standby at any given time, and there are different ways to determine which is active. If the two

servers are on the same subnet there is a virtual IP address, which is labeled the active server address in

the Configure Server – Configure Interfaces screen of the Maintenance Web Interface. Whichever

server is active takes control of the active server address, and telnet-ing or browsing or pointing Avaya

SA to that address accesses the active server. If the two S8700 servers are not on the same subnet (server

separation), there is no virtual active server address. The Status Summary web screen shows the status

of the servers.

The S8700 SAT interface may be accessed using Avaya Site Administration (ASA) or by telnet-ing to

port 5023: telnet <active server address> 5023. A SAT session can also be established by telnet-ing to

the active server and typing sat from the Linux shell. The standby server does not permit access to SAT.

Secure Shell (SSH) access is recommended for encrypted connections to an S87XX server pair. ASA

supports Secure Shell (SSH) access for system administration. A SSH Client can also be used to access

the SAT on port 5022.

SAT access to the S8500 is similar to that of the S87xx server pair, except that there is only one server.

As of CM 3.1 a S8500 main server or S8500 LSP supports Processor Ethernet (PE). The S8500 PE

provides similar functions as a CLAN (TN799DP) Circuit Pack for H.323 IP endpoints, H.248 gateways

and subset of adjuncts. An S8500 PE interface uses one of the native NICs on the server and allows for

direct connections to H.248 Media Gateways without the need for port networks (CLAN + IPSI). There

are, however, configuration limitations, which are defined in the Overview for AVAYA Communication

Manager, Document ID 03-300468, available on the support.avaya.com website.

S87xx/S8500 Speed/Duplex

Speed and duplex for the various S87xx/S8500 Ethernet interfaces are configured using the Configure

Server – Configure Interfaces web admin screen. It is critical to configure the speed and duplex

correctly on the server interfaces used to communicate with the IPSI boards. A speed/duplex mismatch

between these interfaces and the Ethernet switch causes severe call processing problems.

1 ... 26 27 28 ... 81

Comments to this Manuals

No comments

Avaya IP Telephony User Manual Page 27

Comments to this Manuals

Related products and manuals for Network switches Avaya IP Telephony