tandberg telepresence and video conferencing with microsoft

Solution Guide TANDBERG Telepresence and Video

Conferencing with Microsoft Office Communications Server 2007 R2

D1459101

January 2010

TANDBERG Telepresence and Video Conferencing with Microsoft Office Communications Server 2007 R2

© 2010 TANDBERG of 67

Contents 1 Executive summary ......................................................................................................7

2 Business benefits .........................................................................................................8

3 Visual communications network components...........................................................9 3.1 Video conferencing endpoints....................................................................................................... 9 3.2 Video conferencing infrastructure ................................................................................................. 9

3.2.1 Call control and management.......................................................................................... 10 3.2.2 Services ........................................................................................................................... 10

4 TANDBERG integration with Microsoft Office Communications Server 2007 (R2)......................................................................................................................................12

4.1 Background ................................................................................................................................. 12 4.2 Mobility – PC video peripherals................................................................................................... 12 4.3 Small scale integration (Individual registration model)................................................................ 13 4.4 Comprehensive Video Integration (CVI) ..................................................................................... 14

4.4.1 The benefits ..................................................................................................................... 14

5 Individual registration model details.........................................................................17 5.1 Individual registration benefits..................................................................................................... 17 5.2 Solution capabilities..................................................................................................................... 17

5.2.1 Endpoint configuration ..................................................................................................... 17 5.2.2 Authentication & registration............................................................................................ 18 5.2.3 Presence/Search/Instant Messaging............................................................................... 18

5.3 Security ....................................................................................................................................... 20 5.4 Individual registration model call scenarios ................................................................................ 20

5.4.1 Office Communicator to video conference room system................................................. 20 5.4.2 Personal system (MPOP) calling scenario ...................................................................... 22 5.4.3 Escalation ........................................................................................................................ 23 5.4.4 Multiparty calling with TANDBERG endpoints................................................................. 23 5.4.5 Office Communicator call features................................................................................... 24

5.5 Management and directories....................................................................................................... 25 5.6 Individual registration model limitations ...................................................................................... 26

5.6.1 Password management limitations.................................................................................. 26 5.6.2 Bandwidth management limitations................................................................................. 27 5.6.3 Limited interoperability..................................................................................................... 27

5.7 Products supporting Individual registration ................................................................................. 29

6 Comprehensive Video Integration - details ..............................................................30 6.1 SIP trunk base functionality......................................................................................................... 30

6.1.1 Security ............................................................................................................................ 31 6.1.2 Presence/Contact search ................................................................................................ 33 6.1.3 Basic SIP trunk summary ................................................................................................ 34

6.2 SIP trunk advanced capabilities – OCS Relay............................................................................ 34 6.2.1 Simplified password management - Authentication/authorization................................... 36 6.2.2 Presence/Contact search ................................................................................................ 37

6.3 Integrated architecture - VCS considerations ............................................................................. 38



7 CVI use cases..............................................................................................................40 7.1 Office Communicator to video conference room system ............................................................ 40 7.2 Personal system (MPOP) calling scenario.................................................................................. 42 7.3 Office Communicator to/from external H.323/SIP video system calling (Expressway) .............. 43 7.4 Escalation.................................................................................................................................... 45 7.5 Office Communicator call features .............................................................................................. 46 7.6 Multiparty calling with TANDBERG endpoints ............................................................................ 47 7.7 Office Communicator to/from ISDN video calling........................................................................ 48

7.7.1 Outbound calling from Office Communicator to an ISDN video system.......................... 48 7.7.2 Inbound calling to Office Communicator from an ISDN video system............................. 49

7.8 Audio calling to/from video endpoints via an Office Communications Server audio gateway/PBX..................................................................................................................................................... 50

7.9 Telepresence............................................................................................................................... 50 7.10 Conferencing ............................................................................................................................... 52

7.10.1 Conferencing background................................................................................................ 52 7.10.2 Conferencing call scenarios............................................................................................. 54 7.10.3 Call policy enforcement - bandwidth limited calls ............................................................ 57

8 Deployment preparation.............................................................................................59 8.1 Required TANDBERG software versions ................................................................................... 59 8.2 Required Microsoft software versions......................................................................................... 59

9 Solution limitations.....................................................................................................60 9.1 Calling scenarios not supported.................................................................................................. 60 9.2 Additional know limitations .......................................................................................................... 60

10 Understanding HD video calling with Office Communicator ..................................61

Appendix A: Roadmap.....................................................................................................62

Appendix B: VCS details .................................................................................................63

Appendix C: References..................................................................................................64

Appendix D: About TANDBERG .....................................................................................65

Appendix E: VCS SIP trunk and OCS to PBX integration ............................................66

Disclaimers and notices ......................................................................................................67

Figures Figure 1: TANDBERG PrecisionHD USB Camera........................................................................... 12 Figure 2: TANDBERG PrecisionHD USB camera FOV vs. Consumer camera FOV ...................... 13 Figure 3: Small Scale Video Integration........................................................................................... 13 Figure 4: Comprehensive Video Integration – Simplified network diagram.................................... 14 Figure 5: Enabling AD account for Communications Server............................................................ 18 Figure 6: Enhanced 2007 Presence model setting for TANDBERG endpoints ............................... 18 Figure 7: TANDBERG conference room systems in the Office Communicator Contact list............ 19 Figure 8: Multiple device support ..................................................................................................... 20 Figure 9: Example error response when sending IM to a TANDBERG endpoint ............................ 20 Figure 10: Calling from Office Communicator .................................................................................... 21 Figure 11: Example of a contact in the directory on TANDBERG MXP endpoints ............................ 21 Figure 12: Office Communicator to/from conference room calling .................................................... 22 Figure 13: Personal video system (MPOP) calling scenario.............................................................. 23 Figure 14: Office Communicator in a multiparty call hosted on a TANDBERG MXP ........................ 24 Figure 15: Example call forwarding rule screen for Office Communicator......................................... 24 Figure 16: Example Office Communicator Transfer Call screen........................................................ 25 Figure 17: Example screen shot for enabling Enterprise Voice......................................................... 25 Figure 18: TMS and video conferencing system directories.............................................................. 26 Figure 19: Individual registration model call limitations – H.323 calling............................................. 28 Figure 20: Video conferencing to Office Communications Server integration – AD accounts not

required ............................................................................................................................. 31 Figure 21: OCS Relay – Conference room model ............................................................................. 35 Figure 22: OCS Relay – Personal system and single identity support .............................................. 36 Figure 23: OCS Relay and presence aggregation ............................................................................. 38 Figure 24: VCS architecture options .................................................................................................. 38 Figure 25: Example CVI architecture ................................................................................................. 40 Figure 26: Calling from Office Communicator .................................................................................... 41 Figure 27: Office Communicator to/from conference room calling .................................................... 41 Figure 28: Example of a contact in the directory on TANDBERG MXP endpoints ............................ 42 Figure 29: Personal video system (MPOP) calling scenario.............................................................. 43 Figure 30: Home office worker video conference system connectivity .............................................. 44 Figure 31: External organization video conference connectivity by URI dialing ................................ 44 Figure 32: External organization video conference connectivity by IP dialing ................................... 45 Figure 33: Office Communicator call forwarding rule set example .................................................... 46 Figure 34: Office Communicator Transfer Call example.................................................................... 47 Figure 35: Example screen shot for enabling Enterprise Voice......................................................... 47 Figure 36: Office Communicator in a multiparty call hosted on a MXP endpoint............................... 48 Figure 37: Calling ISDN video systems from Office Communicator .................................................. 49 Figure 38: Calling Office Communicator from an ISDN video system ............................................... 50 Figure 39: Office Communicator in a call with the TANDBERG Telepresence solution.................... 51 Figure 40: Telepresence integrated with Office Communications Server.......................................... 51 Figure 41: TANDBERG T3 Telepresence System............................................................................. 52 Figure 42: Active speaker view .......................................................................................................... 53 Figure 43: Four-way continuous presence......................................................................................... 53 Figure 44: 7+1 continuous presence.................................................................................................. 54 Figure 45: Adding Office Communicator users when scheduling a multiparty conference in TMS... 55



Figure 46: Example TMS confirmation message with connection information .................................. 55 At the time of booking TMS verifies that the necessary conferencing resources will be available at the

scheduled time and reserves these resources. ................................................................ 55 Figure 47: Example Contact list with a group of virtual meeting rooms............................................. 56 Figure 48: Main office and branch office connected with a bandwidth policy in place ...................... 58



Revision history Date Version & change information January 2010 Initial Release

Copyright © TANDBERG 2010. All rights reserved. This Solution Guide may not be copied, photocopied, translated, reproduced, or converted into any electronic or machine-readable form in whole or in part without prior written approval of TANDBERG. TANDBERG reserves the right to revise this documentation and to make changes in content from time to time without obligation on the part of TANDBERG to provide notification of such revision or change.

TANDBERG provides this documentation without warranty, term, or condition of any kind, either implied or expressed, including, but not limited to, the implied warranties, terms or conditions of merchantability, satisfactory quality, and fitness for a particular purpose. TANDBERG may make improvements or changes to the product(s) and/or the program(s) described in this documentation at any time. All other product and company names herein may be trademarks of their respective owners.

The software incorporated in this product is owned by Tandberg Telecom AS or its licensors. By using this product you agree to abide by the End User License Agreements for this product, which can be found at www.tandberg.com. Patent, copyright and other information related to this product can also be found at that location.

http://www.tandberg.com/



1 Executive summary Unified Communications (UC) is broadly understood as the seamless integration of communications devices, modalities and capabilities for the individual user; allowing the user to have a single identity rather than a myriad of device identities. Visual communications is among the key communications modes within the UC ecosystem. As organizations begin to evaluate and plan for the deployment of UC solutions, visual communications becomes a key driver to implementation. TANDBERG is the industry leader in visual communications solutions. TANDBERG’s video first, open approach to UC leverages deep integrations with other UC desktop, voice, and network solutions resulting in an end-to-end visual UC solution that works for everyone in the organization —with quality that is absolute. This document focuses on TANDBERG’s open and integrated approach to enabling a visual UC environment with Microsoft Office Communications Server 2007 (R2). This is more than just making a typical video conference room work with a Microsoft Office Communicator client; it enables an organization’s video conferencing assets to work seamlessly with the broader UC environment and enables a user to have one identity in a common corporate directory/phone book, while having the freedom and flexibility to communicate with a wide range of devices in a variety of environments. The TANDBERG approach to Microsoft Office Communications Server integration maximizes ROI by allowing organizations to:

• Support existing investments in standards-based video conferencing systems.

• Migrate existing video conferencing assets into the UC environment with minimal disruption to both the video conferencing deployment and the rest of the communications environment.

• Enable Microsoft Office Communicator users to take advantage of the advanced functionality of the video conferencing network, while maintaining seamless connectivity with the rest of the UC environment.

This document:

• Outlines how the TANDBERG integration with the Microsoft Office Communications Server can leverage the latest advances in video conferencing technology such as Telepresence and High Definition (HD1) video quality.

• Explains how to integrate an existing deployment of TANDBERG or other standards-based video conferencing technology in a range of installations, from the simple to the more comprehensive:

• HD video and the PC

• Desktop video appliances

• Conference room video conference systems

• Multiparty video conferencing

• Cross network connectivity

• Business to business (B2B) connectivity

• Telepresence connectivity 1 For purposes of this document HD means 720p, unless specified otherwise. This convention is used because 720p is the maximum video resolution supported by the Microsoft Office Communicator client. It is important to note that the TANDBERG solution can support up to 1080p.



2 Business benefits The migration from VoIP allowed the telephony service to be provided over the data network. This predominantly benefitted the IT administrator because there was only one network to manage for both voice and data, and simplified moves/new users/configuration changes because moving the CEO’s phone extension became a matter of unplugging the phone and connecting it to the data jack in a new office. While that provided time and cost savings to the IT administrator, the end user experience was fundamentally unchanged; one phone was replaced for another, but the user was still only able to make audio calls. Communicating visually is the “New Way of working”. It delivers on the promise of Unified Communications providing end users a transformative communications experience changing a one dimensional conversation into a multifaceted collaboration experience. Two key attributes of UC:

