Deploying Office Communications Server 2007

at Indiana University
Matt Dixon
December 12, 2007

UNIVERSITY INFORMATION TECHNOLOGY SERVICES

Deploying OCS 2007 at IU

Agenda
Why OCS at IU? Project Methodology Building the OCS Infrastructure Phone Switch Integration Details Essential Tools Lessons Learned

Deploying OCS 2007 at IU

Why OCS at IU?

Causal Factors Declining student phones in residence halls Campus saturated with mobile devices
Faculty & Staff increasingly mobile Students disconnected from campus telephony

Diminishing office & meeting room space Physically dispersed, time shifted work force Overloaded Email storage Cost of supporting multiple vendor solutions:
Email Voicemail IM & conferencing

Pressure from many directions to move to VoIP

Deploying OCS 2007 at IU

Why OCS at IU?

Addressing the Issues Merged operations under one Director
Voice, data, video, messaging Targeted unified communications, not just VoIP

Assembled a technical working group

Monthly meetings to discuss vendor options Considered proprietary & open source solutions Established test environments for various solutions

Still Could not come up with a viable solution

en Th

Microsoft and Nortel form Innovative Communications Alliance

July 2006 Announcement:

Deploying OCS 2007 at IU

Why OCS at IU?

Benefits of the Innovative Communications Alliance Successful history with Nortel & Microsoft Leverages existing skill sets & institutional knowledge
Advanced knowledge of Nortel systems Experienced group of Windows Server & Exchange engineers

Allows merging of campus IP switching onto one platform with Geo Redundancy Supports legacy phone environment
Handset (TDM) phones will be in place for several years Opens up multiple migration paths to VoIP

Deploying OCS 2007 at IU

Why OCS at IU?

Benefits of the Innovative Communications Alliance (Continued) Merges two primary business tools at the desktop
35,000+ Phone lines 34,000+ Exchange mailboxes MS Office is widely used, Outlook calendaring is critical

Provides a robust set of communication tools

Instant Messaging & Presence Awareness Full featured soft phone
Audio / Video Calls Call control features

Live Meeting web conferencing

Deploying OCS 2007 at IU

Why OCS at IU?

Phone Switch Upgrade

Legacy switch hardware

Bloomington Campus: Aging DMS100 Centrex
Limited VoIP capabilities Needed to purchase, convert to SL100

Indianapolis Campus: Nortel SL100

Current software release Self-owned, easy to upgrade

Merged two switches into one Nortel CS2100 with Geo-redundancy

Deploying OCS 2007 at IU

Why OCS at IU?

Rich Client Feature Set

oInstant Messaging (including groups) oEnhanced Presence Awareness oDirectory (GAL) Integration oFile Transfers oVideo Calls oEnterprise Voice \ Call Control
Multiparty Calls Call Hold Call Transfers Call Forwarding Simultaneous Ring with Phone

oSchedule Conferences oLaunch IM within Email oCall all Message Recipients

oAd-hoc Web Conferencing oQ&A Panel oAttendee Polling (survey) oDesktop & Application Sharing oRecord Meeting Content

Deploying OCS 2007 at IU

Why OCS at IU?

Additional Clients
oInstant Messaging oManage Contacts oAudio & Video Calls oFile Transfers oUses Global Address List oBonjour Support oRequires Mac OS X 10.4.10 or above

oInstant Messaging oEnhanced Presence oManage Phone Settings oOption for Forms-based Logon oSupported Browsers:
IE 6 & 7 Firefox 2.0 and later Safari 2.0.4

oInstant Messaging oEnhanced Presence oManage Contacts oMake Calls oSupported on Windows Mobile 5 & 6

Deploying OCS 2007 at IU

Project Methodology - Timeline

Phase Details Procure and install server hardware Phase I: Build Backend Infrastructure (June Sept 2007) Install OCS Public Beta for design testing Install Nortel CS2100 Install Production Ready OCS 2007 RTM version

Phase II: Phone Switch Integration (Oct 2007) Phase III: Pilot Testing (Dec 2007)

Upgrade Nortel CS2100 to OCS capable version SE10 Test all OCS Enterprise Voice features

Prepare Office Communicator client distribution package Normalize Active Directory primary phone numbers Engage high ROI pilot test groups Automate OCS account creation & removal processes Develop client support documentation Develop end-user training programs

Phase IV: General Deployment of Finalize support documentation Implement end-user training programs OC\Live Meeting clients (Jan Begin Office Communicator \ Live Meeting rollout 2008)

