05.03.2013 Views

Hardware Description and Reference for Avaya ... - Avaya Support

Hardware Description and Reference for Avaya ... - Avaya Support

Hardware Description and Reference for Avaya ... - Avaya Support

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Other Servers<br />

Server <strong>for</strong> <strong>Avaya</strong> SIP Enablement Services<br />

Server <strong>for</strong> <strong>Avaya</strong> SIP Enablement Services<br />

<strong>Avaya</strong> SIP Enablement Services (SES) is dedicated to providing a variety of converged<br />

communications services based on the Session Initiation Protocol (SIP). SIP is an<br />

endpoint-oriented, network messaging st<strong>and</strong>ard defined by the Internet Engineering Task<br />

Force. The fundamental concept behind SIP is that a user can have multiple devices.<br />

SES provides the necessary proxy, registrations, <strong>and</strong> redirection tasks necessary <strong>for</strong> SIP<br />

applications, such as Instant Messaging (IM). The server also provides the presence <strong>for</strong> use by<br />

SIP endpoints. An SES Release 3.1 server is set to communicate with one or more Linux-based<br />

media servers that run <strong>Avaya</strong> Communication Manager 3.1 or later. Then, the SIP proxy server<br />

supports communication among the various non-SIP endpoints <strong>and</strong> new SIP-enabled<br />

endpoints. Non-SIP endpoints supported by Communication Manager include analog, DCP, or<br />

H.323 stations <strong>and</strong> analog, digital or IP trunks. SIP endpoints include the <strong>Avaya</strong> 46XX Series<br />

SIP telephones, <strong>Avaya</strong> IP Softphone Release 5.1 <strong>and</strong> later, <strong>and</strong> <strong>Avaya</strong> SIP Softphone R2 <strong>and</strong><br />

later. These SIP endpoints are registered with the <strong>Avaya</strong> proxy. There<strong>for</strong>e, <strong>Avaya</strong> media servers<br />

can manage the SIP endpoints.<br />

Among other features, the SES Server proxies instant messages <strong>and</strong> provides presence<br />

functionality to support the <strong>Avaya</strong> IP Softphone. Meanwhile, <strong>Avaya</strong> Communication Manager<br />

h<strong>and</strong>les the voice <strong>and</strong> telephony features in the <strong>Avaya</strong> IP Softphone R5. <strong>Avaya</strong> Communication<br />

Manager provides added value to SIP endpoints by extending the SIP telephony feature set.<br />

Detailed description<br />

<strong>Avaya</strong>’s SIP architecture supports servers running SES of different types.<br />

There are several types of host architecture in the SES system:<br />

Edge server<br />

● SIngle edge server with one to 20 home servers<br />

● Combined home/edge server.<br />

The Edge server h<strong>and</strong>les SIP requests from all domains, <strong>for</strong>warding requests. These requests<br />

can be received from Home servers, from within the enterprise’s domain, <strong>and</strong> from other SIP<br />

proxies outside the enterprise’s domain. If an Edge server is used, then one or more Home<br />

servers must also exist in this architecture. Only one Edge server, or combined Home/Edge<br />

server, is allowed <strong>for</strong> any one domain. Edge servers can be duplexed <strong>for</strong> local failover.<br />

Issue 6 February 2007 93

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!