Cisco TelePresence Microsoft Lync and Cisco VCS

Size: px
Start display at page:

Download "Cisco TelePresence Microsoft Lync and Cisco VCS"

Transcription

1 Cisco TelePresence Microsoft Lync and Cisco VCS Deployment Guide Cisco VCS X8.1 Microsoft Lync 2010, Lync 2013 D December 2013

2 Contents Introduction 5 Objectives and intended audience 5 Deployment scenario 5 Clustered Lync gateway VCS 7 Why add a Lync gateway VCS? 7 Features and capabilities 8 Summary of configuration objectives 9 Lync environments 10 Prerequisites prior to configuring VCS and Lync to interoperate 14 Benefits of using the B2BUA over legacy OCS Relay 14 Video network: check that calls between endpoints registered to VCS Controls operate as expected 15 VCS Control configuration summary 15 Ensure SIP domain of video network endpoints is configured in the VCS Control 15 Optional. Configuring interworking for H.323 endpoints registered to other systems 15 Lync configuration 15 Registering video endpoints to the video network 16 Video endpoint configuration 16 Confirming registrations 16 Testing the configuration 16 Check that calls between Lync clients registered on Lync Server operate as expected 17 VCS Control configuration 17 Enabling users for Lync 17 Registering Lync clients to the Lync Server 19 Lync client configuration 19 Testing the configuration 20 Enabling endpoints registered on the video network to call clients registered on Lync 22 Video network: VCS Control configuration 22 Video network: Set up a neighbor zone to the Lync gateway VCS 22 Video network: Set up a search rule to route calls to the Lync domain to the Lync gateway VCS 23 Video network: Set up search rules to route calls to the Lync gateway VCS for domains supported on Lync (but not in the video network) 24 Lync gateway VCS configuration (part 1) 25 Lync gateway : Generate and load private key, CA certificate, and server certificate onto Lync gateway VCS (if using TLS) 25 Lync gateway VCS: Configure DNS and local hostname 26 Lync gateway VCS: Ensure that cluster name is configured 27 Lync gateway VCS: Configure an NTP server 27 Lync gateway VCS: Switch on TLS in SIP configuration 27 Lync Server configuration 27 Trust a Lync gateway VCS 28 Configure Lync Server media encryption capabilities 30 Lync gateway VCS configuration (part 2) 30 Configure the B2BUA on the Lync gateway VCS 31 Set up a search rule to route calls to the Lync domain to Lync 32 Set up search rules to route calls to any other domains supported on Lync (but not in the video network) to Lync 33 Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 2 of 82

3 Testing the configuration 34 Enabling Lync clients registered on Lync Server to call endpoints registered on the video network 35 Lync gateway VCS configuration 35 Configuring the B2BUA trusted hosts on the Lync gateway VCS 35 Configuring the Lync gateway VCS with a neighbor zone that contains the video network 36 Setting up search rules to route calls with video network domains to the video network 38 Configuring Lync Server domain static routes 39 Configuring static routes to route calls to the Lync gateway VCS 39 Testing the configuration 40 Enabling Lync clients to see the presence of endpoints registered on VCS Control 41 VCS Control configuration 41 "Lync gateway" VCS configuration 42 Testing the configuration 42 Enabling Microsoft Edge Server and VCS TURN capabilities 43 Using FindMe for enhanced deployments 44 Deployment information 44 Prerequisites 46 Configuring the "Lync gateway" VCS for FindMe 46 Configure all the required SIP domains 46 Configure the B2BUA to register FindMe users to Lync 46 Enable FindMe and create FindMe user accounts for each user that is to share Lync client and VCS endpoints 47 Configuring Lync Active Directory for FindMe users 48 Testing the configuration 51 Enabling Lync clients to see the presence of endpoints registered on VCS Control 51 VCS Control configuration 51 Lync gateway VCS configuration 53 Lync client configuration 54 Log in to the Lync client 54 Appendix 1: Troubleshooting 55 Troubleshooting checklist 55 Problems connecting VCS Control local calls 55 Check for errors in the Event Log 56 Tracing calls 56 Presence not observed as expected 56 Video endpoint reports that it does not support the Lync client SDP 57 TLS neighbor zone to Lync Server is active and messaging is sent from VCS to Lync Server, but Lync debug says Lync fails to open a connection to VCS 57 Lync client initiated call fails to connect 57 Lync responds to INVITE with 488 Not acceptable here 57 Call connects but clears after about 30 seconds 58 Media problems in calls involving external Lync clients connecting via an Edge server 58 One way media: Lync client to VCS-registered endpoint 59 Lync rejects VCS zone OPTIONS checks with 401 Unauthorized and INFO messages with 400 Missing Correct Via Header' 60 Lync client stays in Connecting state 60 Call to PSTN or other devices requiring caller to be authorized fails with 404 not found 60 Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 3 of 82

4 Lync clients try to register with VCS Expressway 60 B2BUA problems 61 B2BUA users fail to register 61 B2BUA Lync Server status reports "Unknown" or "Unknown failure" 61 Lync problems 61 Problems with certificates 61 Appendix 2: Debugging on Lync 62 Use of Lync Server Logging Tool 62 Enabling debug on Lync client 63 Appendix 3: Interoperating capabilities and limitations 64 Known interoperating capabilities 64 SIP and H.323 endpoints making basic calls 64 Upspeeding from a voice call to a video call 64 Multiway generation of ad hoc conferences 64 Known interoperating limitations 64 Video codecs 64 MXP endpoints 64 Joining a Lync conference (AV MCU) 65 Upspeeding from a voice call to a video call 65 Microsoft Mediation Server 65 Cluster calls to endpoints not registered using FindMe 66 Lync client reports no audio device 66 Call forward from Lync to a VCS FindMe or endpoint results in a loop detected call 66 FindMe Caller ID set to FindMe ID causes calls from Lync client to fail 66 Appendix 4: Port reference 67 Appendix 5: Media paths and license usage for calls through B2BUA 69 Lync client call to SIP video endpoint 69 Lync client call to H.323 video endpoint 69 Lync client call to a SIP video endpoint via Cisco AM GW 70 Lync client call to H.323 video endpoint via Cisco AM GW 71 An external Lync client calls an external video endpoint 72 An external Lync client calls an internal SIP video endpoint 73 Appendix 6: Additional information 74 B2BUA registration on Lync gateway VCSs 74 What does Register FindMe users as clients on Lync do? 74 Configuring domains 75 B2BUA and Cisco AM GW integration 75 TEL URI handling for VCS to Lync calls 75 Appendix 7: Microsoft Certification Authority 76 Configuring Windows Server Manager with a "client and server" certificate template 76 Authorizing a request and generating a certificate using Microsoft Certification Authority 78 Document revision history 81 Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 4 of 82

5 Introduction Introduction Objectives and intended audience This deployment guide describes how to configure a Cisco TelePresence Video Communication Server (VCS) using the Back-2-Back-User-Agent (B2BUA) and Microsoft Lync 2010 / 2013 (Lync) to interwork. It also highlights the capabilities and limitations of interoperation of VCS Control and Lync. Deployment scenario A company is introducing a Lync environment into their network and is installing Microsoft Lync clients to provide messaging and presence capabilities for all staff. Integrating this with their existing video network, which handles their video conferencing, provides the ability for video endpoints to make calls to and receive calls from Lync clients, and for Lync clients to see the presence of the video endpoints. This deployment guide uses the example environment depicted below: Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 5 of 82

6 Introduction This guide describes two deployment solutions: 1. Basic configuration using static routes: this uses static routes to route calls from Lync to VCS and provides basic interoperability for voice, video and Presence. This configuration is described below. 2. FindMe-based configuration: uses FindMe to provide an enhanced experience and richer Presence. This configuration builds on the basic configuration and is described in Using FindMe for enhanced deployments [p.44]. The basic configuration environment consists of the following elements: Lync deployment with: a pool of Front End Processors with FQDN feppool.ciscotp.com a pool of Directors with FQDN dirpool.ciscotp.com an Edge server with FQDN lyncedge.ciscotp.com users david.jones@ciscotp.com and alice.parkes@ciscotp.com (among others) Cisco video deployment with: Lync gateway VCS Control (referred to as the "Lync gateway" VCS) with peer FQDN vcs01.ciscotp.com and cluster FQDN lyncvcs.ciscotp.com. The cluster FQDN must resolve to a list of DNS A-records including the IP addresses of all cluster peers (for round-robin operation). Core VCS Control (referred to as the VCS Control) with FQDN corevcs01.ciscotp.com VCS Expressway with FQDN vcse.ciscotp.com Internal and external video endpoints for video users david.jones and alice.parkes MCU registered to a video network VCS Control In this scenario, dialing is typically carried out by users clicking on one of their buddies in the Lync contact list or by selecting a destination from an electronic address book on the video endpoint. This guide describes how to connect Lync and a VCS Control via a Lync gateway VCS using a SIP trunk across an IP network and static routes from Lync to the Lync gateway VCS. The example presented uses the following setup: A VCS Control (or cluster of VCS Control peers) the Lync gateway VCS to act as the link between the existing video network and Lync. The Lync s SIP domain is ciscotp.com. The SIP domain for Lync need not be the same as the AD domain of Lync clients (the Lync login domain used in the login user name may be different from the SIP domain used in the sign-in address). The Cisco video network s domain is vc.ciscotp.com (used for video device registrations). Endpoints registered to the video network may be SIP or H.323 endpoints; they must register with an ID in the format alias@domain, where domain is a domain hosted on the video network (for example firstname.lastname.device_type@vc.ciscotp.com). We recommend that any H.323 to SIP and IPv4 to IPv6 protocol interworking is performed on the VCS Control. Lync clients registered to Lync are identified by URIs, for example: David with a URI david.jones@ciscotp.com Alice with a URI alice.parkes@ciscotp.com Endpoints registered to the video network are identified by URIs, frequently including the location or type of the endpoint, for example: Alice s internal video endpoint with an alias of alice.parkes.office@vc.ciscotp.com Alice s home office video endpoint with an alias of alice.parkes.external@vc.ciscotp.com Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 6 of 82

7 Introduction David s internal video endpoint with an alias of david.jones.office@vc.ciscotp.com David s home office video endpoint with an alias of david.jones.external@vc.ciscotp.com Lync Front End Server is configured with a static domain route which routes URIs with the VCS's video network domain (vc.ciscotp.com) to the VCS. Care must be taken when using domain static routes; any traffic for that domain that Lync cannot handle locally will be routed to VCS. MCUs that will receive calls from Lync can register conferences to the video network with a dedicated MCU domain (mcu.ciscotp.com) and make these available to Lync users via a static SIP domain route from the Lync environment (suitable for ad-hoc conference aliases). A separate domain for MCU registrations is recommended as it more easily allows you to prevent SIP traffic coming from Lync via a static route from propagating further into the video network than needed (by using search rules). The Presence Server residing on the VCS Control publishes presence information into the Lync environment via the B2BUA application on the Lync gateway VCS. This Presence Server must be authoritative for the video domain (vc.ciscotp.com) and any dedicated MCU domains (mcu.ciscotp.com) in use. Clustered Lync gateway VCS When this document refers to a Lync gateway VCS, a cluster of VCSs can also be used. The operation is functionally the same, but there is more capacity available. Calls from Lync Server will typically arrive at a single VCS in the cluster, as Lync Server will use the static domain routes, which has a single IP address for TCP connectivity and a single FQDN for TLS connectivity. If using TLS and round-robin DNS for static route destinations, Lync Server may change the VCS peer that it sends calls to, but only at a maximum rate of change of once per 5 seconds. Lync appears to keep sending all traffic to one VCS unless it loses connection to that VCS, and only then does it swap to another VCS so this provides resilience rather than load balancing. Why add a Lync gateway VCS? The Lync gateway VCS is an interface between an existing working video network and the Microsoft Lync environment. Using this gateway minimizes the changes that need to be made in the video network so as to introduce as few artifacts as possible when adding Lync interoperability to the video network. Having dedicated VCSs for this Lync gateway operation limits the number of VCSs for which the Microsoft Interoperability option key needs to be purchased and enabled. Lync Server can only send calls to a single FQDN (though this may have a round robin DNS address to support a cluster of VCSs for resilience) for calls via a static domain route defined in Lync Server. Lync Server will only accept messages received from peers that it has been configured to trust. Having a dedicated Lync gateway VCS or VCS cluster also limits the number of trusted devices that need to be configured in Lync, as every device that sends SIP messages to Lync Server needs to be explicitly listed as a trusted host in Lync Server. Multiple Lync gateway VCSs per Lync domain Apart from when the VCSs are in a single Lync gateway cluster, this is not a recommended architecture as calls from one video endpoint to another video endpoint that is called via its Lync domain will get routed via Lync rather than directly through the video infrastructure; this will cause users to lose video functionality such as duo video and far end camera control, and also possibly lose encryption and video quality. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 7 of 82

8 Introduction MCUs for ad hoc conferences from Lync The configuration of VCS and Cisco MCU described in Cisco TelePresence Multiway Deployment Guide is the correct configuration for VCS and Cisco MCU when working with Lync Server. The MCU should be configured to support SIP access to conferences to avoid the need to interwork the Lync client calls. MCUs must register to a VCS to allow Lync users to join conferences (MCUs cannot register to Lync Server; the Lync gateway VCS handles the protocol differences on behalf of the MCU). We recommend that MCUs that are used for conferences that Lync clients can dial, are registered using their own domain (different from any other video or Lync domain) to the video network VCSs. When configured in their own domain, the MCU conferences can be accessible via a static route configured on Lync for this MCU domain. If regional MCUs exist, the MCUs should have regional domains. For ad hoc conferences routed via the Lync static domain route: If the conference is not underway presence status will be Offline. If the conference has any participants, presence status will be Available. Calling an MCU conference from a Lync device requires the MCU s domain to be entered. Note that: If the PUA is configured so that registered devices do not report Available, presence will always show Off-line. VCS supports a maximum of 100 presence subscriptions per presentity. Small test/demo networks For small test and demo networks, video endpoints may be registered to the Lync gateway VCS, the small video network being controlled by the same VCS that is the interface to Lync Server. (In this case, you need to configure the SIP domains and enable the Presence Server on the Lync gateway VCS.) Scaling up from a small test/demo network As extra capacity, regional management and reduced license usage is required, you can scale away from the small test and demo network system to the Lync gateway VCS connected to video network approach. This is achieved by adding video network VCSs and neighboring them (directly, or indirectly through other VCSs) to the Lync gateway VCS. Endpoints can be added to the video network VCSs and endpoints and other devices then gradually migrated off the Lync gateway VCS onto the video network VCSs. Features and capabilities The interoperating capabilities of VCS and Microsoft Lync 2010 are broadly the same as between VCS and Lync 2013 except where specified in this document. X8.1 or later is compatible with both Lync 2010 and Lync 2013 clients registered to either Lync 2010 or Lync 2013 front end servers. The main differences in features and capabilities are summarized below. Microsoft Lync 2010 The Microsoft Interoperability option key must be installed to enable encrypted calls to and from Microsoft Lync 2010 Server (for both native SIP calls and calls interworked from H.323). It is also required by the B2BUA when establishing ICE calls to Lync 2010 clients. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 8 of 82

9 Introduction The B2BUA can use the Cisco AM GW to transcode between standard codecs (such as H.264) and Microsoft RT Video and RT Audio to allow high definition calls between Microsoft Lync 2010 clients and Cisco endpoints. Microsoft Lync 2013 The B2BUA provides interworking between standard H.264 AVC and Lync 2013's H.264UC SVC codec. You can still configure the B2BUA to use Cisco AM GW transcoders with Lync 2013, but it is not necessary and we recommend that they are not deployed with Lync Lync 2013 no longer supports H.263, so X8.1 or later software is required to interoperate successfully with Lync X7.2 or earlier software will work with Lync 2013 only if calls are routed through a Cisco AM GW transcoder. The Microsoft Interoperability option key is required for all types of communication with Lync Microsoft Lync B2BUA interoperating capabilities When using the Microsoft Lync B2BUA: Domain static routes are set up on Lync Server to route calls to domains in the video network. Search rules are set up on VCS to route calls to Lync domains. Lync Server accepts and handles call hold (and resume) requests. Lync clients can be the object of a transfer (even if there is an AM gateway involved in the call). Lync clients can be joined into a Multiway conference (even if there is an AM gateway involved in the call). Presence updates are only supported from VCS to Lync Server: Use of Available for registered endpoints is optional via PUA configuration Off-line and Available (not In-call, which requires FindMe-based configuration) are reported for users (for up to 100 subscribers) Passing Lync presence to devices registered to VCS is not supported. Calls to Microsoft Mediation Servers work from endpoints in the VCS video network for SIP initiated calls, but do not work for calls interworked from H.323 (unless the workaround specified in Appendix 3: Interoperating capabilities and limitations [p.64] is implemented). Lync systems may use hardware load balancers for resilience and capacity. A Lync gateway VCS (or VCS cluster) can communicate to Lync via Lync Director. Media encryption (SRTP) is supported when TLS is used between VCS and Lync and the Microsoft Interoperability option key is added to the Lync gateway VCS. SIP signaling and RTP media is always routed via the B2BUA application for calls involving Lync clients. Each B2BUA application (one application per VCS) can handle 100 simultaneous calls between Lync and the VCS video environment. However, a call involving Cisco AM GW will consume two B2BUA call resources. Summary of configuration objectives This document describes how to configure Lync and the VCS in B2BUA mode to enable calls from: SIP and H.323 video endpoints registered in the video network to other SIP and H.323 video endpoints registered in that same video network. Microsoft Lync clients registered on Lync Server to other Lync clients registered on that Lync Server. SIP and H.323 video endpoints registered in the video network to Lync clients registered on Lync. Lync clients registered on Lync Server to SIP and H.323 video endpoints registered in the video network. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 9 of 82

