1. Make Your Mark.

2. Brendan Carius Senior Consultant - Microsoft Consulting Services Planning Voice Deployment for Microsoft Office Communications Server 2007 UNC312

3. Make Your Mark. OCS Voice Components Outside Users MSN AOL Yahoo AccessServer DMZ DataMediaSIP Federated Businesses FE Server(s) (Registrar/Proxy/ Presence Server) InboundRouting OutboundRouting PSTN Backend SQL server UC Endpoints ArchivingCDR AD Advanced Media GWMedia GW(MediationServer) Voice MailVoice MailRouting PRI PBX Public Clouds Exchange 2007 UM2007 UM Voice mailVoice mail Translations Application

4. Make Your Mark. OCS/PSTN Integration Scenarios OCS 2007 Co-existence Interoperability with existing PBXs and IP-PBXs OC user also has PBX phone Based on “Dual Forking” specification OCS 2007 Stand-alone Split PBX dial-plan where some users have OC, others use PBX Phone Available for no-PBX deployments SIP or TDM connectivity

5. Make Your Mark. Media GW Configurations Basic Media GW Basic MGW appliance with UC Mediation Server Advanced & Basic Hybrid Media GWs Rich MGW appliance running mediation server UC Mediation Server UC-compatible media stack Rich GW appliance hosting RTC (compatible) Media Server UC Mediation Server Basic GW Appliance

6. Make Your Mark. Communications Server 2007 Voice Scenarios PBX Phone CSTA Office Communicator No voice OCS 2007 PSTN phone PRI(s) Existing SIP/PSTN Gateway Existing IP PBX PBX Phone Office Communicator No voice Office Communicator Call Control only, no media! Each proxy forks call to the other one (simultaneous ringing)! Mediation Server PSTN Remote Call Control Scenario Office Communicator as a Softphone Scenario OCS 2007 PSTN phone SIP/CSTA Gateway PSTN

7. Make Your Mark. Direct PSTN PRI off TDM-PBX PRI off existing IP-PBX GW PSTN phone OCS 2007 PSTN phone SIP/PSTN Gateway PSTN PRI(s) PBX Phone OCS 2007 PSTN phone SIP/PSTN Gateway PSTN PRI(s) Existing SIP/PSTN Gateway Existing IP PBX PBX Phone OC OCS 2007 SIP/PSTN Gateway PSTN Communications Server 2007 Voice Scenario Unified Communications Scenarios

8. Enterprise Voice Scenarios with Office Communicator Demo

9. Make Your Mark. Recommended for: Companies with an outdated PBX infrastructure Companies that don’t want to touch their existing voice infrastructure Pros No integration necessary with existing voice infrastructure Easy to set up Cons Pilot users typically need new phone numbers External call forwarding has to be configured for pilot users via PSTN in existing voice solution Direct PSTN connection OCS 2007 PSTN phone SIP/PSTN Gateway PSTN

10. Make Your Mark. Recommended for: This is the recommended scenario for all large enterprise environments that still have a TDM-based PBX Companies that have an unused tie line PRI port available, or can configure that easily (with assistance from Microsoft) Tie-line off existing TDM PBX OCS 2007 PSTN phone SIP/PSTN Gateway PBX Phone PRI(s) PBX PSTN

11. Make Your Mark. Pros Core features are transparent to all other PBX users Allows using the existing PBX network for all cross-site call routing Pilot users do not need a new phone number Cons Supplementary services (Call completion on busy subscriber, Team calls, etc.) cannot be used between OC and existing PBX users Routing to pilot users has to be configured in PBX PBX attendant console will not have info on phone presence states (busy lamp field) of those users (OC can be used instead) Tie-line off existing TDM PBX OCS 2007 PSTN phone SIP/PSTN Gateway PBX Phone PRI(s) PBX PSTN

12. Make Your Mark. Recommended for: All large enterprise environments that have already an IP-PBX, but do not want to integrate on SIP layer PRI off existing SIP/PSTN Gateway OCS 2007 PSTN phone SIP/PSTN Gateway PRI(s) Existing SIP/PSTN Gateway Existing IP PBX PBX Phone PSTN

13. Make Your Mark. Pros No SIP to SIP connection between the two VoIP systems needs to be established All cross-system traffic will be “normalised” by the SIP/PSTN Gateways Pilot users do not need a new phone number Cons Supplementary services (Call completion on busy subscriber, Team calls, etc.) cannot be used between OC and existing IP PBX users Routing to pilot users has to be configured in IP PBX and on the existing IP PBX gateway PBX attendant console will not have info on phone presence states (busy lamp field) of those users (OC can be used instead) PRI off existing SIP/PSTN Gateway OCS 2007 PSTN phone SIP/PSTN Gateway PRI(s) Existing SIP/PSTN Gateway Existing IP PBX PBX Phone PSTN

14. Make Your Mark. Recommended for: Progressive customers with minimal legacy- telephony requirements Scenario combination OCS 2007 SIP/ PSTN Gateway Small PBX PSTN phone Fax, Analog/ ISDN Devices PRI(s) PSTN

