Mino – The UC Guy

Microsoft Unified Communications Blog

Posts Tagged ‘AVAYA OCS Integration’

OCS Integration with AVAYA ( 1 of 2 )

Posted by Mino on February 1, 2009

Hi all,

As i have promissed you that I will be back with lots of great information regarding the AVAYA integration.

here we go , i was working with a huge client in Dubai where he has just purchased an AVAYA IP-PBX along with Sip Enablement Server ( SES ) and AVAYA Application Enablement Server ( AES ) .

ok first of all lets us all memorize these two terms , AVAYA SES and AVAYA AES because we will be talking about them both allot.

There are two stories for the AVAYA-Microsoft integration , the AVAYA story and the Microsoft story. we will talk about both stories and the integration idea from each vendor , the limititions from each way of integration along with the pros and cons.

Microsoft Story :

For Microsoft the integration with AVAYA is simply by dealing with them as two separate IP-PBX where Microsoft has an extensions of 3xxx for example and AVAYA with extensions of 7xxx .where you need to create a SIP trunk between both of them to be able to call from here to there and vise verse.

This assures microsoft that the call processing will happen in the Mediation server , which is the target of Microsoft in order to help its users to move to the Microsoft IP PBX concept bit by bit.

for this type of integration you will need AVAYA SIP enablement server only which shall give the AVAYA communication manager the SIP capability to communicate with other system , in this SES we will configure a sip trunk for the 3xxx extensions to route to the mediation Server over TCP-IP port 5060 or through TLS over 5061 after you configure the certificate on the SES Server.

below is a diagram for this type of integration .

avaya-direct-sip

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Good Thing :

1- AVAYA SES is not costy at all  , 2-Full featured OCS capabilities including conferencing,  3- you can do dual forking workarround by adding AVAYA extensions as the similtaniously ring another number in OCS

Bad thing:

no dual forking between AVAYA and OCS which means that each person will have two extensions .

in my oppenion , no Big deal …the client was so happy with this scenario because the second AVAYA scenario will cost him 60$ per users license plus it will not provide him with all capabilities of OCS ( the conferencing for example is dimmed )

in the Second article we will discuss the second way of integration through the AVAYA AES Server

Advertisements

Posted in AVAYA | Tagged: , , , , , , | 2 Comments »

Application Notes for Microsoft Office Communicator Clients with Avaya Communication Manager Phones

Posted by Mino on November 17, 2008

These Application Notes describe the configuration procedures for enabling Microsoft Office

Communicator (MOC) clients to operate Avaya Communication Manager phones. The MOC

client and Microsoft Office Communications Server (OCS) provide the user with multiple

modes of communications, such as Instant Messaging (IM), voice, and video. The

configuration steps described herein focus on the TR/87 integration between Avaya

Application Enablement Services and Microsoft OCS. The TR/87 integration allows MOC

clients to make and answer calls on Avaya Communication Manager phones, as well as

perform basic call control operations such as hold/retrieve, transfer, and disconnect.

ocs-acm-rcc

Posted in AVAYA, communicator client, PBX Integration | Tagged: , , | 2 Comments »