slide1 n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
UNC304: Integrating Office Communications Server 2007 and/or Exchange Server 2007 with a PBX PowerPoint Presentation
Download Presentation
UNC304: Integrating Office Communications Server 2007 and/or Exchange Server 2007 with a PBX

Loading in 2 Seconds...

play fullscreen
1 / 22

UNC304: Integrating Office Communications Server 2007 and/or Exchange Server 2007 with a PBX - PowerPoint PPT Presentation


  • 180 Views
  • Uploaded on

UNC304: Integrating Office Communications Server 2007 and/or Exchange Server 2007 with a PBX. Rudy Gopaul Unified Communications Solutions Architect Dimension Data. OCS 2007 Agenda. OCS 2007 Components and Architecture. Understanding the benefits of PBX integration.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'UNC304: Integrating Office Communications Server 2007 and/or Exchange Server 2007 with a PBX' - ashanti


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
unc304 integrating office communications server 2007 and or exchange server 2007 with a pbx

UNC304: Integrating Office Communications Server 2007 and/or Exchange Server 2007 with a PBX

Rudy Gopaul

Unified Communications Solutions Architect

Dimension Data

ocs 2007 agenda
OCS 2007 Agenda

OCS 2007 Components and Architecture

Understanding the benefits of PBX integration

Deployment scenarios for today

Deployment scenario: Standalone (native OCS system)

Deployment scenario: Remote Call Control (RCC)

Deployment scenario: Co-existence - Dual call forking

ocs 2007 components

Telephony Gateway

OCS 2007 Media Relay

OCS 2007 Conferencing

Exchange Unified Messaging

OCS 2007 Mediation Server

OCS 2007 Components

OCS 2007

Provides voice mail with rich functionality integrated in e-mail.

Exchange Unified Messaging is not part of the OCS 2007 and has to be purchased separately.

The audio/video/data multipoint control unit (MCU) is used in multiparty sessions for mixing multiple incoming media streams and producing a single mixed output stream.

Handles authentication, dial plan implementation, core routing (inbound and outbound), and authorization logic.

Provides a single, trusted connection point through which both inbound and outbound voice can cross Internet firewalls separating an organization from its customers, partners and remote employees.

Translates both signaling and media between the enterprise IP network and the telephony network.

Telephony Gateways are provided by partners.

A mediation server mediates signaling and media between the OCS and PBX systems. It’s necessary if you’re using a basic media gateway.

ocs 2007 architecture
OCS 2007 Architecture

UC endpoints

QOE Monitoring Archiving

CDR

Public IM Clouds

DMZ

MSN

Media Relay

Data

Audio/Video

AOL

Yahoo

Inbound

Routing

Outbound

Routing

SIP

Remote

Users

Voice Mail

Routing

Active Directory

Front-End Server(s)

(IM, Presence)

Conferencing

Server(s)

Backend

SQL server

Access

Server

Exchange

2007 Server UM

Advanced GW

Mediation Server

Federated

Businesses

(GW)

Voicemail

PBX

PSTN

understanding the benefits of pbx integration
Understanding the benefits of PBX integration
  • Single/Familiar interface for multi-modal communication
  • Presence based communication, no phone “tag”
  • Reduced costs of unnecessary calls
  • Desktop integration, click-to-call from desktop applications
  • Increase interaction and collaboration
  • Increase agility - Get the job done quicker
  • Right Person, Right Time, Right Information
  • Mobility and reduced associated call costs (as agile or productive as when in the office)
deployment scenarios stand alone native ocs system
Deployment scenarios: Stand-alone (native OCS system)

Enhanced unified communications

experience for remote workers

  • Migrate remote workers to a telephony solution that works wherever they are
  • Stay connected at home, in hotels or wherever there is Internet access
  • Plug and play without VPN
  • Provide encrypted, secure communications
  • Save on mobile phones and hotel phone bills
  • Standard PBX migration procedures
  • For technical details and supported gateways on Microsoft Unified Communications Open Interoperability Program, see this web site: http://technet.microsoft.com/en-us/office/bb735838.aspx
deployment scenarios remote call control rcc
Deployment scenarios: Remote Call Control (RCC)

PBX call control and MOC

Presence status updates

  • CTI Link (CSTA interface) to existing telephony solution
  • Possible with OCS 2007
  • No VoIP
  • Office Communicator controls PBX phone
  • No softphone or OC device (‘Tanjay’ Phone)
  • For technical details and supported gateways on Microsoft Unified Communications Open Interoperability Program, see this web site: http://technet.microsoft.com/en-us/office/bb735838.aspx
deployment scenarios co existence dual call forking
Deployment scenarios: Co-existence - Dual call forking

Call signaling on MOC and on

IP-PBX phone at the same time