• Presence: presence is the “dial tone” of UC. Presence allows users to see the status (for example, online, free or busy) of the people they are trying to reach and allows them to take action based on this information. Presence changes how, who and when we reach someone thereby making the communications process more efficient, it is not your Grandmother’s dial tone any more.

• Video: video changes how we actually communicate and allows users to communicate more effectively, as proven in study after study. In today’s competitive landscape in which organizations are not only trying to reduce travel and their overall carbon footprint, but also to do more with less, visual communications allows organizations to implement “Green Initiatives” via tele-work; to improve productivity with more effective meetings and individual conversations, and to engender a more tightly-knit workforce. Visual communications is bringing back the sense of community and camaraderie in the ever expanding global work environment, resulting in a more efficient, effective and productive workforce.

UC combines productivity drivers such as presence and visual communications with more traditional and familiar communications tools such as voice and web collaboration in an effort by businesses and organizations to stay ahead in today’s global economy. The ability to tie these communications channels into a combined and seamless experience for the end user is just the first step; ultimately the UC experience becomes interwoven with typical end users’ business processes. Microsoft Office Communications Server 2007 R2 is a platform for UC which provides a couple of the key elements. Combine this with the TANDBERG visual communications solution and you have the major components needed to build the unified communications solution being demanded by the end user.



3 Visual communications network components This chapter provides an overview of the components in a comprehensive visual communications network. For further detail, see the TANDBERG web site (www.tandberg.com).

3.1 Video conferencing endpoints Video conferencing endpoints are purpose-built hardware appliances used for “video conferencing”; often, they are completely integrated packages including the screen(s), camera(s) and microphone(s) in addition to the actual “engine”, which is know as the “codec”. These are always-on IP solutions which do not require a PC to operate. There are three categories: Personal systems: examples shown: TANDBERG E20 and TANDBERG MXP 1700

Conference room systems: examples shown: TANDBERG Dual 52” Profile, TANDBERG C90 Codec, TANDBERG C60 Codec, and TANDBERG C20 Codec

Telepresence systems: examples shown: TANDBERG Immersive T3, TANDBERG Immersive T1)

Industry Products: examples shown: TANDBERG Intern MXP, TANDBERG FieldviewTM, TANDBERG Tactical MXP)

3.2 Video conferencing infrastructure Most communications solutions include network components that the end-user does not see that make them function; for example, a PBX allows phones in an office to work. Equally, the video


http://www.tandberg.com/personal-video-conferencing.jsp

http://www.tandberg.com/video-conferencing-products.jsp

http://www.tandberg.com/telepresence/

http://onetandberg/C2/Telepresence T1/T1 InUse Images/Forms/DispForm.aspx?ID=21

http://www.tandberg.com/video-conferencing-industry-applications.jsp

http://onetandberg/C18/Intern/Image Library/Forms/DispForm.aspx?ID=9

http://onetandberg/C1/Tactical/Image Library/Forms/DispForm.aspx?ID=4

http://onetandberg/C2/Telepresence T1/T1 InUse Images/Forms/DispForm.aspx?ID=21

http://onetandberg/C18/Intern/Image Library/Forms/DispForm.aspx?ID=9

http://onetandberg/C1/Tactical/Image Library/Forms/DispForm.aspx?ID=4



conferencing endpoints described in the previous section rely on a series of infrastructure components, enabling a scalable and manageable deployment with additional services beyond those capable with the endpoints alone.

3.2.1 Call control and management The TANDBERG infrastructure products which provide call control and management are the Video Communications Server (VCS) and the TANDBERG Management Suite (TMS). TANDBERG Video Communications Server (VCS) - this appliance-based server provides:

• H.323 gatekeeper

• SIP registrar/proxy

• Protocol interworking

• Secure B2B connectivity

• Microsoft Office Communications Server interconnect

• PBX trunking

• Call control and bandwidth management

• Call routing

TANDBERG Management Suite (TMS) - even with TANDBERG or other vendors’ endpoints registered individually to Office Communications Server, a software management platform is needed to manage these devices. TMS functionality includes:

• Management

• Monitoring

• Maintenance

• Scheduling

• Common directories

• Call Detail Records

• Software updates

3.2.2 Services Additional core infrastructure products enable services such as:

• Multi-party conferencing between Office Communicator and the standards-based video conferencing environment.

• The ability to record calls from Office Communicator

• Connectivity between Office Communicator and ISDN-based video conferencing devices. A few examples of the TANDBERG network products that provide these services are: TANDBERG product family of Multipoint Conferencing Units (MCUs): An MCU enables multiple video conferencing endpoints (including Office Communicator clients) to meet together in a conference in which all participants are able to see one another. Key features include:

• HD video support.

• Continuous presence – the ability to see all participants on one screen simultaneously.

http://www.tandberg.com/video-conferencing-network-infrastructure/video-communication-server.jsp

http://www.tandberg.com/video-telepresence-management.jsp

http://www.tandberg.com/video-conferencing-multipoint-control.jsp



• Individual transcoding - important in mixed endpoint environments, by allowing all users in the conference to have the best possible experience.

• ClearVision – the ability to provide better video quality than that actually received from the endpoint (making low quality video connections look better).

TANDBERG Telepresence Server: An application-specific MCU enabling multiparty telepresence conferences including standards based telepresence conference rooms and multivendor video conferencing endpoints (including the Office Communicator client). TANDBERG ISDN Gateway: A gateway for ISDN-based video conferencing endpoints that allows IP-only devices, including Office Communicator clients to connect to ISDN-only devices. TANDBERG Content Server (TCS): A network-based recording and streaming solution allowing the recording and streaming of any video conference session, including Office Communicator clients. It also allows any video conferencing endpoint, including an Office Communicator client, to become a studio for creating recordings for purposes such as a team announcement. TCS allows for integration with SharePoint making it easy to leverage any video conference system to create and publish content into SharePoint.

For a complete list of TANDBERG infrastructure products, see the TANDBERG web site: www.tandberg.com

http://www.tandberg.com/telepresence-products/tandberg-telepresence-server.jsp

http://www.tandberg.com/video-conferencing-network-infrastructure/ip-isdn-video-conference.jsp

http://www.tandberg.com/video-conferencing-network-infrastructure/multimedia-content-server.jsp




4 TANDBERG integration with Microsoft Office Communications Server 2007 (R2)

4.1 Background UC provides seamless connectivity between the PC-based communications paradigm and the current and evolving visual communications landscape. The integration of high quality visual communications with tools such as IM and presence elevate the level and quality of communications, enabling greater productivity. The Microsoft UC solution based on Office Communications Server 2007 R2 is a platform for scalable PC-based communications encompassing, instant messaging (IM), presence, voice calling, video calling, conferencing and collaboration - tightly integrated into other Microsoft business productivity applications such as the Exchange, SharePoint and Office. The Office Communications Server platform provides two main user clients, the Office Communicator client and the LiveMeeting client. This document focuses on the interoperability of the video conferencing environment with the Office Communicator client. It showcases how TANDBERG is able to support a range of Office Communications Server deployments, from the smallest to the largest, with a variety of solutions suited to customer needs:

• Mobility – PC video peripherals

• Small scale integration – Individual registration

• Comprehensive video integration – Gateway approach Each one is discussed in greater detail in the rest of this chapter.

4.2 Mobility – PC video peripherals Users of video are demanding that communication from the conference room and on the road is clear, reliable and effective. TANDBERG’s PrecisionHDTM USB Camera is the best in its class of enterprise-grade USB cameras and the first camera providing true 720p widescreen format video at 30fps to be certified as Optimized for Microsoft Office Communicator. When used with Office Communications Server 2007 R2 and the Office Communicator client, the camera enables users to maximize their video communications in business-quality HD and with superior audio capabilities; meaning they can connect with clarity and purpose anywhere, anytime providing mobility of business quality communications.

Figure 1: TANDBERG PrecisionHD USB Camera The camera was also designed to provide a view of the user suitable for today’s demanding business communications environment. The following images show the same user at the same distance from a typical consumer-grade camera and from the enterprise-grade TANDBERG PrecisionHD USB camera, illustrating how the TANDBERG camera enables more effective communication.

http://www.tandberg.com/video-conferencing-telepresence-peripherals/hd-usb-camera.jsp





Figure 2: TANDBERG PrecisionHD USB camera FOV vs. Consumer camera FOV Consumer-grade web cameras tend to have a wide field of view (FOV) resulting in much of the transmitted image being of the user’s surroundings rather than of the actual individual when sitting a normal distance from the camera. The PrecisionHD USB camera has an optimized field of view resulting in a more favorable image of the user. Often in PC-based visual communications, the size of the display dedicated to the video image is only a portion of the total screen real estate; therefore it is critical for the image in the video window be optimized to see the far end participant’s facial features and expressions. This improves the “in person experience” provided by communicating visually, as well as reducing “meeting strain”.

4.3 Small scale integration (Individual registration model) For those customers that want to use video conferencing on a slightly larger scale than just the PC and the Office Communicator client, TANDBERG provides the MXP range of TANDBERG endpoints and the TANDBERG E20 endpoint that can register individually with Office Communications Server. This makes it convenient and easy for small organizations to introduce TANDBERG video conferencing systems into their deployment of video-enabled Office Communicator users.

Figure 3: Small Scale Video Integration

Example registration: All devices register directly with the Office Communications Server

MXP

MXP

E20

Office Communicator

Client

TANDBERG enterprise camera field of view Typical consumer camera field of view



This type of small scale integration is often referred to as “Individual registration”. Office Communicator users can search for these systems, add them as contacts in their Contact list and call them in exactly the same way that they do any other Office Communicator user. A benefit is that no additional equipment is needed, although it is important to note this can limit the overall function/capabilities of the video conferencing network. For details about the Individual registration model see chapter 5.

4.4 Comprehensive Video Integration (CVI) For small installations (typically 10 or fewer video conferencing endpoints) that do not need full video functionality the Individual registration model is acceptable. An environment with typically 10 or less video conferencing endpoints is manageable without additional infrastructure components to manage, maintain and support it. However, for deployments with additional video conferencing systems and infrastructure, TANDBERG strongly recommends an alternative to the Individual registration model which provides a fully-featured video conferencing environment that can also be integrated into the Office Communications Server. Full scale or Comprehensive Video Integration (CVI) is the joining of the TANDBERG Total Solution with the Microsoft Office Communications Server 2007 (R2) environment. This integration is based on the TANDBERG Video Communications Server (VCS) acting as a gateway, thereby providing a SIP trunk between the fully functioning video conference environment and Office Communications Server. This provides the richest feature set on the market of any video integration with Office Communications Server. The benefits of this integration model are explained below and the model is described in detail in chapter 6.

Figure 4: Comprehensive Video Integration – Simplified network diagram

4.4.1 The benefits Bandwidth management Often referred to as Call Admission Control (CAC), the VCS has comprehensive bandwidth management features which are essential to deploying a robust, reliable video conferencing network: it manages the bandwidth for video calls between the two environments (in addition to the bandwidth for calls within the video conferencing environment). Single identity – call forking An important attribute of the Office Communications Server environment is its support of a Single Identity. This is also a very important attribute of call forking and the FindMe functionality in VCS. VCS supports the Office Communications Server call forking model and extends it allowing users to have multiple video conferencing devices in addition to their Office Communicator client/devices. Further, the VCS allows users to configure and control which of these devices ring

Video

Conferencing

Environment

VCS

SIP TRUNK

Office

Communicator

Environment



