2. • 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
3. AudioCodes Edge
Formula for Success
Modularity &
Scalability
Flexibility
Manageability
High
Availability
+
Smart, Flexible, Scalable, Manageable, High Availability
Unified Communications Solutions for Enterprises
4. AudioCodes Edge
Formula 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
6. Media Gateway Types
RTAudio
Basic Hybrid Gateway
with Integrated Mediation Server
SIP/TLS
SRTP
PSTNPSTNPSTNPSTN
PCM
E1/T1/BRI/FXO
PBX
Office
Communication
Server 2007
G.711
SIP/TCP
RTAudio
Microsoft
Mediation Server
Basic Gateway
SIP/TLS
SRTP
PCM
E1/T1/BRI/FXO
PBX
PSTNPSTNPSTNPSTN
Office
Communication
Server 2007
7. 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
8. 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
Highest
Scale
In Market
Uniform Functionality, Manageability and Protocol Support
10. VoIP Gateways provide mediation between the PBX
and SIP based Microsoft applications
SMDI
E1/T1
Exchange
Server
2007
FXO
FXO / BRI
E1/T1
Mediant 1000 (Mixed)
Mediant 2000 (Digital)
MediaPack (Analog)
Office
Communications
Server
2007
Basic Enterprise Network Topologies
Mediation
Server
12. 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
13. Basic configuration
Integrating OCS and UM Using a Single Gateway
• Mediant 1000 operating simultaneously with Exchange and OCS 2007
• Results in CapEx/OpEx reduction
14. 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
15. 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
19. 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
36. 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 routing
Not Required - remain with existing routing
Request (and purchase) PBX technical support to
perform all above Not Required
Using Gateways to Reduce PBX Connections
42. Survivability for Snom IP-Phone & OCS 2007
Point of Failure
Example
Emergency Mode - OCS 2007 server failure at HQ
43. Survivability for Snom IP-Phone & OCS 2007
Point of Failure
Example
Emergency Mode - OCS 2007 server failure at HQ
Registration
44. Survivability for Snom IP-Phone & OCS 2007
Emergency Mode Operation
Point of Failure
Example
Emergency Mode - OCS 2007 server failure at HQ
45. Survivability for Snom IP-Phone & OCS 2007
Example
Emergency Mode – WAN failure/loss at remote branch office
Point of Failure
46. Survivability for Snom IP-Phone & OCS 2007
Example
Emergency Mode – WAN failure/loss at remote branch office
Point of Failure Registration
47. Survivability for Snom IP-Phone & OCS 2007
Emergency Mode Operation
Example
Emergency Mode – WAN failure/loss at remote branch office
Point of Failure