10 Introduction It also describes how to enable presence so that Lync 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. Lync environments Lync environments have a number of building blocks, and so they may be constructed in many ways. A full scale Lync deployment is likely to use Lync Director, Hardware Load Balancers (HLBs), Front End Processors (FEPs) in enterprise pools, and a redundant AD server. For Lync installations, Microsoft recommend that DNS may be used in place of hardware load balancing for routing SIP traffic. Microsoft guidance can be found at An example architecture is shown below: Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 10 of 82

11 Introduction A smaller deployment may not use Lync Director servers, but may just use a Hardware Load Balancer in front of a set of Front End Processors. A Lync environment may use DNS instead of the Hardware Load Balancer, for example: Note that Lync requires that the AD server and FEP are on separate machines. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 11 of 82

12 Introduction Lync deployments may also contain Edge servers to allow Lync clients to register from outside the local network through the Edge server to Lync. Communicating with Lync devices outside the edge server requires both the Edge Server and the VCS Expressway connecting to the public Internet. (Calls involving a Microsoft Edge server require the VCS to have the Microsoft Interoperability option key installed, as this key allows for ICE to be used for media connectivity, which is required in the following scenario.) In any deployment with VCS and Lync: In Lync, traffic sent via a static SIP route is either sent directly from a FEP to the VCS, or from a FEP via a Director and to the VCS. If the Lync environment is fronted by a Hardware Load Balancer in front of Lync 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: Lync Directors should trust the Lync gateway VCS(s). Lync Directors should route the video network domains (vc.ciscotp.com and mcu.ciscotp.com) to the Lync gateway VCS cluster FQDN. Depending on Lync configuration, FEPs may route SIP traffic directly to the VCS, or they may route the traffic through a Director pool. If the Lync environment is fronted by a single Lync Director then calls to and from the video network will go via that Director; they will not be routed directly to or from the FEPs: Lync Directors should trust the Lync gateway VCS(s). Lync Directors should route the video network domains (vc.ciscotp.com and mcu.ciscotp.com) to the Lync gateway VCS cluster FQDN. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 12 of 82

13 Introduction Depending on Lync configuration, FEPs may route SIP traffic directly to the VCS, or they may route the traffic through a Director pool. If the Lync environment has no Lync Director but a Hardware Load Balancer in front of Front End Processor pool(s) then configure the pool(s) (not each FEP): The FEP pools should trust the Lync gateway VCS(s). All FEP pools should route the video network domains (vc.ciscotp.com and mcu.ciscotp.com) to the Lync gateway VCS cluster FQDN. Configuring the pool ensures that the same configuration is applied to every FEP in the pool. If Lync is a single FEP then that FEP should be configured: The single FEP should trust the Lync gateway VCS(s). The single FEP should route the video network domains (vc.ciscotp.com and mcu.ciscotp.com) to the Lync gateway VCS cluster FQDN. We recommend that you use a VCS cluster FQDN (e.g. lyncvcs.ciscotp.com) rather than an individual VCS peer (even if it is a "cluster" of one). If you configure a Trusted Application Pool (Cluster FQDN), you can always add peer FQDNs (VCS peers) to the Application pool later without requiring to remove the existing search rules, static routes or Trusted Applications in the Lync Server. Lync gateway VCS should be configured such that: If the Lync environment is fronted by a Hardware Load Balancer in front of Lync Directors then the B2BUA should be configured to route calls for Lync to the Hardware Load Balancer, and receive calls from either of the Lync Directors: The Lync gateway B2BUA needs to specify the Hardware Load Balancer as the Lync signaling destination address. The Lync gateway B2BUA needs to include the addresses of both Lync Directors as trusted hosts (and any FEPs which might send traffic directly to the B2BUA). Search rules that route calls to Lync will target the B2BUA neighbor zone. If the Lync environment is fronted by a Lync Director or a pool of directors, then the B2BUA should be configured to route calls for Lync to the Lync Director, and receive calls from the Lync Director: The Lync gateway B2BUA needs to specify the Lync Director (pool) as the Lync signaling destination address. The Lync gateway B2BUA needs to include the address of each individual Lync Director as a trusted host (and any FEPs which might send traffic directly to the B2BUA). Search rules that route calls to Lync will target the B2BUA neighbor zone. If the Lync environment has no Lync Director but a Hardware Load Balancer in front of Front End Processors then the B2BUA should be configured to route calls for Lync to the Hardware Load Balancer, and receive calls from any of the FEPs: The Lync gateway B2BUA needs to specify the Hardware Load Balancer as the Lync signaling destination address. The Lync gateway B2BUA needs to include the addresses all of the Lync FEPs as trusted hosts. Search rules that route calls to Lync will target the B2BUA neighbor zone. If Lync is a single FEP then the B2BUA should be configured to route calls for Lync to the single FEP directly, and receive calls from that FEP: The Lync gateway B2BUA needs to specify the FEP as the Lync signaling destination address. The Lync gateway B2BUA needs to include the address of the FEP as a trusted host. Search rules that route calls to Lync will target the B2BUA neighbor zone. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 13 of 82

14 Introduction Prerequisites prior to configuring VCS and Lync to interoperate Before configuring the video network and the Lync environment to interwork, make sure that: The Lync gateway VCS (cluster peers) are running X8.1 code (or later) The Lync gateway VCS (cluster peers) have at least an option key for non-traversal calls applied. The version of Lync is Lync 2010 or Lync Lync is configured and operational and access is available to Active Directory for managing users. The FQDN of all Lync servers is resolvable via the DNS server that the Lync gateway VCS is configured to use (this should be the DNS server used by Lync). The FQDNs of each of the Lync gateway VCSs and if clustered, the FQDN of the Lync gateway cluster must be resolvable via DNS (with round-robin A-records). Validation of the Front End Servers on all Lync Directors and Lync FEPs must show no errors. Use the Topology Validation Tool which can be found in the Lync Resource Toolkit. If TLS is to be used (recommended) ensure that the DNS server supports reverse DNS lookup (often supported using PTR records). Benefits of using the B2BUA over legacy OCS Relay The Lync B2BUA is the preferred method of integrating Lync with VCS. It was introduced in VCS X7. It provides an interface between Lync and the video network and replaces the legacy OCS Relay application (removed from VCS in X8.1). The B2BUA is a new application that expands upon the feature set of OCS Relay by providing: improved stability, speed and performance greatly enhanced logging/diagnostics capabilities (using the "Diagnostics logging" functionality of the VCS) improved ease of use (B2BUA does not require complex CPL to be installed on the VCS, which was required with OCS Relay) improved configuration and control (B2BUA has a variety of available configuration settings whereas OCS Relay was limited in terms of configuration options) support for Lync clients registered via an Edge server (requires a VCS Expressway and the Microsoft Interoperability option key) TURN/ICE support embedded into the B2BUA (requires VCS Expressway and the Microsoft Interoperability option key) Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 14 of 82

15 Video network: check that calls between endpoints registered to VCS Controls operate as expected Video network: check that calls between endpoints registered to VCS Controls operate as expected The configuration described in this section should already be in place and operational. VCS Control configuration summary The configuration of the VCS Control 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 SIP domain of the video network, which is needed for SIP registration and presence handling, is configured. If appropriate, you may also want to configure interworking to handle calls with any H.323 endpoints that are registered to other systems in the video network. Note that in small test and demo networks this configuration is carried out on the same VCS that is the Lync gateway VCS. Ensure SIP domain of video network endpoints is configured in the VCS Control SIP endpoints register with the VCS Control with a URI in the format user-id@sip-domain. The VCS Controls accepting these registrations must be configured with the SIP domain information so that it will accept these registrations. 1. Go to Configuration > Domains. 2. Check that the domain is listed; if it is not listed: a. Click New. b. Set Name to, for example, vc.ciscotp.com. c. Click Create domain. 3. Repeat for any other domains being used, such as mcu.ciscotp.com. Optional. Configuring interworking for H.323 endpoints registered to other systems By default the VCS Control will perform H.323 to SIP protocol interworking between H.323 endpoints registered to the VCS Control and any SIP devices also registered to the VCS Control or to Lync devices. If you have any H.323 endpoints that are registered to other systems in the video network, you will need change the interworking configuration from the default of Registered only to On: 1. Go to Configuration > Protocols > Interworking. 2. Set H.323 <-> SIP interworking mode to On. 3. Click Save. Lync configuration No configuration is required on Lync to allow endpoints registered on the VCS Control to call other endpoints registered on the VCS Control. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 15 of 82

