Specifications

Server for Avaya SIP Enablement Services
Issue 6 February 2007 93
Other Servers
Server for Avaya SIP Enablement Services
Avaya SIP Enablement Services (SES) is dedicated to providing a variety of converged
communications services based on the Session Initiation Protocol (SIP). SIP is an
endpoint-oriented, network messaging standard defined by the Internet Engineering Task
Force. The fundamental concept behind SIP is that a user can have multiple devices.
SES provides the necessary proxy, registrations, and redirection tasks necessary for SIP
applications, such as Instant Messaging (IM). The server also provides the presence for use by
SIP endpoints. An SES Release 3.1 server is set to communicate with one or more Linux-based
media servers that run Avaya Communication Manager 3.1 or later. Then, the SIP proxy server
supports communication among the various non-SIP endpoints and new SIP-enabled
endpoints. Non-SIP endpoints supported by Communication Manager include analog, DCP, or
H.323 stations and analog, digital or IP trunks. SIP endpoints include the Avaya 46XX Series
SIP telephones, Avaya IP Softphone Release 5.1 and later, and Avaya SIP Softphone R2 and
later. These SIP endpoints are registered with the Avaya proxy. Therefore, Avaya media servers
can manage the SIP endpoints.
Among other features, the SES Server proxies instant messages and provides presence
functionality to support the Avaya IP Softphone. Meanwhile, Avaya Communication Manager
handles the voice and telephony features in the Avaya IP Softphone R5. Avaya Communication
Manager provides added value to SIP endpoints by extending the SIP telephony feature set.
Detailed description
Avaya’s SIP architecture supports servers running SES of different types.
There are several types of host architecture in the SES system:
● SIngle edge server with one to 20 home servers
● Combined home/edge server.
Edge server
The Edge server handles SIP requests from all domains, forwarding requests. These requests
can be received from Home servers, from within the enterprise’s domain, and from other SIP
proxies outside the enterprise’s domain. If an Edge server is used, then one or more Home
servers must also exist in this architecture. Only one Edge server, or combined Home/Edge
server, is allowed for any one domain. Edge servers can be duplexed for local failover.