when their Office Communicator address is called. VCS makes it very easy to enable the single identity concept with both TANDBERG and 3rd party video conferencing endpoints. Protocol interworking There are two main voice and video over internet protocols, H.323 and SIP. Office Communications Server supports SIP, traditional endpoints (many of which only support H.323) a converter between SIP and H.323 is required. The VCS is such a converter providing interworking between the SIP and H.323 signaling protocols allowing Office Communicator to connect individually to H.323 (“traditional”) video conferencing devices without the need for additional video conferencing components such as a multipoint control unit (MCU). In the TANDBERG integration with Office Communications Server an MCU is only used when a conference is actually needed. Password management VCS is treated as a trusted host to Office Communications Server; video conferencing devices registered to VCS benefit from this and do not need to be individually authenticated to the Office Communications Server. This is a big benefit for administrators when maintaining their password management policies minimizing potential administrative issues. Advanced conferencing experience The Multiway functionality of VCS is available when there is a TANDBERG Codian MCU in the network. The Multiway conferencing service allows TANDBERG endpoints to easily escalate a point-to-point video call to a multiparty conference by calling and connecting to additional users, including Office Communicator clients. 3rd party video conferencing support VCS supports standards-compliant 3rd party video conferencing equipment and therefore acts as a gateway for legacy endpoints and network devices to interoperate with Office Communications Server. The benefits of the VCS integration with Office Communications Server also apply to these 3rd party endpoints.

Business to Business (B2B) and remote worker video conference connectivity VCS supports the TANDBERG solution known as Expressway, an industry proven, open standard means of providing secure firewall traversal for audio and video media, easily enabling B2B, branch office and tele-worker connectivity. The TANDBERG integration with Office Communications Server allows Office Communicator users to transparently leverage the Expressway solution to connect with customers, partners and remote workers video conferencing systems. Presence enablement Typically, H.323 video conference systems do not publish presence. VCS has an internal presence engine which can create presence on behalf of video conferencing systems and solutions that would never be able to publish presence to Office Communications Sever on their own behalf. This is important because it allows:

• The user to know whether a remote party is available for conferencing or engaged in a call.

• The Office Communicator experience to be transparent (identical) regardless of who or what the user is trying to reach.

Office Communications Server audio gateway/PBX integration interworking VCS enables advanced features such as digit manipulation for complex dial plan integration. For example, the VCS can enable video conferencing systems to call through an Office Communications Server environment which has been integrated with a PSTN audio gateway or PBX integration. By taking advantage of the Office Communications Server’s integration with the audio gateway/PBX, it allows the video devices to make and receive audio calls from the PSTN- or



PBX-based phones respectively and provides a greater ROI for the investment in the audio/PBX integration with Office Communications Server. The call scenarios covered in this document further highlight the benefits mentioned previously of leveraging a SIP trunk between Office Communications Server and the video conferencing environment via the TANDBERG VCS, providing the most feature rich video-enabled UC environment on the market.



5 Individual registration model details This chapter defines the current support for TANDBERG video conferencing systems to act as IP devices in an Office Communications Server environment. It also covers the benefit and limitations of the Individual registration model.

5.1 Individual registration benefits The Individual registration model allows Office Communications Server to enhance the overall visual communications capabilities of a UC solution by registering video conferencing endpoints directly to the Office Communications Server. This provides a low cost of entry to enable personal video conferencing appliances and conference room video conferencing systems to interoperate with the PC-based Office Communicator environment.

5.2 Solution capabilities

5.2.1 Endpoint configuration The following TANDBERG endpoints support the Individual registration model with Office Communications Server (R2).

• MXP (F software series)

• E20 (TE software series) The following summarizes the settings required on these endpoints (see the individual product manual for more detail).

• SIP Mode = On

• SIP Server Type = Microsoft

• SIP Address (URI) = SIP URI assigned to the AD account created for this device.

• Server Discovery = Manual

• Server Address = the address to the Office Communications Server

• Transport = TCP or TLS

• Verify TLS = Off

• SIP Authentication o Username = the login user name of the corresponding AD account. o Password = the corresponding password for the account

Tech Tip: If your Office Communications Server is deployed in a multi-forest domain, please enter your SIP authentication username as <username@DNSDomainName>. Note that the pre-Windows2000 format <domain\user> is not supported. To obtain your login username, open a command line prompt and enter the command “echo %USERDNSDOMAIN%”. The output of this command is your DNSDomainName.



5.2.2 Authentication & registration The endpoints use NTLMv1 authentication, and register to the Office Communications Server as if they were an Office Communicator client. Therefore a valid Active Directory account is required and it must be enabled for Communications Server.

Figure 5: Enabling AD account for Communications Server

5.2.3 Presence/Search/Instant Messaging The TANDBERG endpoints support the Office Communications Server 2007 Enhanced Presence model, which means that this does not need to be disabled when creating the user account. This setting can be found in the Front End server properties, the “Other Settings” option of the “Communications” tab.

Figure 6: Enhanced 2007 Presence model setting for TANDBERG endpoints



When registered to the Office Communications Server, the TANDBERG endpoints can:

• Publish presence. Three states are supported: o Offline o Available o In Call

• Support being searched from the Office Communicator client search field, like any other contact.

Conference room systems TANDBERG endpoints that are conference room systems can be thought of as autonomous “devices” and therefore have their own contact information. For example, the following figure shows several conference rooms added as contacts: the “Bellevue.Rainier” conference room is in a call, while the “SanFrancisco.Baybridge” conference room is online and available.

Figure 7: TANDBERG conference room systems in the Office Communicator Contact list