16 Video network: check that calls between endpoints registered to VCS Controls operate as expected Registering video endpoints to the video network Video endpoint configuration For H.323, configure the endpoints as follows: H.323 ID (for example, H.323 Call Setup Mode = Gatekeeper Gatekeeper IP address = IP address or FQDN of VCS Control (cluster) For SIP, configure the endpoints as follows: SIP Address (URI) (for example, alice.parkes.office@vc.ciscotp.com) Server Address (Proxy address) = IP address or FQDN of VCS Control (cluster) Confirming registrations Registration status can be confirmed on the Registrations page (Status > Registrations). By default the VCS Control accepts all registrations to SIP domains configured in the VCS Control. You can limit registrations by explicitly allowing or denying individual registrations (see VCS Administrator Guide for further details). Calls can now be made between endpoints registered on VCS Control. Testing the configuration To test the configuration: 1. Make some test calls between the endpoints. 2. Clear the calls. 3. Check the Call history page on the VCS Control (Status > Calls > History). Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 16 of 82

17 Check that calls between Lync clients registered on Lync Server operate as expected Check that calls between Lync clients registered on Lync Server operate as expected The configuration described in this section should already be in place and operational. VCS Control configuration No configuration is required on VCS Control for endpoints registered on Lync to call other endpoints registered on Lync Server. Enabling users for Lync By default, Active Directory users are not Lync enabled. Check that users required to support Lync are enabled to do so, and if not enable them. This can be done both by Lync Server Control Panel or through Windows PowerShell commands (using Lync 2010 as an example): 1. Bring up the Lync Server Control Panel (either from the start menu select Lync Server Control Panel, or if there is a desktop icon double click it). 2. On Lync Server Control Panel go to the Users menu: you can see users already enabled for communication server. To add a new user: 1. Select Enable users and click Add. 2. Search for and select the user (in this example, David Jones) Note: to find the user it must already have been defined in Active Directory. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 17 of 82

18 Check that calls between Lync clients registered on Lync Server operate as expected 3. Select the communication server pool to assign to the user. 4. Select your preferred method to Generate user s SIP URI. 5. Select the user s Telephony type. This can be done in single command by CSPS using the command enable-csuser For example: enable-csuser -identity "ciscotp\david.jones" -registrarpool "feppool.ciscotp.com" -sipaddress sip:david.jones@ciscotp.com Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 18 of 82

19 Check that calls between Lync clients registered on Lync Server operate as expected Registering Lync clients to the Lync Server Lync client configuration 1. Install and start the Lync client. 2. On the Sign in screen, click on the icon or select the menu arrow beside it and select Tools > Options. 3. Select Personal. 4. Set up Sign-in address as required. This is the SIP URI of the Lync user, for example 5. Click Advanced. 6. In a production environment ensure Automatic configuration is selected. If this does not work, select Manual configuration and set Internal server name or IP address to the FQDN of the Lync Server. 7. Click OK to return to the Lync - Options panel. 8. Click OK to return to the Lync client. 9. Click Sign In. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 19 of 82

20 Check that calls between Lync clients registered on Lync Server operate as expected 10. Enter the User name and Password. This is the Active Directory name and password of the user. The user name may or may not be the same as the sign in address. Depending on how the network is configured, the User name may need to be in the form <domain>\<user> rather than for example ciscotp\david.jones instead of 11. Click Sign In. Testing the configuration To make a video call between Lync endpoints: 1. Double-click on the buddy you want to call. 2. Click Start a Video Call. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 20 of 82

21 Check that calls between Lync clients registered on Lync Server operate as expected 3. Answer the call on the receiving Lync client. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 21 of 82

22 Enabling endpoints registered on the video network to call clients registered on Lync Enabling endpoints registered on the video network to call clients registered on Lync This is configured in 4 stages: 1. Video network VCS Control configuration 2. Lync gateway VCS configuration (part 1) 3. Lync Server configuration 4. Lync gateway VCS configuration (part 2) Video network: VCS Control configuration The video network must have a link to the Lync gateway ; to configure this: 1. Set up a neighbor zone to the Lync gateway VCS (cluster). 2. Set up a search rule to route calls to the Lync domain to the Lync gateway VCS (cluster). 3. Set up search rules to route calls to any other domains supported on Lync (but not in the video network) to the Lync gateway VCS cluster there may be none of these. Note that in small test and demo networks this configuration is not necessary - the video network VCS is the Lync gateway VCS. In this case, skip the following sections and go to Lync gateway VCS configuration (part 1) [p.25]. Video network: Set up a neighbor zone to the Lync gateway VCS 1. Go to Configuration > Zones > Zones. 2. Click New. 3. Configure the following fields (leave all other fields with default values): Name Type SIP mode SIP port SIP transport An appropriate name, for example To Lync gateway Neighbor On 5061 (or the value that is the same as that configured on the Lync gateway VCS for TLS mode SIP) TLS H.323 mode Off In the Location section: Peer 1 address In the Location section: Peer 2 to Peer 6 address In the Advanced section: Zone profile IP address or FQDN of the Lync gateway VCS (or the 1st VCS in the Lync gateway VCS cluster) IP address or FQDN of the 2nd to 6th Lync gateway cluster peers (if any) Default 4. Click Create zone. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 22 of 82

23 Enabling endpoints registered on the video network to call clients registered on Lync Video network: Set up a search rule to route calls to the Lync domain to the Lync gateway VCS 1. Go to Configuration > Dial plan > Search rules. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 23 of 82

24 Enabling endpoints registered on the video network to call clients registered on Lync 2. Click New. 3. Configure the following fields (leave all other fields with default values): Rule name An appropriate name, for example Route to Lync gateway Priority Leave as default, for example 100 Source Mode Pattern type Pattern string Pattern behavior On successful match Target Any Alias pattern match Leave Continue Select the Lync gateway zone, for example To Lync gateway 4. Click Create search rule. Video network: Set up search rules to route calls to the Lync gateway VCS for domains supported on Lync (but not in the video network) There may be no additional domains supported by Lync, but if there are: 1. Go to Configuration > Dial plan > Search rules. 2. Click New. 3. Configure the following fields (leave all other fields with default values): Rule name An appropriate name, for example Route domain xxx to Lync gateway Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 24 of 82

25 Enabling endpoints registered on the video network to call clients registered on Lync Priority Leave as default, for example 100 Source Mode Pattern type Pattern string Pattern behavior On successful match Target Any Alias pattern match domain>.* Leave Stop Select the Lync gateway zone, for example To Lync gateway 4. Click Create search rule. 5. Repeat the process if additional search rules are needed, for example a search rule for the dedicated MCU domain mcu.ciscotp.com. Lync gateway VCS configuration (part 1) This comprises the following steps: 1. Generate and load private key, root certificate and server certificate onto VCS. 2. Configure DNS. 3. Ensure that a cluster name is configured. 4. Configure an NTP server. 5. Switch on TLS in SIP configuration. We recommend that you use TLS connectivity between VCS and Lync. (TCP may not work for Lync configurations that include HLBs and / or Lync Director and use of TCP prevents use of encryption). If the Lync gateway is a cluster, unless this guide states that configuration is required on each peer, configure the master Lync gateway VCS in the cluster and allow the configuration to be replicated to the other peers automatically. If the Lync gateway is just a single VCS then set up the configuration on that Lync gateway VCS. Lync gateway : Generate and load private key, CA certificate, and server certificate onto Lync gateway VCS (if using TLS) Obtain and load the CA certificate, server certificate and private key onto the VCS. Note that for mutual TLS authentication the server certificate must be capable of being used as a client certificate as well. A certificate must be created for each Lync gateway VCS; the certificate must specify: Subject Name: the VCS peer s FQDN e.g. vcs01.ciscotp.com and if it is part of a cluster: Subject Alternate Name: a comma separated list of the VCS cluster s FQDN and the VCS peer s routable FQDN, e.g. lyncvcs.ciscotp.com, vcs01.ciscotp.com The VCS s trusted CA certificate is loaded via Maintenance > Security certificates > Trusted CA certificate. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 25 of 82

26 Enabling endpoints registered on the video network to call clients registered on Lync The VCS s server certificate is loaded via Maintenance > Security certificates > Server certificate. See VCS Certificate Creation and Use Deployment Guide for more details about creating certificates for VCS. Also, information specific to Microsoft Certification Authorities is contained in Appendix 7: Microsoft Certification Authority [p.76] in this document. Lync gateway VCS: Configure DNS and local hostname Configure the DNS server details The Lync gateway VCS(s) should be configured to use the same DNS server(s) as Lync Server. On a machine running Lync Server: 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 server(s). Note: a DNS server IP address of means that Lync Server is using a DNS server on its own hardware. Instead of entering on the VCS, use the IP address of the Lync Server platform instead. On each Lync gateway VCS peer: 1. Go to System > DNS. 2. If the DNS server that Lync Server uses can provide all DNS lookups needed by VCS: a. Set Default DNS Server Address 1 to the IP address of DNS server noted earlier. b. If Lync Server has more than one DNS server defined, configure the additional default DNS server fields (Address 2, Address 3 and so on) with the IP addresses of the additional servers. 3. If the VCS must use other DNS servers for normal calls and only the Lync DNS server for Lync access: Configure the Default DNS servers with the servers which will be used for normal, non-lync related DNS operation and configure the Per-domain DNS servers section as follows: Address 1 Domain names Address 2 5 Domain names 2 5 IP address of the DNS server used by Lync Server Domain shared with Lync Use these fields only if Lync Server uses more than one DNS server Use these fields only if Lync Server uses more than one DNS server; configure with the domain shared with Lync 4. Configure the next available Per-domain DNS server address to contain the IP address of the Lync Front End Processor, and specify the Lync domain e.g. ciscotp.com as the associated Domain name. (This is required in some network setups: Lync frequently embeds hostnames inside contact headers and sometimes these can be unresolvable outside of the Windows domain.) 5. Click Save. Ensure that Local hostname and DNS domain are configured For each Lync gateway VCS peer, ensure that a unique Local host name is set up and that the DNS Domain name is set up: Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 26 of 82

27 Enabling endpoints registered on the video network to call clients registered on Lync 1. Go to System > DNS and set: a. Local host name to a unique hostname for this VCS. b. Domain name to the domain name for this VCS. 2. Click Save. Note that: the Local host name concatenated with DNS Domain name is the routable FQDN of this VCS. if these items are not configured and the connection between Lync Server and VCS is TLS, then although the neighbor zone goes active and VCS can send messaging to Lync Server, Lync Server will never open a TLS connection back to VCS, resulting in no calls from Lync to VCS and other strange behavior. Lync gateway VCS: Ensure that cluster name is configured Lync will be configured with a static route that uses the "Lync gateway" VCS's cluster name / FQDN (e.g. lyncvcs.ciscotp.com) regardless of whether the "Lync gateway" VCS is part of a cluster or not. For each Lync gateway VCS peer, ensure that Cluster name (System > Clustering) is the same, and is set up to be the FQDN of the cluster. Note that this should have been set up when the cluster was created see VCS Cluster Creation and Maintenance Deployment Guide. If the cluster name needs changing follow the procedure in that document. Lync gateway VCS: Configure an NTP server On each Lync gateway VCS peer: 1. Go to System > Time. 2. Set NTP server 1 to the IP address of an NTP server. 3. Optionally set NTP server 2 to the IP address of an additional NTP server. 4. Set Time zone as appropriate to the location of the VCS. You can find out which time server that the Windows server (the Lync Server) is using by typing net time /querysntp from the windows command line. Lync gateway VCS: Switch on TLS in SIP configuration 1. Go to Configuration > Protocols > SIP. 2. Ensure that TLS mode is On. Lync Server configuration The configuration will vary depending upon the architecture of the Lync Server installation. If a Lync Director is in use, then configure the Lync Director (pool) to trust the Lync gateway VCS and to route traffic to VCS. Other FEPs receiving calls for the video domain may not know how to route them (depending on Lync SIP routing configuration), and may pass the calls to the Director pool for routing. If there is just a hardware load balancer in front of a set of FEP pools, configure each FEP pool. If there is just a single FEP, configure it. To allow the Lync gateway VCS to communicate with Lync Server: Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 27 of 82

28 Enabling endpoints registered on the video network to call clients registered on Lync 1. For a TLS (encrypted signaling) connection between the Lync gateway VCS and Lync Server (recommended), TLS must be allowed on Lync Server. For a TCP connection (not recommended), TCP must be allowed on Lync Server. 2. Configure Lync Server to trust the Lync gateway VCS(s). 3. Configure Lync Server media encryption capabilities. Trust a Lync gateway VCS Lync trust can either be set up for a single Lync gateway VCS or multiple VCSs (for example when using a cluster for Lync gateway VCS. On Lync Server (using Lync 2010 as an example): 1. Select Start > All Programs > Microsoft Lync Server 2010 > Lync Server Management Shell. 2. Set one or more "Lync gateway" VCSs as a trusted application for Lync Server (VCS is treated as an application by Lync Server). Use the command New-CsTrustedApplicationPool with the following parameters: -Identity: specifies the "Lync gateway" VCS cluster FQDN. This name must match the Common Name / Subject Alternate Name specified in the VCS server certificate e.g. lyncvcs.ciscotp.com. -ComputerFqdn: specifies the "Lync gateway" VCS peer FQDN (specify the master VCS FQDN if running a cluster), e.g. vcs01.ciscotp.com. This name must match the Common Name specified in the VCS server certificate. -Registrar: specifies the FQDN of the registrar for the Lync pool -Site: specifies the siteid on which this application pool is homed Note: you can use the command Get-CsSite to get the full list of sites (SiteID) and related pools. -RequiresReplication: specifies that this trusted application must not be replicated between Pools (must be $false) -ThrottleAsServer: reduces the message throttling as it knows the trusted device is a server, not a client (must be $true) -TreatAsAuthenticated: specifies that this application is authenticated by default (must be $true) For example: C:\Users\administrator.CISCOTP>New-CsTrustedApplicationPool -Identity lyncvcs.ciscotp. com -ComputerFqdn vcs01.ciscotp.com -Registrar feppool.ciscotp.com -site 1 -RequiresRe plication $false -ThrottleAsServer $true -TreatAsAuthenticated $true 3. (For TCP only deployments) Use the Topology Builder to configure the IP address of the "Lync gateway" VCS as a trusted server: a. Select Start > All Programs > Microsoft Lync Server 2010 > Topology Builder. b. Under Lync Server 2010 >Trusted Application Servers, right-click on the VCS host and select Edit Properties. c. In the General tab, select Limit service usage to selected IP addresses, enter the Primary IP address of the VCS and click OK. d. Publish the topology (you may need to restart the Lync Front-End Service to make sure that topology changes are applied). 4. If using a cluster of Lync gateway VCSs, use the shell to add the additional cluster peer members as computers to the trusted application pool using the command New- CsTrustedApplicationComputer with the following parameters: -Identity: specifies the FQDN of the VCS cluster peer being added, e.g. vcs02.ciscotp.com. This name must match the Common Name specified in the VCS server certificate. -Pool: specifies the FQDN of the application pool this VCS is being added to (identical to the FQDN used for -Identity in the previous step, e.g. lyncvcs.ciscotp.com. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 28 of 82

29 Enabling endpoints registered on the video network to call clients registered on Lync For example: C:\Users\Administrator.CISCOTP> New-CsTrustedApplicationComputer -Identity vcs02.cisco tp.com -Pool lyncvcs.ciscotp.com 5. Assign an application to a specific application pool: Use the command New-CsTrustedApplication with the following parameters: -ApplicationID: specifies a label for the "Lync gateway" VCS application (it is internal to Lync only, not a DNS name) -TrustedApplicationPoolFQDN: specifies the "Lync gateway" VCS FQDN (or "Lync gateway" VCS Cluster name if present) -Port: specifies TLS/TCP port to use for neighboring. This should be set to the port configured as Port on B2BUA for Lync call communications in the B2BUA advanced settings on the VCS (default 65072). -enabletcp: this must be included only if TCP is the chosen transport protocol For example, for TLS: C:\Users\administrator.CISCOTP>New-CsTrustedApplication -ApplicationId VCSApplication1 -TrustedApplicationPoolFqdn lyncvcs.ciscotp.com -Port For example, for TCP: C:\Users\administrator.CISCOTP>New-CsTrustedApplication -ApplicationId VCSApplication1 -TrustedApplicationPoolFqdn lyncvcs.ciscotp.com -Port EnableTCP 6. Apply the configuration Use the command Enable-CsTopology. For example: C:\Users\administrator.CISCOTP>Enable-CsTopology To verify that all VCS systems integrated with Lync Servers are assigned to the correct trusted Application Pool on the LSCP (Lync Server Control Panel): Topology > Status: To verify trusted application and its assignment to the correct Application Pool on the LSCP (Lync Server Control Panel): Topology > Trusted Application menu: Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 29 of 82

30 Enabling endpoints registered on the video network to call clients registered on Lync Configure Lync Server media encryption capabilities By default Lync Server mandates the use of encrypted media. However, the headers used in Lync SRTP are different from those used by video network devices. VCS has the capability to carry out on-the-fly modification of these headers if the Microsoft Interoperability option key is enabled on the Lync gateway VCS. The choice of how to configure Lync s encryption capabilities depends on: Is the connection between Lync and the Lync gateway VCS over TLS? If it is not TLS, then crypto keys will not pass (they can be sent only over a secure encrypted signaling link), encryption must not be set to require on Lync Server. Does the Lync gateway VCS have the Microsoft Interoperability option key enabled? If no, encryption must not be set to require on Lync Server. Do all video endpoints support encrypted media, and will they offer encrypted media when initiating calls? If no, then configure the relevant VCS so that the Media encryption policy for that endpoint's zone/subzone is set to Force encrypted. To configure the way Lync will handle encryption, use the command: set-csmediaconfiguration -EncryptionLevel <value> where <value> is one of RequireEncryption, SupportEncryption, DoNotSupportEncryption. For example: C:\Users\administrator.CISCOTP> set-csmediaconfiguration -EncryptionLevel supportencryption Note that: This parameter is a value communicated to Lync clients to affect its operation. To activate this change on a Lync client, sign out, then sign back into the Lync client. 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 Lync clients for them take on the new value. If the Microsoft Interoperability option key is installed and the connection between the VCS and Lync Server is TLS, then the default setting of the command set-csmediaconfiguration EncryptionLevel RequireEncryption may be used. However, be aware that if RequireEncryption is set on Lync, either all video endpoints must support encryption or the VCS's Media encryption policy for the relevant zones and subzones must be set to Force encrypted. Otherwise, calls will fail consider using SupportEncryption instead. Lync gateway VCS configuration (part 2) This comprises the following steps: 1. Configure the B2BUA on the Lync gateway VCS. 2. Set up a search rule to route calls to the Lync domain to Lync. 3. If required, set up search rules to route calls to any other domains supported on Lync (but not in the video network) to Lync. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 30 of 82

31 Enabling endpoints registered on the video network to call clients registered on Lync Configure the B2BUA on the Lync gateway VCS When configuring the B2BUA, two of the fields to configure are the destination address and destination port for the B2BUA to send signaling to in the Lync environment. The values that need to be entered depend on the structure of the Lync environment: If the Lync environment is fronted by a Hardware Load Balancer in front of Lync Directors is fronted by a Lync Director or Director pool has no Lync Director but a Hardware Load Balancer in front of Front End Processors is a single FEP Configure the signaling destination address and port to be that of the Hardware Load Balancer Lync Director (pool) Hardware Load Balancer FEP 1. Go to Applications > B2BUA > Microsoft Lync > Configuration. 2. Configure the fields as follows: Microsoft Lync B2BUA Lync signaling destination address Enabled IP address or FQDN of device specified above, for example dirpool.ciscotp.com Lync signaling destination port IP port used by device specified above typically 5061 Lync signaling transport Register FindMe users as clients on Lync Enable transcoders for this B2BUA Offer TURN Services Advanced settings TLS No If no Cisco AM GW is to be used, set to No. If an Cisco AM GW is to be used, see Microsoft Lync 2010, VCS and Cisco AM GW Deployment Guide No Leave all advanced settings at their default values 3. Click Save. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 31 of 82

32 Enabling endpoints registered on the video network to call clients registered on Lync "To Microsoft Lync Server via B2BUA" neighbor zone When the B2BUA is enabled, a non-configurable neighbor zone called To Microsoft Lync Server via B2BUA is automatically set up: Set up a search rule to route calls to the Lync domain to Lync Search rules are used to specify the URIs to be forwarded to Lync (for example, by matching the domain of the destination or by matching some element in the URI). Search rules can also be used to transform URIs before they are sent to a neighbor, for example to add or modify the domain or add, remove or translate user-id prefixes and even to add extra tags to SIP URIs, such as user=phone (see TEL URI handling for VCS to Lync calls [p.75] for further information about user=phone). For this scenario, anything with a domain ciscotp.com will be matched (and passed to Lync via the B2BUA); no transformation is required. 1. Go to Configuration > Dial plan > Search rules. 2. Click New. 3. Configure the search rule so that all calls to URIs in the format.+@ciscotp.com.* are forwarded to Lync. (To handle presence messaging a.* is included at the end of the domain to allow any parameters Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 32 of 82

33 Enabling endpoints registered on the video network to call clients registered on Lync following the domain to be retained in the SIP messaging.) Rule name To Lync Priority 100 Source Mode Pattern type Pattern string Pattern behavior On successful match Target zone Any Alias pattern match Leave Stop To Microsoft Lync Server via B2BUA 4. Click Save. Note: never use a Mode of Any alias. Always use a pattern string which matches the Lync domain as closely as possible so that only calls, notifies and other messages that are handled by Lync get sent to it. If Any alias were to be selected, then all calls and other messages would be routed to Lync subject to no higher priority search rules matching whether or not Lync supports that call or message and it may introduce delays, or worse cause calls, presence etc to fail. Set up search rules to route calls to any other domains supported on Lync (but not in the video network) to Lync If Lync supports only a single domain then no other search rule is required here. If Lync supports other domains and video endpoints should be able to call these devices, one or more additional search rules can be added. 1. Go to Configuration > Dial plan > Search rules. 2. Click New. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 33 of 82

34 Enabling endpoints registered on the video network to call clients registered on Lync 3. Configure the search rule so that all calls to the relevant URI are routed to Lync. Rule name xxxx To Lync Priority 100 Source Mode Pattern type Pattern string Pattern behavior On successful match Target zone Any Alias pattern match (never use a Mode of Any alias) Regex.+@<relevant domain>.* Leave Stop To Microsoft Lync Server via B2BUA 4. Click Save. 5. Repeat for all domains supported on Lync (that are not used in the video network). Calls can now be made between SIP / H.323 endpoints registered on the video network to Lync clients registered on Lync Server. Testing the configuration Test calls from endpoints registered on the video network to Lync clients registered on Lync Server. For example, call david.jones@ciscotp.com or alice.parkes@ciscotp.com from both SIP and H.323 endpoints registered on VCS Control. Note that if Lync for Mac OS X is used and a Cisco AM GW is not installed, the call will result in an audio only call as Lync for Mac does not support any video codecs supported by standards-based endpoints. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 34 of 82

35 Enabling Lync clients registered on Lync Server to call endpoints registered on the video network Enabling Lync clients registered on Lync Server to call endpoints registered on the video network This is configured in 2 stages: 1. Lync gateway VCS configuration (B2BUA trusted hosts, neighbor zone and search rules to the video network). 2. Lync Server configuration (domain static routes to the Lync gateway VCS). Lync gateway VCS configuration This comprises the following steps: 1. Configure the B2BUA trusted hosts on the Lync gateway VCS. 2. Configure the Lync gateway VCS with a neighbor zone that contains the video network. 3. Set up one or more search rules to route calls with video network domains to the video network (include a rule for the MCU domain if used). Configuring the B2BUA trusted hosts on the Lync gateway VCS The Lync devices that must be trusted by the VCS depend on the structure of the Lync environment: If static routes are to be created from the Lync environment the Lync environment is fronted by a Hardware Load Balancer in front of Lync Directors the Lync environment is fronted by a Lync Director the Lync environment has no Lync Director but a Hardware Load Balancer in front of Front End Processors Lync is a single FEP Trust the Lync FEPs which will be sending traffic towards the Lync gateway VCSs Hardware Load Balancer and the Lync Directors Lync Director Hardware Load Balancer and the Lync FEPs Lync FEP 1. Go to Applications > B2BUA > Microsoft Lync > B2BUA trusted hosts. 2. Click New. 3. Configure the fields as follows: Name IP address Type Name to identify Lync device IP address of the device Lync device 4. Click Save. 5. Repeat these steps until all Lync devices that need to be trusted have been added. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 35 of 82

36 Enabling Lync clients registered on Lync Server to call endpoints registered on the video network Note that trusted host verification only applies to calls initiated by Lync that are inbound to the VCS video network. It is not necessary to configure trusted hosts if calls are only ever to be initiated from the VCS video network. Configuring the Lync gateway VCS with a neighbor zone that contains the video network Note that in small test and demo networks, this step is not necessary as the video network VCS is the Lync gateway VCS. 1. Go to Configuration > Zones > Zones. 2. Click New. We recommend that the connection to the Lync gateway VCS uses SIP over TLS to communicate so that encrypted calls can be handled. 3. Configure the following fields: Name Type SIP mode SIP port SIP transport To Video network Neighbor On 5061 (or the value that is the same as that configured on the video network VCS for TLS mode SIP) TLS H.323 mode Off Location: Peer 1 address Location: Peer 2 to Peer 6 address Advanced: Zone profile IP address or FQDN of the video network VCS (or the 1st VCS in the video network cluster) IP address or FQDN of the 2nd to 6th video network cluster peers (if any) Default 4. Click Save. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 36 of 82

37 Enabling Lync clients registered on Lync Server to call endpoints registered on the video network Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 37 of 82

38 Enabling Lync clients registered on Lync Server to call endpoints registered on the video network Setting up search rules to route calls with video network domains to the video network Note that in small test and demo networks, this step is not necessary as the video network VCS Control is the Lync gateway VCS. 1. Go to Configuration > Dial plan > Search rules. 2. Click New. 3. Configure the following fields: 4. Configure the search rule to match the domain supported in the video network: Rule name An appropriate name, for example Route to Video network Priority Leave as default, for example 100 Source Mode Pattern type Pattern string Pattern behavior On successful match Target zone Any Alias pattern match Regex Anything in the video network domain, for Leave Continue Select the video network zone, for example To Video network 5. Click Save. 6. Repeat these steps to add a rule for each video network domain, including the mcu domain (for example,.+@mcu.ciscotp.com). Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 38 of 82

39 Enabling Lync clients registered on Lync Server to call endpoints registered on the video network Configuring Lync Server domain static routes This involves configuring domain static routes that route calls to the video and MCU domains to the Lync gateway VCS. The routes should reside on the Director (pool) if present, otherwise on the FEP (pool). Configuring static routes to route calls to the Lync gateway VCS 1. Create a static route from Lync to the "Lync gateway" VCS. Use the command New-CsStaticRoute with the following parameters: $=: the label referring to this specific new route. -TLSRoute: specifies that the route is TLS (recommended). -TCPRoute: specifies that the route is TCP. -Destination: the "Lync gateway" VCS Cluster FQDN for TLS routes. Use the IP Address in case of TCP routes. -MatchUri: the SIP domain that "Lync gateway" VCS is authoritative for. -Port: the TLS/TCP port to use for neighboring. It should be the port configured as Port on B2BUA for Lync call communications in the B2BUA advanced settings on the VCS (default 65072). -UseDefaultCertificate: to use the default certificate assigned to the Front End (must be $true) when using TLS. Do not specify this switch when using TCP. For example, for TLS: C:\Users\administrator.CISCOTP> $Route1=New-CsStaticRoute -TLSRoute -Destination "lync vcs.ciscotp.com" -MatchUri "vc.ciscotp.com" Port UseDefaultCertificate $true For example, for TCP: C:\Users\administrator.CISCOTP> $Route1=New-CsStaticRoute -TCPRoute -Destination " " -MatchUri "vc.ciscotp.com" Port Assign a static route. Use the command Set-CsStaticRoutingConfiguration with the following parameters: -Identity: specifies where to apply the route. It can be at the global level or on a specific pool. assigns the route defined earlier to the specified Identity (note that brackets are curly ). For example: C:\Users\administrator.CISCOTP> Set-CsStaticRoutingConfiguration -Identity global -Rou 3. Verify the static route assignment. Use the command : Get-CsStaticRoutingConfiguration Select-Object -ExpandProperty Route 4. Repeat the process for the mcu domain mcu.ciscotp.com and any other domains in the video network. To do this for the mcu domain, create and assign the static route using the same commands as above, but use a different label ($Route2) and specify -MatchUri "mcu.ciscotp.com". Note that: When Lync Server tries to route a call it will first check all its registrations: If any registration is found that matches the called URI, the call will be sent to that device, or if multiple registrations exist, the call will be forked to all registered devices that match the URI. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 39 of 82

40 Enabling Lync clients registered on Lync Server to call endpoints registered on the video network If there is no registration, Lync Server will then check the static domain routes and if there is one for this domain then Lync Server will route the call to the destination specified. If static routes are set up, VCS will receive any requests to that domain that Lync cannot handle, and thus may receive significant volumes of mis-dial traffic. Testing the configuration Test calls from Lync clients registered on Lync Server to endpoints registered on VCS Control. For example, call from a Lync client registered on Lync Server. Double-click on the buddy then click Video->Start a Video Call to make a video call: Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 40 of 82

41 Enabling Lync clients to see the presence of endpoints registered on VCS Control Enabling Lync clients to see the presence of endpoints registered on VCS Control Lync and VCS support for presence is as follows: Using SIP-SIMPLE, Lync Server 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. VCS only supports a maximum of 100 subscriptions per presentity. Lync Server does not supply presence status information about its registered endpoints using SIP-SIMPLE and so no presence information can be supplied to endpoints registered on VCS about endpoints registered on Lync Server. Lync clients registered to Lync Server can see the presence status of other Lync clients registered to Lync Server. Endpoints registered to VCS Control can see the presence status of other endpoints registered to VCS Control. In summary: to VCS to Lync Server VCS to Full presence available Presence = Available only Lync Server to No presence information available Full presence available Note that if you configure your system to register FindMe IDs to Lync Server, In-call states are also provided to Lync Server. See Using FindMe for enhanced deployments [p.44] VCS Control configuration We recommend that the Presence Server is enabled on the VCS Control. If endpoints registered to the VCS Control do not support the generation of presence information, the VCS Control can generate it on their behalf by enabling the PUA (Presence User Agent): PUA generates Presence of In-call if the endpoint is in a call PUA optionally (and by default) generates Presence of Available if the endpoint is registered If an endpoint is generating presence and the PUA is enabled, the VCS Presence Server will use the endpoint generated presence information. Note that for H.323 devices to supply presence (via the PUA), the registered H323 ID of that endpoint must resemble a SIP URI (in the format name@domain). The PUA will publish presence for that URI. To configure presence on the VCS Control: 1. Go to Applications > Presence. 2. Configure the following fields: SIP SIMPLE Presence User Agent On (if VCS Control is to generate presence information for registered endpoints) Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 41 of 82

42 Enabling Lync clients to see the presence of endpoints registered on VCS Control Default published status for registered endpoints SIP SIMPLE Presence Server Online On 3. Click Save. "Lync gateway" VCS configuration Ensure that the Presence Server is not enabled on the "Lync gateway" VCS. Testing the configuration Set up the endpoints registered on VCS as buddies in Lync clients. Check the status of the Lync users on the Lync gateway VCS by looking at the Lync user status page (Status > Applications > Lync users). Check that: Registration state = Registered Subscription state = Subscribed Presence state = offline or online See the icon on Lync client change from gray to green when an endpoint is registered on VCS (if Default published status for registered endpoints is set to Online). See the icon on Lync client change from green to gray if the endpoint becomes de-registered from VCS (if Default published status for registered endpoints is set to Online). Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 42 of 82

43 Enabling Microsoft Edge Server and VCS TURN capabilities Enabling Microsoft Edge Server and VCS TURN capabilities Ensure that the Microsoft Interoperability option key has been installed on the Lync gateway VCS. To enable call connectivity with Lync clients calling via an Edge server, the B2BUA needs to have TURN services properly configured to point to a VCS Expressway with TURN enabled. 1. Go to Applications > B2BUA > B2BUA TURN servers. 2. Click New. 3. Configure the fields as follows: TURN server address IP address of a VCS Expressway which has TURN enabled. (Just a single VCS; it may be just one peer from a cluster.) TURN server port 3478 The port on the VCS Expressway that is listening for TURN requests. On Large VM server deployments you can configure a range of TURN request listening ports. The default range is Description TURN services username and TURN services password An optional description of this TURN server. The username and password to access the TURN server. 4. Click Add address. 5. Go to Applications > B2BUA > Microsoft Lync > Configuration. 6. Configure the fields as follows: Offer TURN Services Yes 7. Click Save. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 43 of 82

44 Using FindMe for enhanced deployments Using FindMe for enhanced deployments You can optionally extend the deployment described in this guide by configuring your video network deployment to use FindMe. This provides richer presence and a more integrated environment. It uses the example deployment depicted below: Deployment information This deployment configuration consists of: FindMe accounts (also known as FindMe users) on the Lync gateway VCS that use the Lync network's domain (ciscotp.com in this example). The B2BUA registers these FindMe accounts into Lync so that Lync sees them as though they were Lync client registrations, for example: David with a URI david.jones@ciscotp.com, containing devices david.jones.office@vc.ciscotp.com and david.jones.external@vc.ciscotp.com Alice with a URI alice.parkes@ciscotp.com, containing devices alice.parkes.office@vc.ciscotp.com and alice.parkes.external@vc.ciscotp.com These FindMe accounts specify single or multiple endpoints as primary devices to call; the primary devices can be located anywhere in the video network or anywhere accessible via the video network. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 44 of 82

45 Using FindMe for enhanced deployments When Lync Server tries to route a call it will first check all its registrations: If any registration is found that matches the called URI, the call will be sent to that device, or if multiple registrations exist, the call will be forked to all registered devices that match the URI. If a registration is to a B2BUA registered FindMe account, Lync Server will send the call to the B2BUA. If there is no registration, Lync Server will then check the static domain routes and if there is one for this domain then Lync Server will route the call to the destination specified. If a corresponding Lync client also exists from a PC, the Lync client on the PC and the video endpoints specified in the FindMe will ring simultaneously when called, whether called from an endpoint communicating with VCS, or whether called from an endpoint communicating with Lync. For calls into Lync (from whichever video endpoint the user wants to call from) to have a Caller ID / call back ID that works, FindMe must re-write the caller ID of calls to Lync with the relevant Lync SIP user ID. For FindMe to be able to do this, calls must be routed through the VCS holding the relevant FindMe; having a Lync gateway helps funnel all calls through the correct place. MCUs that will receive calls from Lync can register conferences to the video network with a dedicated MCU domain (mcu.ciscotp.com) and make these available to Lync users via a FindMe account (suitable for static conference aliases). Alternatively, you can still use a static SIP domain route from the Lync environment (suitable for ad-hoc conference aliases). The Lync static routes defined in the basic solution are no longer required (apart from those used for ad-hoc conference aliases). The Presence Server must reside on the "Lync gateway" VCS, and the "Lync gateway" VCS must be authoritative for the domain shared by Lync and the VCS (ciscotp.com), and all of the other domains used in the video network. It must hold the presence status of endpoints specified in the FindMe accounts in the Lync domain existing on this Lync gateway VCS (cluster), as FindMe presence only represents the presence of devices whose presence is known on that VCS (cluster). Available, off-line and in-call presence may be observed by Lync clients for users and any MCU conferences that are associated with a FindMe account on the Lync gateway VCS. Note: this requires that the primary video devices within the FindMe account have a URI-based alias, for example firstname.lastname@domain and that their presence is also held on the Presence Server on the Lync gateway VCS. Clustered Lync gateway VCS To provide enhanced load balancing, the Lync gateway VCS peers will distribute the shared domain FindMe users between themselves, and register their set with Lync Server. When Lync Server makes a call to one of these user IDs, the call will be presented to the VCS that made the registration hence the calls are statically load-shared across the cluster. If any peers go out of service, the remaining active peers take over the registrations of the unavailable peers. Lync gateway VCS and multiple Lync domains If Lync supports multiple domains, and the video network is to support these domains as well, we recommend that one Lync gateway VCS or VCS cluster is used to handle each domain. This is because the B2BUA only supports registering a single domain. If some domains are not used in the video network, but need calls to be routed to them, there does not need to be a Lync gateway VCS for those domains. Search rules can be added to support routing to these domains. If different Lync SIP domains are handled by different Lync gateway VCSs or VCS clusters, take care to ensure that each Lync gateway VCS or VCS cluster is authoritative for the presence information that is required for the B2BUA registered FindMe users for that one shared domain and all endpoints that are referenced by those FindMe entries. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 45 of 82

46 Using FindMe for enhanced deployments MCU configuration for ad hoc conferences from Lync We recommend that FindMe accounts are created for static/permanent conferences, where the FindMe account contains the SIP URI of the conference as a device. For FindMe-based permanent conferences, presence will show as: Available if conference does not have participants In-Call if conference has participants Optionally, a FindMe account can be created which contains the SIP URI of the MCU s auto attendant. This will allow Lync users to join any conference via the auto attendant. However, this method will not utilize the In-call presence status available for individual FindMe-based conferences. Prerequisites The FindMe option key must be installed on the Lync gateway VCS. Configuring the "Lync gateway" VCS for FindMe The "Lync gateway" VCS FindMe configuration consists of the following steps: 1. Configure all the required SIP domains. 2. Configure the B2BUA to register FindMe users to Lync. 3. Enable FindMe and create FindMe user accounts for each user that is to share Lync client and VCS endpoints. Configure all the required SIP domains B2BUA-registered FindMe users need the Lync gateway VCS to be authoritative for the Lync server s shared domain (ciscotp.com). It also needs to be authoritative for any other domains in the video network (to support the Presence Server, and to aggregate presence information for devices associated to the FindMe accounts). 1. Go to Configuration > Domains. 2. Click New. 3. Set Name to ciscotp.com. 4. Click Create domain. 5. Repeat for all the other domains in the video network, including vc.ciscotp.com and mcu.ciscotp.com. Configure the B2BUA to register FindMe users to Lync 1. Go to Applications > B2BUA > Microsoft Lync > Configuration. 2. Configure the fields as follows: Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 46 of 82

47 Using FindMe for enhanced deployments Register FindMe users as clients on Lync Lync domain Yes Select the shared Lync domain, e.g. ciscotp.com 3. Click Save. Enable FindMe and create FindMe user accounts for each user that is to share Lync client and VCS endpoints 1. Go to Maintenance > Option keys and ensure that the FindMe key is listed. 2. Go to Applications > FindMe. a. Set Mode to On. b. Set Caller ID to FindMe ID. Setting FindMe to present the FindMe ID (rather than the endpoint ID) means that any device in the primary list of FindMe devices will provide the FindMe ID as the Caller ID. Thus, if a called party rings the caller ID back, all FindMe endpoints will ring, not just the endpoint that made the initial call. c. Click Save. 3. For each user that is to share Lync client and VCS endpoints, create a FindMe user account on the VCS with the same URI as the Lync client: Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 47 of 82

48 Using FindMe for enhanced deployments a. Go to Users > FindMe accounts. (If you are using Cisco TMSPE you must set up the accounts via Cisco TMS instead.) b. Click New. c. Configure the following fields: Username Display name Phone number FindMe ID Principal device address Initial password and Confirm password FindMe type Username used by the FindMe user to log in to VCS to administer this account. Full name of this user. E164 number to use when outdialing to a gateway. URI with Lync s domain that will register to Lync Server as though it were a Lync client. Routable endpoint URI / E164 or H.323 ID to call when this FindMe is called. Password needed by the FindMe user to log in to VCS to administer this account. (Not configurable if VCS is configured with User authentication source as Remote.) Individual 4. Ensure that the domain shared with the Lync is resolvable by the DNS server; this is usually best achieved by using the same DNS server that Lync Server uses. See Lync gateway VCS: Configure DNS and local hostname [p.26]. Configuring Lync Active Directory for FindMe users Ensure that Active Directory user accounts exist for all FindMe accounts on the Lync gateway VCS(s) that will register to Lync Server (FindMe accounts that have the same domain as Lync). On the PC running the Active Directory for Lync users: 1. Select Start > Control Panel > Administrative Tools > Active Directory Users and Computers. or Start > All Programs > Administrative Tools > Active Directory Users and Computers. 2. Select the Users folder under the required domain: Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 48 of 82

49 Using FindMe for enhanced deployments For each new user that needs to be created: 1. Click Create new user in the current container or select Action > New > User. 2. Configure the following fields: First name Last name User logon name The user s first name The user s last name The user s logon name 3. Click Next. 4. Configure the following fields: Password Confirm password Password never expires The user s password Retype the password Select this check box. 5. Click Next. 6. Click Finish. 7. Enable the user for Lync: a. Bring up the Lync Server Control Panel (either from the start menu select Lync Server Control Panel, or if there is a desktop icon double click it). b. On Lync Server Control Panel go to the Users menu: you can see users already enabled for communication server. To add a new user: a. Select Enable users and click Add. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 49 of 82

50 Using FindMe for enhanced deployments b. Search for and select the user (in this example, David Jones) Note: to find the user it must already have been defined in Active Directory. c. Select the communication server pool to assign to the user. d. Select your preferred method to Generate user s SIP URI. e. Select the user s Telephony type. This can be done in single command by CSPS using the command enable-csuser For example: enable-csuser -identity "ciscotp\david.jones" -registrarpool "feppool.ciscotp.com" -sipaddress sip:david.jones@ciscotp.com Log in to each Lync client Lync Server will not provide presence for FindMe users to other Lync clients until the Lync client associated with a FindMe has been signed into using a Lync client registered to Lync Server. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 50 of 82

51 Using FindMe for enhanced deployments For each FindMe user that has been created: 1. Log into a Lync client as that user. 2. Log out. 3. Repeat for all users. Verify that the FindMe accounts are registered After the FindMe accounts have been configured for at least 60 seconds: 1. On the "Lync gateway" VCS, go to Status > Applications > Lync users. 2. Verify the following for each FindMe user: Registrations state is Registered Presence state is Online (if Default published status for registered endpoints is set to Online, otherwise expect to see Offline) Subscription state is Subscribed If the states are not as expected, check that the FindMe and Lync (Active Directory) registered names are identical. Testing the configuration Test calls from Lync clients registered on Lync Server to endpoints registered on VCS Control. For example, call david.jones@ciscotp.com or alice.parkes@ciscotp.com from a Lync client registered on Lync Server. Double-click on the buddy then click Video->Start a Video Call to make a video call. 1. Test that calls to Lync registered FindMe users from VCS registered endpoints fork to VCS registered endpoints listed in the FindMe entry and also to the Lync client for this user. 2. Test that calls to Lync registered FindMe users from Lync clients fork to the Lync client and also to VCS registered endpoints listed in the FindMe entry for this user. Enabling Lync clients to see the presence of endpoints registered on VCS Control When using FindMe: The Presence Server must be enabled on the "Lync gateway" VCS (and disabled on the VCS Control). The "Lync gateway" VCS must be authoritative for the shared Lync/FindMe domain (ciscotp.com) and for the domains of all devices that are referenced in the FindMe users that register to Lync, as FindMe will only aggregate presence data for devices where their presence state is known on the same VCS as the FindMe resides. When the B2BUA is configured to register FindMe IDs to Lync Server, gray (not available), green (available) and In-call states are provided to Lync Server. VCS Control configuration Disable the Presence Server on the VCS Control To disable the Presence Server on the VCS Control: 1. Go to Applications > Presence. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 51 of 82

52 Using FindMe for enhanced deployments 2. Configure the following fields: SIP SIMPLE Presence User Agent Default published status for registered endpoints SIP SIMPLE Presence Server On (if VCS Control is to generate presence information for registered endpoints) Online Off (the "Lync gateway" VCS will be the Presence Server) Configure a search rule to route messages to the Presence Server on the "Lync gateway" VCS The PUA on the VCS Control needs to be able to route PUBLISH messages from its domain endpoints to the Presence Server running on the "Lync gateway" VCS. To do this, a search rule is required: 1. Go to Configuration > Dial plan > Search rules. 2. Click New. 3. Configure the following fields: Rule name An appropriate name, for example Route publish messages to Lync gateway Priority Leave as default, for example 100. Note that this should be a lower priority (a larger number) than the priority configured for the LocalZoneMatch. Source Mode Pattern type Pattern string Pattern behavior On successful match Target Any Alias pattern match Regex Configure the pattern to match the domain supported in the video network, for example:.*@vc\.ciscotp\.com Leave Continue Select the Lync gateway zone, for example To Lync gateway 4. Click Create search rule. Note that this search rule does not conflict with Local Zone searches (which may contain the same pattern match string) because the PUA is not treated as a Local Zone registered device. 5. Create additional search rules for any other SIP domains (such as mcu.ciscotp.com) supported by this Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 52 of 82

53 Using FindMe for enhanced deployments VCS (i.e. for endpoints that are registered to the VCS Control) otherwise Presence will not work (messages will not get forwarded). Lync gateway VCS configuration Enable the Presence Server on the Lync gateway VCS On the Lync gateway VCS: 1. Go to Applications > Presence. 2. Configure the following fields: SIP SIMPLE Presence User Agent Default published status for registered endpoints SIP SIMPLE Presence Server Off Online On Ensure the Presence Server can receive presence messages Ensure that the zone to the video network has an authentication policy of Treat as authenticated (the Presence Server accepts PUBLISH messages only if they have been authenticated): 1. Go to Configuration > Zones > Zones. 2. Select the To Video network zone. 3. Ensure that Authentication policy is set to Treat as authenticated. Notes: The Lync gateway VCS that connects to the Lync Server must be the presence server for any SIP domains that Lync Server might want to look at for presence; this limits the number of VCSs that Lync server s presence requests will travel through. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 53 of 82

54 Using FindMe for enhanced deployments Presence requests use up SIP resources and with Lync typically having thousands of Lync clients connected that may be requesting presence, it is best to limit the range of where the presence requests can go, especially not letting them reach VCSs that may already be heavily used for taking calls. Lync client configuration Set up Sign-in address as required. This is the SIP URI of the Lync user; if this user also has video endpoints on the video network, this URI will be the same URI as that configured as the B2BUA registered FindMe user ID (set up later), for example Log in to the Lync client Lync Server will not provide presence for FindMe users to other Lync clients until the Lync client associated with a FindMe has been signed into using a Lync client registered to Lync Server. For each FindMe user that has been created and not already been signed into: 1. Sign into a Lync client as that user. 2. Sign out. 3. Repeat for all users. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 54 of 82

55 Appendix 1: Troubleshooting Appendix 1: Troubleshooting Troubleshooting checklist If you are experiencing a problem with the Lync integration, we recommend that you go through the following list when performing the initial faultfinding. It will help to uncover any potential problems with the base configuration and status of the deployment: Ensure that video endpoints and infrastructure devices are running up-to-date software. Doing so lowers the chances for interoperability issues between the video environment and Lync. Ensure that all "Lync gateway" VCSs can successfully look up all Lync Server A-record FQDNs in DNS (this includes both Director and FEPs). You can use Maintenance > Tools > Network utilities > DNS lookup on the VCS. Ensure that all Lync servers can successfully look up all Lync gateway VCS peer A-record FQDNs and cluster FQDN in DNS. You can use the nslookup command-line utility locally on each Lync Server. Verify that the B2BUA has connectivity both with the Lync environment and the VCS (on the Status > Applications > Lync B2BUA page, Status = Alive is the desired state for both), and, if using FindMe, that the B2BUA has successfully registered FindMe accounts to Lync (on the Status > Applications > Lync users page Registration state = Registered and Subscription state = Subscribed are the desired states). Problems connecting VCS Control local calls Look at search history to check the applied transforms 1. In VCS, go to Status > Search history. 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. 2. Select the relevant search attempt. The search history for that search attempt shows: the incoming call s details any transforms applied by pre-search transforms or CPL or FindMe in priority order, zones which matched the required (transformed) destination, reporting on: o any transforms the zone may apply o found or not found status o if not found, the error code as seen in the zone s search response repeated until a zone is found that can accept the call, or all matches have been attempted (The search may be not found due to lack of bandwidth or because the search from the zone resulted in an H.323 rejection reason or a non 2xx response to a SIP request.) 3. If the search indicates: Found: False Reason: 480 Temporarily Not Available this could be because the VCS s zone links are not correctly set up. From the command line execute: xcommand DefaultLinksAdd to set up the links for the default zones. Also check that the links for other zones that have been created. Note that each H.323 call will have 2 entries in the search history: An ARQ to see if the endpoint can be found. The SETUP to actually route the call. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 55 of 82

56 Appendix 1: Troubleshooting The ARQ search does not worry about links or link bandwidth, and so if links do not exist or link bandwidth is insufficient it may still pass, even though the SETUP search will subsequently fail. Each SIP call will usually only have a single search history entry for the SIP INVITE. Look at Call History to check how the call progressed 1. Go to Status > Calls > History. The summary shows the source and destination call aliases, the call duration and whether the call is a SIP, H.323 or SIP< -- >H.323 interworking call. 2. Select the relevant call attempt. The entry shows the incoming and outgoing call leg details, the call s status and the zones that the VCS Control used to route the call. Check for errors in the Event Log Check the Event Log (Status > Logs > Event Log). Tracing calls Tracing calls at SIP / H.323 level 1. Go to Maintenance > Diagnostics > Diagnostic logging. 2. Optionally, select Take tcpdump while logging. 3. Click Start new log. 4. (Optional) Enter some Marker text and click Add marker. The marker facility can be used to add comment text to the log file before certain activities are performed. This helps to subsequently identify the relevant sections in the downloaded diagnostic log file. You can add as many markers as required, at any time while the diagnostic logging is in progress. Marker text is added to the log with a "DEBUG_MARKER" tag. 5. Reproduce the system issue you want to trace in the diagnostic log. 6. Click Stop logging. 7. Click Download log to save the diagnostic log to your local file system. You are prompted to save the file (the exact wording depends on your browser). 8. If appropriate, click Download tcpdump to also download the tcpdump file to your local file system. Presence not observed as expected Presence Server status Go to Status > Applications > Presence > Publishers to check who is providing presence information to the VCS Presence Server. Go to Status > Applications > Presence > Presentities to check whose presence is being watched for (on domains handled by VCS Presence Server). Go to Status > Applications > Presence > Subscribers to check who is watching for presence (of one or more entities in domains handled by VCS Presence Server): Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 56 of 82

57 Appendix 1: Troubleshooting No presence being observed Check that there is no transform that may be inadvertently corrupting the presence Publication, Subscription or Notify, for example that there is no transform modifying the presence URI. (Notifies are sent to the subscription contact ID, typically address>:<ip port>;transport=xxx. Any transforms that modify this are likely to stop the presence Notify being routed appropriately.) Lync client fails to update status information If a Lync client is started before the Presence Server is enabled, the Lync client may need to be signed out and signed 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 and the logging facilities mentioned in the Check for errors section above. Video endpoint reports that it does not support the Lync client SDP If a video endpoint reports that it does not support the Lync client SDP, for example by responding 400 Unable to decode SDP to a SIP INVITE message containing the Lync multi-part mime SDP sent to it: 1. Check whether the Lync Server is sending calls to the VCS incoming IP port, rather than the B2BUA IP port that should be receiving the incoming SIP messages. 2. Reconfigure Lync Server to send calls to the B2BUA IP port. TLS neighbor zone to Lync Server is active and messaging is sent from VCS to Lync Server, but Lync debug says Lync fails to open a connection to VCS The local host name and domain name fields must be configured in the VCS System > DNS page so that VCS can use its hostname (rather than IP address) in communications. Lync requires the use of VCS hostname so that it can open a TLS connection to the VCS. Lync client initiated call fails to connect If a call fails to connect, check that the endpoint, IP Gateway, MCU or ISDN Gateway is NOT in Microsoft mode; ensure that it is in Standard or Auto mode. (From a H.323/SIP trace, an indication that the device is in Microsoft mode is the presence of a proxy=replace field in the contact header of the 200 OK from the device.) Lync responds to INVITE with 488 Not acceptable here There can be two causes for this message: From IP address This is normally seen if the B2BUA forwards an INVITE from a standards-based video endpoint where the From header in the SIP INVITE only contains the IP address of the endpoint, e.g. From: Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 57 of 82

58 Appendix 1: Troubleshooting <sip: >;tag=d29350afae33. This is usually caused by a misconfigured SIP URI in the endpoint. In future versions of B2BUA, the From -header will be manipulated if necessary to avoid this issue. Encryption mismatch Look for the reason for the 488. If it mentions encryption levels do not match, ensure that you have configured encryption appropriately, either: Lync gateway VCS has the Microsoft Interoperability option key included, or Lync is configured such that encryption is supported (or set as DoNotSupportEncryption ) note that if the encryption support is changed on Lync then a short time must be left for the change to propagate through Lync Server and then the Lync client must be signed off and then signed back in again to pick up the new configuration. Call connects but clears after about 30 seconds If a call connects but shortly later clears, this is likely to be because the caller s ACK response to the 200 OK is not being properly routed. To resolve this, make sure that the VCS and Lync servers are able to resolve each other s FQDNs in DNS. VCS to Lync Server calls fail DNS server VCS needs to have details about DNS names of Lync pools and servers, and therefore needs to have one of its DNS entries set to point to a DNS server which can resolve the FQDNs of the Lync pools and servers. VCS to Lync calls fail Hardware Load Balancer If the Lync environment has FEPs with an HLB in front, ensure that the VCS is neighbored with the HLB. If it is neighbored with an FEP directly, trust for VCS will be with the FEP. VCS will send call requests to the FEP, but the FEP will record-route the message such that the ACK response should be sent to the HLB. The ACK sent to the HLB gets rejected by Lync Server, so Lync clears the call after the SIP timeout due to the FEP not seeing the ACK. (Calls from Lync client registered to the FEP to VCS may still work.) Media problems in calls involving external Lync clients connecting via an Edge server RTP over TCP/UDP The Edge server supports RTP media over both TCP and UDP, whereas the B2BUA and standards based video endpoints only support RTP over UDP. The Edge server and any firewalls that the Edge server may pass media traffic through may need to be reconfigured to allow RTP over UDP as well as RTP over TCP to be passed. ICE negotiation failure This can usually be detected by the call clearing with a BYE with reason header failed to get media connectivity. Video endpoints only support UDP media. ICE usually offers 3 candidates: Host (private IP) Server Reflexive (outside IP address of firewall local to the media supplying agent B2BUA or Lync Client) TURN server (typically the Edge Server/VCS Expressway) Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 58 of 82

59 Appendix 1: Troubleshooting For ICE to work where an endpoint is behind a firewall, the endpoint must offer at least one publicly accessible address (the Server Reflexive address or the TURN server address). This is used both for the B2BUA to try and send media to, but also to validate bind requests sent to the VCS Expressway s TURN server bind requests are only accepted by the TURN server if they come from an IP address that is known. If a Lync INVITE offers only host candidates for UDP, for example: a=candidate:1 1 UDP typ host a=candidate:1 2 UDP typ host a=candidate:2 1 TCP-ACT typ srflx raddr rport a=candidate:2 2 TCP-ACT typ srflx raddr rport only one UDP candidate (two lines, one for RTP and one for RTCP) and they are for the host (private, presumably non-routable by VCS address) and the B2BUA responds, for example: a=candidate:1 1 UDP typ host a=candidate:1 2 UDP typ host a=candidate:4 1 UDP typ relay raddr rport a=candidate:4 2 UDP typ relay raddr rport Host and Relay candidates are both offered. Neither device will be able to reach the other s private (host) address, and if the Lync client tries to bind to the VCS Expressway TURN server it will get rejected because the request will come from the server reflexive address rather than private address and Lync client has not told the B2BUA what that IP address is. Thus, Lync Server and the Microsoft Edge Server must be configured such that a Lync client offers at least one public address with UDP media for this scenario to work. Note that in the above scenario the B2BUA may not offer the Server Reflexive address if the Server Reflexive address is seen to be the same as the host address. Call between endpoint and Lync fails with reason 'ice processing failed' If the search history on VCS shows calls failing with 'ice processing failed', this means that all ICE connectivity checks between the B2BUA and the remote Lync device have failed. Verify that the TURN server on VCS Expressway has been enabled and that the TURN user credentials on VCS Expressway and B2BUA configuration match properly. This failure could also indicate a network connectivity issue for STUN/TURN packets between B2BUA, VCS Expressway/TURN server and the far end TURN server/microsoft Edge. One way media: Lync client to VCS-registered endpoint When using Microsoft Edge Server When Lync clients register to Lync through a Microsoft Edge Server, the local IP address and port that the Lync client declares is usually private and un-routable (assuming that the Lync client is behind a firewall and not registered on a public IP address). To identify alternate addresses to route media to, the Lync client uses SDP candidate lines. Calls traveling through the Microsoft Edge server are supported when using the B2BUA with the Microsoft Interoperability option key applied to the Lync gateway VCS, and where the video architecture includes a VCS Expressway with TURN enabled and the B2BUA is configured to use that TURN server. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 59 of 82

60 Appendix 1: Troubleshooting When using a Hardware Load Balancer in front of Lync VCS modifies the application part of INVITEs / OKs received from Lync clients to make them compatible with traditional SIP SDP messaging. VCS only does this when it knows that the call is coming from Lync. If there are problems with one-way media (media only going from Lync client to the VCS registered endpoint), check the search history and ensure that the call is seen coming from a Lync trusted host. Otherwise, the call may be coming from a FEP rather than the load balancer. See Lync gateway VCS configuration (part 2) [p.30] and configure Lync trusted hosts containing the FEP IP addresses. Lync rejects VCS zone OPTIONS checks with 401 Unauthorized and INFO messages with 400 Missing Correct Via Header' A response 400 Missing Correct Via Header is an indication that Lync does not trust the sender of the message. A response 401 Unauthorized response to OPTIONS is another indication that Lync does not trust the sender of the OPTIONS message. Ensure that Lync environment has been configured to trust the VCS which is sending these messages, as described previously in this document. Note, this can also be seen if a load balancer is used in front of the Lync, and Lync is configured to authorize the VCS (Lync sees calls coming from the hardware load balancer rather than from the VCS). Lync client stays in Connecting state Lync client does not change into the connected state until it receives RTP (media) from the device with which it is in a call. Call to PSTN or other devices requiring caller to be authorized fails with 404 not found In some Lync configurations, especially where Lync PSTN gateways are used, calls are only allowed if the calling party is authorized. Thus, the calling party s domain must be the Lync Server shared domain. For calls from endpoints that are not part of a FindMe, this means that the endpoints must register to the video network with a domain that is the same as the Lync domain. For calls from endpoints that are part of a FindMe, the endpoints can register with any domain so long as the FindMe ID has the same domain as the shared Lync domain and in the FindMe configuration Caller ID is set to FindMe ID (instead of Incoming ID). Lync clients try to register with VCS Expressway SIP video endpoints usually use DNS SRV records in the following order to route calls to VCS: _sips._tcp.<domain> _sip._tcp.<domain> and _sip._udp.<domain> Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 60 of 82

61 Appendix 1: Troubleshooting Lync clients use: _sipinternaltls._tcp.<domain> - for internal TLS connections _sipinternal._tcp. <domain> - for internal TCP connections (only if TCP is allowed) _sip._tls. <domain> - for external TLS connections Lync clients only support TLS connection to the Edge Server. The _sip._tcp.<domain> DNS SRV record should be used for the VCS Expressway. B2BUA problems B2BUA users fail to register If B2BUA registration fails to register FindMe users (Registration status = failed), check: 1. The FindMe name is correctly entered into Active Directory. 2. A Lync client can register as the FindMe name you need to log in first from a Lync client before the B2BUA can properly control the Lync user. B2BUA Lync Server status reports "Unknown" or "Unknown failure" Check that the VCS application has been added to the Lync trusted application pool and is configured to contact the VCS B2BUA via port See Trust a Lync gateway VCS [p.28] for more information. Lync problems Run the Lync Server Best Practices Analyzer to help identify configurations that may be incorrect on Lync Server. Details and the download for Lync Server 2010 can be found at and Lync Server 2013 content is at Problems with certificates If a non-lync application is used to create certificates to load onto VCS for use with Lync (for example when purchased from a certificate authority) it is vital that the Subject name and Subject Alternate Name contain the same details as they would if the certificates were created by Lync. Specifically, if both Subject name and Subject Alternate Name are used, then the name entered in the Subject name must also appear in the Subject Alternative Name list. See also VCS Certificate Creation and Use Deployment Guide. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 61 of 82

62 Appendix 2: Debugging on Lync Appendix 2: Debugging on Lync Use of Lync Server Logging Tool For debugging it is important to enable the logging on the appropriate Lync pool. If a Lync Director is in use, tracing here is a good starting point. Looking at the record-route headers in SIP messages from Lync will identify the FEP and Director involved in the call. 1. On Lync Server select Start > All Programs > Microsoft Lync Server 2010 > Lync Server Logging Tool. 2. Select the logging option, for example SIPStack to look at SIP logs. (Details about the logging tool may be found at: 3. Click Start Logging. 4. Make the call, or perform the function that needs to be debugged. 5. Click Stop Logging. 6. Click Analyze Log Files (install the Lync Server Resource Kit Tools if prompted to do so). 7. Review the trace: Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 62 of 82

63 Appendix 2: Debugging on Lync Enabling debug on Lync client If the Lync client is not working correctly, 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: a. Select Turn on logging in Lync. b. Select Turn on Windows Event logging for Lync. Lync log files may be found in: c:\documents and Settings\<user>\Tracing where <user> is the login name of the windows login. The.uccplog file can be viewed with a text editor, or (more clearly) with the application provided in the Lync resource kit snooper.exe. Windows event logging can be observed using the Windows Event Viewer. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 63 of 82

64 Appendix 3: Interoperating capabilities and limitations Appendix 3: Interoperating capabilities and limitations Known interoperating capabilities SIP and H.323 endpoints making basic calls SIP and H.323 endpoints can make calls via VCS Control to Lync clients registered to Lync Server. Lync clients registered to Lync can make calls to SIP and H.323 endpoints on VCS Control. Upspeeding from a voice call to a video call If a voice call is made from a Lync client to a video endpoint registered to VCS Control and then the video button is selected to enhance the call to a video call, the video endpoint will correctly upspeed to video. When interworking a Lync client to an H.323 endpoint, the call will only upspeed from voice to video if the upspeed request occurs before the endpoint sends a BRQ lowering the connection bandwidth. Multiway generation of ad hoc conferences Endpoints can join Lync clients into an ad hoc conference using the Multiway feature. When a Lync client is transferred into a Multiway conference, the client will connect using audio only. The Lync user will then manually have to enable video on the client after connecting to the conference. Known interoperating limitations Video codecs If Lync 2010 is used, the video endpoints registered to the VCS Control must support H.263; this is the common video codec supported by endpoints and the Lync client. (The Lync client does not support H.264.) The Lync 2010 client for Apple Mac OS X only supports RTVideo, no standards-based video codecs (H.263 or H.264). To make video calls between this client and standards-based video endpoints, a Cisco AM GW is needed to transcode between RTVideo and H.263/H.264. Video codec selection When the B2BUA receives a call with no SDP that is, without a list of codecs that can be used for the call (for example, a call that has been interworked from H.323), the B2BUA must populate the SDP with a preconfigured list of codecs from which Lync can select, as Lync does not support INVITES with no SDP. The codecs offered and selected, therefore, may not reflect the best codecs that could have been selected by the endpoints. Changing the pre-configured SDP The settings for the pre-configured SDP are configurable via the CLI only, using the xconfiguration Zones Zone [ ] [Neighbor/DNS] Interworking SIP commands. MXP endpoints Video from MXP endpoints to Lync 2013 H.264 SVC is limited to 15fps (video with other endpoints is 30fps). Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 64 of 82

65 Appendix 3: Interoperating capabilities and limitations Joining a Lync conference (AV MCU) Using a Lync client to invite a third party to join the call does not work if the third endpoint is an endpoint registered to the VCS Control, or if the endpoint registered to the VCS Control is already in the call and another Lync client is introduced into the call. This is because when the Lync client invites a third party to join a call, the Lync client tries to create a conference using Microsoft proprietary messaging (xml in SIP messages), and this is not supported by standards-based video endpoints. Neither VCS Control nor standards-based video endpoints support the Microsoft proprietary signaling. Note, however use of Multiway on endpoints can join Lync clients into an ad hoc conference (see Cisco TelePresence Multiway Deployment Guide). Upspeeding from a voice call to a video call Interworking a Lync client to an H.323 endpoint, the call will only upspeed from voice to video if the upspeed request occurs before the endpoint sends a BRQ lowering the connection bandwidth. Microsoft Mediation Server Calls to Microsoft Mediation Servers work from endpoints in the 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 VCS INFO message, sent to check availability of the destination number). A workaround is possible if the format of the numbers that will be routed to the mediation server can be configured in VCS. Configure the Lync gateway VCS with a second zone to connect to the Lync Server. Select the Custom zone profile and configure the options as listed below and then configure one or more search rules so that calls destined for the mediation server are routed to this zone rather than to the standard To Microsoft Lync Server via B2BUA" zone. Setting Monitor peer status Call signaling routed mode Automatically respond to H.323 searches Automatically respond to SIP searches Send empty INVITE for interworked calls SIP poison mode SIP encryption mode SIP SDP attribute line limit mode Lync Server zone configuration Yes Auto Off On Off On Microsoft On SIP SDP attribute line limit length 130 SIP multipart MIME strip mode SIP UPDATE strip mode Interworking SIP search strategy On On Info Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 65 of 82

66 Appendix 3: Interoperating capabilities and limitations Setting SIP UDP/BFCP filter mode SIP Duo Video filter mode SIP record route address type SIP Proxy-Require header strip list Lync Server zone configuration Off On Hostname <blank> Cluster calls to endpoints not registered using FindMe This can occur, for example, with MCU calls where MCU is in its own dedicated domain. Lync does not have a way of load balancing calls to a cluster of VCSs. Lync does not support DNS SRV, but it does allow the DNS record to be a Round-Robin record listing all VCSs in the Lync gateway cluster./ Lync seems to continue to use just a single VCS until it loses connectivity to that VCS. At that time it will choose a different VCS from the Round-Robin DNS record. Use of VCS clusters with Lync without B2BUA FindMe registration therefore provides resilience, not extra capacity / load balancing. Lync client reports no audio device Lync client sometimes complains that it has no audio device configured when selecting resume follow Lync client s instructions to update the audio device and resume will then work. Call forward from Lync to a VCS FindMe or endpoint results in a loop detected call If a call from VCS is made to a Lync client which has a forward to another VCS registered endpoint or a FindMe, then VCS sees this as a looped call. FindMe Caller ID set to FindMe ID causes calls from Lync client to fail If all of the following are true: FindMe Caller ID is set to FindMe ID a Lync client s URI is in the active location of a FindMe a call is made from that Lync client to a SIP destination the call will fail because Lync does not expect the caller ID (From: header) to be modified. If the call is interworked on the Lync gateway VCS, the call will work as required. Best practice is that a Lync client should never be included as a FindMe device. Lync clients and video endpoints are related to one another using B2BUA registration of FindMe IDs where the FindMe URI is the same as the Lync client URI. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 66 of 82

67 Appendix 4: Port reference Appendix 4: Port reference The port numbers listed below are the default port values. The values used in a real deployment may vary if they have been modified, for example, by changes of registry settings or through group policy, on Lync and Lync client, or configuration on VCS (Applications > B2BUA). Between B2BUA and Lync Purpose Protocol B2BUA IP port Lync IP port Signaling to Lync Server TLS (Lync signaling destination port) Signaling from Lync Server TLS Lync ephemeral port Presence to Lync Server TLS (Lync signaling destination port) Presence from Lync Server TLS Lync ephemeral port Media (the Lync B2BUA should be deployed on a separate "Lync Gateway" VCS and thus there should be no conflict with the standard traversal media port range) UDP to Lync client media ports Between B2BUA and VCS (internal communications) Purpose Protocol B2BUA IP port VCS IP port Internal communications with VCS application TLS SIP TCP outbound port Between B2BUA and VCS Expressway hosting the TURN server Purpose Protocol B2BUA IP port VCS Expressway IP port All communications UDP to (media/signaling) * Ensure that the firewall is opened to allow the data traffic through from B2BUA to VCS Expressway. * On Large VM server deployments you can configure a range of TURN request listening ports. The default range is External Lync client and Edge server Purpose Protocol Edge server Lync client SIP/MTLS used between Lync Client and Edge server for signaling (including any ICE messaging to the Edge Server) TCP SIP/TLS TCP Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 67 of 82

68 Appendix 4: Port reference Purpose Protocol Edge server Lync client STUN UDP UDP Media UDP TCP Media TCP External Lync client / Edge server and VCS Expressway Purpose Protocol Lync client / Edge server VCS Expressway ICE messaging (STUN/TURN) if media is sent via the VCS Expressway UDP media if it is sent via the VCS Expressway UDP UDP ** ** The default TURN relay media port range of applies to new installations of X8.1 or later. The previous default range of still applies to earlier releases that have upgraded to X8.1. Between B2BUA and transcoder Purpose Protocol B2BUA IP port Transcoder B2BUA communications with transcoder (Cisco AM GW) TLS Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 68 of 82

69 Appendix 5: Media paths and license usage for calls through B2BUA Appendix 5: Media paths and license usage for calls through B2BUA Lync client call to SIP video endpoint For a call of this type: Signaling flows through Lync, B2BUA, and VCS Control. Media is connected directly between the Lync client and the B2BUA. Media is connected directly between the internal video endpoint and the B2BUA (as the call is SIP to SIP). Calls made in the opposite direction, internal video endpoint to Lync client use the same signaling and media paths. Licenses: 1 non-traversal call license on VCS Control 1 non-traversal call license on Lync gateway VCS Signaling Media Lync client call to H.323 video endpoint For a call of this type: Signaling flows through Lync, B2BUA, and VCS Control. Media is connected directly between the Lync client and the B2BUA. Media from the internal video endpoint flows through the VCS Control and is then connected directly to the B2BUA. Calls made in the opposite direction, internal video endpoint to Lync client use the same signaling and media paths. Licenses: 1 traversal call license on VCS Control 1 non-traversal call license on Lync gateway VCS Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 69 of 82

70 Appendix 5: Media paths and license usage for calls through B2BUA Signaling Media Lync client call to a SIP video endpoint via Cisco AM GW For a call of this type: Signaling flows through Lync, B2BUA, Cisco AM GW and VCS Control. Media is connected directly between the Lync client and the B2BUA. Media is connected directly between the internal video endpoint and the B2BUA (as the call is SIP to SIP), and then flows to the Cisco AM GW and back to the B2BUA. Calls made in the opposite direction, internal video endpoint to Lync client use the same signaling and media paths. Licenses: 1 non-traversal call license on VCS Control 1 non-traversal call license on Lync gateway VCS Signaling Media Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 70 of 82

71 Appendix 5: Media paths and license usage for calls through B2BUA Lync client call to H.323 video endpoint via Cisco AM GW For a call of this type: Signaling flows through Lync, B2BUA, Cisco AM GW and VCS Control. Media is connected directly between the Lync client and the B2BUA. Media from the internal video endpoint flows through the VCS Control and is then connected directly to the B2BUA. It then flows to the Cisco AM GW and back to the B2BUA. Calls made in the opposite direction, internal video endpoint to Lync client use the same signaling and media paths. Licenses: 1 traversal call license on VCS Control 1 non-traversal call license on Lync gateway VCS Signaling Media Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 71 of 82

72 Appendix 5: Media paths and license usage for calls through B2BUA An external Lync client calls an external video endpoint In this scenario an external Lync client (alice.parkes) calls an external video endpoint (david.jones.external). Signaling flows through the Microsoft Edge Server, Lync, B2BUA, VCS Control and VCS Expressway. Media between the Lync client and the B2BUA flows either through the Microsoft Edge server or through the VCS Expressway TURN server ICE searching is used to determine the best path. Media between the external video endpoint and the B2BUA flows through the VCS Control / VCS Expressway traversal link. Calls made in the opposite direction, external video endpoint to external Lync client use the same signaling and media paths. Licensing 1 traversal call license and up to 18 TURN licenses on the VCS Expressway 1 traversal call license on the VCS Control 1 non-traversal call license on the Lync gateway VCS Signaling Media Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 72 of 82

73 Appendix 5: Media paths and license usage for calls through B2BUA An external Lync client calls an internal SIP video endpoint In this scenario an external Lync client (alice.parkes) calls an internal video system (david.jones.office). Signaling flows through the Microsoft Edge Server, Lync, B2BUA, and VCS Control. Media between the Lync client and the B2BUA flows either through the Microsoft Edge server or through the VCS Expressway TURN server ICE searching is used to determine the best path. Media is connected directly between the internal video endpoint and the B2BUA (as the call is SIP to SIP). Calls made in the opposite direction, internal video endpoint to external Lync client will use the same signaling and media paths. Licensing 1 non-traversal call license on the VCS Control, as it is a SIP endpoint (an H.323.endpoint would use 1 traversal call license on the VCS Control) 1 non-traversal call license on the Lync gateway VCS Signaling Media Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 73 of 82

74 Appendix 6: Additional information Appendix 6: Additional information B2BUA registration on Lync gateway VCSs The B2BUA FindMe registration function allows personal video endpoints to appear in a similar manner to an endpoint registered directly to Lync Server with the same credentials as an existing Lync user, but still maintain the benefits of having the endpoint register to the VCS which is designed to support video calling. The B2BUA registration function also means that the user credentials are no longer needed on each individual video endpoint. This is possible because the VCS B2BUA is configured as a trusted host to Lync Server. This simplifies the long term endpoint management since passwords do not need to be regularly updated on the video endpoints. What does Register FindMe users as clients on Lync do? When enabled, FindMe users that are in the shared domain with Lync are registered to Lync Server so that they appear like Lync clients. This means that if a Lync client registers to Lync Server, and a FindMe user is registered as that same user to Lync Server, when the user is called by another Lync client, the call will be forked to both the registered Lync client and also to the VCS s FindMe. This means that Lync clients and all video endpoints configured as primary devices in the FindMe will ring when called at the Lync client address. Without registering the shared domain FindMe user, Lync Server will not fork the call to VCS, but: if a Lync client is registered with the called address then just that Lync client will ring. if there is no Lync client registered but there is a static domain route to the VCS for that domain the call will be routed to VCS to handle. if there is no Lync client registered and there is no static domain route for this call then the call will just fail. Lync Server only allows FindMe users to register if the FindMe ID being registered is a valid user in the Lync Active Directory (in the same way that Lync clients can only register if they have a valid account enabled in the Lync AD). Registering FindMe users also allows the presence of these users to be provided to Lync Server and for incall as well as available and off-line status to be provided. Endpoint devices and FindMe entries that are not registered to Lync Server can only communicate available and off-line status to Lync Server. The Lync gateway VCS (or VCSs) must host the presence server for the domain shared with Lync (ciscotp.com) in order for presence to be provided to Lync Server. The Lync gateway VCS must also host the presence server for the domain of the video network (vc.ciscotp.com). This is because presence of a FindMe entry can only be provided if the presence status of the device(s) in the active location of the FindMe entry are hosted on the Lync gateway VCS. If FindMe entries contain multiple devices in the active location, VCS will aggregate the presence of those devices whose presence is hosted on the Lync gateway VCS 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 whichever video endpoint makes the call, the receiving Lync client and video endpoints will see the call as having come from the FindMe ID. This is especially useful when the called party wants to return the call; the return call calls the FindMe ID resulting in all endpoints relating to this FindMe and any Lync clients registered with this ID all ringing simultaneously rather than the return call being addressed directly to the single endpoint that made the call. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 74 of 82

75 Appendix 6: Additional information Configuring domains It is best practice to keep the video endpoints in their own domain, and just have the FindMe users on the Lync gateway VCS with the same domain as Lync Server. This avoids any confusion as to what functionality will be received for each entity. When a call arrives for the FindMe user, FindMe will forward calls appropriately to the defined endpoints, whichever domain they are in. For example, when alice.parkes@ciscotp.com is called, the call will fork to the Lync client with the same name, and also to alice.parkes.office@vc.ciscotp.com and alice.parkes.external@ciscotp.com (assuming that these two devices are listed as primary devices in Alice Parkes FindMe.) We strongly recommend that the user is created on the Lync Server first and signed in to at least once from a Lync client. 5 to 10 minutes later the FindMe account can be created on the Lync gateway VCS when the user is fully available on Lync Server. B2BUA and Cisco AM GW integration For full instructions about how to configure the Microsoft Lync B2BUA with a Cisco TelePresence Advanced Media Gateway (Cisco AM GW), see Microsoft Lync 2010, VCS and Cisco AM GW Deployment Guide. Previous versions of that document are also available for earlier, non-b2bua VCS and Cisco AM GW deployments. TEL URI handling for VCS to Lync calls If an endpoint wants to dial a telephone number rather than selecting a user from a directory, the VCS Control must format the telephone number appropriately for Lync to be able to look it up. Lync expects to see telephone numbers (known as TEL: URIs) in the form: +<country code><full dialed number> VCS Control can use transforms to appropriately format the telephone numbers. These transforms can either be implemented globally using Configuration > Dial plan > Transforms or just for the Lync neighbor zone or B2BUA neighbor zone by configuring the transform in the appropriate search rules. For example, for 4 digit extension number dialing to be expanded to a full telephone number for a company in the UK whose telephone number is 781xxx, an extension number 1008 would need to be expanded to This can be implemented by configuring a transform as follows: Priority 80 (match in preference to the no transform needed rule - 80 is higher priority than 100) Source Mode Pattern type Pattern string Patter behavior Replace string On successful match Target Zone Any Alias pattern match Regex (1 )@ciscotp\.com(.*) Replace \1;@ciscotp.com;user=phone\2 Continue To Microsoft Lync Server via B2BUA Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 75 of 82

76 Appendix 7: Microsoft Certification Authority Appendix 7: Microsoft Certification Authority Configuring Windows Server Manager with a "client and server" certificate template The default "Web Server" certificate template used by the Microsoft Certification Authority application will only create a certificate for Server Authentication. The server certificate for the VCS also needs Client Authentication if you want to configure a neighbor or traversal zone with mutual authentication (where TLS verify mode is enabled). To set up a certificate template with Server and Client Authentication: 1. In Windows, launch Server Manager (Start > Administrative Tools > Server Manager). (Server Manager is a feature included with server editions of Windows.) 2. Expand the Server Manager navigation tree to Roles > Active Directory Certificate Services > Certificate Templates (<domain>). 3. Right-click on Web Server and select Duplicate Template. 4. Select Windows Server 2003 Enterprise and click OK. 5. On the General tab, enter the Template display name and Template name, for example Web client and server and Webclientandserver. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 76 of 82

77 Appendix 7: Microsoft Certification Authority 6. On the Extensions tab, select Application Policies and click Edit. 7. Add Client Authentication to the set of application policies: a. Click Add. b. Select Client Authentication and click OK. c. Click OK. 8. Click OK to complete the addition of the new template. 9. Add the new template to the Certificate Authority: a. Go to Roles > Active Directory Certificate Services > <your certificate authority>. b. Right-click on Certificate Templates and select New > Certificate Template to Issue. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 77 of 82

78 Appendix 7: Microsoft Certification Authority c. Select your new Web client and server template and click OK. The new Web client and server template can now be used when submitting a certificate request to that Microsoft Certification Authority. Authorizing a request and generating a certificate using Microsoft Certification Authority This section describes how to authorize a certificate request and generate a PEM certificate file using Microsoft Certification Authority. The Microsoft Certification Authority application may be installed on the Lync Server, or another server in the network. 1. Copy the certificate request file (for example, certcsr.der if generated via OpenSSL) to a location, such as the desktop, on the server where the Microsoft Certification Authority application is installed. 2. Submit the certificate request from a command prompt: To generate a certificate with Server Authentication and Client Authentication, which is required if you want to configure a neighbor or traversal zone with mutual authentication (TLS verify mode), type: certreq -submit -attrib CertificateTemplate:Webclientandserver C:\Users\<user>\Desktop\certcsr.der Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 78 of 82

79 Appendix 7: Microsoft Certification Authority See section Configuring Windows Server Manager with a "client and server" certificate template [p.76] above for details about how to set up the Webclientandserver certificate template. To generate a certificate with Server Authentication only, type: certreq -submit -attrib CertificateTemplate:WebServer C:\Users\<user>\Desktop\certcsr.der This triggers the Certification Authority window to open: Note that the command must be run as the administrator user. 3. Select the Certification Authority to use (typically only one is offered) and click OK. 4. When requested, save the certificate (browse to the required folder if the default Libraries > Documents folder is not to be used) calling it server.cer for example. 5. Rename server.cer to server.pem for use with the VCS. Get the Microsoft CA certificate 1. In your web browser, go to <IP or URL of the Microsoft Certificate Server>/certsrv and log in. 2. Select Download a CA certificate, certificate chain or CRL. 3. Select Base Select Download CA certificate. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 79 of 82

80 Appendix 7: Microsoft Certification Authority 5. Choose Save File and click OK. 6. Rename certnew.cer to certnew.pem. Files server.pem and certnew.pem are now available for uploading to VCS. Microsoft Lync and Cisco VCS Deployment Guide (X8.1) Page 80 of 82

Cisco VCS and Microsoft Lync

Cisco VCS and Microsoft Lync Cisco VCS and Microsoft Lync Deployment Guide First Published: October 2008 Last Updated: February 2016 Cisco VCS X8.7 Microsoft Lync 2010, Lync 2013 Cisco Systems, Inc. www.cisco.com Preface Preface Change

More information

Cisco VCS and Microsoft Infrastructure

Cisco VCS and Microsoft Infrastructure Cisco VCS and Microsoft Infrastructure Deployment Guide First Published: October 2008 Last Updated: July 2016 Cisco VCS X8.8 Microsoft Lync 2010, Lync 2013 Skype for Business Server 2015 Cisco Systems,

More information

Cisco VCS and Microsoft Infrastructure

Cisco VCS and Microsoft Infrastructure Cisco VCS and Microsoft Infrastructure Deployment Guide First Published: October 2008 Last Updated: July 2018 Cisco VCS X8.11 Microsoft Lync 2010, Lync 2013 Skype for Business Server 2015 Cisco Systems,

More information

Cisco TelePresence Multiway

Cisco TelePresence Multiway Cisco TelePresence Multiway Deployment Guide Cisco VCS X8.2 or later MCU version 4.4 or later Conductor XC2.3 or later D14366.12 Revised July 2014 Contents Introduction 4 Objectives and intended audience

More information

Cisco TelePresence Device Authentication on Cisco VCS

Cisco TelePresence Device Authentication on Cisco VCS Cisco TelePresence Device Authentication on Cisco VCS Deployment Guide Cisco VCS X8.5 December 2014 Contents About device authentication 4 Authentication policy 6 Configuring VCS authentication policy

More information

Microsoft OCS 2007, Lync 2010, Cisco VCS and Cisco AM GW

Microsoft OCS 2007, Lync 2010, Cisco VCS and Cisco AM GW Microsoft OCS 2007, Lync 2010, Cisco VCS and Cisco AM GW Deployment Guide Cisco VCS X7.0 Microsoft OCS 2007 R2, Lync 2010 Cisco AM GW 1.0, 1.1 D14652.04 October 2011 Contents Contents Document revision

More information

Cisco VCS Authenticating Devices

Cisco VCS Authenticating Devices Cisco VCS Authenticating Devices Deployment Guide First Published: May 2011 Last Updated: November 2015 Cisco VCS X8.7 Cisco Systems, Inc. www.cisco.com 2 About Device Authentication Device authentication

More information

Cisco TelePresence VCS Cluster Creation and Maintenance

Cisco TelePresence VCS Cluster Creation and Maintenance Cisco TelePresence VCS Cluster Creation and Maintenance Deployment Guide Cisco VCS X8.5 Cisco TMS 13.2 or later December 2014 Contents Introduction 4 Prerequisites 5 Upgrading an X7.1 or later cluster

More information

Cisco TelePresence Conductor with Cisco Unified Communications Manager

Cisco TelePresence Conductor with Cisco Unified Communications Manager Cisco TelePresence Conductor with Cisco Unified Communications Manager Deployment Guide XC2.2 Unified CM 8.6.2 and 9.x D14998.09 Revised March 2014 Contents Introduction 4 About this document 4 Further

More information

Cisco TelePresence Conductor with Cisco VCS (Policy Service)

Cisco TelePresence Conductor with Cisco VCS (Policy Service) Cisco TelePresence Conductor with Cisco VCS (Policy Service) Deployment Guide TelePresence Conductor XC3.0 Cisco VCS X8.x Revised January 2015 Contents Introduction 5 About the Cisco TelePresence Conductor

More information

Cisco Expressway with Microsoft Infrastructure

Cisco Expressway with Microsoft Infrastructure Cisco Expressway with Microsoft Infrastructure Deployment Guide First Published: December 2013 Last Updated: July 2017 Cisco Expressway X8.9 Microsoft Lync Server 2010 or 2013 Skype for Business Server

More information

Cisco TelePresence Conductor with Cisco Unified Communications Manager

Cisco TelePresence Conductor with Cisco Unified Communications Manager Cisco TelePresence Conductor with Cisco Unified Communications Manager Deployment Guide TelePresence Conductor XC4.0 Unified CM 10.5(2) January 2016 Contents Introduction 6 About this document 6 Related

More information

Cisco TelePresence Video Communication Server Basic Configuration (Control with Expressway)

Cisco TelePresence Video Communication Server Basic Configuration (Control with Expressway) Cisco TelePresence Video Communication Server Basic Configuration (Control with Expressway) Deployment Guide Cisco VCS X8.6 July 2015 Contents Introduction 4 Example network deployment 5 Network elements

More information

Cluster creation and maintenance

Cluster creation and maintenance Cluster creation and maintenance Cisco TelePresence Deployment Guide Cisco VCS X6.1 Cisco TMS 12.6 or later D14367.08 May 2011 Contents Contents Document revision history... 5 Introduction... 6 Prerequisites...

More information

Cisco TelePresence Microsoft Lync 2010, Cisco VCS and Cisco AM GW

Cisco TelePresence Microsoft Lync 2010, Cisco VCS and Cisco AM GW Cisco TelePresence Microsoft Lync 2010, Cisco VCS and Cisco AM GW Deployment Guide Cisco VCS X8.2 Microsoft Lync 2010 Cisco AM GW 1.1 D14652.09 June 2014 Contents Introduction 4 Prerequisites to setting

More information

Cisco Expressway with Microsoft Infrastructure

Cisco Expressway with Microsoft Infrastructure Cisco Expressway with Microsoft Infrastructure Deployment Guide First Published: December 2013 Last Updated: September 2018 Cisco Expressway X8.11.1 Microsoft Lync Server 2010 or 2013 Skype for Business

More information

Cisco TelePresence Conductor with Unified CM

Cisco TelePresence Conductor with Unified CM Cisco TelePresence Conductor with Unified CM Deployment Guide TelePresence Conductor XC3.0 Unified CM 10.x Revised February 2015 Contents Introduction 5 About this document 5 Related documentation 5 About

More information

Cisco TelePresence Conductor

Cisco TelePresence Conductor Cisco TelePresence Conductor Deployment Guide XC1.2 D14827.02 May 2012 Contents Contents Introduction... 4 About the Cisco TelePresence Conductor... 4 Call flow with the Cisco TelePresence Conductor...

More information

Cisco TelePresence Video Communication Server

Cisco TelePresence Video Communication Server Cisco TelePresence Video Communication Server Administrator Guide D14049.11 August 2011 Software version: X7.0 Contents Introduction 18 About the Cisco TelePresence Video Communication Server (VCS) 19

More information

Cisco TelePresence Basic Cisco VCS configuration

Cisco TelePresence Basic Cisco VCS configuration Cisco TelePresence Basic Cisco VCS configuration Deployment Guide D14651.02 September 2011 Cisco VCS Control with Cisco VCS Expressway X7.0 Contents Document revision history 5 Introduction 6 Out of scope

More information

Cisco Expressway Session Classification

Cisco Expressway Session Classification Cisco Expressway Session Classification Deployment Guide First Published: December 2016 Last Updated: December 2017 Expressway X8.10 Cisco Systems, Inc. www.cisco.com 2 Preface Preface Change History Table

More information

Polycom RealPresence Access Director System

Polycom RealPresence Access Director System Release Notes 3.1.1 April 2014 3725-78700-001C1 Polycom RealPresence Access Director System Polycom announces the release of the Polycom RealPresence Access Director system, version 3.1.1. This document

More information

Cisco Expressway Options with Cisco Meeting Server and/or Microsoft Infrastructure

Cisco Expressway Options with Cisco Meeting Server and/or Microsoft Infrastructure Cisco Expressway Options with Cisco Meeting Server and/or Microsoft Infrastructure Deployment Guide First Published: December 2016 Last Updated: October 2017 Expressway X8.9.2 Cisco Systems, Inc. www.cisco.com

More information

Configure Call Control

Configure Call Control Call Control Overview, page 1 Cisco Expressway and TelePresence Configuration Tasks, page 2 Configuring Cisco Unified Communications Manager, page 5 Provisioning Endpoint Display Names, page 10 Call Control

More information

Cisco TelePresence Video Communication Server Basic Configuration (Single VCS Control)

Cisco TelePresence Video Communication Server Basic Configuration (Single VCS Control) Cisco TelePresence Video Communication Server Basic Configuration (Single VCS Control) Deployment Guide Cisco VCS X7.2 D14524.03 August 2012 Contents Introduction 3 Example network deployment 3 Internal

More information

Cisco VCS Expressway and VCS Control - Basic Configuration

Cisco VCS Expressway and VCS Control - Basic Configuration Cisco VCS Expressway and VCS Control - Basic Configuration Deployment Guide First Published: November 2010 Last Updated: July 2016 Cisco VCS X8.8 Cisco Systems, Inc. www.cisco.com 2 Preface Preface Change

More information

Cisco TelePresence Video Communication Server Basic Configuration (Single VCS Control)

Cisco TelePresence Video Communication Server Basic Configuration (Single VCS Control) Cisco TelePresence Video Communication Server Basic Configuration (Single VCS Control) Deployment Guide Cisco VCS X8.2 D14524.05 June 2014 Contents Introduction 3 Example network deployment 3 Network elements

More information

Pexip Infinity. Microsoft Lync / Skype for Business Deployment Guide

Pexip Infinity. Microsoft Lync / Skype for Business Deployment Guide Pexip Infinity Microsoft Lync / Skype for Business Deployment Guide Software Version 13 Document Version 13.a October 2016 Contents Introduction 5 Architecture overview 5 On-prem deployment 5 Public DMZ

More information

Cisco Single VCS Control - Basic Configuration

Cisco Single VCS Control - Basic Configuration Cisco Single VCS Control - Basic Configuration Deployment Guide First Published: September 2009 Last Updated: December 2016 Cisco VCS X8.9 Cisco Systems, Inc. www.cisco.com 2 Preface Preface Change History

More information

Cisco TelePresence Video Communication Server

Cisco TelePresence Video Communication Server Cisco TelePresence Video Communication Server Administrator Guide Software version: X7.1 D14049.12 March 2012 Contents Introduction 12 About the Cisco TelePresence Video Communication Server (VCS) 13 VCS

More information

Cisco Single VCS Control - Basic Configuration

Cisco Single VCS Control - Basic Configuration Cisco Single VCS Control - Basic Configuration Deployment Guide First Published: September 2009 Last Updated: November 2015 Cisco VCS X8.7 Cisco Systems, Inc. www.cisco.com Introduction The Cisco TelePresence

More information

Cisco TelePresence Video Communication Server Update. Arne B. Østensen, Team Lead

Cisco TelePresence Video Communication Server Update. Arne B. Østensen, Team Lead Cisco TelePresence Video Communication Server Update Arne B. Østensen, Team Lead Cisco Support Community Expert Series Webcast Today s featured expert is Team Lead Arne B. Østensen Ask him questions now

More information

Cisco TelePresence Cisco Unified Communications Manager with Cisco VCS (SIP Trunk)

Cisco TelePresence Cisco Unified Communications Manager with Cisco VCS (SIP Trunk) Cisco TelePresence Cisco Unified Communications Manager with Cisco VCS (SIP Trunk) Deployment Guide Cisco VCS X8.1 CUCM 8.6.x, 9.x January 2015 Contents Introduction 5 Deployment scenario 5 Summary of

More information

Cisco TelePresence Video Communication Server

Cisco TelePresence Video Communication Server Cisco TelePresence Video Communication Server Administrator Guide D14049.09 December 2010 Software version: X6 Contents Contents Contents 2 About the Cisco TelePresence Video Communication Server (Cisco

More information

Pexip Infinity. Microsoft Lync / Skype for Business Deployment Guide

Pexip Infinity. Microsoft Lync / Skype for Business Deployment Guide Pexip Infinity Microsoft Lync / Skype for Business Deployment Guide Software Version 14 Document Version 14.a January 2017 Contents Introduction 5 Architecture overview 5 On-prem deployment 5 Public DMZ

More information

Cisco Expressway Cluster Creation and Maintenance

Cisco Expressway Cluster Creation and Maintenance Cisco Expressway Cluster Creation and Maintenance Deployment Guide Cisco Expressway X8.6 July 2015 Contents Introduction 4 Prerequisites 5 Upgrading an X8.n cluster to X8.6 6 Prerequisites 6 Upgrade Expressway

More information

Configure Mobile and Remote Access

Configure Mobile and Remote Access Mobile and Remote Access Overview, on page 1 Mobile and Remote Access Prerequisites, on page 3 Mobile and Remote Access Configuration Task Flow, on page 4 Mobile and Remote Access Overview Cisco Unified

More information

Cisco VCS Expressway and VCS Control - Basic Configuration

Cisco VCS Expressway and VCS Control - Basic Configuration Cisco VCS Expressway and VCS Control - Basic Configuration Deployment Guide First Published: November 2010 Last Updated: January 2019 Cisco VCS X8.11.4 Cisco Systems, Inc. www.cisco.com 2 Preface Preface

More information

Pexip Infinity and Cisco VCS Deployment Guide

Pexip Infinity and Cisco VCS Deployment Guide Introduction Pexip Infinity and Cisco VCS Deployment Guide The Cisco TelePresence Video Communication Server (VCS) is a SIP/H.323 registrar and call control device. This guide describes how to integrate

More information

FindMe. Cisco TelePresence Deployment Guide Cisco VCS X6 D

FindMe. Cisco TelePresence Deployment Guide Cisco VCS X6 D FindMe Cisco TelePresence Deployment Guide Cisco VCS X6 D14525.03 February 2011 Contents Contents Document revision history... 3 Introduction... 4 Related documents... 4 Set up FindMe... 5 Create user

More information

Interdomain Federation to Microsoft Lync

Interdomain Federation to Microsoft Lync within an Enterprise, page 1 Configuration Task Flow for Microsoft Lync Federation, page 2 within an Enterprise Figure 1: Interdomain Federation to Microsoft Server within an Enterprise When the Microsoft

More information

Cisco Unified Communications Manager with Cisco VCS

Cisco Unified Communications Manager with Cisco VCS Cisco Unified Communications Manager with Cisco VCS Deployment Guide Cisco VCS X7.0 CUCM v6.1, 7.x and 8.x SIP trunk D14602.09 October 2011 Contents Contents Document revision history... 5 Introduction...

More information

Acano solution. Third Party Call Control Guide. December F

Acano solution. Third Party Call Control Guide. December F Acano solution Third Party Call Control Guide December 2015 76-1055-01-F Contents Contents 1 Introduction... 3 1.1 How to Use this Guide... 3 1.1.1 Commands... 4 2 Example of Configuring a SIP Trunk to

More information

Cisco Expressway-E and Expressway-C - Basic Configuration

Cisco Expressway-E and Expressway-C - Basic Configuration Cisco Expressway-E and Expressway-C - Basic Configuration Deployment Guide First Published: December 2013 Last Updated: March 2018 Cisco Expressway X8.9 Cisco Systems, Inc. www.cisco.com 2 Preface Preface

More information

cisco. Number: Passing Score: 800 Time Limit: 120 min.

cisco.  Number: Passing Score: 800 Time Limit: 120 min. 500-006 cisco Number: 500-006 Passing Score: 800 Time Limit: 120 min Question Set 1 QUESTION 1 How many conferencing bridges can a single full-capacity Cisco TelePresence Conductor support? A. 1 B. 10

More information

A. On the VCS, navigate to Configuration, Protocols, H.323, and set Auto Discover to off.

A. On the VCS, navigate to Configuration, Protocols, H.323, and set Auto Discover to off. Volume: 383 Questions Question No: 1 Which parameter should be set to prevent H.323 endpoints from registering to Cisco TelePresence Video Communication Server automatically? A. On the VCS, navigate to

More information

Cisco Expressway Cluster Creation and Maintenance

Cisco Expressway Cluster Creation and Maintenance Cisco Expressway Cluster Creation and Maintenance Deployment Guide First Published: December 2009 Last Updated: April 2017 Cisco Expressway X8.9.2 Cisco Systems, Inc. www.cisco.com Contents Preface 3 Change

More information

Polycom RealPresence Access Director System

Polycom RealPresence Access Director System Release Notes Polycom RealPresence Access Director System 4.0 June 2014 3725-78700-001D Polycom announces the release of the Polycom RealPresence Access Director system, version 4.0. This document provides

More information

Cisco TelePresence Video Communication Server

Cisco TelePresence Video Communication Server Data Sheet Cisco TelePresence Video Communication Server Product Overview The Cisco TelePresence Video Communication Server (Cisco VCS) is deployed in three versions: Control, Expressway, and Starter Pack

More information

Unified Communications in RealPresence Access Director System Environments

Unified Communications in RealPresence Access Director System Environments [Type the document title] 2.1.0 March 2013 3725-78704-001A Deploying Polycom Unified Communications in RealPresence Access Director System Environments Polycom Document Title 1 Trademark Information POLYCOM

More information

Unified Communications Mobile and Remote Access via Cisco VCS

Unified Communications Mobile and Remote Access via Cisco VCS Unified Communications Mobile and Remote Access via Cisco VCS Deployment Guide Cisco VCS X8.5.2 Cisco Unified CM 9.1(2)SU1 or later April 2015 Contents Mobile and remote access overview 5 Jabber client

More information

Cisco TelePresence Management Suite Provisioning Extension

Cisco TelePresence Management Suite Provisioning Extension Cisco TelePresence Management Suite Provisioning Extension Deployment Guide Cisco TMSPE 1.0 Cisco TMS 13.2 Cisco VCS X7.1, X7.2 D14941 06 October 2012 Contents Introduction 6 Cisco TMSPE versus Cisco TMS

More information

Cisco Expressway-E and Expressway-C - Basic Configuration

Cisco Expressway-E and Expressway-C - Basic Configuration Cisco Expressway-E and Expressway-C - Basic Configuration Deployment Guide First Published: December 2013 Last Updated: July 2017 Cisco Expressway X8.10 Cisco Systems, Inc. www.cisco.com 2 Preface Preface

More information

Multimedia C onnector for Skype for Business Configuration of Microsoft Skype for Business platform

Multimedia C onnector for Skype for Business Configuration of Microsoft Skype for Business platform Multimedia C onnector for Skype for Business Configuration of Microsoft Skype for Business platform 1. Executive Summary This paper describes how to configure Microsoft Skype for Business or Lync 2013

More information

Acano solution. Third Party Call Control Guide. 07 June G

Acano solution. Third Party Call Control Guide. 07 June G Acano solution Third Party Call Control Guide 07 June 2016 76-1055-01-G Contents 1 Introduction 3 1.1 How to Use this Guide 3 1.1.1 Commands 5 2 Example of Configuring a SIP Trunk to CUCM 6 2.1 Prerequisites

More information

Deploy Webex Video Mesh

Deploy Webex Video Mesh Video Mesh Deployment Task Flow, on page 1 Install Webex Video Mesh Node Software, on page 2 Log in to the Webex Video Mesh Node Console, on page 4 Set the Network Configuration of the Webex Video Mesh

More information

Pexip Infinity and Cisco VCS Deployment Guide

Pexip Infinity and Cisco VCS Deployment Guide Introduction Pexip Infinity and Cisco VCS Deployment Guide The Cisco TelePresence Video Communication Server (VCS) is a SIP/H.323 registrar and call control device. This guide describes how to integrate

More information

Interdomain Federation Guide for IM and Presence Service on Cisco Unified Communications Manager, Release 11.5(1)SU2

Interdomain Federation Guide for IM and Presence Service on Cisco Unified Communications Manager, Release 11.5(1)SU2 Interdomain Federation Guide for IM and Presence Service on Cisco Unified Communications Manager, Release 11.5(1)SU2 First Published: 2017-11-29 Last Modified: 2017-12-01 Americas Headquarters Cisco Systems,

More information

Cisco VCS SIP Trunk to Unified CM

Cisco VCS SIP Trunk to Unified CM Cisco VCS SIP Trunk to Unified CM Deployment Guide First Published: January 2010 Last Updated: July 2017 Cisco VCS X8.8 Unified CM 8.6.x, 9.x, 10.x, 11.x Cisco Systems, Inc. www.cisco.com Contents Preface

More information

Cisco Expressway with Jabber Guest

Cisco Expressway with Jabber Guest Cisco Expressway with Jabber Guest Deployment Guide First Published: Decemeber 2016 Cisco Expressway X8.9 Cisco Jabber Guest Server 10.6.9 (or later) Cisco Systems, Inc. www.cisco.com Contents Preface

More information

Cisco Video Communication Server Control

Cisco Video Communication Server Control Cisco Video Communication Server Control The Cisco TelePresence portfolio creates an immersive, face-to-face experience over the network empowering you to collaborate with others like never before. Through

More information

Cisco Expressway Cluster Creation and Maintenance

Cisco Expressway Cluster Creation and Maintenance Cisco Expressway Cluster Creation and Maintenance Deployment Guide First Published: December 2009 Last Updated: December 2017 Cisco Expressway X8.10 Cisco Systems, Inc. www.cisco.com Contents Preface 3

More information

"Charting the Course... Implementing Cisco Telepresence Video Solutions Part 2 (VTVS2) Course Summary

Charting the Course... Implementing Cisco Telepresence Video Solutions Part 2 (VTVS2) Course Summary Description Course Summary Implementing Cisco TelePresence Video Solutions, Part 2 (VTVS2) v1.0 is a 5-day instructor-led course that is designed to teach technicians who install and support Cisco TelePresence

More information

Skype for Business Configuration for Partitioned Intradomain Federation

Skype for Business Configuration for Partitioned Intradomain Federation Skype for Business Configuration for Partitioned Intradomain Federation Skype for Business Intradomain Federation, page 1 Skype for Business Intradomain Federation Task Flow, page 1 Skype for Business

More information

Cisco Expressway Registrar

Cisco Expressway Registrar Cisco Expressway Registrar Deployment Guide First Published: July 2016 Last Updated: August 2016 Cisco Expressway X8.8 Cisco Systems, Inc. www.cisco.com 2 Preface Preface Change History Table 1 Deployment

More information

Unified Communications Mobile and Remote Access via Cisco Expressway

Unified Communications Mobile and Remote Access via Cisco Expressway Unified Communications Mobile and Remote Access via Cisco Expressway Deployment Guide Cisco Expressway X8.1.1 or later Cisco Unified CM 9.1(2)SU1 or later D15068.01 April 2014 Contents Mobile and remote

More information

Cisco Expressway-E and Expressway-C - Basic Configuration

Cisco Expressway-E and Expressway-C - Basic Configuration Cisco Expressway-E and Expressway-C - Basic Configuration Deployment Guide First Published: December 2013 Last Updated: July 2018 Cisco Expressway X8.11 Cisco Systems, Inc. www.cisco.com 2 Preface Preface

More information

Cisco Expressway-E and Expressway-C - Basic Configuration

Cisco Expressway-E and Expressway-C - Basic Configuration Cisco Expressway-E and Expressway-C - Basic Configuration Deployment Guide First Published: December 2013 Last Updated: January 2019 Cisco Expressway X8.11.4 Cisco Systems, Inc. www.cisco.com 2 Preface

More information

Unified Communications Mobile and Remote Access via Cisco Expressway

Unified Communications Mobile and Remote Access via Cisco Expressway Unified Communications Mobile and Remote Access via Cisco Expressway Deployment Guide Cisco Expressway X8.5.3 Cisco Unified CM 9.1(2)SU1 or later June 2015 Contents Mobile and remote access overview 5

More information

Cisco VCS Expressway Starter Pack

Cisco VCS Expressway Starter Pack Cisco VCS Expressway Starter Pack Cisco TelePresence Deployment Guide Cisco VCS X5.1 D14618.02 November 2010 Contents Contents Introduction...4 Purpose of this guide... 4 Related documents... 5 Configuring

More information

Cisco TelePresence Video Communication Server X7.0.1

Cisco TelePresence Video Communication Server X7.0.1 Cisco TelePresence Video Communication Server X7.0.1 Software release notes D14851.04 November 2011 Contents Contents Document revision history... 4 Introduction... 5 Deployments with FindMe and MCUs...

More information

Cisco TelePresence Video Sales Engineer.

Cisco TelePresence Video Sales Engineer. Cisco 650-296 TelePresence Video Sales Engineer http://killexams.com/exam-detail/650-296 QUESTION: 31 Which is the primary function of the Cisco MSE 8321 ISDN GW blade? A. To provide up to 60 1080p high-definition

More information

Presence Service Configuration

Presence Service Configuration Presence Service Configuration 28 Mar 2019 TM and copyright 2010-2019 Imagicle spa Table of Contents Presence Service Configuration...1/13 Imagicle Presence Service Configuration...1/13 Configuration for

More information

Configure Centralized Deployment

Configure Centralized Deployment Centralized Deployment Overview, on page 1 Centralized Deployment Prerequisites, on page 4 Centralized Deployment Configuration Task Flow, on page 6 Centralized Deployment Field Descriptions, on page 16

More information

Cisco Implementing Cisco IP Telephony and Video, Part 2 (CIPTV2)

Cisco Implementing Cisco IP Telephony and Video, Part 2 (CIPTV2) Cisco 300-075 Implementing Cisco IP Telephony and Video, Part 2 (CIPTV2) https://killexams.com/pass4sure/exam-detail/300-075 QUESTION: 90 An engineer is configuring a new DX-80 in Cisco Unified Communications

More information

Test-king. Number: Passing Score: 800 Time Limit: 120 min File Version:

Test-king.  Number: Passing Score: 800 Time Limit: 120 min File Version: 300-075 Test-king Number: 300-075 Passing Score: 800 Time Limit: 120 min File Version: 14.1 http://www.gratisexam.com/ 300-075 Implementing Cisco IP Telephony & Video, Part 2 v1.0 Version 14.1 Exam A QUESTION

More information

Partitioned Intradomain Federation for IM and Presence Service on Cisco Unified Communications Manager, Release 11.5(1)SU2

Partitioned Intradomain Federation for IM and Presence Service on Cisco Unified Communications Manager, Release 11.5(1)SU2 Partitioned Intradomain Federation for IM and Presence Service on Cisco Unified Communications Manager, First Published: 2017-01-10 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose,

More information

CCNP COLLABORATION. Cisco Certified Network Professional Collaboration

CCNP COLLABORATION. Cisco Certified Network Professional Collaboration Cisco Certified Network Professional Collaboration O V E R VIE W For collaboration and unified communications network engineers who want develop advanced collaboration skills designing, deploying, configuring,

More information

examcollection.premium.exam.161q

examcollection.premium.exam.161q 300-075.examcollection.premium.exam.161q Number: 300-075 Passing Score: 800 Time Limit: 120 min File Version: 6.0 300-075 Implementing Cisco IP Telephony & Video, Part 2 v1.0 Version 6.0 Exam A QUESTION

More information

Cisco TelePresence Integration Guide Documentation for integrating Cisco CTS/TX TelePresence Systems with BlueJeans

Cisco TelePresence Integration Guide Documentation for integrating Cisco CTS/TX TelePresence Systems with BlueJeans Cisco TelePresence Integration Guide Documentation for integrating Cisco CTS/TX TelePresence Systems with BlueJeans Last Updated: April 2018 5 1 6 C l y d e A v e n u e M o u n t a i n V i e w, C A 9 4

More information

Integrate Microsoft Office Communicator and Microsoft Lync Clients for Cisco UC

Integrate Microsoft Office Communicator and Microsoft Lync Clients for Cisco UC Integrate Microsoft Office Communicator and Microsoft Lync Clients for Cisco UC Overview, page 1 Limitations and considerations, page 2 Cisco UC Integration for Microsoft Office Communicator client design

More information

Pexip Infinity. Microsoft Lync / Skype for Business Deployment Guide

Pexip Infinity. Microsoft Lync / Skype for Business Deployment Guide Pexip Infinity Microsoft Lync / Skype for Business Deployment Guide Software Version 16 Document Version 16.a August 2017 Contents Introduction 5 Architecture overview 5 On-premises deployment 5 Public

More information

ITBraindumps. Latest IT Braindumps study guide

ITBraindumps.   Latest IT Braindumps study guide ITBraindumps http://www.itbraindumps.com Latest IT Braindumps study guide Exam : 300-075 Title : Implementing Cisco IP Telephony & Video, Part 2 v1.0 Vendor : Cisco Version : DEMO Get Latest & Valid 300-075

More information

Nortel Converged Office Fundamentals Microsoft Office Communications Server 2007

Nortel Converged Office Fundamentals Microsoft Office Communications Server 2007 Nortel Converged Office Fundamentals Microsoft Office Communications Server 2007 NN43001-121 Document status: Standard Document version: 0103 Document date: 30 April 2008 All Rights Reserved LEGAL NOTICE

More information

Implementing Jabber with VCS-Expressway and MRA

Implementing Jabber with VCS-Expressway and MRA 6210 Central Ave, Portage, IN. 46368 Phone: 219.764.3800 Fax: 219.764.3805 Web: http://www.ctclc.com Implementing Jabber with VCS-Expressway and MRA This is a three day instructor-led course that focuses

More information

Cisco TelePresence Video Communication Server

Cisco TelePresence Video Communication Server Data Sheet Cisco TelePresence Video Communication Server Cisco TelePresence Video Communication Server: Advanced Applications and Session Management Product Overview Figure 1. Cisco TelePresence Video

More information

Acano solution. Acano Server & VM Release R1.8 H.323 Gateway Deployment Guide. September B

Acano solution. Acano Server & VM Release R1.8 H.323 Gateway Deployment Guide. September B Acano solution Acano Server & VM Release R1.8 H.323 Gateway Deployment Guide September 2015 76-1056-02-B Contents Contents 1 Introduction... 3 1.1 How to Use this Guide... 3 1.1.1 Commands... 4 2 H323

More information

Authenticating Devices

Authenticating Devices Authenticating Devices Cisco TelePresence Deployment Guide Cisco VCS X6.1 D14819.01 May 2011 Contents Contents Document revision history... 4 Introduction... 5 Local database... 6 Configuration... 6 H.350

More information

Cisco Meeting Server. Cisco Meeting Server Release 2.3. with Cisco Unified Communications Manager Deployment Guide

Cisco Meeting Server. Cisco Meeting Server Release 2.3. with Cisco Unified Communications Manager Deployment Guide Cisco Meeting Server Cisco Meeting Server Release 2.3 with Cisco Unified Communications Manager Deployment Guide May 11, 2018 Cisco Systems, Inc. www.cisco.com Contents Change History 4 1 Introduction

More information

Cisco Expressway Registrar

Cisco Expressway Registrar Cisco Expressway Registrar Deployment Guide First Published: July 2016 Last Updated: September 2018 Cisco Expressway X8.11 Cisco Systems, Inc. www.cisco.com 2 Preface Preface Change History Table 1 Deployment

More information

Integrate Microsoft Office Communicator Client and Microsoft Lync Client for Cisco UC

Integrate Microsoft Office Communicator Client and Microsoft Lync Client for Cisco UC Integrate Microsoft Office Communicator Client and Microsoft Lync Client for Cisco UC Overview, page 1 Limitations and considerations, page 2 Microsoft Office Communicator, page 3 Microsoft Lync, page

More information

CCNP Voice (CCVP) Syllabus/Module Details CVOICE Cisco Voice over IP and QoS v8.0 (CVOICE v8.0)

CCNP Voice (CCVP) Syllabus/Module Details CVOICE Cisco Voice over IP and QoS v8.0 (CVOICE v8.0) CCNP Voice (CCVP) Syllabus/Module Details 642-437 CVOICE Cisco Voice over IP and QoS v8.0 (CVOICE v8.0) 642-447 CIPT1 Implementing Cisco Unified Communications Manager, Part 1 v8.0 (CIPT1 v8.0) 642-457

More information

Mobile and Remote Access Through Cisco Video Communication Server

Mobile and Remote Access Through Cisco Video Communication Server Mobile and Remote Access Through Cisco Video Communication Server Deployment Guide First Published: April 2014 Last Updated: June 2017 Cisco VCS X8.8.n Cisco Unified Communications Manager 9.1(2)SU4 or

More information

Mobile and Remote Access Through Cisco Expressway

Mobile and Remote Access Through Cisco Expressway Mobile and Remote Access Through Cisco Expressway Deployment Guide First Published: April 2014 Last Updated: April 2016 Cisco Expressway X8.7 Cisco Unified CM 9.1(2)SU1 or later Cisco Systems, Inc. www.cisco.com

More information

One-Voice Resiliency. Branch Voice Resilience for Microsoft Skype for Business or Lync Server Environments and Skype for Business Online. Version 7.

One-Voice Resiliency. Branch Voice Resilience for Microsoft Skype for Business or Lync Server Environments and Skype for Business Online. Version 7. Configuration Note AudioCodes One Voice for Skype For Business One-Voice Resiliency Branch Voice Resilience for Microsoft Skype for Business or Lync Server Environments and Skype for Business Online Version

More information

Polycom RealPresence Access Director System

Polycom RealPresence Access Director System RELEASE NOTES Version 4.1 April 2015 3725-78700-001E1 Polycom RealPresence Access Director System Polycom, Inc. 1 Polycom RealPresence Access Director System Release Notes Version 4.1 Contents What s New

More information

Microsoft Selftestengine Exam Questions & Answers

Microsoft Selftestengine Exam Questions & Answers Microsoft Selftestengine 70-337 Exam Questions & Answers Number: 70-337 Passing Score: 800 Time Limit: 120 min File Version: 32.4 http://www.gratisexam.com/ Microsoft 70-337 Exam Questions & Answers Exam

More information

One-Voice Resiliency with SIP Trunking

One-Voice Resiliency with SIP Trunking Configuration Note AudioCodes One Voice for Skype For Business One-Voice Resiliency with SIP Trunking For Branch Sites in Microsoft Lync Server or Skype for Business Environments Version 7.2 Configuration

More information

Mobile and Remote Access Through Cisco Expressway

Mobile and Remote Access Through Cisco Expressway Mobile and Remote Access Through Cisco Expressway Deployment Guide First Published: April 2014 Last Updated: November 2017 Cisco Expressway X8.8.n Cisco Unified Communications Manager 9.1(2)SU4 or later

More information

Spectralink IP-DECT Server 400 and 6500 and Microsoft Lync Server Configuration Guide

Spectralink IP-DECT Server 400 and 6500 and Microsoft Lync Server Configuration Guide Spectralink IP-DECT Server 400 and 6500 Spectralink IP-DECT Server 400 and 6500 and Microsoft Lync Server Configuration Guide Using a Spectralink IP-DECT Server 400 or Spectralink IP-DECT Server 6500 in

More information