Lync 2010 : PBX integration Integration methods

This is one of the hot topics still in UC world, as versions of Communications Server have come and gone, there has also been discussion around whether the product was fit to be a complete replacement for any existing voice infrastructure. Here we are going to discuss about the migration or testing scenario to provide integration with the existing voice services. 

Integration Methods

• Direct SIP
• Media Gateways
• Remote Call Control
• Dual Forking
• SIP Provider Trucking

Direct SIP

The easiest and generally most cost-effective way of integrating Lync Server with an existing PBX is if the PBX supports SIP trunks. Many IP PBXs support this functionality, and many other hybrid PBXs support SIP trunks with additional hardware and software upgrades.

Here the mediation server acts as a conversion point between the two systems. The Lync is using a codec called RTAudio were PBX commonly use G .711.

In this method a range of extensions are allocated to both PBX and LYNC server, in the calling search space of both systems we will define these extensions. So once a call generated if the call belongs to other system it will send across the SIP trunk to other system.

Media Gateways

If Direct SIP is not an option because the PBX does not support the feature nor has no IP PBX capabilities, a third-party device called a media gateway can be used to complete the integration. Media gateways act as an intermediary between the PBX and Lync Server to help translate traditional PBX protocols to SIP traffic, which Lync Server understands. They typically have traditional telephony connections for T1/E1 systems on the PBX side along with network adapters to communicate with Lync Server.

  

Different Lync Certified Gateway Models:

Vendor	Qualified Device	Qualified Firmware
Audiocodes	Mediant 800 SBA	SBA: 1.1.8.21, Gateway: 6.00A.033.005
Audiocodes	Mediant 1000 SBA	SBA: 1.1.8.21, Gateway: 6.00A.033.005
Audiocodes	Mediant 2000 SBA	SBA: 1.1.8.21, Gateway: 6.00A.033.005
Dialogic	DMG4000 SBA	SU4, SIPControl 2.5, Diva System Release 9.5 WIN
Ferrari electronic AG	OfficeMaster SBA	3.3
HP	Survivable Branch Communication zl Module	SBA: 1.0.5, Gateway: 3.0.3
NET	UX1000	SBA: 4.0.7577.0, Gateway: 2.0.1v118
NET	UX2000	SBA: 4.0.7577.0, Gateway: 1.0.1.194
NET	UX2000	SBA: 4.0.7577.0, Gateway: 2.0.1v118

Also, as when configuring a Direct SIP trunk link, configuration of the old PBX is necessary so that it knows to route calls for specific extensions to the media gateway, which delivers the calls to Lync Server.

Will continue ...............