Deploying OCS 2007 at IU

Project Methodology Team Roles

Role
Executive Sponsor

Responsibilities
Ensures the relevance of the project Establishes objectives and constraints Helps to secure funding Communicates benefits and goals to upper managers (Champion)

Project Manager

Responsible for coordination of the overall project Defines and publishes the Project Statement, including:

Brief Summary Objectives Milestones Invites Consultants & Representatives as required Maintains and communicates the overall Project Plan, which includes: Master schedule of target dates Based on input from Team Leaders Task priorities Task owners Task progress indicators Task dependencies

Chairs weekly meetings with Project Team Leaders

Communicates overall project status to upper managers

Ensures teams have the required resources Keeps project within the scope of the objectives Plans contingencies as needed

Continued

Deploying OCS 2007 at IU

Project Methodology Team Roles

Role Infrastructure Team Leader

Responsibilities
Responsible for server infrastructure deployment tasks, such as: Prototype, performance & pilot testing Defining server topology Ensuring integration with telephony components Identifying server hardware\software requirements Server equipment installation Defining backup & fault tolerance strategies Planning the feature deployment path Preparing process & operations documentation Attends weekly meeting with Project Manager Gives update on teams activities Works with other Team Leaders as required

Infrastructure Team Member Executes tasks assigned by the Infrastructure Team Leader

Continued

Deploying OCS 2007 at IU

Project Methodology Team Roles

Role
Telephony Team Leader

Responsibilities
Responsible for telephony equipment deployment tasks, such as: Prototype, performance & pilot testing Defining telephony topology Ensuring integration with server components Identifying telephony hardware\server requirements Telephony equipment upgrades & installation Defining backup & fault tolerance strategies Planning the feature deployment path Preparing process & operations documentation Attends weekly meeting with Project Manager Gives update on teams activities Works with other Team Leaders as required

Telephony Team Member

Executes tasks assigned by the Telephony Team Leader

Continued

Deploying OCS 2007 at IU

Project Methodology Team Roles

Role
Marketing Team Leader

Responsibilities
Responsible for project communication tasks, such as: Develop general Communication Plan Identify target audiences Determine how to showcase new features Suggest optimal methods communication Plan and execute user community presentations Assist Project Manager with tools to communicate project status Attends weekly meeting with Project Manager Gives update on teams activities Works with other Team Leaders as required

Marketing Team Member

Executes tasks assigned by the Communications Team Leader

Continued

Deploying OCS 2007 at IU

Project Methodology Team Roles

Role
Training Team Leader

Responsibilities
Responsible for project training tasks, such as: Develop general Training Plan Identify groups that will require training Suggest optimal training methods, such as: Online media training Classroom Train the trainers Prepare required Knowledge Base articles Attends weekly meeting with Project Manager Gives update on teams activities Works with other Team Leaders as required

Training Team Member

Executes tasks assigned by the Training Team Leader

Continued

Deploying OCS 2007 at IU

Project Methodology Team Roles

Role
Digital Media Consultant Network Consultant

Responsibilities

Provide input on integration issues with Digital Media services Attend Project Meeting as required

Provide input on integration issues with Network services Assist Infrastructure Team with network performance analysis Attend Project Meetings as required

Security Consultant

Provide input on general security issues Perform threat analysis against all facets of the new service Attend Project Meetings as required

Identity Consultant

Provide input on account management issues, such as: Service activation Disabling the service Impact of renaming accounts Work with Infrastructure and Telephony Teams to plan account management processes Attend Project Meetings as required

Continued

Deploying OCS 2007 at IU

Project Methodology Team Roles

Role
Software Distribution Consultant

Responsibilities
Provide input on client deployment issues, such as: Operating System integration Client networking requirements Software installation troubleshooting Work with Infrastructure & Telephony Teams to determine optimal client software configuration settings Prepare the client software package for distribution Attend Project Meetings as required

User Community Representative

Represent the needs of various user communities, one from each: Faculty Students Staff Attend sharing sessions, product demonstrations & project update presentations Describe current needs as related to features of the new service Share ideas for beneficial usage scenarios with the project team Be an early adopter of the new technology Communicate experiences to others within the respective user community

Deploying OCS 2007 at IU

Building the OCS Infrastructure

1 Phone Switch Upgrade
(Nortel CS2100 w/SE10 load)

5 Installed Load Balancers 6 Configured OCS Pool & Install Front-end servers 7 Installed Web & A/V Conferencing Servers 8 Installed Mediation Server
M ed ia Ga tew ay ( IW - SPM )

