Microsoft OCS 2007 and Cisco VCS Cisco TelePresence Deployment Guide Cisco VCS X5.2 Microsoft OCS 2007 (R1 & R2) D14269.
Contents Contents Introduction ............................................................................................................................6 Objectives and intended audience .......................................................................................................... 6 Deployment scenario............................................................................................................................... 6 Why add an “OCS Gateway” Cisco VCS Control? ...................
Contents Set up H.323 SIP interworking ............................................................................................... 33 Set Call routed mode to Always ..................................................................................................... 34 OCS configuration ................................................................................................................................. 35 Allow (M)TLS or TCP connection to OCS .............................................
Contents When using a Hardware Load Balancer in front of OCS ............................................................... 67 OCS rejects Cisco VCS zone alive OPTIONS checks with ‘401 Unauthorized’ and INFO messages with ‘400 Missing Correct Via Header'................................................................................................... 67 MOC stays in ‘Connecting …’ state.......................................................................................................
Contents Appendix 7 – Presence with and without transforms.......................................................77 OCS receiving Presence from non-OCS Relay FindMe™ entries, where there is no transform for Cisco VCS devices accessing OCS ...................................................................................................... 77 OCS receiving Presence from non-OCS Relay FindMe™ entries, where there is a transform for Cisco VCS devices accessing OCS ............................................
Introduction Introduction Objectives and intended audience This deployment guide provides instructions on how to configure a Cisco TelePresence Video Communication Server (Cisco VCS) Control version X5.2 and OCS (Microsoft OCS 2007 R1 or R2) to interwork. This guide also highlights the capabilities and limitations of interoperation of Cisco VCS Control and OCS.
Introduction The existing Video Network’s domain is vcs.domain, and can, if desired, also include devices registering with the domain test-customer.com. Endpoints registered to the Video Network may be SIP or H.323 endpoints; they must register with an ID in the format name@domain, where domain is a domain hosted on the Video Network (for example vcs.domain, or if desired test-customer.com). MOC clients registered to OCS are identified by URIs, for example: Steve with a URI steve.
Introduction Why add an “OCS Gateway” Cisco VCS Control? The “OCS gateway” Cisco VCS is an interface between an existing working video network and the Microsoft OCS system. There are a number of settings that need to be configured on the “OCS gateway” that are different from the recommended configurations for standard video routing Cisco VCSs.
Introduction Features and capabilities with different versions of software The versions of software (Cisco VCS X3 or X4, and OCS R1 or R2 / standard, enterprise) affect the capabilities of the deployed system. Cisco VCS works equally well with OCS Standard edition and OCS Enterprise edition. Cisco VCS X4.2 or X4.
Introduction Cisco VCS X4.2 or X4.
Introduction Cisco VCS X5 or later and OCS R1 As in X4: Cisco VCS can be in: the same domain as OCS a separate domain from OCS the same and separate domains from OCS Same domain is used by FindMe™ entries on Cisco VCS, which register as MOC devices on OCS (using OCS Relay): domain static route(s) are set up on OCS to route calls to Cisco VCS’s separate domain(s) Presence is only supported Cisco VCS to OCS: “Off-line” and “Available” and “In-call” are supported for “same domai
Introduction Same domain calls OCS to Cisco VCS can be made to “same domain” OCS Relay FindMe™ users and also to other devices with that domain which are routable from the “OCS gateway” Cisco VCS. OCS accepts and handles call hold (and resume) requests. OCS MOC clients can be joined into a Multiway™ conference.
Introduction SIP and H.323 video endpoints registered in the Video Network to MOC clients registered on OCS. MOC clients registered on OCS to SIP and H.323 video endpoints registered in the Video Network. It also describes how to enable presence so that MOC clients can see the presence status of endpoints registered in the video network. The configuration process describes each of these stages separately, so that individual stages can be implemented and tested before moving on to the next.
Introduction Different structures for OCS OCS systems have a number of building blocks, and so OCS systems may be constructed in many ways. A full scale OCS deployment is likely to use OCS Director, Hardware Load Balancers (HLBs), Front End Processors (FEPs) in enterprise pools, and a redundant AD server. For example: A smaller deployment may not use OCS Director servers, but may just use a Hardware Load Balancer in front of a set of Front End Processors.
Introduction OCS should be configured so that: 1. If the OCS system is fronted by a Hardware Load Balancer in front of OCS Directors then calls to and from the video network will go via the Directors; they will not be routed directly to or from the FEPs: OCS Directors should trust the “OCS gateway” Cisco VCS(s) OCS Directors should route Video network SIP domain(s) (and the OCS SIP domain) to the “OCS gateway” Cisco VCS cluster FQDN (or if only a single Cisco VCS, the FQDN of that Cisco VCS) 2.
Introduction 4. the “OCS gateway” Cisco VCS(s) also need to have 1 or more neighbor zones that contain the Peer addresses of all the OCS FEPs. the Hardware Load Balancer neighbor zone is pointed to by the Search rule(s) that route calls to OCS. the neighbor zones to the other FEPs must also have their Zone profile set to Microsoft Office Communications Server 2007 but must not be referenced by any Search rules.
Enabling calls between endpoints registered on Cisco VCS Controls in the video network Enabling calls between endpoints registered on Cisco VCS Controls in the video network Video network Cisco VCS Control configuration summary The configuration of the Cisco VCS Control(s) in the video network to allow calls to be made between endpoints that register to them should already have been carried out. Ensure that the following 2 items are configured: 1.
Enabling calls between endpoints registered on Cisco VCS Controls in the video network If any links are missing, log onto the command line interface and execute the command: xcommand DefaultLinksAdd OCS configuration No configuration is required on OCS to allow endpoints registered on the Cisco VCS Control to call other endpoints registered on the Cisco VCS Control. Registering endpoints to the Video Network Endpoint configuration. For H.323, configure the endpoints as follows: H.
Enabling calls between MOC clients registered on OCS Enabling calls between MOC clients registered on OCS Cisco VCS Control configuration No configuration is required on Cisco VCS Control for endpoints registered on OCS to call other endpoints registered on OCS. OCS configuration summary To configure OCS to enable calls to be made between MOC clients that register to it: 1. Create new users (if required) using active directory 2. Edit user properties to allow MOC usage 3.
Enabling calls between MOC clients registered on OCS 4. Right-click on Users and choose New > User. 5. Enter details of the new user: First name, Last name and User logon name (Steve.Test and Steve.Test for example). 6. Click Next. Cisco VCS Deployment Guide: Microsoft OCS 2007 R1 and R2 and Cisco VCS X5.
Enabling calls between MOC clients registered on OCS 7. Enter and confirm a password for the user and select the required password handling options: 8. Click Next. 9. Click Finish. Edit user properties to allow MOC usage In Active Directory now set up the properties of the user: 1. From this Users directory, right-click on this newly created user (Steve Test, for example) and choose Properties. 2. Select the Communications tab. 3. Select Enable user for Office Communications Server. 4.
Enabling calls between MOC clients registered on OCS 6. Click OK. Cisco VCS Deployment Guide: Microsoft OCS 2007 R1 and R2 and Cisco VCS X5.
Enabling calls between MOC clients registered on OCS Registering MOC clients to the OCS MOC client configuration 1. 2. Install MOC (Microsoft Office Communicator 2007). From the menu, go to Connect > Change Sign-In address… 3. Set up Sign-in address as required. This is the SIP URI of the MOC; if this user also has Video endpoints on the Video network, this URI will be the same URI as that configured as the OCS Relay FindMe™ user ID (set up later), for example steve.hight@test-customer.com.
Enabling calls between MOC clients registered on OCS 7. Click OK to return to the Office Communicator panel. 8. 9. Click Sign In. Username is the Active Directory name of the user. This may or may not be the same as the sign in address. Note: Depending on how the network is configured, the User name may need to be in the form \ rather than @ for example ocs2007.lcs.codian.com\Steve.Test instead of Steve.Test@ocs2007.lcs.codian.com 10.
Enabling calls between MOC clients registered on OCS 11. Click Sign In. Testing the configuration To make a video call between MOC endpoints: 1. Double-click on the buddy you want to call. 2. 3. Click (the web-cam). Answer the call on the receiving MOC Client. Cisco VCS Deployment Guide: Microsoft OCS 2007 R1 and R2 and Cisco VCS X5.
Enabling endpoints registered on the video network to call MOC clients registered on OCS Enabling endpoints registered on the video network to call MOC clients registered on OCS This is configured in 4 stages: 1. Video Network Cisco VCS Control Configuration 2. “OCS gateway” Cisco VCS Control configuration (1) 3. OCS Configuration 4. “OCS gateway” Cisco VCS Control configuration (2) Video network Cisco VCS Control configuration The video network must have a link to the “OCS gateway”; to configure this: 1.
Enabling endpoints registered on the video network to call MOC clients registered on OCS 4. Click Create Zone. It is recommended that the connection to the “OCS gateway” Cisco VCS uses SIP over TLS to communicate so that encrypted calls can be handled. H.323 mode should also be enabled, so that any interworking that has to be done for calls with OCS is carried out on the “OCS gateway” Cisco VCS. 5. Configure the following fields: 6.
Enabling endpoints registered on the video network to call MOC clients registered on OCS Set up a search rule to route calls with the OCS domain to the “OCS gateway” Cisco VCS (cluster). 1. 2. Go to the Rules page (VCS Configuration > Search rules > Rules). Click New. 3. Configure the following fields: Rule name An appropriate name, for example “Route to OCS gateway” Zone name Select the OCS gateway zone, for example “To OCS gateway” 4. Click Create rule. 5. Configure the following fields: 6.
Enabling endpoints registered on the video network to call MOC clients registered on OCS To configure an “OCS gateway” Cisco VCS Control: 1. Generate and load private key, root certificate and server certificate onto Cisco VCS. 2. Set up the SIP domain of the “OCS gateway” Cisco VCS. 3. Ensure that the default links between the “OCS gateway” Cisco VCS Control’s zones are set up. 4. Configure DNS. 5. Ensure that cluster name is configured. 6. Configure an NTP server. 7. Switch on TLS in SIP configuration.
Enabling endpoints registered on the video network to call MOC clients registered on OCS Set up the SIP domain of the “OCS gateway” Cisco VCS OCS Relay FindMe™ users need to have the “OCS gateway” Cisco VCS handle the OCS’s domain. 1. Go to the Domains page (VCS Configuration > Protocols > SIP > Domains). 2. Click New. 3. 4. Set Name to test-customer.com. Click Create Domain.
Enabling endpoints registered on the video network to call MOC clients registered on OCS Configure DNS details Configure the DNS Server details The “OCS gateway” Cisco VCS(s) should be configured to use the same DNS servers as OCS. On the machine running OCS: 1. From the Windows Start menu choose Run. 2. Type cmd into the Open field and click OK. A command window opens. 3. In the cmd.exe window type: ipconfig /all 4. Note down the DNS servers. Note: If the DNS server IP address is 127.0.0.
Enabling endpoints registered on the video network to call MOC clients registered on OCS 1. On the DNS page (System configuration > DNS) set: Local host name to a unique hostname for this Cisco VCS Domain name to the domain name for this Cisco VCS 2. Click Save. Note that the Local host name concatenated with DNS Domain name is the routable FQDN of this Cisco VCS.
Enabling endpoints registered on the video network to call MOC clients registered on OCS Configure an NTP server On each “OCS gateway” Cisco VCS Control peer: 1. Go to the Time page (System Configuration > Time). 2. 3. Set NTP server to the IP address of an NTP server Set Time zone as appropriate to the location of the Cisco VCS.
Enabling endpoints registered on the video network to call MOC clients registered on OCS When H.323 endpoints are interworked to OCS SIP, the Cisco VCS carrying out the interworking needs to know that it is interworking to OCS (as the interworking functionality needs to specifically handle the requirements of OCS), therefore the interworking must be carried out on the “OCS gateway” Cisco VCS. To ensure interworking is carried out on this “OCS gateway” Cisco VCS, set H.
Enabling endpoints registered on the video network to call MOC clients registered on OCS OCS configuration The configuration will vary depending upon the architecture of the OCS installation. If an OCS Director is in use then configure the OCS Director (pool) to trust the “OCS Gateway” Cisco VCS and to route traffic to Cisco VCS. (Other FEPs receiving calls for the Video domain will not know how to route them, so will pass the calls to the Director for routing.
Enabling endpoints registered on the video network to call MOC clients registered on OCS or if OCS Directors are being configured, right click on the OCS Director and choose Properties > Front End Properties. Cisco VCS Deployment Guide: Microsoft OCS 2007 R1 and R2 and Cisco VCS X5.
Enabling endpoints registered on the video network to call MOC clients registered on OCS If using Enterprise Edition Servers: a. Expand Enterprise Pools. b. Expand the required Pool. c. Right click on the relevant FEP and choose Properties > Front End Properties. 3. Select the General tab Cisco VCS Deployment Guide: Microsoft OCS 2007 R1 and R2 and Cisco VCS X5.
Enabling endpoints registered on the video network to call MOC clients registered on OCS 4. For TLS (recommended): Ensure that there is an entry that allows MTLS (Mutual Transport Layer Security) connectivity on port 5061. Typically this will be allowed from any IP address but could be limited to the “OCS gateway” Cisco VCS(s)’ IP address(es). If required, to create a new entry, click Add. For TCP (not recommended): Ensure that there is an entry that allows TCP connectivity on port 5060.
Enabling endpoints registered on the video network to call MOC clients registered on OCS a. b. expand Standard Edition Servers. right-click on the specific OCS FEP pool and choose Properties > Front End Properties. or right click on the OCS Director pool and choose Properties > Front End Properties. Cisco VCS Deployment Guide: Microsoft OCS 2007 R1 and R2 and Cisco VCS X5.
Enabling endpoints registered on the video network to call MOC clients registered on OCS If using an Enterprise Edition Server: a. expand Enterprise Pools. b. right-click on the FEP pool and choose Properties > Front End Properties. 3. On the Front End Properties dialog select the Host Authorization tab. Cisco VCS Deployment Guide: Microsoft OCS 2007 R1 and R2 and Cisco VCS X5.
Enabling endpoints registered on the video network to call MOC clients registered on OCS 4. 5. Click Add or Edit (depending on whether a new entry is to be added, or a previous one modified). For TLS (recommended) configure: FQDN FQDN of the “OCS gateway” cluster or FQDN of an “OCS gateway” Cisco VCS, for example vcsocsgateway.testcustomer.com, or vcsocspeerX.test-customer.
Enabling endpoints registered on the video network to call MOC clients registered on OCS Configure static route(s) to route calls to the “OCS gateway” Cisco VCS(s) If a call is to be routed to a Video Network device that is not registered to OCS (i.e. that is not an OCS Relay FindMe™ user), OCS needs to have static domain routes set up to identify which domains are video network domains accessible via the “OCS gateway” Cisco VCS(s).
Enabling endpoints registered on the video network to call MOC clients registered on OCS Note: The FQDN and the Domain do not have to be identical: The FQDN must be a routable domain name for the “OCS gateway” Cisco VCS / cluster of Cisco VCS peers; a DNS lookup must correctly resolve the FQDN to the IP address of the Cisco VCS / Cisco VCS peers e.g. vcsocsgateway.test-customer.com. The Domain is the domain to be routed from OCS to Cisco VCS e.g. vcs.
Enabling endpoints registered on the video network to call MOC clients registered on OCS 6. Repeat steps 3 to 5 for all domains routable to or through the “OCS gateway” Cisco VCS(s), including the domain shared between OCS and Cisco VCS (If there is a shared domain). Note: Static routes should be set up for all domains handled by the Cisco VCS, including the domain shared by Cisco VCS and OCS if Cisco VCS and OCS share the same domain.
Enabling endpoints registered on the video network to call MOC clients registered on OCS Note: This parameter is a value communicated to MOC to affect its operation. To activate this change on a MOC client, the MOC client must be logged off and logged back in again. It may take a while for the parameter to be shared throughout the pool (up to an hour) so you may have to wait a while before restarting the MOC clients for them take on the new value.
Enabling endpoints registered on the video network to call MOC clients registered on OCS “OCS gateway” Cisco VCS Control configuration (2) 1. 2. 3. Configure the “OCS gateway” Cisco VCS with a neighbor zone that contains OCS. Set up a Search rule to select what gets routed to the OCS zone. If Hardware Load Balancers are used, set up neighbor zones to receive calls from OCS Configure the “OCS gateway” Cisco VCS with a neighbor zone that contains OCS 1. 2. Go to the Zones page (VCS configuration > Zones).
Enabling endpoints registered on the video network to call MOC clients registered on OCS 5. For SIP over TLS configure the following fields: SIP mode On SIP port 5061 (or the value that is the same as that configured on OCS for Cisco VCS access over TLS) SIP transport TLS Not recommended, but if SIP over TCP is required, configure the following fields: 6.
Enabling endpoints registered on the video network to call MOC clients registered on OCS 3. Configure the following fields: Rule name To OCS Zone name OCS 4. Click Create rule. 5. Configure the Search Rule so that all calls to URIs in the format .*@test-customer.com are forwarded to OCS. (To handle presence messaging a .* is included at the end of the domain to allow any parameters following the domain to be retained in the SIP messaging.) 6.
Enabling endpoints registered on the video network to call MOC clients registered on OCS If Hardware Load Balancers are used, set up neighbor zones on the “OCS gateway” Cisco VCS(s) to receive calls from OCS If Hardware Load Balancers are used then OCS will still send messages to Cisco VCS from the devices directly behind the main Hardware Load Balancer.
Enabling endpoints registered on the video network to call MOC clients registered on OCS 5. For SIP over TLS configure the following fields: SIP mode On SIP port 5061 (or the value that is the same as that configured on OCS for Cisco VCS access over TLS) SIP transport TLS Not recommended, but if SIP over TCP is used, configure the following fields: 6. 7.
Enabling MOC clients registered on OCS to call endpoints registered on the video network Enabling MOC clients registered on OCS to call endpoints registered on the video network ”OCS gateway” Cisco VCS Control configuration 1. 2. Configure the “OCS gateway” Cisco VCS with a neighbor zone that contains the video network. Set up one or more Search rules to route calls with video network domains to the video network.
Enabling MOC clients registered on OCS to call endpoints registered on the video network 4. Click Create Zone. It is recommended that the connection to the “OCS gateway” Cisco VCS uses SIP over TLS to communicate so that encrypted calls can be handled. H.323 mode should also be enabled, so that any interworking that has to be done for calls with OCS is carried out on the “OCS gateway” Cisco VCS. 5. 6.
Enabling MOC clients registered on OCS to call endpoints registered on the video network Set up one or more search rules to route calls with video network domains to the video network 1. 2. Go to the Rules page (VCS Configuration > Search rules > Rules) Click New. 3. Configure the following fields: Rule name An appropriate name, for example “Route to Video network” Zone name Select the Video network zone, for example “To Video network” 4. Click Create rule. 5.
Enabling MOC clients registered on OCS to call endpoints registered on the video network Testing the configuration Test calls from MOC Clients registered on OCS to endpoints registered on Cisco VCS Control. For example, call mary@vcs.domain or john@vcs.domain from a MOC client registered on OCS. (Double click on the buddy then click to make a video call.) Cisco VCS Deployment Guide: Microsoft OCS 2007 R1 and R2 and Cisco VCS X5.
Enabling MOC clients to see the presence status of endpoints registered on Cisco VCS Control Enabling MOC clients to see the presence status of endpoints registered on Cisco VCS Control Using SIP-SIMPLE, OCS only supports the reception of the “available” status, so presence is limited to buddies indicating “gray” (not available), or “green” (available). “In-call” and other rich presence states are not handled by OCS.
Enabling MOC clients to see the presence status of endpoints registered on Cisco VCS Control SIP SIMPLE Presence User Agent On (if Cisco VCS Control is to generate presence information for registered endpoints) Note: The Cisco VCS that connects to OCS should be the presence server for ALL sip domains that OCS might want to look at for presence; this limits the number of Cisco VCSs that OCS’s presence requests will travel through.
OCS Relay configuration of “OCS gateway” Cisco VCS(s) OCS Relay configuration of “OCS gateway” Cisco VCS(s) The OCS Relay function allows personal video endpoints to appear in a similar manner to an MXP endpoint registered directly to OCS with the same credentials as an existing OC user, but still maintain the benefits of having the endpoint register to the Cisco VCS which is designed to support video calling.
OCS Relay configuration of “OCS gateway” Cisco VCS(s) presence of those devices whose presence is hosted on the “OCS gateway” Cisco VCS(s) and present the appropriate overall presence status. Use of FindMe™ also allows any endpoint that is referred to in the FindMe™ to take on the caller ID of that FindMe™ entry. This means that which ever video endpoint makes the call, the receiving MOC and video endpoints will see the call as having come from the FindMe™ ID.
OCS Relay configuration of “OCS gateway” Cisco VCS(s) For each new user that needs to be created: 3. 4. 5. 6. Click Create new user in the current container. Configure the following fields: First name The user’s first name Last name The user’s last name User logon name The user’s logon name Click Next. Configure the following fields: Password The user’s password Confirm password Retype the password Password never expires Select this check box. 7. 8. 9. Click Next. Click Finish.
OCS Relay configuration of “OCS gateway” Cisco VCS(s) 11. Click OK. 12. Repeat steps 3 to 11 for each new user account that needs to be set up. 13. Wait approximately 10 minutes for Active Directory / OCS to replicate the relevant data. To verify that OCS now recognizes this new user, log in to MOC as this new user. “OCS gateway” Cisco VCS Configuration The shared Cisco VCS / OCS domain test-customer.
OCS Relay configuration of “OCS gateway” Cisco VCS(s) Note: If SIP registration proxy mode is already configured as ProxyToAny this is also suitable. 12. Ensure that presence is enabled (as described in Enabling MOC clients to see the presence status of endpoints registered on Cisco VCS Control). 13. Ensure that the OCS Neighbor zone is set up as described in”“OCS gateway” Cisco VCS Control configuration (2)”.
OCS Relay configuration of “OCS gateway” Cisco VCS(s) PAGE 63OCS Relay configuration of “OCS gateway” Cisco VCS(s) Display name Full name of this user Phone number E164 number to use when outdialing to a gateway FindMe ID URI with OCS’s domain that will register to OCS as though it were a MOC Principal device address Routable endpoint URI / E164 or H.323 ID to call when this FindMe™ is called. Initial password Password needed by the FindMe™ user to log in to Cisco VCS to administer this account Confirm password As Initial password 23.
Appendix 1 - Troubleshooting Appendix 1 - Troubleshooting Problems connecting Cisco VCS Control local calls Look at Search History to check the applied transforms. 1. Go to the Search history page (Status > Search history). 2. Search history entries report on any searches initiated from a SETUP/ARQ /LRQ in H323 and from an INVITE/OPTIONS in SIP. The summary shows the source and destination call aliases, and whether the destination alias was found. Select the relevant search attempt.
Appendix 1 - Troubleshooting Check for errors Event log Check the Event log (Status > Logs > Event log). Real time detailed event log To obtain a more detailed log of key events and errors, start up netlog level 1 logging and then try the call or initiate a presence action. 1. Log in to Cisco VCS Control as admin using an SSH or Telnet connection. 2. At the prompt type: netlog 1 3.
Appendix 1 - Troubleshooting MOC client fails to update status information If a MOC client is started before the presence server is enabled, the MOC client may need to be logged out and logged back in again before it will display the correct presence information. Check for errors Checking for presence problems should be carried out in the same way as checking for errors with calls: check the event log (available from the web browser) and the syslog 1 log.
Appendix 1 - Troubleshooting One way media: MOC endpoint registered to Cisco VCS When using Microsoft Edge Server When MOC registers to OCS through a Microsoft Edge Server, the local IP address and port that the MOC declares are usually private and un-routable (assuming that MOC is behind a firewall and not registered on a public IP address). In order to identify alternate addresses to route media to, the MOC uses ICE candidates.
Appendix 1 - Troubleshooting No video through an ISDN gateway Some ISDN endpoints initiate a call using one set of codecs, then before media is sent, change the codecs to better codecs (for example an initial offering of H.261 is updated to H.263). Neither MOC R1, nor MOC R2 accepts a change in codec before media is sent. To work around this, “Meet me” on a conference, so that the ISDN endpoint sets up a call and connects to the MCU and MOC sets up a call and connects to the MCU independently.
Appendix 1 - Troubleshooting OCS Relay FindMe™ users fail to register. If OCS Relay fails to register FindMe™ users (Registration status = failed), check: 1. The FindMe™ name is correctly entered into Active Directory. 2. A MOC client can register as the FindMe™ name. 3. The Cisco VCS SIP registration proxy mode is set to ProxyToKnownOnly (or ProxyToAny). 4. That there is no transform that may be inadvertently corrupting the registration – e.g.
Appendix 2 – Known interoperating capabilities Appendix 2 – Known interoperating capabilities SIP and H.323 endpoints making basic calls SIP and H.323 endpoints can make calls via Cisco VCS Control to MOC clients registered to OCS. MOC clients registered to OCS can make calls to SIP and H.323 endpoints on Cisco VCS Control.
Appendix 3 – Benefits of using Cisco VCS with OCS Appendix 3 – Benefits of using Cisco VCS with OCS Separate management of video systems and PC based systems Video managers can manage the video endpoints in the Cisco VCS environment that they know, and IT managers can focus on managing the PCs without needing to learn about video. Cisco VCS brings H.323 integration to OCS OCS works with SIP. Cisco VCS Control works with SIP and H.323 and can interwork H.323 calls to SIP calls allowing H.
Appendix 4 – Known interoperating limitations Appendix 4 – Known interoperating limitations Video codecs If MOC (Microsoft Office Communicator) is used, then the video endpoints registered to the Cisco VCS Control must support H.263; this is the common video codec supported by endpoints and the MOC client. (The MOC client does not support H.264.) Video codec selection When the Cisco VCS Control receives an H.
Appendix 4 – Known interoperating limitations Microsoft Mediation Server Using OCS R1 Calls to Microsoft Mediation Servers are not supported by Cisco VCS. Using OCS R2 Calls to Microsoft Mediation Servers work from endpoints in the Cisco VCS Video Network for SIP initiated calls, but do not work for interworked H.323 initiated calls (the mediation server does not respond to the Cisco VCS INFO message, sent to check availability of the destination number).
Appendix 4 – Known interoperating limitations DTMF MOC R1 generates in-band DTMF only – this is good as it will work with any recipient requiring DTMF, whether the call is delivered to the endpoint as a SIP call or whether the call is delivered interworked to H.323. MOC R2 generates RFC2833 DTMF only – this causes problems if the OCS call is interworked by Cisco VCS to H.323.
Appendix 5 – Advanced parameters set by selecting zone profile ‘Microsoft Office Communications Server 2007’ Appendix 5 – Advanced parameters set by selecting zone profile ‘Microsoft Office Communications Server 2007’ By setting the Zone profile to Microsoft OCS 2007, the following Advanced zone parameters are set: Searches are automatically responded to Off Empty INVITE allowed Off See “Appendix 6 – Setting default codecs for H.323 to SIP calls” to modify codecs offered in the initial INVITE.
Appendix 6 – Setting default codecs for H.323 to SIP calls Appendix 6 – Setting default codecs for H.323 to SIP calls Codecs to be offered H.323 video calls typically do not provide codec information until after the call has connected. By contrast, in SIP, the codec information exchange is typically started in the original INVITE. By default, when interworking an H.
Appendix 7 – Presence with and without transforms Appendix 7 – Presence with and without transforms Presence SIP messages often have extra parameters in the URI header after the user-id@domain. In order to ensure that these extra parameters do not cause the search rules to fail to match, a ‘.*’ is appended to pattern strings. OCS receiving Presence from non-OCS Relay FindMe™ entries, where there is no transform for Cisco VCS devices accessing OCS For example, where to reach a MOC steve.
Appendix 7 – Presence with and without transforms Pattern type Regex Pattern string .*@test-customer.com.* Pattern behavior Leave On successful match Stop Target zone OCS Cisco VCS Deployment Guide: Microsoft OCS 2007 R1 and R2 and Cisco VCS X5.
Appendix 8 – TEL URI handling for Cisco VCS to OCS calls Appendix 8 – TEL URI handling for Cisco VCS to OCS calls If an endpoint wants to dial a telephone number rather than selecting a user from a directory, the Cisco VCS Control must format the telephone number appropriately for OCS to be able to look it up. OCS expects to see telephone numbers (known as TEL: URIs) in the form: + Cisco VCS Control can use transforms to appropriately format the telephone numbers.
Appendix 9 – Debugging on OCS Appendix 9 – Debugging on OCS Use of OCS Logging tool For debugging it is important to enable the logging on the appropriate OCS pool. If an OCS Director is in use, tracing here is a good starting point. Looking at the record-route headers from OCS will identify the FEP and Director involved in the call. 1. On OCS select Start > Administrative Tools > Office Communications Server 2007. 2. Expand Enterprise pools or Standard Edition Servers as required. 3.
Appendix 9 – Debugging on OCS 4. 5. Select the logging option, for example SIPStack to look at SIP logs. (Details about all the logging options may be found at: http://technet.microsoft.com/en-us/library/bb936621.aspx) Click Start Logging. 6. Make the call, or perform the function that needs to be debugged. 7. Click Stop Logging. 8. Click Analyze Log Files (install the OCS Resource Kit Tools if prompted to do so). 9.
Appendix 10 – Enable Debug on MOC Appendix 10 – Enable Debug on MOC If MOC is not behaving as it should, then logging can be enabled and SIP messaging and other logging can be checked. 1. Select Tools > Options. 2. Select the General tab. 3. In the Logging section: Select Turn on logging in Communicator Select Turn on Windows Event logging for Communicator Communicator log files may be found in: c:\Documents and Settings\\Tracing where is the login name of the windows login. The .
Appendix 11 – Endpoint specific configuration Appendix 11 – Endpoint specific configuration T150 Use code version L5.1 or greater. Set Network > SIP Settings > Server Type to Auto (not Microsoft). For versions prior to L6.0 set Security > Encryption to Off MXP 1000, MXP 1700 and MXP 6000 Use code version F7.0 or greater. Set Network > LAN Settings > SIP Settings > SIP Server Settings > Server Type to Auto (not Microsoft).
Appendix 11 – Endpoint specific configuration Other endpoints Other endpoints need to be tested for compatibility and required configuration. Although Cisco VCS does some manipulation of signaling data to make Microsoft SIP work with standard SIP and H.323 endpoints, Cisco VCS is not designed to fully insulated the Cisco VCS registered devices from OCS signaling nor OCS from the signaling of devices registered to the Cisco VCS. The Polycom FX endpoint running version 6.0.5 code is known to generate H.
Appendix 12 – Cisco TelePresence MCU configuration Appendix 12 – Cisco TelePresence MCU configuration MCU connectivity with OCS R1, OCS R2 and Cisco VCS When using OCS R1, MCUs can be configured to register to Cisco VCS or can be configured to register directly with OCS R1. With the changes Microsoft introduced in OCS R2, which include the use of multi-part mime, MCUs can not accept OCS R2 calls directly.
Appendix 13 – Cisco VCS and hardware load balancers in front of a bank of FEPs Appendix 13 – Cisco VCS and hardware load balancers in front of a bank of FEPS Background For OCS to scale to support large numbers of users, a pool of Front End Processors (FEPs) can be created for the OCS system. Each FEP is then run on a separate piece of physical hardware so that the hardware resources of a single platform are no longer the limitation on call and IM processing.
Appendix 13 – Cisco VCS and hardware load balancers in front of a bank of FEPs If Host Authorization is set to IP, the FEP checks that the source IP address of any incoming messages match an authorized IP address, if not they are rejected. If Host Authorization is set to FQDN, then the connection to OCS must be TLS, and that link must have certificates that authenticates that the connection comes from the stated FQDN. (A certificate can be generated on the OCS system, or can be created externally.
Appendix 13 – Cisco VCS and hardware load balancers in front of a bank of FEPs Responses directly from devices behind a Hardware Load Balancer If Source Address NATing is enabled on the HLB, responses to messages (like TRYING to an INVITE) will be routed back to the Cisco VCS via the HLB because the new transaction will be sent to the ‘From’ address, however, mid dialogue requests (like Re-INVITE and BYE) will be sent to the Cisco VCS directly because they will be sent to the device identified in the Recor
Appendix 14 – Cisco VCS and Microsoft OCS Director Appendix 14 – Cisco VCS and Microsoft OCS Director Background Microsoft recommends that OCS Director is deployed when an organization hosts multiple Standard Edition Servers or Enterprise pools. Microsoft OCS Director accesses the AD domain controllers for the whole network and can therefore both authenticate incoming requests, and also directs them to the appropriate enterprise pool or Standard edition server.
Appendix 14 – Cisco VCS and Microsoft OCS Director When used with Cisco VCS the OCS Director should be configured to be the receiver of calls from the “OCS gateway” Cisco VCS and the source of calls from OCS to the “OCS gateway” Cisco VCS (see configuration sections in the main part of this document).
Appendix 15 – Cisco VCS and OCS voicemail Appendix 15 – Cisco VCS and OCS voicemail Video endpoints picking up voicemail from OCS If you want to pick up voicemail from OCS using a SIP video network endpoint rather than using MOC, this can be achieved by calling the MOC URI with “;opaque=app:voicemail” appended, e.g. steve.hight@test-customer.com;opaque=app:voicemail If the user is a FindMe™ ID (e.g.
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