Personal systems TANDBERG endpoints in the Office Communications Server environment can also be personal systems. They can register with the same credentials as an existing Office Communicator user. Office Communications Sever supports the concept of Multiple Points of Presence (MPOP; the ability to register multiple “devices” with a given Office Communicator user. Office Communications Server is responsible for aggregating the presence from the multiple devices associated with a given individual and publishing one combined presence state. Therefore, with the Personal System model a user would not search for a “video conference system contact” but rather the individual they are trying to reach. This is explained further in the call scenarios section later in this chapter.



Figure 8: Multiple device support

Instant Messaging TANDBERG video conference systems are not designed to support Instant Messaging (IM). When an Office Communicator user tries to IM a contact which is a video conference system a message is displayed in the Office Communicator chat window.

Figure 9: Example error response when sending IM to a TANDBERG endpoint

5.3 Security There are two main protocols for securing a real time communications session in SIP: Transport Layer Security (TLS) and Secure Real Time Protocol (SRTP). TLS encrypts the SIP signaling stream while SRTP encrypts the actual audio and video media streams, preventing others from eavesdropping in on the actual audio/video call. The TANDBERG devices which register directly with Office Communications Server support interoperability with the Office Communications Server implementation of TLS and SRTP, ensuring that both signaling and media are encrypted. Tech Tip: Since the TANDBERG endpoints that register directly to Office Communications Server support interoperable SRTP, it is possible to leave the Front End Server policy setting to “Require Encryption”. Note this is the default out of the box setting with Office Communications Server 2007 R2.

5.4 Individual registration model call scenarios

5.4.1 Office Communicator to video conference room system To call from Office Communicator to a TANDBERG video conference room, users:

Bob’s office

Registration with OCS

Both the OC client and the 1700 MXP register to OCS as [email protected]

Bob has multiple devices associated with him, however he appears as a single contact in the Contact list



• Search for the conference system, if it is not already in the user’s Contact list.

• Right-click on the conference room system contact.

• Start video call.

Figure 10: Calling from Office Communicator When users in the conference room want to call an Office Communicator user, they search for the address of the Office Communicator user in the directory of the video conference system. (Directories of video conference systems are discussed later in this document.)

Figure 11: Example of a contact in the directory on TANDBERG MXP endpoints



An example of the call flow for a call in either direction is shown below.

Figure 12: Office Communicator to/from conference room calling

5.4.2 Personal system (MPOP) calling scenario When a TANDBERG video conference system is registered to the Office Communications Server with an existing user’s credentials, the calling process is the same as described above. The call will be forked to all devices.

Tech Tip: Forking, also known as call splitting, is a feature that enables an incoming call to ring several extensions either in parallel or sequentially, or in a combination of these two. The first one extension that answers establishes the session.

Call forking is associated with the MPOP functionality in the Office Communications Server environment. The TANDBERG VCS FindMe functionality also leverages forking capabilities.

In the typical Personal System scenario, a user has a TANDBERG video conferencing system such as the TANDBERG 1700 MXP or the TANDBERG E20 on their desk. The device is often also used as their phone replacement because it can provide audio-only calling in addition to high quality video. Reasons why users have a dedicated video conference system on their desk in addition to running Office Communicator on their PC include:

• The ability to provide a “personal telepresence” experience.

• Dedicated screen real estate to video participants leaving the PC screen for content.

• Dedicated processing leaving the PC to be used for processing intensive data activities.

• Always-on functionality and reliability, i.e. there is no PC required When calling a user with both an Office Communicator client and a TANDBERG personal video conferencing system, the calling party doesn’t need to know what devices the callee has. They need only know that they are trying to connect with a specific individual – they simply call the user. The call is forked to both the Office Communicator client and the video conference system. Typically, the user answers the call with the personal video conference system when in the office. When on the road, the call can be answered with the Office Communicator client. The figure below shows the following call scenario:

• Alice finds Bob in the Contact list.

• Alice right-clicks on Bob to start a video call.

Call signaling Media path



• The call rings on Bob’s PC with Office Communicator and on the 1700 MXP.

• Bob is in the office; therefore, he answers the call on the 1700 MXP.

Figure 13: Personal video system (MPOP) calling scenario

5.4.3 Escalation Escalation from voice to video is supported for both the conference room and personal system models. The typical scenario for this is when an Office Communicator user selects a contact and

clicks the “Communicator Call” icon . This establishes an audio call with the video conference

system and then the user can click the camera icon in Office Communicator which will escalate the call to a video session.

5.4.4 Multiparty calling with TANDBERG endpoints Several of the TANDBERG MXP endpoints support a feature called Multisite. Multisite is the ability for the video conferencing system to host a multiparty call, similar to a second and third line conferencing capability of many phones. Multiple Office Communicator users can call into the video conferencing system or the video conferencing system can call out to multiple users. The call process is the same as that described above when calling between Office Communicator and a video conferencing system in that each Office Communicator user would start a video call with the conference room or the video conference system would call out to each Office Communicator participant, or some combination. The conference room video endpoint manages the multiple connections and the combined video image showing all participants. Refer to the TANDBERG MXP endpoints datasheet and Administrator guide for more information on the number of sites which may be hosted in a multisite call, as well as the video layouts supported.

Alice Bob’s office




Figure 14: Office Communicator in a multiparty call hosted on a TANDBERG MXP

5.4.5 Office Communicator call features The TANDBERG endpoints which support registration directly to Office Communications Server are also able to support the following Office Communicator client features when they are initiated from the Office Communicator interface.

• Call Transfer

• Call Forward

• Call Redirect

• Call Hold/Resume

• Audio and Video Mute

• Audio and Video Pause

An Office Communicator user would define their personal call forwarding/redirect rules in the configuration screen.

Figure 15: Example call forwarding rule screen for Office Communicator

Tech Tip: It is important to note that all of the individual call forwarding/redirect rules as shown above are “number” based and not URI based.



The following image shows the screen an Office Communicator user would see when trying to transfer a call. The user would select from the list of available contacts to transfer too, or search in the search bar for the appropriate contact.

Figure 16: Example Office Communicator Transfer Call screen

Tech Tip: Office Communicator users must be enabled for Enterprise Voice in order to leverage the call transfer features and other “Enterprise Voice” features of the Office Communications Server platform. Consult the Microsoft documentation for further detail.

Figure 17: Example screen shot for enabling Enterprise Voice

5.5 Management and directories Endpoints which are registered directly to the Office Communications Server are not managed or provisioned by it. This is a major consideration for the Individual registration model, being appropriate for a small scale integration of video conferencing equipment with Office Communicator.



It is possible to manage the TANDBERG video conferencing system individually; however, for a more scalable deployment the TANDBERG Management Suite (TMS) should be deployed. TMS allows an administrator to manage and maintain all of the video conferencing endpoints. One very important attribute of TMS is support for managing directories/phone books on the video conferencing systems. These are essential for users to easily find and connect with one another and with conference rooms. TANDBERG is able to provide a directory of the Office Communicator users based on the LDAP integration capabilities of TMS. TMS pulls the list of SIP URIs of the Office Communicator users from Active Directory and makes a phone book available on the video conferencing systems, allowing the video conference system user to easily place calls to individual Office Communicator users.

Figure 18: TMS and video conferencing system directories

5.6 Individual registration model limitations While the Individual registration model provides a simple method for providing integration of video conferencing with Office Communicator, it is important to understand the limitations. These limitations can be addressed with the Comprehensive Video Integration approach - see the next chapter.

5.6.1 Password management limitations It is common practice for IT administrators to set a password renewal policy in which users must create a new password at a set interval. Users are familiar with re-setting their password on their PC; however, there are a couple of issues when dealing with passwords on video conferencing systems.

• Password expiration notification

• Changing the password

Email is often used as a notification mechanism for changing a user’s password. There is no parallel notification mechanism for video conferencing systems; therefore, it is likely that the password on a video conferencing system could expire, and the system would stop functioning, resulting in calls to the help desk. Additionally, the actual process of setting a password on a video conferencing system with a typical remote control interface is often an administrative rather than an end-user function.

TMS

Directories/ Phone books



This issue can be mitigated by changing the password expiration policy so that passwords don’t expire. This may work for conference room systems but, typically, is not acceptable for personal video systems because it would mean that the user’s password policy would also be set not to expire. The TANDBERG Comprehensive Video Integration model (see the next chapter) provides an alternative approach, which simplifies password management and is more scalable.

5.6.2 Bandwidth management limitations Video conferencing equipment that registers directly with the Office Communications Server is limited to the feature set of that platform. Office Communications Server (R2) does not provide mechanisms for bandwidth management. (You can set the maximum bandwidth for video calls via Group Policy; however, there is no mechanism for Call Admission Control-type functionality.) Due to the bandwidth consumption of video calling, an important attribute in a typical video conferencing deployment is to allow the network administrator to control the bandwidth of video calls and the maximum number of video calls allowed over different portions of the network. This is done in order to ensure the quality of the calls and that there is bandwidth for other applications. The TANDBERG Comprehensive Video Integration model (see the next chapter) provides an alternative allowing for bandwidth management of the video conferencing assets in the network and all video calls between Office Communicator and video conferencing systems.

5.6.3 Limited interoperability

Existing video conferencing deployment limitations Most existing video conferencing deployments are based on a standard called H.323. Many of today’s video conferencing systems, including the TANDBERG MXP series of endpoints, support both the H.323 and SIP protocols. It is possible to simultaneously register an endpoint to both the existing H.323 video conferencing environment and to Office Communications Server (i.e. the SIP environment). While this is functional, it has some limitations, described here. Management and Administration Video conferencing systems that are dual registered must be managed both as an Office Communicator registration and as a video conferencing registration. This can cause confusion about which group in the IT organization is responsible for the day to day maintenance and administration of the device. Calling H.323-only systems require an MCU or embedded Multisite When the user of a video conferencing system registered directly to Office Communications Server wants interoperability with an existing H.323 video conferencing deployment (either internal to the organization or potentially an external customer or partner), an MCU is needed to mix the SIP and H.323 protocols as shown in the diagram below. In addition, the call model is not as simple as selecting a contact from the Contact list and calling; the user must know that there is an MCU and organize a “meeting” with the H.323 participant. While this is functional, TANDBERG recommends the CVI approach to integration which allows calling to H.323 systems directly from Office Communicator.



Figure 19: Individual registration model call limitations – H.323 calling Calling ISDN video conferencing systems requires an MCU or embedded Multisite The same restrictions apply when trying to call an ISDN video conferencing system from an Office Communicator client as when calling from Office Communicator to an H.323 video conferencing system. For this reason, TANDBERG also recommends the CVI approach to integration (see the next chapter). Audio gateway calling not supported with Individual registration When using an audio gateway or PBX integration with Office Communications Server, the Microsoft environment expects the number normalization to occur on the end client (Office Communicator or the video conferencing endpoint in this case). Typically, number normalization occurs in the network and not on the end client. Unless the endpoint supports the Microsoft model of number normalization, even if the endpoint can register with the Office Communications Server and make audio/video calls with Office Communicator clients, it will not be able to leverage the audio gateway associated with the environment. This is limiting for conference room based meetings in which an audio participant is added to the video call hosted on the conference room

Alice


With Individual registration, Alice is not able to call the H.323-only system directly; Alice must call into a device that can literally bridge the Microsoft-SIP with the H.323 protocol. This presents user experience issues as well as it is a resource intensive solution for mixing signaling protocols

Alice

X* H.323-only systems cannot register with Office Communications Server

SI H.32

SI H.32

H.323-

H.323-



system. It is also limiting in the environment where users would like the video conferencing endpoint to be their phone replacement. The TANDBERG CVI integration provides a solution to this limitation of the Individual registration model – see the next chapter. Video conferencing feature set limitations When a video conferencing system is registered to Office Communications Server or any other call control platform that is not designed with video conferencing in mind, typically there are limitations to the video conferencing feature set. For example, there is a protocol for content sharing in the video conference environment; however, this is not support by Office Communications Server. Therefore, video conferencing endpoints lose this feature with the Individual registration model. This is addressed in the CVI model – see the next chapter.

5.7 Products supporting Individual registration The following TANDBERG products support Individual registration:

• MXP (F software series) with Office Communications Server 2007 R1 and R2

• E20 (TE software series) with Office Communications Server 2007 R1 and R2

• MCU 4200 and 4500 series and the MSE 8420 and 8510 blades series – Office Communications Server 2007 R1 only (For R2 interoperability the CVI model described later is this document is required)



6 Comprehensive Video Integration - details The integration between VCS and Office Communications Server is based on a SIP trunk between both environments (see Figure 4). Leveraging the SIP trunk capabilities of VCS enables the most dynamic combined environment by allowing them to work seamlessly with one another without limiting the unique capabilities of each environment. This section provides additional detail about this SIP trunk and two possible options for how to leverage it in an Office Communications Server environment. (Refer to the TANDBERG Deployment Guide: Microsoft OCS 2007 R1 and R2 and VCS Control X5 for details on how this trunk is configured.) There are two elements to the SIP trunk between VCS and Office Communications Server: the SIP trunk itself and an application which runs on the VCS that utilizes it known as the “OCS Relay”. This application enables additional advanced functionality above that possible with a standard SIP trunk in an Office Communications Server environment. In order to leverage the SIP trunk between VCS and Office Communications Server, there are two main attributes which must be configured on Office Communications Server.

• Trusted Host: The SIP Trunk between VCS and Office Communications Server leverages the Trusted Host model supported by Office Communications Server; therefore, the VCS must be configured as a Trusted Host.

• Static Route: In order to route calls from the Office Communications Server Environment to the video conferencing environment a static route must be defined on Office Communications Server. While Office Communications Server R1 only allowed routing to a separate domain, Office Communications Server R2 allows the configuration of a static route to the same domain.

Tech Tip: The VCS to Office Communications Server integration makes use of the Office Communications Server routing logic to operate. For this reason it is important to understand the call routing logic of the Office Communications Server. When Office Communications Server receives a call it checks the following:

• If the user is registered to Office Communications Server. The call is only proxied to the registered OC user.

• If the user is not registered but there is an account in AD, Office Communications Server responds with a 480 Temporarily Unavailable.

• If the user is not in AD (i.e. therefore not registered to Office Communications Server) the call will be routed through the configured static route.

6.1 SIP trunk base functionality This section describes the basic level of functionality provided by VCS over the SIP trunk with Office Communications Server without the OCS Relay capability enabled. This is provided for customers who wish to enable and test the basic connection between VCS and Office Communications Server so they know what to expect before enabling the recommended OCS Relay capability for the best level of support and the most scalable solution. See the section, SIP trunk advanced capabilities – OCS Relay Basic SIP Trunk functionality includes:

• Authentication/authorization: AD accounts not required

• Basic presence: offline and available presence for VC systems registered into the VCS network



• Protocol interworking: Microsoft SIP to SIP/H.323 o Enables support for 3rd Party video conferencing systems

• Bandwidth management for calls between VCS and

• Video conference feature set o Dual stream support o Multiway

6.1.1 Security

Authentication/authorization When video conference endpoints register individually with Office Communications Server, they must have a valid AD account. Often this is not an issue, particularly for customers who are using the TANDBERG – Microsoft Exchange integration. In this case, AD accounts will have been created previously for the endpoints in order to create their exchange mailbox accounts for scheduling purposes. However many deployments do not have AD accounts configured for video conferencing endpoints. The SIP trunk between VCS and Office Communications Server allows for these devices to be easily integrated into the Office Communications Server environment with minimal additional configuration. Example An organization is trying to integrate their existing video conferencing network with their Office Communications Server deployment. The video conferencing network is deployed as [email protected] and their Office Communications Server deployment is configured as [email protected]

Figure 20: Video conferencing to Office Communications Server integration – AD accounts not required This organization can configure their VCS to interface with Office Communications Server and define a static route on Office Communications Server to interface with VCS. This configuration allows calling between Communicator and the conference room in both directions. The above case is an example of a multiple domain deployment. The VCS also supports single domain deployments. (The section on the Advanced capabilities of the SIP trunk covers how to

SIP TRUNK

[email protected]

Any standards-based video conferencing system supported by VCS

[email protected]

Alice can enter [email protected] in the Office Communicator search Field; she can then right click to “Start a Video Call”.

@fictbiz.com @video.fictbiz.com

In this example no AD account is needed for the conference room system, however Alice must know the full URI. Also a route is needed to video.fictbiz.com

mailto:[email protected]





leverage AD accounts in the integration so that users do not need to be aware of the multiple domains and can take advantage of the Office Communicator search capabilities.)

Signaling encryption (TLS vs. TCP) Where the OCS gateway VCS communicates directly to an Office Communications Server Director or Front End Processor (FEP) (not through a Hardware Load Balancer) use of TCP in the initial deployment can facilitate functional verification and troubleshooting. Certificate creation, loading and then enabling TLS can be carried out once the system is operational. If hardware load balancers front end the Office Communications Server system, it is recommended that TLS is used from the outset. In general TANDBERG recommends using TLS in final deployments, following the certificate creation guide and the VCS deployment guide will lead you through to a successful TLS installation. See the reference section of this document for further information on the aforementioned guides

Media encryption (SRTP) Currently both TANDBERG and Microsoft have implementations of the SRTP (Secure Real Time Transport) protocol for encryption of media (i.e. encryption of the audio and video traffic). However, the implementations are not interoperable at this time. TANDBERG is working on addressing these differences, as well as investigating the implications for interoperability between the SIP and H.323 versions of media encryption. Therefore on the Office Communications Server Front End Servers, it is important to set encryption to either “Support Encryption” which means it is optional or “Do Not Support” which means it is turned off. TANDBERG recommends setting the encryption state to “Support Encryption” in order to allow Office Communicator to Office Communicator calls to be encrypted, while calls over the SIP trunk between Office Communicator and video conferencing systems will not be encrypted. If encryption is set to “Required” on the Front End Servers, calls will fail between Office Communicator and the video conferencing environment.

Tech Tip: The Microsoft Office Communications Server 2007 R2 is delivered with the Front End Server encryption policy set to “Required”. While the Office Communicator 2007 R2 client has its encryption setting as “best effort” by default the Front End server setting has precedence; therefore this is all that is needed to force encryption in an Office Communicator environment. However, some organizations also leverage a Group Policy object to set the registry on the client machine to “require” encryption as well. TANDBERG is not recommending this practice but rather drawing attention to it in order to help with troubleshooting when there is a security mismatch.

If there is a security incompatibility as indicated above, when calling between Office Communicator and the video conferencing environment over the TANDBERG VCS Gateway integration with Office Communications Server, the following should be checked:



It is also possible to verify the value of the registry setting on a client machine to determine the encryption state. 0 = Support Encryption 1 = Require 2 = Do Not Support

6.1.2 Presence/Contact search The TANDBERG VCS supports SIP for Instant Messaging and Presence Leveraging Extensions (SIMPLE) for presence. With the base SIP trunk between VCS and Office Communications Server the “offline” and “available” call states are supported via standards-based SIMPLE interoperability. Office Communications Server has implemented a variation of the SIMPLE protocol when it comes to the “in call” presence state; therefore, “in call” presence is not supported. Office Communicator users must enter the entire name/address of the user/room they are trying to connect to if that user/room does not have a valid AD account. This is the case with the basic SIP trunk between VCS and Office Communications Server.



Tech Tip: Office Communicator leverages AD to search for users. Because the basic SIP trunk between VCS and OCS does not require an AD account for the video conferencing system, the Office Communicator user must enter the entire name of the video system they are trying to reach. After the name has been entered in Office Communicator, the contact can be added to the Contact list like any other contact and called like any other contact (right click and select Start a video call).

The OCS Relay function of VCS supports both the “in call” presence state and actual search from Office Communicator; another reason why TANDBERG recommends that the basic SIP trunk capabilities between VCS and OCS be used only for initial set up and testing, as well as to understand the interworking between VCS and OCS. However, the recommendation is to leverage the OCS Relay function of VCS which provides advanced capabilities over the basic SIP trunk capabilities. OCS Relay is described later in this document.

Tech Tip: In an “OCS Gateway” deployment, the VCS presence server for the OCS Relay / OCS Domain should be enabled on the OCS Gateway VCS

6.1.3 Basic SIP trunk summary The implementation of the basic SIP trunk as outlined in this section enables the core capabilities of the integration between the VCS and Office Communications Server. After the SIP trunk is in place, the VCS can be used for the following Office Communicator scenarios:

• Basic presence indication of video conferencing systems in Office Communicator (offline and available).

• Point-to-point calling to/from Office Communicator to video conferencing systems regardless of protocol, including: o Telepresence. o Conference rooms. o Personal video conference systems. o External H.323 video conferencing systems.

• Multiparty conferences on standards-based MCUs.

• Video conference system calling to PSTN via OCS-based audio gateway.

• Bandwidth management for the above call scenarios. These scenarios are covered in more detail in the CVI use cases chapter.

6.2 SIP trunk advanced capabilities – OCS Relay VCS contains an application called “OCS Relay” which provides advanced functionality in addition to the basic SIP Trunk between VCS and Office Communications Server. OCS Relay allows video conferencing systems which are registered into the VCS environment to have their registration “proxied” into Office Communications Server allowing video conference systems to appear as Office Communicator clients to the Office Communications Server. This provides several benefits which are described in more detail later in this document:

• Simplifies password management on video conferencing endpoints

• Support for contact search from Office Communicator

• Single identity support

• Improved presence support



Tech Tip: OCS Relay requires additional configuration as described in the Configuration Guide and a valid AD/Office Communicator account be configured.

Tech Tip: OCS Relay works in both a “same domain” and “separate domain” configuration. In both cases Office Communications Server Relay enables the appearance of a single domain as far as the Communicator user is concerned.

The following diagrams show how OCS Relay is used for both the personal device and conference room scenarios. OCS Relay can be extended to any SIP or H.323 registration on VCS; for example, Telepresence systems and conferences hosted on an MCU. This is very useful when enabling 3rd party devices with Office Communications Server, as well as for older video conferencing systems which only support H.323 and may never be able to register directly with Office Communications Server.

Figure 21: OCS Relay – Conference room model



Figure 22: OCS Relay – Personal system and single identity support

6.2.1 Simplified password management - Authentication/authorization The Individual registration model requires that the video conferencing devices register and authenticate directly with the Office Communications Server, which can present some administrative challenges. Often organizations have password expiration policies that require users to reset their passwords on a set interval. This is a common practice and easily adhered to in a PC environment; however, it may present issues when video conferencing devices are registered individually to Office Communications Server because most video conferencing devices often do not provide a user interface that is conducive to accessing and changing passwords. This has traditionally been the domain of the video conferencing equipment administrator. One option is to allow passwords not to expire for video conferencing systems. Whether this is an acceptable solution depends on the level of adherence to the internal policy. However, there is another consideration which must be taken into account. Personal video conferencing systems such as the TANDBERG 1700 MXP or TANDBERG E20 have grown in popularity over the years: these systems are often configured with the credentials of a given user. When considering personal video conferencing appliances it is no longer a simple matter of setting the password expiration policy to never expire. The VCS provides a better approach to password management, leveraging the Trusted Host relationship with Office Communications Server. Both personal systems and conference room systems may be registered with VCS and then the OCS Relay proxies their registration into Office Communications Server making them appear like any other Office Communicator registration without the need to administer password credentials on the video conferencing systems themselves. Note there are authentication mechanisms which may be employed between the endpoint and VCS. (See the TANDBERG endpoint and VCS Administrator guides for additional information.)



6.2.2 Presence/Contact search The VCS’s OCS Relay application has three key elements relating to presence:

• Implementation of the Microsoft Office Communications Server 2007 enhanced presence model

• Support for single identity

• Presence aggregation Enhanced presence model The OCS Relay application on VCS leverages the Office Communications Server 2007 Enhanced Presence Model (in contrast to other video conferencing vendors who have only implemented the Microsoft 2005 Presence Model that is a remnant from the Live Communications Server environment). Implementation of the 2007 Enhanced Presence Model simplifies configuration of the corresponding Office Communicator account – there is no need to disable “enhanced presence” for these accounts, and doing so limits user functionality provided by Office Communications Server 2007(R2). Single identity The notion of a “single identity” is a very important paradigm in Unified Communications. Microsoft has a function called MPOP (Multiple Points of Presence): the ability for the Office Communications Server platform to support multiple devices registered as a single user. For example, MPOP allows a user to be logged in on Office Communicator on two different PCs as well as running Communicator Mobile. The presence from all three devices is then aggregated by Office Communications Server and calls to this user are forked to all three devices, as appropriate. VCS supports a similar call forking mechanism based on its FindMe functionality. The OCS Relay ties these “single identity” mechanisms together, allowing users to have both Office Communicator devices and video conferencing devices under one single identity in the combined Office Communications Server and VCS environment. When OCS Relay is enabled and configured, the accounts which have been registered to Office Communications Server via the OCS Relay have valid AD accounts (see Figure 21:and Figure 22:). Therefore searching for these users is just like searching for any other valid contact from within Office Communicator: just start entering the name in the search field and Office Communicator does the look up. This applies to both personal users and room systems. For personal users, the Office Communicator URI is found and there is no indication if the user has a corresponding OCS Relay registration. This is the normal and correct behavior because it allows the user to have a single identity regardless of what devices may be associated with the user. Then it is possible to initiate a video call to that user and the called party is able to answer the call on the device that is most convenient, possibly a PC with a USB camera or their TANDBERG video endpoint. Presence aggregation The use of OCS Relay also has deployment benefits: when OCS Relay is implemented, the video conferencing systems publish presence to the Office Communications Server. It is then the responsibility of Office Communications Server to manage presence subscriptions from Office Communicator clients. OCS Relay allows customers to take advantage of the scale that Office Communications Server enables for managing and distributing presence across a very large organization.



Figure 23: OCS Relay and presence aggregation

6.3 Integrated architecture - VCS considerations There are two main VCS architecture options for integration with Office Communications Server.

• Recommended architecture based on a separate VCS environment serving as the gateway to Office Communications Server, called the “OCS Gateway” in this document.

• Simplified architecture based on enabling the Office Communications Server gateway functionality on the VCS environment, which also acts as the VCS Control for the video conferencing environment.

Figure 24: VCS architecture options The following benefits of a dedicated VCS acting as an OCS Gateway should be taken into account when determining the architecture for a given deployment.



Simplified administration

• All OCS-related functionality is running on a dedicated VCS environment.

• All video conferencing is running on a dedicated VCS environment.

• Limits the number of “trusted devices” configured on Office Communications Server.

• Simplified “domain” support between the Office Communications Server environment and the video conferencing environment.

VCS license utilization Office Communications Server interworking requires that all calls are interworked and therefore routed through the VCS in order to modify the Microsoft signaling to work with the standards-based video conferencing environment. This means that VCS must have its “Call Routed Mode” set to “Always”. In a typical video conferencing deployment, TANDBERG recommends the “Call Routed Mode” be set to “Optimal” in order to make the most efficient usage of the call licenses. Therefore a separate VCS environment acting as an OCS Gateway is recommended. Presence propagation A separate VCS environment acting as the OCS Gateway which is configured as the video network’s presence server allows the OCS Gateway to handle the subscriptions and presence requests from Office Communications Server for the video network. This prevents presence requests from having to propagate through the video conferencing network. Advanced Configuration The OCS Relay function leverages a configuration tool on the VCS knows as CPL (Call Processing Language). CPL is also used on VCS for advanced functions such as defining policy for ISDN gateway usage or policy for compliance recording of video conference calls. It is often difficult to combine CPL for various functions; therefore, enabling a separate VCS environment to act as an OCS Gateway provides separate CPL scripts for the appropriate portions of the network. See the TANDBERG Deployment Guide: Microsoft OCS 2007 R1 and R2 and VCS Control X5 for:

• Additional information behind the importance of a dedicated VCS environment acting as an OCS Gateway. (See the section, “Why add an OCS Gateway VCS Control”.)

• Architecture implications of the Microsoft Director server. (See the appendix, “VCS and Microsoft OCS Director”.)

• Architecture implications of hardware load balancers in the Microsoft Office Communications Server environment. (See the section, “VCS and hardware load balancers in front of a bank of FEPS”.)



7 CVI use cases The following use cases are based on an environment configured with OCS Relay. The following diagram depicts the elements required in the solution for the various call scenarios: not all elements are required for all call scenarios. Note: The VCS Control shown in this diagram has been simplified for the purpose of illustration: the VCS Control image represents both a VCS environment acting as the OCS Gateway and the VCS Control for the video conferencing network.

Figure 25: Example CVI architecture

7.1 Office Communicator to video conference room system This model provides the same user experience as that of the Individual registration call scenario between Office Communicator and video conference rooms. However, this model extends the reach of this scenario to any standards-based video conferencing system supported by VCS. These can be SIP- or H.323-based video conferencing systems (TANDBERG and 3rd party video conferencing equipment), and the OCS Gateway model removes these protocol complexities from the end user allowing them to use the interface that they are familiar with. In order to make a video call from Office Communicator to a video conference room, users:

• Search for the conference system, if it is not already in the user’s Contact list.

• Right-click on the conference room system contact.

• Start the video call.



Figure 26: Calling from Office Communicator

Figure 27: Office Communicator to/from conference room calling

Note: Figure 27: shows the media path going through the VCS. In a basic end-to-end SIP call (i.e. the video conferencing system supports SIP), the media path would actually go directly between the Office Communicator client and the video conferencing system. All call scenarios in which interworking is required the media will traverse the OCS Gateway VCS allowing it to perform the necessary interworking. An example of an interworked call scenario is Office Communicator to H.323 video conference systems. As more advanced features are added to the OCS Gateway VCS in the future, more call scenarios will be interworked through VCS.

When users in the conference room want to call an Office Communicator user, they search for the address of the Office Communicator user in the directory of the video conference system. This applies to all standards-based video conference systems supported by VCS. (Populating directories on video conferencing systems was discussed in the section Management and directories.) The same model of management and directory support applies to both the Individual registration model and the CVI model.

SIP TRUNK

Alice

Call set up


Bellevue conference room

Media path



Figure 28: Example of a contact in the directory on TANDBERG MXP endpoints

7.2 Personal system (MPOP) calling scenario In the typical personal system scenario, a user has a TANDBERG video conferencing system such as the 1700 MXP or the E20 on their desk. (Note: the VCS integration allows any video conference device to be utilized as a personal system, for example some executives have their own personal large screen system in their office). The device is often also used as their phone replacement because it can provide audio-only calling in addition to business-quality video performance up to high definition. Reasons why users have a dedicated video conference system on their desk in addition to running Office Communicator on their PC include:

• The ability to provide a “personal telepresence” experience.

• Dedicated screen real estate to video participants leaving the PC screen for content.

• Dedicated processing leaving the PC to be used for processing intensive data activities.

• Always-on functionality and reliability: no PC is required

When calling a user with both an Office Communicator client and a TANDBERG personal video conferencing system, the calling party doesn’t need to know what devices the callee has, only that they are trying to connect to a specific individual – they simply call the user. The call is forked to both the Office Communicator client and the video conference system. Typically, the user answers the call with the personal video conference system when in the office. When on the road, the call can be answered with the Office Communicator client. This model provides the same user experience as that of the Individual registration call scenario between Office Communicator and the personal video conference system. However, this model extends the reach of this scenario to any standards-based video conferencing system supported by VCS. These can be SIP- or H.323-based video conferencing systems and the OCS Gateway model abstracts all of these protocol complexities from the end user allowing them to use the interface that they are familiar with.

The figure below shows the following call scenario:

• Alice finds Bob in the Contact list.

• Alice right-clicks on Bob to start a video call.

• The call rings on Bob’s PC with Office Communicator and on the 1700 MXP.

• Bob is in the office; therefore, he answers the call on the 1700 MXP.



Figure 29: Personal video system (MPOP) calling scenario

7.3 Office Communicator to/from external H.323/SIP video system calling (Expressway)

The same user experience of calling from Office Communicator to a video conference system (room or personal) can also be extended to home office workers with a video conferencing system and to other organizations that have video conferencing solutions. These external connectivity scenarios are made possible with the TANDBERG Expressway solution. Expressway is a secure and standards-based mechanism for firewall traversal - in contrast to firewall bypass, which many other video conferencing vendors provide. (A full description of Expressway is beyond the scope of this document; go to http://www.tandberg.com/support/video-conferencing-documentation.jsp for more information.)

Home office worker with a video conferencing system In the following example Bob has an E20 in his home office. When Alice tries to reach Bob she doesn’t need to know anything about Bob’s communications capabilities; she need only search for Bob in the Office Communicator Contact list, right-click on the contact name and select Start a video call. If Bob happens to be in his home office he can take the call on his E20. Conversely, Bob can use his E20 in his home office to call anyone in his organization by using the directory on the E20 and (provided via TMS integration with LDAP) and making a call to the appropriate contact. This will route back through Office Communications Server and can ring an Office Communicator user.

Alice selects Bob and starts a video call

Alice

Call set up


Bob

Media path

Bob

1 2 2 2

1

2 The call is routed to all of Bob’s devices

3

3 In this scenario Bob answers the call on his 1700MXP

http://www.tandberg.com/support/video-conferencing-documentation.jsp




Figure 30: Home office worker video conference system connectivity

Connecting with an external organization’s video conference system by URI dialing Another scenario that the OCS Gateway and Expressway solution enable is the ability for Office Communicator users to call directly to video conferencing systems in other organizations by entering the full URI of the external organization’s conference room system or personal video conferencing system; for example: [email protected]. The Office Communicator user will not see presence for this external system because there is no presence capability for the external party’s video conference system; however, this contact can be added to the user’s Office Communicator Contact list just like any other contact and the user can right-click on the entry to make a video call.

Figure 31: External organization video conference connectivity by URI dialing

Tech Tip: The domain of the external company will need to be configured in the OCS route table to ensure that the call is routed via the OCS Gateway.




Connecting with an external organization’s video conference system by IP dialing Many organizations still have their video conferencing systems either outside their firewall on a public IP address, or in the DMZ and also reachable via a public IP address. The OCS Gateway and Expressway solution also enables Office Communicator users to connect to these systems by dialing the IP address of the external party with a domain that has been configured in Office Communications Server for this external calling scenario. For example it is possible to configure a route in Office Communications Server to the domain “external.com”. If the Office Communicator user needs to reach a partner or customer who provided an IP address of 12.1.1.1, the user would enter [email protected] in Office Communicator and right-click to start a video call. This routes the call to the OCS Gateway VCS which would be provisioned to strip the domain and then route the call over the public internet to 12.1.1.1.

Figure 32: External organization video conference connectivity by IP dialing

Tech Tip: A fictitious domain for external IP calling will need to be configured in the Office Communications Server route table to ensure that the call is routed via the OCS Gateway. Also, the TANDBERG VCS environment will need a transform to remove the domain and route the call to the public IP address. Example: dial IP<IP Address>@external.com to dial <IP Address> VCS Transform: IP(\d+\.\d+\.\d+\.\d+)@external.com \1 Search rule for local zone:

Source = Any Mode = anyIPAddress Target zone = local zone

7.4 Escalation Escalation from voice to video is supported through the OCS Gateway. The typical scenario for this is

when an Office Communicator user selects a contact and clicks the “Communicator Call” icon . This establishes an audio call with the video conference system. The user then clicks the camera icon

in Office Communicator to escalate to a video call.




7.5 Office Communicator call features The TANDBERG OCS Gateway supports additional Office Communicator call features with TANDBERG endpoints registered to the VCS. It is possible that some of the following functionality works with 3rd Party endpoints however this is beyond the scope of this document and should be verified with the individual 3rd party endpoint manufacturer. The additional Office Communicator call features include the following functions when initiate from the Office Communicator client.

• Call transfer

• Call forward

• Call redirect

• Call hold/resume

• Audio and video mute

• Audio and video pause

Note: Redirect: VCS provides loop detection. If a call comes from the VCS side of the solution and is redirected back to the VCS side of the solution, VCS will block this scenario and the redirect will fail. This is done in order to prevent endless call loops.

Note: Additional configuration may be required to leverage the above features. For example, in order to redirect an incoming call to Office Communicator, the numbers which the call can be redirected too must be pre-provisioned. Also, the dial plan needs to be established between the video conferencing network and the Office Communicator environment.

Figure 33: Office Communicator call forwarding rule set example



Figure 34: Office Communicator Transfer Call example

Tech Tip: Office Communicator users must be enabled for Enterprise Voice in order to leverage the call transfer features and other “Enterprise Voice” features of the Office Communications Server platform. Consult the Microsoft documentation for further detail.

Figure 35: Example screen shot for enabling Enterprise Voice

7.6 Multiparty calling with TANDBERG endpoints Several of the TANDBERG endpoints (MXP series and C series devices for example) support a feature called Multisite. Multisite is the ability for the video conferencing system to host a multiparty call, similar to a second and third line conferencing capability of many phones.

Multiple Office Communicator users can call into the video conferencing system or the video conferencing system can call out to multiple users. The call process is the same as that previously



described in this document when calling between Office Communicator and a video conferencing system in that each Office Communicator user would start a video call with the video conference system or the video conference system would call out to each Office Communicator participant, or some combination. The conference room video endpoint manages the multiple connections and the combined video image showing all participants.

Refer to the TANDBERG endpoints datasheet and Administrator guide for more information on the number of sites which may be hosted in a multisite call as well as the video layouts supported.

Figure 36: Office Communicator in a multiparty call hosted on a MXP endpoint

7.7 Office Communicator to/from ISDN video calling The video conferencing environment still consists of large number of systems which use the ISDN network. Organizations that have migrated to IP for video conferencing often have an ISDN video gateway that allows their IP-based video conferencing systems to connect with remote sites, partners, and customers who still have ISDN-based video conferencing systems. This is very similar to the migration to VoIP, much of which still utilizes a PSTN-based audio gateway for external connectivity. The OCS Gateway allows Office Communicator users which are IP-based to leverage the TANDBERG ISDN gateway to make and receive video calls from remote sites, partners and customers that have ISDN video conferencing systems.

7.7.1 Outbound calling from Office Communicator to an ISDN video system

The Office Communicator user only needs to dial the ISDN address of the external party with a domain that has been configured in OCS for this external ISDN calling scenario. For example, it is possible to configure a route in OCS to the domain “@ISDN.com”. To reach a partner or customer who has provided an ISDN video conferencing number, the Office Communicator user enters: [email protected] in the Office Communicator client and right-clicks to start a video call. This routes the call to the OCS Gateway VCS which is provisioned to strip the domain and then route the call to the ISDN video gateway and out over the public ISDN network.




Figure 37: Calling ISDN video systems from Office Communicator Note: A fictitious domain for external ISDN calling needs to be configured in the Office Communications Server route table to ensure that the call is routed via the OCS Gateway. Also, the TANDBERG VCS environment needs a transform to remove the domain and route the call to the TANDBERG ISDN Gateway.

7.7.2 Inbound calling to Office Communicator from an ISDN video system

Inbound calling from the ISDN network to an Office Communicator client is more complex than the outbound scenario. It is important to consider the Office Communicator audio number plan because DID-based (Direct Inward Dial) numbers have probably been assigned to the Office Communicator users. If this is the case, this number space will have been occupied and it will not be possible to get the same numbers for ISDN inbound calling. Therefore, TANDBERG recommends leveraging IVR-based dialing when calling Office Communicator users. An inbound ISDN caller would dial the number of the ISDN Gateway. They would then be prompted to enter the extension of the party they are trying to reach. This would be the pre-assigned audio number for the Office Communicator user.



Figure 38: Calling Office Communicator from an ISDN video system

7.8 Audio calling to/from video endpoints via an Office Communications Server audio gateway/PBX

The OCS Gateway can provide number manipulation on behalf of video conferencing systems so that they can make and receive audio calls to and from both a PBX integration and an audio gateway integration with the Office Communications Server. This allows the video conferencing environment to make audio calls via the Microsoft mediation server to audio gateway/PBX integration. The OCS Gateway also allows the video conferencing environment to bypass the Microsoft environment and trunk to the PBX directly to enable audio calling. This has the benefit of not limiting the audio codec to G.711.

7.9 Telepresence The TANDBERG Telepresence solution can be added to the overall integrated solution, as described in this document. It can make/receive calls to/from Office Communicator in the same manner as previously described in this chapter for typical conference room video conferencing systems. A TANDBERG Telepresence endpoint appears to Office Communicator like any other video conference endpoint. Equally, to the TANDBERG Telepresence endpoint, an Office Communicator client is just another video endpoint. That being said, the TANDBERG Telepresence solution has some additional functionality which provides the industry’s best integration between Office Communicator and a telepresence system. When an Office Communicator client is connected to the TANDBERG Telepresence solution, the Office Communicator is not treated as a “second class” participant in the conference: the Office Communicator user sees all other members of the conference as shown in the figure below.



Figure 39: Office Communicator in a call with the TANDBERG Telepresence solution A critical element to the TANDBERG Telepresence solution is the TANDBERG Telepresence Server. This is an application-specific MCU for telepresence that provides the industry’s most robust offering for multipoint telepresence conferencing and interoperability. The TANDBERG architecture for integrating from VCS to Office Communications Server via a SIP trunk makes it easy to add the TANDBERG Telepresence solution (telepresence rooms and the Telepresence Server) to an Office Communications Server environment.

Figure 40: Telepresence integrated with Office Communications Server The typical use case for connecting an Office Communicator client to a point-to-point or multiparty telepresence conference is for the telepresence room to call out to the Office Communicator user. (Telepresence conferences are typically a “high value” event and, as a result, are often scheduled. An Office Communicator user is often a last minute addition to the meeting, typically due to being a subject matter expert.) It is possible for Office Communicator users to call individually into a TANDBERG Telepresence system, however this is beyond the scope of this document. The following call scenario list is a representative, rather than exhaustive, list of call scenarios possible between the TANDBERG Telepresence solution and Office Communicator.

• Single T3 to briefer (see note below).

• Single T3 to multiple briefers.

• Point-to-point T3 plus a call out to one or more briefers.



• Multiple T3 in a conference with one or more briefers.

TANDBERG’s flagship Telepresence product is known as the T3 and is shown in the figure below.

Figure 41: TANDBERG T3 Telepresence System

Note: There is a term used in the TANDBERG lexicon when talking about Telepresence interoperability with standards based video conferencing. The term is “briefer”. A “briefer” is a standards-based video conferencing endpoint or Office Communicator client which is connected into a Telepresence conference. The purpose of the term is to distinguish between devices with true Telepresence functionality (telepresence environment etc) and the myriad of other possible video devices that may be connected to a meeting (both high definition capable systems as well as standard definition solutions).

Note: When the T3 moves from point-to-point mode to conference mode on the Telepresence Server, the Telepresence Server places outbound calls to the previously connected briefers. This is important because the Office Communicator user needs to know to answer the incoming call from the Telepresence Server.

7.10 Conferencing

7.10.1 Conferencing background The Office Communications Server environment provides multiparty video conferencing capability via the Microsoft AVMCU (Audio/Video Multipoint Control Unit). Currently, the Microsoft AVMCU does not interoperate with any standards-based video conferencing endpoints because:

• The Microsoft AVMCU only supports the proprietary Microsoft video codec known as RT Video (Real Time Video codec). The video conferencing industry supports a standard video codec known as H.264.

• The Microsoft AVMCU requires the endpoint connecting to it to support the Microsoft specific conferencing protocol.

• The Microsoft AVMCU requires the endpoint connecting to it to support the Office Communicator R1 version of ICE.

Note: While RT Video is a proprietary Microsoft video codec, it is based on the standard VC1 codec. Modifications by Microsoft to make the codec “adaptive” to network conditions make the codec proprietary. In order to provide interoperability between the video conferencing industry standard of H.264, TANDBERG has licensed RT VIDEO from Microsoft. (Consult your TANDBERG representative regarding the product roadmap)



Additional items to note about the Microsoft AVMCU and why a TANDBERG MCU can add value in an Office Communications Server environment are:

• The Microsoft AVMCU only supports the “voice switched” conferencing mode. Voice-switched conferencing is a term used in the video conferencing industry to describe a multi-party video conference in which only the active speaker of the conference is visible to the other participants. This is in contrast to what is known as “continuous presence” or “Hollywood squares” in which multiple (typically all) participants are visible simultaneously. (See below for more information.)

• The Microsoft AVMCU only supports RT VIDEO - CIF at 15fps (this applies to R1 and R2 of Office Communications Server), whereas the TANDBERG MCU is capable of resolutions up to HD at full frame rate.

Voice-switched versus continuous presence Typical views are shown below.

Figure 42: Active speaker view

Figure 43: Four-way continuous presence Continuous presence conference views are often a hybrid of the voice-switched and continuous presence views (see below) with the active speaker being switched into the large image known as a “pane” but other participants are also visible. In the video industry this is still referred to as a continuous presence view.



Figure 44: 7+1 continuous presence

7.10.2 Conferencing call scenarios The Office Communications Server platform does not provide a mechanism to “replace” the AVMCU with a 3rd Party MCU such as the TANDBERG Codian MCU (in which case the user scenario for conference creation would be identical regardless of MCU). Given this condition, the TANDBERG MCU must integrate with the Office Communications Server solution differently then AVMCU; the result is a slightly different user model for conferencing on a TANDBERG MCU compared to on the Microsoft AVMCU. The following call scenarios define how the TANDBERG MCU can be used in an Office Communications Server environment. Note this document does not cover any call scenarios based on the Microsoft AVMCU; see the Microsoft documentation for that detail. The TANDBERG Integration with Office Communications Server via the TANDBERG VCS and the Comprehensive Video Integration model provides four main mechanisms for multiparty conferencing support:

• Scheduled conferencing • Pre-provisioned conferencing (Virtual Conference Room) • Ad hoc conferencing • Multiway (conference initiation from TANDBERG endpoints only)

Scheduled TANDBERG MCU conferences with Office Communicator The TANDBERG TMS software suite has a scheduling component which can be integrated with Microsoft Exchange allowing users to book meetings directly from their Outlook calendar. The TANDBERG integration synchronizes the calendar between Exchange and TMS allowing TMS to automatically launch the call at the scheduled date and time. Full coverage of the TANDBERG Exchange integration is beyond the scope of this document. Refer to the TMS documentation on the TANDBERG web site. The remainder of this section focuses on scheduling directly from TMS. TMS allows users to book video conferencing systems as well as “users”. The following image shows the TMS booking interface and the selection of users. It is possible to reserve ports for inbound callers, similar to how users call into an audio bridge. TMS sends an email to the meeting organizer with the necessary conference information including the dial-in information. This information can then be forwarded to the required participants.



Figure 45: Adding Office Communicator users when scheduling a multiparty conference in TMS

Figure 46: Example TMS confirmation message with connection information

At the time of booking TMS verifies that the necessary conferencing resources will be available at the scheduled time and reserves these resources. At the time of the scheduled meeting, TMS automatically sets up the conference and dials out to the numbers (conference rooms and or users) which were selected at the time of booking. Also after the conference has been initiated by TMS, the dial in ports will be active allowing the participants to call into the meeting from either a video conferencing system or from their Office Communicator client.

The MCU will dial out to the SIP URI; [email protected], which will ring the users Office Communicator client as well as this users video conferencing devices.




Pre-provisioned conference (virtual meeting room) The concept behind this conference option is to emulate the conference room experience, albeit virtually. The TANDBERG MCU is pre-provisioned with conferences. These conferences are given AD accounts and configured with OCS Relay so they can show “in call” state presence. The end users are informed of the name range for these virtual meeting rooms. For example, the marketing team may have the following virtual meeting rooms: MarketingMeetingRoom1 MarketingMeetingRoom2 MarketingMeetingRoom3 The marketing team could then create a group in their Office Communicator Contact list for their virtual meeting rooms. When a group of users needs to collaborate they can look in their Contact list, see which virtual meeting room is “Available” and agree to meet in that virtual meeting room. Each Office Communicator user would make a video call into that room. Additionally if a group of users is in a physical conference room they can look up that virtual meeting room in the directory and also call into the meeting. The team is then all connected in that virtual meeting room on the TANDBERG MCU and they are able to collaborate visually with a mix of Office Communicator clients and standards-based video conferencing systems.

Figure 47: Example Contact list with a group of virtual meeting rooms

Ad hoc TANDBERG MCU conference A third approach to conference integration supported by the TANDBERG integration with Microsoft Office Communications Server is to allow for ad hoc conference creation on the TANDBERG MCU and “on the fly” conference creation from an Office Communicator client or video conference system for that matter. The TANDBERG MCU supports an ad hoc conference mechanism that is outlined in this section (refer to the MCU documentation on the TANDBERG web site for more details). The TANDBERG MCU can be provisioned to match on a pattern and create a conference if the pattern is matched - or to direct a user to the appropriate conference if the pattern is matched and a conference has already been started. Note that the Office Communications Server environment also needs to be configured to route calls to the VCS based on the same pattern match.



Example Alice is chatting with Bob and Charlie and they all agree that a video call would be better. Alice sends an IM to Bob and Charlie asking them to call her at personal meetme conference number. (Alice’s personal meetme number is nothing more than a number prefix followed by her unique phone extension, for example 55 8675389.) The TANDBERG MCU is configured for ad hoc conferencing on the pattern match of 55. When the first user calls 55 8675389, the MCU recognizes the 55 pattern as an indication to create an ad hoc conference. Before creating the conference the MCU checks whether 8675389 already exists as a valid conference; if not, the MCU creates a conference with a unique ID of 8675398. When the next user calls 55 8675389 a new conference is not created because the TANDBERG environment recognizes that 8675389 is already a valid conference; instead, the user is connected to this conference. Both Microsoft Office Communicator users and users of standards-based video conferencing systems can call the 55 8675389 number to join Alice’s meetme conference.

This mechanism provides a scalable means to add multiple TANDBERG MCUs to a mixed Office Communications Server and video conferencing environment. It allows an organization to start with one MCU and add MCUs as more ports are needed, while leaving the user experience untouched. OCS Relay is not used for this ad hoc conferencing model. The ad hoc conferences are created and removed on the fly as they are used. Not using OCS Relay means that AD accounts are not needed which allows for a dynamic ad hoc conference creation environment.

Multiway The fourth conference mechanism supported is based on the TANDBERG feature known as Multiway. Multiway is a feature that allows TANDBERG video conferencing endpoints (MXP, C series and E20) to easily escalate from a point-to-point call into a multiparty call with three or more participants. It leverages the TANDBERG MCU for ad hoc multiparty conferencing without the need for pattern matches or scheduling. Only TANDBERG endpoints can initiate Multiway calls, however Office Communicator clients can be called. Two main Multiway scenarios for a TANDBERG endpoint in a call with another endpoint or Office Communicator are:

• Placing the initial call on hold, calling another endpoint/Office Communicator and then conferencing all three sites together, which moves all participants to a multiparty conference on the TANDBERG MCU.

• Receiving a call from another endpoint/Office Communicator. The TANDBERG endpoint can place the first call on hold, answer the second call and then join both participants in a conference hosted on an MCU.

7.10.3 Call policy enforcement - bandwidth limited calls The bandwidth of the calls in the use cases outlined in this section can be controlled via the call policy functions of the VCS. For example, an enterprise deployment may have a branch office with a TANDBERG video conferencing endpoint in the conference room. The branch office is connected to the corporate network over a limited bandwidth connection such as a T1/E1. In order to preserve bandwidth for data activities over this connection, the VCS can be configured to allow a maximum of 768kbps of bandwidth for video calling. In this case, two 384kbps calls would be allowed over the connection; a third call would not be allowed. This is done to ensure that:

• The video calling adheres to the applied policy rules.



• The quality of the existing calls is maintained. It is possible to configure the VCS to allow more than two 384kbps calls over the pipe, it was just an example. The actual configuration will be based on the customer’s objectives and policies. The benefit of the VCS integration with Office Communications Server is that when calls go between the Office Communicator client and a video conferencing environment with the VCS acting as an OCS Gateway, then the VCS call policy can be enforced for those calls.

Figure 48: Main office and branch office connected with a bandwidth policy in place

Alice

Media path

IP Network

Enterprise - FictBiz.com

BoardRoom

Remote branch

100 Mbps Network Connection VCS can be configured to limit the bandwidth of this call

2 Mbps Network Connection

VCS and OCS Gateway Environment



8 Deployment preparation

8.1 Required TANDBERG software versions The following software versions are required:

• VCS X5.0 or later • MXP F8.1 or later • TMS 12.5 – when using VCS Clustering in X5 and FindMe, otherwise earlier versions of TMS

may be acceptable. See the TMS documentation for the devices it supports. • MCU 3.0 and later • ISDN Gateway (1.17N)

8.2 Required Microsoft software versions The following software versions are required (when these products are included in the solution):

• Microsoft Windows Server 2003 • Microsoft Windows Server 2008 (Microsoft Windows Server 2008 R2 is NOT supported) • Office Communications Server 2007 • Office Communications Server 2007 R2 • Office Communicator Client • Office Communicator Client R2



9 Solution limitations

9.1 Calling scenarios not supported The following call scenarios are not supported with the current integration:

• External Office Communicator clients

• Office Communicator users must be on the network, either physically or via VPN, for video calling to work between Office Communicator and the video conferencing solution. There is no interoperability with the Microsoft AV Edge server technology at this time.

• Microsoft Conferencing (AVMCU)

• There is no support for interoperability with the Microsoft Audio/Video MCU, therefore if a video conferencing endpoint is invited into an AVMCU conference it will not connect with video.

• Data collaboration via LiveMeeting or Desktop Sharing

• The video conferencing industry supports a standard known as H.239 over H.323 and BFCP over SIP. This is a mechanism to share content in a second video stream. The Microsoft model does not support these standards and the video conferencing space does not support the LiveMeeting or R2 based Desktop sharing mechanism.

• It is possible to share content via BFCP/H.239 from a video conferencing system in the TANDBERG solution while that same PC can be connected to a Live Meeting data collaboration session in which the content will be shared with the Live Meeting participants. All participants can be connected via audio and video into the TANDBERG MCU.

9.2 Additional know limitations • DTMF Interworking on VCS

• The VCS does not interwork Office Communicator R2 DTMF from SIP to H.323, since R2 leverages out-of-band DTMF.

• R1 leveraged in-band DTMF which is supported since there is no interworking requirement.

• ISDN calling to Polycom VSX is not supported



10 Understanding HD video calling with Office Communicator

It is important to understand how Office Communicator operates in order to ensure the user is getting the experience they expect from the TANDBERG PrecisionHD USB camera or any camera with Office Communicator. Refer to the PrecisionHD USB Camera Quick Reference Guide for Microsoft Office Communicator which can be found on the following site: http://www.tandberg.com/partners/unified‐communications‐microsoft.jsp Microsoft requirements for supporting HD video

• The Office Communication Server software ships with HD video disabled by default. The administrator must enable support for HD video on the Front End server.

• Office Communicator requires a PC with a quad-core CPU in order to support HD video. If the

user’s PC is dual core, Office Communicator will support a maximum resolution of VGA and if it is a single core it will only support CIF resolution video.

• When a call is initially established with Office Communicator it is in CIF resolution by default.

The user must select the appropriate video window size to enable HD. Note that the “small” window supports CIF, the “medium” window supports VGA and the “large” window supports HD.

• Support for HD video in Office Communicator uses the Microsoft proprietary RT VIDEO codec

only. Therefore interoperability of HD video with any standards-based video conferencing solution will require the video conferencing solution to support RT VIDEO since there is no support for H.264 in Office Communicator. (Note the video conferencing industry has standardized on H.264 for HD video.)

http://www.tandberg.com/partners/unified-communications-microsoft.jsp



Appendix A: Roadmap The TANDERG VCS is a major part of the TANDBERG UC Gateway technology. TANDBERG will be adding hardware and software to enhance the integration between the standards based video conferencing environment with Office Communicator. The TANDBERG roadmap is designed around allowing customers to implement the solution today based on the CVI model and then layer on the added roadmap functionality. For more detailed product roadmap information contact your TANDBERG representative.

Quality TANDBERG is working to add network based media processing capabilities that will build on the TANDBERG VCS as a network based UC Gateway solution for integration of the video conferencing environment with Office Communicator environment. The network based media processing capability will allow for Office Communicator clients to communicate in much higher video quality than is possible today. It will enable video resolutions between Office Communicator and standards based video conferencing environment, which leverages the H.264 standard, up to and including HD. The benefit of this capability is to enable higher quality video calling between Office Communicator and the standards-based video conferencing environment. The reason to implement this capability at the network level is to allow for high quality video calling from Office Communicator to the widest range of video conferencing endpoints and network products such as MCUs and recording devices.

External Office Communicator Connectivity TANDBERG is exploring solutions that will provide interoperability with the Microsoft Access Edge server technology. This will allow an organization to enable their remote Office Communicator clients to connect with the corporate enterprise video conferencing environment without the need for a VPN.

Security TANDBERG is exploring solutions to allow for video calls between Office Communicator and the standards based video conferencing environment to be have their media streams (audio and video) to be encrypted.



Appendix B: VCS details This chapter is a helpful primer on the basic workings of the VCS. This provides an important foundation for understanding the capabilities that VCS enables in an Office Communications Server environment. This chapter is not intended to cover the VCS in its entirety, please refer to addition documentation on the VCS. The VCS is powerful platform allowing corporate video conferencing environments based on the H.323 standard to continue to operate over H.323 while introducing connectivity to SIP-based environments such as Microsoft’s Office Communications Server platform. The VCS can be thought of as two core products with several applications and capabilities:

• At its core, the VCS is both a H.323 gatekeeper and a SIP Server. o On top of this, VCS does SIP to H.323 interworking. It is this function that makes the VCS

a very powerful tool in the video conferencing network allowing migration from H.323 to SIP

• The VCS also is a Call Policy server that defines bandwidth rules for a network - and enforces call policy based on those user defined rules.

A couple of applications that run on VCS and work seamlessly together are FindMe and the Office Communications Server Relay:

• FindMe brings the notion of a PBX-based hunt group to the video conferencing world.

• Office Communications Server Relay allows any standards-based video conferencing device which can register with VCS to be proxied into Office Communications Server making it appear to Office Communications Server as a Communicator client registration.

Finally, the VCS is the TANDBERG platform for secure firewall traversal: the marketing term for this is Expressway. Expressway is not to be confused with firewall bypass. Expressway actually traverses the corporate firewall and consequently helps preserve IT policy by not circumventing the corporate firewall. In summary, the VCS provides the following:

• H.323 gatekeeper

• SIP server (registrar/proxy and more)

• SIP to H.323 interworking

• IPv4 to IPv6 interworking. (Note this was not addressed in this document, please refer to the VCS references in the References section.)

• Call policy server – bandwidth management

• FindMe – FindMe follow-me type functionality

• Office Communications Server integration via OCS Relay

• Firewall traversal platform

• Conference factory (Multiway). (For additional information please refer to the VCS references in the References section.)



Appendix C: References See the following documents for additional information. TANDBERG documentation: http://www.tandberg.com/support/video-conferencing-documentation.jsp Product = VCS, List of all of the VCS related documentation. Listed below are a few of the more relevant documents as it pertains to Office Communications Server integration:

• TANDBERG VCS Administrator Guide (X5) • TANDBERG FindMe User Guide (X5) • TANDBERG VCS Deployment Guide - Microsoft OCS 2007 (R1 and R2) and VCS Control

(X5) • TANDBERG VCS Deployment Guide - Certificate creation and use with VCS • TANDBERG VCS Deployment Guide - Multiway Deployment (X5)

Product = Management Suite (TMS) Lists TANDBERG Management Suite related documentation.

• TANDBERG Management Suite v12.2 Administrators Guide • TANDBERG Conferencing eXtensions for Microsoft Exchange Administrator Guide

Search for TANDBERG endpoint, MCU and PrecisionHD USB Camera documentation along with all other TANDBERG product documentation at the aforementioned site.


http://www.tandberg.com/support/dl.php?id=1066&dir=User_Manuals&fn=TANDBERG%20VCS%20Administrator%20Guide%20(X5).pdf

http://www.tandberg.com/support/dl.php?id=1067&dir=User_Manuals&fn=TANDBERG%20FindMe%20User%20Guide%20(X5).pdf

http://www.tandberg.com/support/dl.php?id=1118&dir=Deployment_Guides&fn=TANDBERG%20VCS%20Deployment%20Guide%20-%20Microsoft%20OCS%202007%20(R1%20and%20R2)%20and%20VCS%20Control%20(X5).pdf

http://www.tandberg.com/support/dl.php?id=1118&dir=Deployment_Guides&fn=TANDBERG%20VCS%20Deployment%20Guide%20-%20Microsoft%20OCS%202007%20(R1%20and%20R2)%20and%20VCS%20Control%20(X5).pdf

http://www.tandberg.com/support/dl.php?id=1115&dir=Deployment_Guides&fn=TANDBERG%20VCS%20Deployment%20Guide%20-%20Certificate%20creation%20and%20use%20with%20VCS.pdf

http://www.tandberg.com/support/dl.php?id=1119&dir=Deployment_Guides&fn=TANDBERG%20VCS%20Deployment%20Guide%20-%20Multiway%20Deployment%20(X5).pdf

http://www.tandberg.com/support/dl.php?id=837&dir=User_Manuals&fn=TANDBERG%20Management%20Suite%20v12.2%20Administrators%20Guide.pdf

http://www.tandberg.com/support/dl.php?id=838&dir=User_Manuals&fn=TANDBERG%20Conferencing%20eXtensions%20for%20Exchange%20Administrator.pdf



Appendix D: About TANDBERG TANDBERG is the market leader in visual communications, offering a comprehensive range of voice, video, and data communications solutions. A Microsoft Gold Partner, TANDBERG provides sales, support, and value added services in over 90 countries.

Appendix E: VCS SIP trunk and OCS to PBX integration

Office Communications Server provides mechanisms for integrating the PBX. There are several options for integrating the telephone user experience of the PBX with Office Communications Server; these include “Dual Forking” and “Simul-Ring” (see the Microsoft documentation for further information). The challenge with leveraging either of these Office Communications Server to PBX integration mechanisms for integrating visual communications with Office Communications Server is that they are limited in functionality and telephony-focused. An integration between Office Communications Server and the PBX typically leverages the Microsoft Mediation server; either as an integrated part of the PBX manufacturer’s integration with Office Communications Server or as a standalone server role. The Mediation Server essentially terminates the Microsoft-specific SIP implementation, the Microsoft conferencing protocol and the Microsoft audio codecs, and provides a standard SIP interface as well as audio that is transcoded into a standard form such as G.711 so that other vendors can easily integrate with the Office Communications Server environment. The important thing regarding video integration is that the Mediation Server only supports audio and therefore cannot be used for video integration. Because of these limitations TANDBERG took the approach of integrating VCS with the Office Communications Server directly via the SIP protocol. (Note that the Microsoft Mediation Server is not used for the TANDBERG to Office Communications Server integration; the VCS to Office Communications Server integration is a “Direct SIP” integration.) TANDBERG supports the Microsoft variety of SIP on the interface between the VCS and Office Communications Server. The VCS then translates this into standard SIP and/or H.323 for interworking calls between Office Communicator clients and other standards-based SIP or H.323 video devices. In so doing, there are several benefits of this OCS Gateway approach to Office Communications Server integration. It:

• Does not alter the Office Communications Server interface with the PBX.

• Allows all three environments (Office Communications Server, PBX, and video conferencing) to work together.

• Simplifies the development needed for Office Communications Server integration of the video conferencing environment by centralizing the Microsoft-specific functionality in the VCS interface which is scalable and resilient.



Disclaimers and notices The objective of this guide is to provide the reader with assistance in using and configuring this product. Product capabilities of TANDBERG and other manufacturers’ products change over time and so the required configuration may be different from that indicated here. If you have any suggestions for changes to this document, please feed them back to TANDBERG through your TANDBERG Authorized Service Representative. If you need technical support, please contact your TANDBERG Authorized Service Representative. The specifications for the product and the information in this Guide are subject to change at any time, without notice, by TANDBERG. Every effort has been made to supply complete and accurate information in this Guide; however, TANDBERG assumes no responsibility or liability for any errors or inaccuracies that may appear in this document. TANDBERG® is a registered trademark belonging to Tandberg ASA. Other trademarks used in this document are the property of their respective holders. This Guide may be reproduced in its entirety, including all copyright and intellectual property notices, in limited quantities in connection with the use of the VCS product. Except for the limited exception set forth in the previous sentence, no part of this Guide may be reproduced, stored in a retrieval system, or transmitted, in any form, or by any means, electronically, mechanically, by photocopying, or otherwise, without the prior written permission of TANDBERG. www.tandberg.com

tandberg telepresence and video conferencing with microsoft

Documents

video conferencing endpoints

tandberg integration

authentication registration

video conference room

mobility pc video peripherals

office communicator

business benefits

solution capabilities