© 2008 audiocodes ltd. all rights reserved. advanced topologies for microsoft unified...

© 2008 AudioCodes Ltd. All rights reserved.

Advanced Topologies for Microsoft Unified Communications Networks

Haim MelamedDirector, Corporate & Channel Marketinghmelamed@audiocodes.com

• Long standing technology alliance– Microsoft developed its SIP VoIP gateway interfaces with AudioCodes Mediant 2000

• Marketing partners – AudioCodes MediaPacks were the only gateways chosen for the “OCS Ignite Road show”

– Global train-the-trainer tour in San-Francisco, Toronto, London, Amsterdam, Singapore

• “Dogfood” for Microsoft IT– AudioCodes gateways are used within Microsoft IT for OCS deployments

AudioCodes and Microsoft

AudioCodes EdgeFormula for Success

Modularity & Scalability

Flexibility

Manageability

High Availability

+

Smart, Flexible, Scalable, Manageable, High AvailabilityUnified Communications Solutions for Enterprises

AudioCodes EdgeFormula for Success

Flexibility

• Wide range of interfaces• Wide protocol support• Interoperability with: Softswitches, PSTN, PBXs and IP-PBXs

Modularity & Scalability

• Number of ports from 2FXS to 240 E1s on same chassis

Manageability

• CLI, WEB, Telnet• Central Management system for large installations

High Availability

• Dual PS• PSTN fallback• Life Line

Media Gateway Types

G.711

SIP/TCP

RTAudio

Microsoft Mediation Server

Basic Gateway

SIP/TLSSRTP

PCM

E1/T1/BRI/FXO

PBX

PSTNPSTNPSTNPSTN

OfficeCommunication

Server 2007

Media Gateway Types

RTAudio

Basic Hybrid Gateway with Integrated Mediation Server

SIP/TLSSRTP

PSTNPSTNPSTNPSTN PCM

E1/T1/BRI/FXO

PBX

OfficeCommunication

Server 2007

G.711

SIP/TCP

RTAudio

Microsoft Mediation Server

Basic Gateway

SIP/TLSSRTP

PCM

E1/T1/BRI/FXO

PBX

PSTNPSTNPSTNPSTN

OfficeCommunication

Server 2007

High Availability Flexibilty ManageabilityScalability

Gateway Breadth and Scalability

– Low end demo kit & small branch office – MediaPack MP114/118

• MediaPack 114 - 2FXS/2FXO and MediaPack 118 - 4FXS/4FXO

– Entry level and Mid Range – Mediant 1000

• Up to 4 E1/T1 + a mix of up to 20 BRI/FXS/FXO in 1U chassis

• Supports “Basic Hybrid Gateway” for 30 active channels (OCS R1 – OSN1)

• Supports “Basic Hybrid Gateway” for 120 active channels (OCS R2 – OSN3)

Uniform Functionality, Manageability and Protocol Support

High Availability Flexibilty ManageabilityScalability

Gateway Breadth and Scalability

– High End – Mediant 2000

• Up to 16 E1/T1 in 1U chassis

• Supports “Basic Hybrid Gateway” for 120 active channels (OCS R2)

– High End – Mediant 3000/5000/8000*

• Mediant 3000 with up to 63 E1/84 T1 in 2U chassis*

• Mediant 5000 with up to 96 E1/T1 in 5U chassis*

• Mediant 8000 with up to 240 E1/T1 in 12U chassis*

• High availability platforms

* Formal certification pending

HighestScale

In Market

Uniform Functionality, Manageability and Protocol Support

© 2008 AudioCodes Ltd. All rights reserved.

Basic OCS and Exchange 2007 Topologies

VoIP Gateways provide mediation between the PBX

and SIP based Microsoft applications

SMDI

E1/T1

ExchangeServer2007

FXO

FXO / BRI

E1/T1Mediant 1000 (Mixed)

Mediant 2000 (Digital)

MediaPack (Analog)

OfficeCommunicationsServer2007

Basic Enterprise Network Topologies

MediationServer

© 2008 AudioCodes Ltd. All rights reserved.

Advanced Topologies For Microsoft Solutions

Advanced Topologies For Microsoft Solutions