2 Extended Active Directory Schema 3 Installed SQL 2005 Cluster 4 Installed Archiving Server
(w/File Shares & SQL 2005)
PBX ( s )

Active Directory

O CS Me dia ti on S er ver

PSTN Network

SIP Gateway ( NGSS )

Internal IP Clients

Nortel Equipment
LAN Switch LB Subnet

IU Private Network

Lo ad Ba lancers ( Primary & Failover )

OCS Front - en d S er ver s ( with Web Components )

OCS Pool

SQL B ack - en d S erv er s

A / V C on fer en cin g Web C onf er enc in g Ser ve r Ser ve r

OC S A rc hiv in g & C DR Se rve r

Tr usted External Co mmunicator & Live Meeting Clients

Building the OCS Infrastructure (Edge)

Internet
P ubl ic IM S erv ic e Pr ovi de rs

Federated OCS Partner ( s )

LAN Switch

IU Public Subnet
LB Subnet

L oad B ala ncers ( Primary & Failover )

Access Edge Server ( s )

A / V Confe re nci ng Edge Se rve r ( s )

W eb Co nfe re nci ng Ed ge Se rv er ( s )

C omm un ica to r W eb Ac ces s Ser ve r ( s )

IS A HTT P Pr oxy S erv er ( s )

Campus Router

1 Install Load Balancers 2 Build ISA array (HTTP Proxy) 3 Install CWA Server 4 Install OCS Director

5 Install Access Edge Server 6 Install A/V Conf. Edge Server 7 Install Web Conf. Edge Server 8 Configure external access features

OCS Director ( s )

Deploying OCS 2007 at IU

Phone Switch Integration Details

Communicator to Telephone Call
OCS Mediation Server
R T P

Media Gateway ( Nortel IW SPM )

Ring!

R T P

SIP Session Progress

x-msrta 8000Hz (RTAudio)

P SI ss Se

G.711 PCMU 8000Hz PSTN Network

S P I S P I SI Se S IN P ssi S P I V Tr on P I O T I yi Pr B K E ng r og Y e ss E

SIP Trying SIP INVITE SIP OK SIP BYE

IN I V T E

OCS Front - end Servers

g yin Tr SIP SI P
Y E

ion ss re I og S P Pr O SI K
P

Phone Switch ( Nortel CS2100 )

SIP / CSTA Gateway ( Nortel NGSS )

Deploying OCS 2007 at IU

Essential Tools
Troubleshooting
OCS Best Practices Analyzer Network Packet Tracers OCS Logging & Snooper Communicator Log

Enterprise Voice Router Helper Address Book Normalization

ABS Configuration Tool ABServer.exe

OCS Account Management

Deploying OCS 2007 at IU

Essential Tools OCS Best Practices Analyzer

Deploying OCS 2007 at IU

Essential Tools Packet Tracing

Network Monitor 3.1

Wireshark

Deploying OCS 2007 at IU

Essential Tools OCS Logging & Snooper

Logging Tool

Debug Session Log Analyzer (Snooper.exe)

Deploying OCS 2007 at IU

Essential Tools Communicator Logging

Communicator log folder: [HOMEPATH]\tracing

Log file name: Communicator-uccp-0.uccplog

Deploying OCS 2007 at IU

Essential Tools Enterprise Voice Router Helper

Deploying OCS 2007 at IU

Essential Tools Address Book Overview

Deploying OCS 2007 at IU

Essential Tools Address Book Overview

OCS Client

Downloads latest AB to file named GalContacts.db via HTTPS Thru Virtual Directory to file share

NTFS File Share

Pushes optional phone numbers (e.g. Mobile, Home)

Pushes AB data to the share as .dabs and .lsabs files on regular schedule

Sends some attributes to backend SQL DB

Normalizes Phone Numbers

OCS Front - end Servers

User Replicator pulls AD attributes (e.g. sn, givenName title, telephoneNumber)

Active Directory

OCS Back - end SQL

( Running

Address Service )

Book

Deploying OCS 2007 at IU

Essential Tools Address Book Normalization

Attempts to translate numbers to E.164 format, such as:
(812) 555-1234 to +18125551234 51234 to +18125551234

Uses regular expressions Create the customized rules file in the address book folder:
Company_Phone_Number_Normalization_Rules.txt

Deploying OCS 2007 at IU

Essential Tools Address Book Normalization