(dual forking)

  • Provide interoperability with IP-PBX systems
  • Allow a single user to have both OC and a IP-PBX hard phone
  • Deliver full Communicator experience in interoperability mode
  • Limit the changes needed to the IP-PBX and associated clients
  • Utilize existing PBX capabilities
  • For technical details and supported gateways on Microsoft Unified Communications Open Interoperability Program, see this web site: http://technet.microsoft.com/en-us/office/bb735838.aspx
exchange 2007 agenda
Exchange 2007 Agenda

Exchange 2007 Unified Messaging Architecture

Understanding the benefits of PBX integration

Integration Considerations

UM Integration Options: PBX and IP-PBX support

exchange 2007 um architecture
Exchange 2007 UM Architecture

ActiveSync/Outlook/OWA

Public (SMTP)

Message

Archiving

DMZ

Edge Servers

Remote

Users

Active Directory

Client Access / Hub Transport Servers

Mailbox

Servers

UM VoIP

Gateway(s)

Unified Messaging Server(s)

PBX

PSTN

IP-PBX

understanding the benefits of pbx integration1
Understanding the benefits of PBX integration
  • Single/Unified mailbox for email, voicemail and fax
  • Access mailbox content from GUI (Outlook, OWA, Mobile Active-sync)
  • Access e-mail, voice mail, calendar, and contacts from TUI (Telephone User Interface) – Speech and Touchtone
  • Automated Attendant
integration considerations
Integration Considerations
  • Dependant on your specific Private Branch eXchange (PBX) or IP PBX configurations
  • May require that you install IP gateways, purchase additional PBX hardware, or configure and enable features on your PBXs or IP PBXs
  • In some cases, PBX may cause reduced functionality or limitations in the Unified Messaging features
um integration options ip pbx support
UM Integration Options: IP-PBX Support
  • For an IP PBX to interoperate with Exchange 2007 Unified Messaging, the IP PBX generally must support the following:
    • Session Initiation Protocol (SIP) over Transmission Control Protocol (TCP)
    • T.38 for fax
  • Examples of supported IP-PBXs:
    • Avaya Communication Manager
    • Cisco CallManager 5.x
    • Interactive Intelligence CIC
    • Mitel 3300
    • Nortel CS 1000

Exchange

environment

Unified Messaging Server(s)

  • For a list of supported IP PBXs, see the Telephony Advisor for Exchange Server 2007 Web site: http://www.microsoft.com/technet/prodtechnol/exchange/telephony-advisor.mspx

IP-PBX

PSTN

um integration options pbx support
UM Integration Options: PBX Support
  • For a PBX to interoperate with Exchange 2007 Unified Messaging, a VoIP is required:
    • VoIP gateway(s) to translate the media and signaling data between circuit-switched protocol formats (understood by TDM-based PBXs) and IP-based, packet-switched formats (understood by Exchange 2007 UM).
  • Examples of supported VoIP gateways:
    • AudioCodes
    • Dialogic
    • Quintum
    • See Microsoft's Telephony Advisor for:
    • PBX configuration note contains information about deploying Exchange 2007 UM with a particular PBX

Exchange

environment

Unified Messaging Server(s)

VoIP Gateway

  • To give you the most up-to-date PBX configuration information and support list, see the Telephony Advisor for Exchange Server 2007 Web site: http://www.microsoft.com/technet/prodtechnol/exchange/telephony-advisor.mspx

PBX

PSTN

in conclusion
In Conclusion

What have we learnt?

Practical Experience – Lessons Learnt

what have we learnt
What have we learnt?
  • Understand OCS and Exchange 2007 architecture and supported interfaces, connectivity, protocols
  • Understand integration types and best fit for your organization
  • Capacity planning and forecasting (i.e. Network, Telephony)
  • Understand supported gateways, PBX, IP-PBX and functionality

Unified Messaging Server(s)

CSTA

Mediation Server(s)

VoIP

Gateway(s)

PSTN

CTI

SIP

PBX

practical experience lessons 1
Practical Experience – Lessons 1
  • Pre-project capacity planning and forecasting requirements
    • RCC telephony integration to IP-PBX (VoIP gateway used)
    • CTI configuration had to be enabled for each UC user / IP-PBX device
    • Telephony Design and limitations were not taken into consideration (coupled with required configurations)
    • Result: Each CTI enabled device in effect became 3 devices, IP-PBX ran out of capacity. Cost of project increased

X

IP-PBX

practical experience lessons 2
Practical Experience – Lessons 2
  • Number Normalization is very important
    • AD was not populated correctly (according to E.164 number plan)
    • Number normalization strings were not correctly defined
    • Result: Call routing including number association issues (missed call notifications)

Advanced GW

Mediation Server

(GW)

X

PBX

PSTN

practical experience lessons 3
Practical Experience – Lessons 3
  • Plan and architect solution according to Microsoft best practices
    • Exchange 2007 UM servers hardware sized and configured not according to best practice for the amount of users and voice traffic
    • Result: UM Voice Access produced jitter and did not meet expectations

X

slide22

Thank you

http://www.microsoft.com/southafrica/ucs/2007