1. Basic configuration - Integrating OCS and UM Using a Single Gateway

2. Enabling Auxiliary Services (such as Fax, Modem, Alarm systems) on OCS 2007

3. Enabling Connectivity of Non-certified IP-Telephony systems to Exchange 2007

4. Enabling Connectivity of Non-certified IP-Telephony systems to OCS 2007

5. Enabling Connectivity of Internet Telephony Service Provider (SIP Trunking) to OCS 2007

6. Migration Path to Unified Communications

7. Alternative Routing in Failure Conditions

8. Using the Gateway in a “Drop & Insert” configuration

9. Active Directory Lookup support for Survivability and Smooth Migration

10. SNOM Phones redundant solution

Basic configuration Integrating OCS and UM Using a Single Gateway

• Mediant 1000 operating simultaneously with Exchange and OCS 2007• Results in CapEx/OpEx reduction

Enabling Auxiliary Services on OCS 2007

• OCS 2007(Mediation Server) does not support Fax, Modem & Alarm systems services• Enterprise wishes to use OCS, but wants to continue providing these auxiliary services• AudioCodes gateways enable existing Fax machines at the enterprise to remain

operable • Regular operation of Fax machines is kept by using advanced dialing plans

Enabling Connectivity of Non-certified IP-Telephony systems to Exchange 2007

• Most IP-Telephony systems don’t meet Microsoft’s functional specifications • The few IP-Telephony systems that do meet Microsoft’s functional specifications require

hardware and/or software upgrades• By using AudioCodes Media gateway IP-to-IP mediation, the existing IP telephony system

does not need to be upgraded or replaced

• Simple and cost-effective solution

Enabling Connectivity of Non-certified IP-Telephony systems to OCS 2007

IP Network (LAN) H.323 Gatekeeper

H.323IP-Phone

H323 PSTNVoIP Gateway

PSTN

H.323IP-Phone

AudioCodesMediant 2000

Microsoft OCS Server

Microsoft Mediation

Server

OC

OC

SIP

H.323

H.323

SIP

(H.323-SIP)

Example:Cisco Call Manager

Enabling Connectivity of Non-certified IP-Telephony systems to OCS 2007

IP Network (LAN)

SIP IP-Phone

PSTN

SIP Proxy

SIP PSTN VoIP Gateway

SIP IP-Phone

AudioCodesMediant 2000

Microsoft OCS Server

Microsoft Mediation

Server

OC

OC

SIP(TCP)

SIP (UDP)

SIP (UDP)

SIP (TCP)

(SIP-SIP)

Enabling Connectivity of Non-certified IP-Telephony systems to OCS 2007

Enabling Connectivity of Internet Telephony Service Provider (SIP Trunking) to OCS

• Using AudioCodes gateway for interworking between OCS 2007 and the ITSP (SIP Trunking) offers Enterprises the following benefits:

• Easy and smooth integration with one or more ITSP SIP trunks with different behaviors or requirements for the same device