ABSConfig.exe from the OCS 2007 Resource Kit

Activate the custom rules

Deploying OCS 2007 at IU

Essential Tools Address Book Normalization

Use the ABServer.exe command switches What rules are in effect?
ABServer.exe -dumpRules

Will a phone number normalize?

ABServer.exe testPhoneNorm (812) 5551212

Want to force an ABS synchronization?

ABServer.exe syncNow

Deploying OCS 2007 at IU

Essential Tools Account Management

Methods of Enabling OCS Users 2
Option Explicit Dim ADSI string=

Active Directory Users 1 & Computers OCS Snap-in (Manual)

HR / Bursar Mgmt System

ADSI Script

3
MS Identity Lifecycle Mgmt Server

Telecom Work Order System

Modifies ~10 User Object Attributes

Add Phone Line Feature

Active Directory

Phone Switch

Deploying OCS 2007 at IU

Essential Tools Account Management

OCS Active Directory User Object Attributes
Sample Value
sip:username@indiana.edu smtp:username@indiana.edu sip:username@indiana.edu CN=LC Services,CN=Microsoft, CN=unicom, CN=Pools, CN=RTC Service,CN=Microsoft, CN=System, DC=ads,DC=iu,DC=edu TRUE FALSE TRUE 12

Attribute
proxyAddresses msRTCSIP-PrimaryUserAddress msRTCSIP-PrimaryHomeServer

Description
Users SIP URI added to recipient addresses (Multi-valued Unicode string) Users OCS sign-in name (Unicode string) Users assigned OCS server or pool (Distinguished name)

msRTCSIP-UserEnabled msRTCSIP-FederationEnabled msRTCSIP-InternetAccessEnabled msRTCSIP-ArchivingEnabled

OCS features enabled \ disabled (Boolean) Federation enabled \ disabled (Boolean) Remote user access enabled \ disabled (Boolean) Bit mask for setting archiving options:
0000 (0) = No archiving or use global default setting 0100 (4) = Archive internal IM conversations 1000 (8) = Archive federated IM conversations

Deploying OCS 2007 at IU

Essential Tools Account Management

Attribute
msRTCSIP-Line msRTCSIP-LineServer msRTCSIP-OptionFlags

OCS Active Directory User Object Attributes (Continued)

Sample Value
tel:+18125551212 sip:grp=IULBR;pw=xxxx;IULBR@scai 896

Description
E.164 normalized Line URI of the users telephony device (Unicode string) SIP URI that matches a route to the SIP Gateway server (Unicode string) Bit mask for various user options:
00000000001 (1) = Enable Public IM connectivity 00000010000 (16) = Enable Remote call control (RCC) 00001000000 (64) = Allow user to organize meetings with anonymous participants 00010000000 (128) = Enable Enterprise Voice 00100000000 (256) = Enable Enhanced Presence 01000000000 (512) = Enable Enterprise Voice with PBX integration (aka RCC Dual Mode) 10000000000 (1024) = Enable as an auto-attendant number

Deploying OCS 2007 at IU

Lessons Learned - Building the OCS Infrastructure

Determine Load Balancer Type
DNAT vs. SNAT (SNAT preferred)

Thoroughly research certificate requirements

Understand Subject Alternate Names (SANs)
Use UC certs from an approved partner (MS KB 929395)

Mark all certs as exportable Include client EKU in requests in MTLS certs

Know the required Port Numbers!!!

Test through Firewall, Load Balancer & IPSec Filters

Use the Validation Wizard after each step Get to know the LcsCmd.exe & Resource Kit utilities

Deploying OCS 2007 at IU

Lessons Learned Telephony Integration

Study your telephony Dial Plan
Be prepared to modify your PBX Dial Plan

Normalize Phone Numbers right in Active Directory (E.164 format) Review new Call Detail Records (CDR)
May need to address billing processes

Watch Voicemail rollover ring time

Could affect Simultaneous Ring or Forward to

No Emergency 911 support from OC client

Consider having users sign a waiver document

Headset / mic / webcam features & form factors

Test & publish a short list of recommend devices

Deploying OCS 2007 at IU

Lessons Learned Project Methodology

Senior management support a necessity Telecom Techs are your new best friends!!! Engage deep dive PBX vendor support Target Highly Communicative pilot groups
Registrar, Bursar, Financial Aid, Researchers, etc.

Use department specific, real world demos to generate enthusiasm Develop business case based on new value, not cost savings

Deploying OCS 2007 at IU

QUESTIONS?