15. Make Your Mark. Pros Easy to configure from OCS perspective Small PBX for legacy devices is inexpensive and may already be available at customer site Cons Small PBX can only provide missing connectivity but not additional features for the Office Communicator/ Tanjay clients Small PBX has to be configured Current Office Communicator/Tanjay feature set has to match customers requirements PRI off existing SIP/PSTN Gateway OCS 2007 SIP/ PSTN Gateway Small PBX PSTN phone Fax, Analog/ ISDN Devices PRI(s) PSTN

16. Make Your Mark. Site-based migration decision Media Gateway SQL Server Exchange Server with Unified Messaging WAN OCS 2007 pool OCS 2007 Conferencing (server role) Management (MOM, MMC) Media Gateway PSTN

17. Configuring Enterprise Voice Demo

18. Make Your Mark. AudioCodes Mediant 1000 & 2000 Dialogic DMG 4060DTI, DMG 4120DTI, TIMG 600DTI, TIMG 1200DTI Quintum Tenor AX, Tenor DX VegaStream Vega 400 …more to come SIP/PSTN gateways tested with Communications Server

19. Make Your Mark. Does the gateway have the required certifications for operation in the designated country? Does the gateway provide the right protocols to connect with the local PSTN or with the existing PBX system? Does the gateway provide the right number and type of PRI connections? Does the gateway provide the necessary number manipulation capabilities (converting Called Party Numbers in E.164 format from Communications Server 2007 to the locally expected format and vice versa) in the admin program? Do you need to prepare a special connection cable or does it come with the gateway shipment? Do you need an adapter for the power supply unit of the gateway? Per-site gateway decision

20. Make Your Mark. SIP URI-based Routing on Communications Server OCS 2007 SE PSTN phone E.164 format SIP URI National format SIP/ PSTN Gateway Mediation Server UC endpoints identified by SIP URI OCS matches E.164 numbers to SIP URIs Gateway or OCS Called P. no. normalizes to E.164 format INVITE TO: sip:john@contoso.com FROM: sip:+ 61298703002 @contoso.com;user=phone INVITE TO:sip:+6493622001@contoso.com;user=phone FROM:sip:+ 61298703002 @contoso.com;user=phone Called Party Number: 03622001 Calling Party Number: 00161298703002 PSTN

21. Make Your Mark. Numbering Considerations Media Gateway. SQL Server Exchange Server with Unified Messaging WAN OCS 2007 pool PSTN OCS 2007 Conferencing (server role) Management (MOM, MMC) Media Gateway. Logical Site A Logical Site B Logical Site C (or A or B)

22. Make Your Mark. Numbering Considerations Media Gateway. SQL Server Exchange Server with Unified Messaging WAN OCS 2007 pool NZ PSTN AUST PSTN OCS 2007 Conferencing (server role) Management (MOM, MMC) Media Gateway. +64 9 362-xxxx +61 2 9870-xxxx TBD

23. Make Your Mark. SIP URI-based Routing on Communications Server SQL Server WAN OCS 2007 pool NZ PSTN +64 9 362 2001 A A B B D D E E x2001 GW+ Med. Srv. WAN US PSTN Called Party Number= +64 9 3622001 Called Party Number= +4533210022 Called Party Number Modifications A: 3622001 B: 2001 C: +6493622001 D: sip:john@contoso.com E: sip:john@contoso.com C C

24. Make Your Mark. Inbound PSTN call—User is mobile Media Gateway SQL Server Exchange Server with Unified Messaging WAN OCS 2007 pool Aust PSTN OCS 2007 Conferencing (server role) Management (MOM, MMC) x2001 Called Party Number= +6493622001 +64 9 362-xxxx Media Gateway

25. Make Your Mark. Outbound PSTN call SQL Server WAN OCS 2007 pool NZ PSTN +64 9 362-xxxx E E D D C C B B A A x22 GW+ Med. Srv. WAN US PSTN Called Party Number= +4533210022 Called Party Number= +64 9 362-2001 Called Party Number Modifications A: sip:03922001@con.. B: sip:+6493622001@con.. C: sip:+6493622001@con.. D: 03622001 E: 3622001

26. Make Your Mark. Outbound PBX call SQL Server OCS 2007 pool NZ PSTN +64 9 362-xxxx D D C C B B A A x2001 GW+ Med. Srv. WAN US PSTN Called Party Number= 3007 x3007 Called Party Number Modifications A: sip:3007@con.. B: sip:+6493623007@con.. C: sip:+6493623007@con.. D: 3007

27. Make Your Mark. Outbound PSTN call with Least Cost Routing WAN OCS 2007 pool NZ PSTNAust PSTN Called Party Number= +61298703221 +64 9 362-xxxx SQL Server C C A A x2001 B B Called Party Number Modifications A: sip:00161298703221@con.. B: sip:+61298703221@con.. C: 0298703221

28. OCS Route Helper Demo

29. Questions?

30. Evaluation Forms

31. © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.