• Registration and authentication with ITSP servers (on behalf of the Enterprise's IP telephony system) even if the Enterprise's IP telephony system does not support registration and authentication

• Alternative routing to different destinations when the connection with the ITSP network is down• Fallback to legacy PSTN telephone network upon Internet connection failure

Two ITSPs providers

PSTN

PBX

Phones & Faxes

LegacyVoicemail

Migration Path to Unified Communications(Today)

Migration Path to Unified Communications(Introducing Exchange 2007)

Exchange UM

PSTN

PBX

Phones & Faxes

LAN

AudioCodesMediant

Migration Path to Unified Communications (Introducing OCS)

OCS Clients(OC & IP Phones)

OCS Exchange UM

PSTN

PBX

Phones & Faxes

LAN

AudioCodesMediant

Migration Path to Unified Communications (Complete)

PSTN Phones & Faxes

OCS Clients(OC & IP Phones)

OCS Exchange UM

LAN

AudioCodesMediant

Alternative Routing in Failure Conditions(OCS ->PBX/PSTN)

Example

X

Alternative Routing in Failure Conditions(OCS ->PBX/PSTN)

Example

X

Alternative Routing in Failure Conditions(OCS ->PBX/PSTN)

Example

Alternative Routing in Failure Conditions(PBX/PSTN->OCS)

Example

X

X

Alternative Routing in Failure Conditions(PBX/PSTN->OCS)

Example

X

X

Alternative Routing in Failure Conditions(PBX/PSTN->OCS)

Example

PSTN

100

101

533-1214-2167

443-8834-5xxx

PSTNSwitch

1

Example

Using Gateways to Reduce PBX Connections

IP Network (LAN)

AudioCodesMediant 1000

Microsoft OCS Server

Microsoft Mediation

Server

OC

OC200

201

PSTN

100

101

533-1214-2167

443-8834-5xxx

PSTNSwitch

12

Example

Using Gateways to Reduce PBX Connections

IP Network (LAN)

AudioCodesMediant 1000

Microsoft OCS Server

Microsoft Mediation

Server

OC

OC200

201

PSTN

100

101

533-1214-2167

443-8834-5xxx

PSTNSwitch

1

Example

Using Gateways to Reduce PBX Connections

IP Network (LAN)

AudioCodesMediant 1000

Microsoft OCS Server

Microsoft Mediation

Server

OC

OC200

201

PSTN

100

101

533-1214-2167

443-8834-5xxx

PSTNSwitch

1

Example

Using Gateways to Reduce PBX Connections

IP Network (LAN)

AudioCodesMediant 1000

Microsoft OCS Server

Microsoft Mediation

Server

OC

OC200

201

PSTN

100

101

533-1214-2167

443-8834-5xxx

PSTNSwitch

1

Example

Using Gateways to Reduce PBX Connections

IP Network (LAN)

AudioCodesMediant 1000

Microsoft OCS Server

Microsoft Mediation

Server

OC

OC200

201

PSTN

100

101

533-1214-2167

443-8834-5xxx

PSTNSwitch

1

Example

Using Gateways to Reduce PBX Connections

Implementing AudioCodes gateways eliminates all the costly drawbacks of a typical topology

as listed below:

Typical Deployment (Without AudioCodes Gateway)

Deployment Using AudioCodes Gateway

Purchase new trunk(s)Not Required - remain with existing trunks

Upgrade PBX (software and/or hardware) to support more concurrent calls Not Required - PBX handles only calls

related to PBX users

Purchase PBX licenses to support additional trunks and calls Not Required - remain with existing license

Modify PBX routingNot Required - remain with existing routing

Request (and purchase) PBX technical support to perform all above Not Required

Using Gateways to Reduce PBX Connections

Active Directory Lookup support for Survivability and Smooth Migration

Active Directory Lookup support for Survivability and Smooth Migration

Survivability for Snom IP-Phone & OCS 2007

Survivability for Snom IP-Phone & OCS 2007

ExampleNormal Mode

Registration

Survivability for Snom IP-Phone & OCS 2007

Normal Mode Operation

ExampleNormal Mode

Survivability for Snom IP-Phone & OCS 2007

Point of Failure

ExampleEmergency Mode - OCS 2007 server failure at HQ

Survivability for Snom IP-Phone & OCS 2007

Point of Failure

ExampleEmergency Mode - OCS 2007 server failure at HQ

Registration

Survivability for Snom IP-Phone & OCS 2007

Emergency Mode Operation

Point of Failure

ExampleEmergency Mode - OCS 2007 server failure at HQ

Survivability for Snom IP-Phone & OCS 2007

ExampleEmergency Mode – WAN failure/loss at remote branch office

Point of Failure

Survivability for Snom IP-Phone & OCS 2007

ExampleEmergency Mode – WAN failure/loss at remote branch office

Point of Failure Registration

Survivability for Snom IP-Phone & OCS 2007

Emergency Mode Operation

ExampleEmergency Mode – WAN failure/loss at remote branch office

Point of Failure

Advanced Scenarios Documentation

Product Support

• On AudioCodes Websitewww.audiocodes.com/microsoft

Exchange 2007 Details• User Manuals• Demo• Firmware• Certified PBX’s• Qualified Products

OCS 2007 Details• User Manuals• Demo• Firmware• Certified PBX’s• Qualified Products