Cisco (Tandberg) OCS Unified Communication Configuration Guide

Cisco (Tandberg) OCS Unified Communication Configuration Guide
Microsoft Office
Communications
Server 2007
Interoperability
®
Configuration Guide
D50521 revision 1.0
March 2008
This document is not to be reproduced in whole or in part without permission in writing from TANDBERG
COPYRIGHT © 2008, TANDBERG – All rights reserved
TABLE OF CONTENTS
TANDBERG - MICROSOFT .......................................................................................................5
Introduction .................................................................................................................................5
Purpose.......................................................................................................................................5
TANDBERG OFFICE COMMUNICATIONS SERVER 2007 INTEROPERABILITY ..................6
Adhoc Communications ..............................................................................................................7
MXP Configuration – Room Systems ...............................................................................8
Single Identity............................................................................................................................10
MXP Configuration – Single Identity ...............................................................................10
Conferencing.............................................................................................................................11
Conferencing Configuration – TANDBERG Codian MCU...............................................12
Conferencing Configuration – TANDBERG MPS ...........................................................14
Standards Integration................................................................................................................16
H.323 and H.320 Configuration ......................................................................................16
Directories and Management ....................................................................................................17
TMS Directory Configuration...........................................................................................17
SUPPORTED EQUIPMENT AND SOFTWARE .......................................................................18
ADDITIONAL INFORMATION..................................................................................................19
Page 2
of 19
LIST OF FIGURES
Figure 1.
Figure 2.
Figure 3.
Figure 4.
Figure 5.
Figure 6.
Figure 7.
Figure 8.
Figure 9.
Figure 10.
TANDBERG Video Systems Appear in Office Communicator Contact List ..........7
TANDBERG MXP endpoint registered to Office Communications Server ............8
Example Active Directory Account for a TANDBERG MXP ..................................8
TANDBERG MXP SIP Configuration.....................................................................9
TANDBERG MXP SIP Registration.......................................................................9
Single Identity ......................................................................................................10
Conferencing .......................................................................................................11
Example Office Communicator client showing Virtual Conference Rooms .........12
Standards Integration Example ...........................................................................16
TMS Directory Support ........................................................................................17
Page 3
of 19
DOCUMENT REVISION HISTORY
Revision 1.0
Initial version
Page 4
of 19
TANDBERG - MICROSOFT
Introduction
TANDBERG has been a long standing Microsoft® developer partner and has focused on
providing interoperability between the TANDBERG total solution and various Microsoft
th
offerings. On October 16 2007, Microsoft launched its unified communications software
package known as Microsoft® Office Communications Server 2007 (OCS) and the Microsoft
Office Communicator 2007 client (MOC). In February of 2007 TANDBERG released its first
version of software providing interoperability with Office Communications Server 2007.
The combined capabilities of Office Communications Server 2007 along with TANDBERG’s
interoperable software allows TANDBERG and Microsoft customers to leverage business
quality visual communications tools in their daily business process enabling more effective and
efficient communications.
TANDBERG has been providing interoperable solutions with various Microsoft platforms for
years. These solutions included integration with Microsoft Live Communications Server 2005
(LCS 2005), as well as integration with Exchange Server 2000 and 2003. The TANDBERG
Exchange server integration has been an industry leading solution due to being true server
side integration rather than just a client side plug-in for Outlook. TANDBERG has also
provided innovative solutions making it easy to record and stream content from standard
based visual communications devices via the TANDBERG Content Server, with the use of the
Content Server APIs, Microsoft SharePoint 2007 can provide a front end portal to this content.
Purpose
The purpose of this document is to outline the supported interoperability between TANDBERG
and Office Communications Server 2007 as well as to provide the necessary TANDBERG
configuration information. While this document may provide some basic Microsoft configuration
information for reference purposes, it is not the intent nor is it within the scope of this
document to address Office Communications Server configuration. Please refer to the
Microsoft web site for the relevant Microsoft documentation.
This document only addresses TANDBERG device configuration as it relates to interoperability
with Office Communications Server, it is not an exhaustive device configuration guide. Please
see the relevant individual TANDBERG product manuals for additional information, which can
be found at http://www.tandberg.com/support/documentation.
Page 5
of 19
TANDBERG OFFICE COMMUNICATIONS
SERVER 2007 INTEROPERABILITY
The Microsoft Office Communications Server platform is intended to unify the many
communications modalities available to the end user today; providing a software based
platform for unifying voice, instant messaging, presence, email, calendars, and most
importantly video. The intent is to provide the end user with a simple interface that allows for
the seamless transition between communications modalities based on the needs of the end
user rather than having the work flow dictate the communications process.
The audio and video capabilities of the Office Communications Server solution are based on
the underlying SIP protocol. TANDBERG has been leading the video conferencing industry
with its support for video conferencing over multiple protocols including SIP. The
interoperability described in this guide is based on leveraging TANDBERG’s SIP
implementation and ensuring interoperability with the Microsoft Office Communications Server
2007 implementation. TANDBERG’s interoperability broadens the scope and reach of the
Office Communications Server solution enabling communication with other standards based
visual communications that have been deployed for years based on the H.320, H.323 and
H.324M standards.
TANDBERG’s interoperability with Office Communications Server also unifies the range and
scope of visual communications tools available to the user. Interoperability with Office
Communications Server allows users to leverage web cameras, TANDBERG Personal
Telepresence Systems, High Definition Conference room systems and ultimately integration
with both the TANDBERG Experia and HP Halo Studios Telepresence solutions. This allows
for the user to have access to the right communications tools at the right time for the most
efficient and effective communications flow.
This configuration guide will outline the following initial points of interoperability between the
TANDBERG solution and Microsoft Office Communications Server 2007 Environment.
•
•
•
•
•
Adhoc Communications
Single Identity
Conferencing
Standards Interoperability
Directories and Management
Page 6
of 19
Adhoc Communications
The Microsoft Office Communications Server and Office Communicator Client provide a
powerful tool for adhoc communications. The Office Communicator client makes provides a
powerful interface to easily initiate communications.
The TANDBERG solution leverages the power of the Office Communicator interface allowing
Office Communicator users to connect with TANDBERG video devices the same way a Office
Communicator user would connect with another Office Communicator user.
All TANDBERG MXP endpoints which run the F-series software require upgrade to F6.3. The
F6.3 software allows the TANDBERG MXP endpoints to register and authenticate (NTLM) with
Office Communications Server 2007.
In order for the TANDBERG video systems to register with Office Communications Server they
must have a valid Active Directory account. This is applicable to conference room systems
which are typically a shared resource. Personal systems may not require a unique account in
Active Directory and may be able to leverage an existing Active Directory account of an
individual. This is explained in more detail below.
The TANDBERG MXP systems will also be able to be able to publish presence providing a
consistent user experience. The ability of the MXP endpoints to publish presence is planned
for a subsequent software release. Once the TANDBERG MXP endpoints have registered with
Office Communications Server, they can be searched for and added to a contact list, just like
other Office Communicator users.
The image below shows an example of a contact list with a group for conference room
systems.
Calling the conference room systems is the same as calling another Office Communicator
client. Either right-click over the contact and select “Start a video conference” or double-click a
conference room contact and then click on the camera icon...
Figure 1.
TANDBERG Video Systems Appear in Office Communicator Contact List
Page 7
of 19
SIP (Microsoft OCS Infrastructure)
MOC
OCS
SIP signaling
SIP Registration
Media
MXP
Figure 2.
TANDBERG MXP endpoint registered to Office Communications Server
MXP Configuration – Room Systems
The following steps are required to configure the F6.3 software on the MXP device.
A valid account in Active Directory is required for each TANDBERG room system which will
register with Office Communications Serer. Configuration of Microsoft Active Directory is
beyond the scope of this document; please refer to Microsoft for further information. The
following figure is provided as an example of an Active Directory account for a room system
being enable for Office Communications Server.
Figure 3.
Example Active Directory Account for a TANDBERG MXP
Page 8
of 19
Log on to the web interface of the TANDBERG MXP device and go to the SIP Configuration
page. See Figure 4 below for an example configuration.
1)
Mode = On
2)
SIP Address (URI) = SIP URI assigned to the AD account created for this device.
3)
Server Discovery = Manual
4)
Server Address = the address to the Office Communications Server
5)
Transport =TLS
6)
Verify TLS = Off
7)
SIP Authentication
Username = the login user name of the corresponding AD account.
Password = the corresponding password for the account
If your Office Communications Server is deployed in a multi-forest domain, please
enter your SIP authentication username as <username@DNSDomainName>.
Notice that the pre-Windows2000 format (<domain\user> is not supported.
To get your login username, open a command line prompt, “echo
%USERDNSDOMAIN%” the output of this command will give you your
DNSDomainName.
Set the system to Microsoft SIP mode
1)
2)
3)
Open a command line prompt
Telnet into your system
Type the command “xConfiguration SIP Server Type: Microsoft”
Note: this can also be configured with the remote control and system UI from the SIP
settings screen.
Verify that your system is Registered (See Figure 4 below for an example of the registration
status screen.
Figure 4.
TANDBERG MXP SIP Configuration
Figure 5.
TANDBERG MXP SIP Registration
Page 9
of 19
Single Identity
The Microsoft Office Communications Server supports a concept known as Multiple Points of
Presence (MPOP). This allows a user to have multiple devices registered with the same
credentials as their Office Communicator client, allowing for a single user identity with the
Office Communications Server solution. TANDBERG MXP devices support the MPOP
mechanism. This will allow, for example, an executive to have a TANDBERG 1700 on their
desk running along side their Office Communicator client. In the figure below, Alice wants to
contact Bob. Alice sees Bob in her contact list and places a video call to Bob. Alice does not
know and does not need to know anything about Bob’s available devices. The call from Alice
simultaneously rings on Bob’s TANDBERG 1700 and Office Communicator client. Bob is able
to answer on which ever device is appropriate at the time. If he is in the office he can answer
the call with his TANDBERG 1700 personal telepresence system and if he is traveling he can
answer the call with his Office Communicator client.
SIP (Microsoft OCS Infrastructure)
MOC
OCS
SIP signaling
SIP Registration
Media
Note: depending on how the call is
answered media will go to
either the T1700 or MOC
MXP
Figure 6.
Executive
Desktop
Single Identity
In contrast to the room system scenario detailed in the Adhoc Communications section above,
no additional Active Directory account is needed for the TANDBERG 1700 in this example.
The TANDBERG 1700 in this example leverages the same user credentials as the Office
Communicator user.
MXP Configuration – Single Identity
The MXP configuration for Single Identity is identical to the room system configuration
described in the preceding section with one exception.
The SIP Address (URI) = the same SIP URI as that of the Office Communicator client
The SIP Authentication credentials are those of the Office Communicator users
Please refer to section 2.2.1 step 7 for further details on the appropriate format for the SIP
Authentication credentials.
Page 10
of 19
Conferencing
The TANDBERG Bridging solutions also provides interoperability with Office Communications
Server 2007. This allows for mixing multiple Office Communicator users together in a
conference along with any other standards based visual communications equipment. The
TANDBERG conferencing solutions provide a feature rich environment to meet the needs of
different meeting formats from voice switched to various continuous presence layouts. The
TANDBERG conferencing solution also provides a high quality conferencing experience when
mixing different meeting participants connecting via systems with varied capabilities, ultimately
providing the highest quality experience that each user is capable of based on their resources.
High definition capable systems continue to get high definition conferencing experience.
The conferencing model provided by the TANDBERG solution is a “Virtual Meeting Room”
concept. This allows Office Communicator users to click on a “Virtual Meeting Room” contact
in their contact list connecting them to the meeting.
SIP (Microsoft OCS Infrastructure)
MOC
SIP signaling
H.323 signaling
OCS
Media
MCU Experia/Halo
MXP
Executive
Desktop
Legacy H.323 VC
VCS
H.323 GK
H.323 (Tandberg VCS Infrastructure)
Figure 7.
Conferencing
Page 11
of 19
Figure 8.
Example Office Communicator client showing Virtual Conference Rooms
The TANDBERG Codian MCU and the TANDBERG MPS have slightly different
implementations. The Codian MCUs require a valid Active Directory Account for each of the
Virtual Meeting Rooms registered into Office Communications Server, while the MPS does not
require accounts to be created in Active Directory.
Conferencing Configuration – TANDBERG Codian MCU
The following steps are required to configure the TANDBERG Codian 4200 and 4500 MCUs.
Valid Active Directory accounts are required for each of the conferences that the MCU will
register with Office Communications Server.
Office Communications Server configuration
----------------1) Start the Office Communications Server interface by going to Start > Administrative Tools >
Office Communications Server 2007.
2) Office Communications Server uses TLS by default; therefore TCP needs to be enabled in
addition.
2.1) Right-click on the fully-qualified domain name (e.g. ocs-server.codian.com), then
select Properties > Front end properties.
2.2) The Front End Server Properties dialog appears. Click Add.
2.3) For IP Address, select All.
2.4) For Port, enter 5060.
2.5) For Transport, select TCP.
2.6) Click OK twice.
3) Right click on the server name (e.g. ocs-server) and select Properties > Front end
properties.
4) In the Host Authorization tab click Add and enter the IP address of the MCU / IP VCR / IP
GW that will register with Office Communications Server. Tick the Treat as Authenticated
check box.
5) On the Office Communications Server, set up a user for the MCU / IP VCR / IP GW:
5.1) Click on Start > Administrative Tools > Active Directory Users and Computers.
5.2) Right-click on Users and select New > User.
Page 12
of 19
5.3) Enter a name for the MCU / IP VCR / IP GW (that will appear in people’s contact
lists) and give it a logon name of the form “examplename@example.com”.
5.4) Click Next.
5.5) Enter a password for the MCU / IP VCR / IP GW. Note that this is not used
because the unit is an authorized host. Un-tick the check box that will prompt the user
to change their password next time they log in, and tick the check box that display the
message that the password never expires.
5.6) Click Next, then click Finish.
6) In the list of users, double click on the MCU / IP VCR / IP GW that you just created and
select the Communications tab.
7) Tick the check box Enable user for Office Communications Server.
8) Enter the logon name, now prefixed with “sip:”. In our example this would be
“sip:examplelogon@example.com”.
9) Select the server name from the Server or Pool drop down list and click OK.
10) Repeat steps 5 to 9 for any conferences and auto attendants that you wish to register. In
step 8 the logon that you choose should be the numeric ID of the conference/recording or auto
attendant.
- For each conference, select it from the Conference list on the MCU and click the
Configuration tab, then tick the SIP registrar box. Then go to Settings > SIP and for SIP
registration setting, select Allow Conference Registration.
- For each recording, select it from the Recording list on the IP VCR and tick the SIP
registrar box. Then go to Settings > SIP and for SIP registration setting select Allow Recording
Registration.
Codian configuration
----------------1) On the MCU / IP VCR / IP GW, go to Network > Services and enable Incoming SIP (TCP)
and SIP (UDP) for port A (and for port B, if it is enabled).
2) Go to Settings > SIP.
3) If you did not register conferences, recordings or auto attendants individually in step 10,
then for SIP registration setting select Register MCU, Register IP VCR or Register IP GW.
Otherwise choose Allow conference registration or Allow Recording registration, as
appropriate.
4) Enter the address or host name of the Office Communications Server into the SIP registrar
address field.
5) For SIP registrar type, select Microsoft LCS.
6) Enter the username, e.g. examplelogon@example.com. (Note a password is not needed
because the unit is an authenticated host.)
7) For Audio codec, select G.723.1. This is a lower bandwidth codec than G.711u. The
remaining fields can be left as their defaults.
8) Click Apply changes. The screen will refresh, including an indication that the unit is
registered. (This may take a second or two to process: you may need to refresh the page
again to see it).
9) The MCU / IP VCR / IP GW can now be entered into contact lists in Office Communicator
and called into video and audio calls.
Launching calls from the TANDBERG Codian
----------------1) To call from the MCU / IP VCR:
1.1) Go to the Add Participant page (MCU) or either the Call out and record or Call out
and play recording page (IP VCR).
1.2) For Address/Host name or IP Address, type the user name without the domain
(i.e. “examplename” not “examplename@example.com”).
1.3) For Call protocol, select SIP.
1.4) Select the Use SIP registrar check box.
1.5) Click Call endpoint.
2) To call from the IP GW, set up a dial plan rule whose action type is 'SIP Registrar' using the
online help if necessary.
Page 13
of 19
From the Office Communicator Client
---------------1) Search for the conferences just as you would search for any other Office Communicator
contact.
2) To add the virtual meeting to your contact list, right click on the contact that appears in the
"results field", and choose "Add to contact list"
3) Right-click on the contact and click "Start a Video Call"
Conferencing Configuration – TANDBERG MPS
The following steps are required to configure the J4.2 software on the TANDBERG MPS
(Note, the J4.2 software is planned for release in Q1/08)
MPS configuration
----------------1) System Configuration -> SIP
1.1) Address = Office Communications Server 2007 address
1.2) Type = Microsoft
1.3) Mode = on
1.4) Transport Protocol, default = TCP
1.5) TLS, verify = off
2) System Configuration -> IP
2.1) DNS Interface 1, Address 1 -> Point to appropriate DNS server
2.2) DNS Interface 2, Address 2 -> Point to appropriate DNS server
3) Reboot MPS
4) MCU Configuration
4.1) Personal Conferences
4.2) Create a new conference, e.g. name: John, sip uri: John@mps.tandberg.com
Office Communications Server configuration
----------------1) Open Office Communications Server administrator snap-in
2) Right click with your mouse on Forest -> pool -> Front Ends, click Properties
3) Host authorization tab
3.1) add the MPS IP as "treat as authenticated"
3.2) Click "apply"
4) Routing tab
4.1) Click Add
4.2) (e.g.) Domain: mps.tandberg.com, IP: the IP of the MPS, transport TCP, Port 5060
4.3) Apply
5) Wait some time to have the new routes and host authorization lists to be updated
(The following steps may be require for TCP connections, if not already configured)
6) Expand the "Front ends"
7) Right-click the Office Communications Server to configure, click Properties
8) "Add..."
9) IP address "all", Port: 5060, Transport: TCP
From the Office Communicator Client
---------------1) Enter the name of the personal conference in the "search field", just below your contact
information field in your Office Communicator client.
2) The presence information will be propagated from the MPS, as "available" if the conference
is available.
3) Right-click on the contact that appears in the "results field", and click "Start a Video Call"
4) To add the virtual meeting to your contact list, right click on the contact that appears in the
"results field" (pkt. 3), and choose "Add to contact list"
Page 14
of 19
Page 15
of 19
Standards Integration
TANDBERG interoperability with Office Communications Server provides the ability to allow
Office Communicator clients to connect with other standards based H.320, H.323 and H.324M
devices via the dual registration capability of the TANDBERG equipment. This requires the
TANDBERG video endpoints and bridges to be registered via SIP to the Office
Communications Server and via H.323 to the TANDBERG VCS (or Gatekeeper).
The dual registration model allows both the TANDBERG video endpoints with an embedded
bridge to connect to Office Communicator users over SIP as well as any other video device
over H.323, effectively providing connectivity between Office Communicator users and
standards based H.323 and H.320 users. The same applies to the TANDBERG Conferencing
solutions which allow conferencing between SIP based Office Communicator users with
standard H.323 and H.320 systems. This includes external H.323 participants which are
utilizing H.460 firewall traversal.
SIP (Microsoft OCS Infrastructure)
MOC
SIP signaling
H.323 signaling
OCS
Media
Remote Access
Remote Users
Internet
MCU Experia/Halo
MXP
Executive
Desktop
VCS
H.323 BC
Remote H.323
Legacy H.323 VC
VCS
H.323 GK
H.323 (Tandberg VCS Infrastructure)
Figure 9.
Gateway
ISDN
Remote H.320
Standards Integration Example
H.323 and H.320 Configuration
Support for H.323 and H.320 connectivity is beyond the scope of this document. Please refer
to the individual device manuals for additional information on H.323 and H.320 configuration.
Page 16
of 19
Directories and Management
Directories are essential for allowing users to easily find and connect with other users, conference
rooms and conferences. As described above the TANDBERG equipment registered with Office
Communications Server will provide both an identity to Office Communications Server as well as
presence information making it very easy for the Office Communicator users to join conferences,
connect to conference rooms and reach other individuals using TANDBERG equipment or Office
Communicator.
It also needs to be easy to reach Office Communicator users from the conference room. This is where
directories become essential. TANDBERG is able to provide a directory of the Office Communicator
users based on the LDAP integration capabilities of the TANDBERG Management Suite (TMS). TMS is
able to pull the list of SIP URIs of the Office Communicator users from Active Directory and populate
this as a phone book in the TANDBERG MXP endpoints allowing a user of a TANDBERG MXP
endpoint registered to Office Communications Server to easily place calls to individual Office
Communicator users.
Management Infrastructure
AD
TMS
TMS Phonebook
Exchange
SIP (Microsoft OCS Infrastructure)
MOC
Experia/Halo
OCS
MXP
Executive
Desktop
Figure 10. TMS Directory Support
TMS Directory Configuration
Directory support is a standard function of TMS and is beyond the scope of this document. Please refer
to the appropriate TMS documentation.
The TANDBERG Management Suite is also essential even for an Office Communications Server
environment for providing the requisite management capabilities for the TANDBERG video conferencing
equipment. A full description of TMS is beyond the scope of this document.
Page 17
of 19
TANDBERG Office Communications Server 2007 Interoperability Configuration Guide
SUPPORTED EQUIPMENT AND SOFTWARE
The following is a list of TANDBERG equipment and the relevant software version needed to support
the aforementioned capabilities;
TANDBERG Management Suite
TANDERBG MXP Endpoints (F series software)
TANDBERG Conferencing Solutions
Codian 4200/4500
MPS 200/400
TMS 11.8 or later
F6.3
2.2(1.3)
J4.2 (planned for Q2/08)*
* Pre-release information and subject to change. Please check with the TANDBERG website for the
actual release.
DXXXXXXX
Page 18 of 19
TANDBERG Office Communications Server 2007 Interoperability Configuration Guide
ADDITIONAL INFORMATION
Please visit the TANDBERG website www.tandberg.com for additional information on all TANDBERG
Solutions
DXXXXXXX
Page 19 of 19
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising