The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This section provides information on planning for a deployment.
Note |
Microsoft Lync 2013 64 bit is not supported. |
Directory integration with OpenLDAP requires you to define specific parameters in a Cisco UC Integration for Microsoft Lync configuration file. See LDAP Directory Servers for more information.
Cisco UC Integration for Microsoft Lync requires Microsoft Internet Explorer 7.0, 8.0, or 9.0. The application uses the Microsoft Internet Explorer rendering engine to display HTML content.
Note |
Microsoft Lync 2013 is installed with Microsoft Office 2013 but Click to Call is not supported. |
Cisco UC Integration for Microsoft Lync sends Internet Control Message Protocol (ICMP) requests to the TFTP server. These requests enable the client to determine if it can connect to Cisco Unified Communications Manager. You must configure firewall settings to allow ICMP requests from the client. If your firewall does not allow ICMP requests, the application cannot establish a connection to Cisco Unified Communications Manager.
Cisco UC Integration for Microsoft Lync uses the ports and protocols listed in the following table. If you plan to deploy a firewall between the application and a server, configure the firewall to allow these ports and protocols.
Port | Protocol | Description |
---|---|---|
Inbound | ||
16384 to 32766 | UDP | Receives Real-Time Transport Protocol (RTP) media streams for audio and video. You set these ports in Cisco Unified Communications Manager. |
Outbound | ||
69 | UDP | Trivial File Transfer Protocol (TFTP) service |
6970 | HTTP | TFTP service to download client configuration |
443 | TCP (HTTPS) |
Cisco Unity Connection for voicemail |
7080 | TCP (HTTPS) |
Cisco Unity Connection for notifications of voice messages |
389 | UDP / TCP | LDAP directory server |
636 | LDAPS | LDAP directory server (secure) |
3268 | TCP | Global Catalog server |
3269 | LDAPS | Global Catalog server (secure) |
2748 | TCP | CTI gateway |
5060 | UDP / TCP | Session Initiation Protocol (SIP) call signaling |
5061 | TCP | Secure SIP call signaling |
8443 | HTTPS | Web access to Cisco Unified Communications Manager and includes connections for the following: |
16384 to 32766 | UDP | RTP media streams for audio and video |
53 | UDP / TCP | Domain Name System (DNS) traffic |
3804 | TCP | Locally Significant Certificates (LSC) for IP phones This is the listening port for Cisco Unified Communications Manager Certificate Authority Proxy Function (CAPF) enrollment. |
Cisco UC Integration for Microsoft Lync supports the same CTI devices as Cisco Unified Communications Manager version 8.6(1). See the CTI supported device matrix table in the CTI Supported Devices topic at the following URL:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/tapi_dev/8_6_1/supporteddevices.html
Plantronics Blackwire C420 | Plantronics Voyager Pro UC B230 |
Plantronics Blackwire C610 | Plantronics Voyager Pro UC BT300 |
Plantronics Blackwire C620 | Jabra BIZ 2400 |
Plantronics C220UC | Jabra BIZ 620 |
Plantronics C420 | Jabra Go 6470 |
Plantronics Calisto P420 | Jabra PRO 930 |
Plantronics Calisto P800 series headset | Jabra Speak 410 |
Plantronics DSP400 | Jabra-8120 |
Plantronics W740 | Jabra GN2000 |
Plantronics WO200/A | Jabra PRO 9470 |
Plantronics WO300 | Polycom CX100 Speakerphone |
Plantronics Voyager Pro UC WG200/B | - |
Plantronics Blackwire C310 | Plantronics Voyager 510SL |
Plantronics Blackwire C320 | Plantronics Voyager Pro UC B230 |
Plantronics Blackwire C420 | Plantronics DSP 400 |
Plantronics Blackwire C435 | Plantronics Savi 740 |
Plantronics Blackwire C610 | Plantronics Savi 440 |
Plantronics Blackwire C620 | Jabra GN2000 CIPC Mono |
Plantronics Blackwire C710 | Jabra GN2000 CIPC Duo |
Plantronics Blackwire C720 | Jabra Go 6470 |
Plantronics Calisto P240 series | Jabra Pro 930 |
Plantronics Calisto P420 | Jabra Speak 410 |
Plantronics Calisto P610 series | Jabra BIZ 2400 |
Plantronics Calisto P800 series | Polycom CX100 Speakerphone |
Plantronics Voyager Pro UC WG200/B | - |
Microsoft LifeCam 6000 | Tandberg Precision HD devices |
Logitech Pro 9000 | Cisco VTIII, resolution up to VGA |
Logitech C920 | - |
Cisco AnyConnect refers to a server-client infrastructure that enables the application to connect securely to your corporate network from remote locations such as Wi-Fi or mobile data networks.
Provides a service to secure remote access.
Establishes an secure connection to Cisco Adaptive Security Appliance from the user's computer.
See the Cisco AnyConnect documentation for information and procedures on the configuration of this infrastructure. It is located here: http://www.cisco.com/en/US/products/ps10884/tsd_products_support_series_home.html.
The following data is based on testing in a lab environment. This data is intended to provide an idea of what you can expect in terms of bandwidth usage. The content in this topic is not intended to be exhaustive or to reflect all media scenarios that might affect bandwidth usage.
Codec | RTP payload in kilobits (kbits) per second | Actual bitrate (kbits per second) | Notes |
---|---|---|---|
g.722.1 | 24/32 | 54/62 | High quality compressed |
g.711 | 64 | 80 | Standard uncompressed |
g.729a | 8 | 38 | Low quality compressed |
Resolution | Pixels | Measured bit rate (kbits per second) with g.711 audio |
---|---|---|
w144p | 256 x 144 | 156 |
w288p This is the default size of the video rendering window. |
512 x 288 | 320 |
w448p | 768 x 448 | 570 |
w576p | 1024 x 576 | 890 |
720p | 1280 x 720 | 1300 |
Pixels | Estimated wire bit rate at 2 fps (kbits per second) | Estimated wire bit rate at 8 fps (kbits per second) |
---|---|---|
720 x 480 | 41 | 164 |
704 x 576 | 47 | 188 |
1024 x 768 | 80 | 320 |
1280 x 720 | 91 | 364 |
1280 x 800 | 100 | 400 |
You specify the maximum payload bit rate in Cisco Unified Communications Manager in the Region Configuration window. This maximum payload bit rate does not include packet overhead, so the actual bit rate used is higher than the maximum payload bit rate you specify.
Desktop sharing session | Audio | Interactive video (Main video) | Presentation video (Desktop sharing video) |
---|---|---|---|
No | The application uses the maximum audio bit rate | The application allocates the remaining bit rate as follows: The maximum video call bit rate minus the audio bit rate. |
- |
Yes | The application uses the maximum audio bit rate | The application allocates half of the remaining bandwidth after subtracting the audio bit rate. | The application allocates half of the remaining bandwidth after subtracting the audio bit rate. |
Upload speed | Audio | Audio + Interactive video (Main video) | Audio + Presentation video (Desktop sharing video) | Audio + Interactive video + Presentation video |
---|---|---|---|---|
125 kbps under VPN | At bandwidth threshold for g.711. Sufficient bandwidth for g.729a and g.722.1. | Insufficient bandwidth for video. | Insufficient bandwidth for video. | Insufficient bandwidth for video. |
384 kbps under VPN | Sufficient bandwidth for any audio codec. | w288p (512 x 288) at 30 fps | 1280 x 800 at 2+ fps | w144p (256 x 144) at 30 fps + 1280 x 720 at 2+ fps |
384 kbps in an enterprise network | Sufficient bandwidth for any audio codec. | w288p (512 x 288) at 30 fps | 1280 x 800 at 2+ fps | w144p (256 x 144) at 30 fps + 1280 x 800 at 2+ fps |
1000 kbps | Sufficient bandwidth for any audio codec. | w576p (1024 x 576) at 30 fps | 1280 x 800 at 8 fps | w288p (512 x 288) at 30 fps + 1280 x 800 at 8 fps |
2000 kbps | Sufficient bandwidth for any audio codec. | w720p30 (1280 x 720) at 30 fps | 1280 x 800 at 8 fps | w288p (1024 x 576) at 30 fps + 1280 x 800 at 8 fps |
Note that VPN increases the size of the payload, which increases the bandwidth consumption.
The application uses video rate adaptation to negotiate optimum video quality. Video rate adaptation dynamically increases or decreases video bit rate throughput to handle real-time variations on available IP path bandwidth.
Users should expect video calls to begin at lower resolution and scale upwards to higher resolution over a short period of time. The application saves history so that subsequent video calls should begin at the optimal resolution.
Review the different Cisco Options Package (COP) files that you might require to deploy the application.
COP File | Description | Cisco Unified Communications Manager Versions |
---|---|---|
ciscocm.installcsfdevicetype.cop.sgn | Adds the CSF device type to Cisco Unified Communications Manager. For more information, see Software Requirements. |
7.1.3 |
cmterm-bfcp-e.8-6-2.cop.sgn | Enables CSF devices to support BFCP video desktop sharing. For more information, see Apply COP File for BFCP Capabilities. |
8.6.2 only |
ciscocm.addcsfsupportfield.cop.sgn | Adds the CSF Support Field field for group configuration files. For more information, see Create Group Configurations. |
8.6.x and lower |
cmterm-cupc-dialrule-wizard-0.1.cop.sgn | Publishes application dial rules and directory lookup rules to Cisco UC Integration for Microsoft Lync. For more information, see Publish Dial Rules. |
All supported versions |
Enhanced Directory Integration (EDI) uses native Microsoft Windows APIs to retrieve contact data from Microsoft Active Directory.
Cisco UC Integration for Microsoft Lync will automatically discover the directory service and connect to a Global Catalog if it has been installed on a workstation that is registered to an Active Directory domain. This connection can be customized in the configuration file as follows:
Cisco UC Integration for Microsoft Lync can connect to a Global Catalog or Domain Controller to retrieve Active Directory attributes. Use the following information when determining how the application will receive attributes in your network.
Cisco UC Integration for Microsoft Lync connects to a Global Catalog server by default . If you use the default settings, you must ensure that all attributes reside on your Global Catalog server.
Note |
Replicating attributes to your Global Catalog server generates traffic between Active Directory servers in the domain. |
See the appropriate Microsoft documentation for instructions on replicating attributes to a Global Catalog server with the Active Directory Schema snap-in.
Note |
The application queries only a single domain if you configure it to connect to a Domain Controller. |
Specify 1 as the value of the ConnectionType parameter to configure the application to connect to a Domain Controller. See Directory Connection Parameters for more information.
Ensure you index any attributes you use for contact resolution on your directory.
UDS is an interface on Cisco Unified Communications Manager that provides contact resolution. You synchronize contact data into Cisco Unified Communications Manager from Microsoft Active Directory or another LDAP directory source. Cisco UC Integration for Microsoft Lync automatically retrieves that contact data directly from Cisco Unified Communications Manager using the UDS interface.
You must configure the application to retrieve contact photos if you integrate with UDS. For more information, see Contact Photo Retrieval.
For contact resolution with multiple Cisco Unified Communications Manager clusters, you should synchronize all users on the corporate directory to each Cisco Unified Communications Manager cluster. You should then provision a subset of those users on the appropriate Cisco Unified Communications Manager cluster.
When users in Europe call users in North America, the application retrieves the contact details for the user in Europe from cucu-cluster-na.
When users in North America call users in Europe, the application retrieves the contact details for the user in North America from cucu-cluster-eu.
Cisco UC Integration for Microsoft Lync supports the following directory services:
Evaluate your directory service to determine the characteristics of the schema before configuring Cisco UC Integration for Microsoft Lync.
Note |
The application automatically connects to the Global Catalog. The application must be configured to locate an LDAP service. |
In some instances, the value of the USERDNSDOMAIN environment variable does not resolve to the DNS domain name that corresponds to the domain name of the entire forest. For example, an instance where this configuration occurs is when an organization uses a sub-domain or resource domain. In such a configuration, the USERDNSDOMAIN environment variable resolves to a child domain, not the parent domain. The result of this type of configuration is that the application cannot access information for all users in the organization.
If the USERDNSDOMAIN environment variable resolves to a child domain, you can use one of the following configuration options to connect to a service in the parent domain:
Tip |
Cisco recommends deploying with Cisco Media Services Interface (MSI). This method effectively improves the quality of experience and reduces cost of deployment and operations. MSI also enables the client to become network aware so it can dynamically adapt to network conditions and integrate more tightly with the network. |
Cisco Media Services Interface provides a Microsoft Windows service that works with Cisco Prime Collaboration Manager and Cisco Medianet-enabled routers to ensure that Cisco UC Integration for Microsoft Lync can send audio media and video media on your network with minimum latency or packet loss.
Before Cisco UC Integration for Microsoft Lync sends audio media or video media, it checks for Cisco Media Services Interface.
Note |
Cisco UC Integration for Microsoft Lync checks for Cisco Media Services Interface for each audio call or video call. |
You must install Cisco Media Services Interface separately and ensure your network is enabled for Cisco Medianet. You must also install Cisco Prime Collaboration Manager and routers enabled for Cisco Medianet.
Set Differentiated Services Code Point (DSCP) values in RTP media packet headers to prioritize Cisco UC Integration for Microsoft Lync traffic as it traverses the network.
You define the port range that the client uses on the SIP profile in Cisco Unified Communications Manager. The client then uses this port range to send RTP traffic across the network.
To specify a port range for the client to use for RTP traffic, do the following:
As a result of splitting the port range for audio media and video media, the client creates identifiable media streams. You can then classify and prioritize those media streams by setting DSCP values in the IP packet headers.
Method for Setting DSCP Values | Microsoft Windows XP | Microsoft Windows 7 |
---|---|---|
Set DSCP values with Microsoft Group Policy | No | Yes |
Set DSCP values on network switches and routers | Yes | Yes |
Set DSCP values on Cisco Unified Communications Manager | Yes | No |
You can set DSCP values for audio media and video media on Cisco Unified Communications Manager. Cisco UC Integration for Microsoft Lync can then retrieve the DSCP values from the device configuration and apply them directly to the IP headers of RTP media packets.
The DSCP values that you set on Cisco Unified Communications Manager take effect only on Microsoft Windows XP.
For later operating systems such as Microsoft Windows 7, Microsoft implements a security feature that prevents applications from setting DSCP values on IP packet headers. For this reason, you should use an alternative method for marking DSCP values, such as Microsoft Group Policy.
If you deploy Cisco UC Integration for Microsoft Lync on Microsoft Windows XP, you must configure a registry setting to enable the client to set DSCP values for RTP media packets.
Complete the steps in the following Microsoft support article to create the DisableUserTOSSetting registry key and set the value to 0: http://support.microsoft.com/kb/248611
If you deploy Cisco UC Integration for Microsoft Lync on a later Windows operating system such as Microsoft Windows 7, you can use Microsoft Group Policy to apply DSCP values.
Complete the steps in the following Microsoft support article to create a group policy: http://technet.microsoft.com/en-us/library/cc771283%28v=ws.10%29.aspx
Attributes | Audio Policy | Video Policy | Signaling Policy |
---|---|---|---|
Application name | CUCILync.exe | CUCILync.exe | CUCILync.exe |
Protocol | UDP | UDP | TCP |
Port number or range | Corresponding port number or range from the SIP profile on Cisco Unified Communications Manager. | Corresponding port number or range from the SIP profile on Cisco Unified Communications Manager. | 5060 for SIP 5061 for secure SIP |
DSCP value | 46 | 34 | 24 |
You can configure switches and routers to mark DSCP values in the IP headers of RTP media.
You can identify signaling between the client and servers based on the various ports required for SIP, CTI QBE, and XMPP. For example, SIP signaling between Cisco UC Integration for Microsoft Lync and Cisco Unified Communications Manager occurs through port 5060.
You should mark signaling packets as AF31.