key elements to deploying ocs n.
Skip this Video
Loading SlideShow in 5 Seconds..
Key Elements to Deploying OCS PowerPoint Presentation
Download Presentation
Key Elements to Deploying OCS

Loading in 2 Seconds...

play fullscreen
1 / 26

Key Elements to Deploying OCS - PowerPoint PPT Presentation

  • Uploaded on

Key Elements to Deploying OCS. Where to Start. OCS can seem to require an awful lot of servers _ Edge, Director, Front End, SQL, Monitoring, SQL, Archiving, SQL, Mediation, Group Chat, SQL, …

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

Key Elements to Deploying OCS

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
where to start
Where to Start
  • OCS can seem to require an awful lot of servers _ Edge, Director, Front End, SQL, Monitoring, SQL, Archiving, SQL, Mediation, Group Chat, SQL, …
  • Project I was working on the objectives where to reduce mobile phone spend by offering enterprise voice and reduce conferencing by offering live meeting to external users.
    • 80K users, 10K ent voice, UK & USA phone numbers
  • Phased Implementation
    • Lab
    • Pilot (7k)
    • Production 80K, 10K ent voice
  • High level planning tool is the OCS Planning Tool
  • Capacity largely determined by number of concurrent users
    • Logon rate and number of endpoints
    • Contention rate to PSTN
  • Considerations disaster recovery and resilience
  • Network Impact _ in particular voice and video
key requirements
Key Requirements
  • Active Directory
    • Windows Server 2003 Domain functional level. DCs W2k3 SP1+
    • If LCS or OCS R1. Global Settings may be in system container. If multiple domains suggest moving to config container before schema prep
  • Significant Certificate and DNS requirements which will be covered later
  • Hardware\OS 64 bit only
dns and certificates
DNS and Certificates
  • The supported SIP URIs drive the DNS and certificate requirements
    • For each domain supported DNS records and certificates are required
  • Typically the SIP URI is the same as a user’s e-mail address Eg
  • There are two clients Communicator and Live Meeting. Two Sets of DNS records for internal and external connection.
    • “;gruu;opaque=app:conf:focus:id385aa8ec0fcb4879dcb40c%3Fconf-key=JvrI7t324Vx”
  • Federation requires
  • Phone edition requires
access edge certificates
Access Edge Certificates
  • For PIC a single FQDN of the access edge is given and this is the primary name in cert. eg
  • Also for
  • Now for the server offering the service for can NOT be acp. but must be same domain as srv record. Eg This name needs to be added as a SAN to the certificate
example of edge server
Example of Edge Server
  • Cert Assigned to access Edge
    • Acp.
      • San, etc
  • Cert Assigned to web edge
  • Cert Assigned to av ege
  • Cert Assigned to intranet edge
    • Edge. (Can be internal cert. NB HLB etc)
example of director
Example of Director
  • When deployed
  • Similar to the access edge role a cert is required with typically multiple SANs
  • Primary cert name is that of pool
  • Then for each domain _sipinternaltls._tcp. will point to sip.
  • will point to
deploying edge servers
Deploying Edge Servers
  • Decide on redundancy requirements, dr.
  • Capacity will drive minimum number
  • Co-locate all roles unless a good reason not to do so
  • For single edge box it is acceptable to have a NATed AV edge server (public ip)
  • For load balanced edge boxes the AV edge public IP must not be NATed
  • The intranet IP must never be NATed but must be routable
install steps
Install Steps
  • Install files, activate, choose roles, account, configure IP and names,
directors are they required
Directors _ Are they required
  • No…
  • But they are recommended
role of director
Role Of Director
  • Internally
    • When multiple pools deployed
    • Deterministic Client Connection. Re-directs clients
    • Only point where multiple SANs required
  • From Outside
    • Next hop from access edge
    • Authenticates users before proxying on data