Avaya 555-245-600 manual SIP Adjuncts, SIP Endpoints Features

Call processing

feature using Feature Name URIs, and retrieving state through event packages. Advanced SIP users must be provisioned both on SES as a SIP user and as an OPTIM station on Communication Manager. There must be a SIP trunk configured on Communication Manager, and a corresponding server configured on SES.

For AST, calls will be routed through Communication Manager for feature processing in both originating and terminating features.

Non-SIP endpoints can be dialed from SIP endpoints (and vice versa) by having server address maps on SES.

SIP Adjuncts

The first SIP adjunct supported was Modular Messaging, where message waiting indicator (MWI) and message retrieval are provided via SIP. In SES 4.0, Voice Portal support was added. Additionally, the development teams for Communication Process Manager (CPM) and Meeting Exchange Express Version are performing interoperability testing with SES.

SIP Endpoints

l Table 18: SIP Endpoints

Endpoint	Features
4602	Basic SIP phone, voice, no IM or presence
4610	Basic SIP phone, voice, no IM or presence
4620	Basic SIP phone, voice, no IM or presence
Avaya IP Softphone R5	H.323 voice, SIP IM and presence
Avaya one-X Mobile Edition	SIP voice, IM, Presence, advanced profile features
(SIP Softphone)
Avaya one-X Deskphone SIP	Advanced SIP telephony, advanced profile features,
(9620,9630)	IM/Presence
Toshiba SIP Phone	Advanced SIP telephony, advanced profile features,
	no IM/Presence

In addition to the endpoints listed, other third party endpoints are supported though the Avaya Solution Interoperability Lab.

138 Avaya Application Solutions IP Telephony Deployment Guide