More about Cisco UC Integration for Microsoft Lync. Free up 48.22 MB on the hard drive for setting up Cisco UC Integration for Microsoft Lync v10.6.2.939. Belonging to the Communication category, namely Instant Messaging, makes it popular among such programs. The mostly used program version running on Windows 7 is 10.6. Cisco UC Integration for Microsoft Lync Release 8.6.2 Question Hello Team, Could you please advise if CUCI-Lync integration 8.6.2 supports CUCM 9.1(2) and CUC 9.1.(2)?
Contents
The section contains information on resolving common issues with Cisco UC Integration for Microsoft Lync.
Configuration Issues
TFTP and CCMCIP Server Configuration Not Working
Problem description: The TFTP and CCMCIP server values specified in the configuration file are not used by the application.
Resolution: The TFTP and CCMCIP servers can be configured using the configuration file or through registry key settings. Ensure that the misconfigured values are not specified in a registry setting. Registry key values for the TFTP and CCMCIP servers take precedence over the configuration file on a key by key basis. See Phone Parameters for more information on this feature. Registry key values for TFTP and CCMCIP servers are only supported at this time.
Configuration File Does Not Download
Problem description:Cisco UC Integration for Microsoft Lync does not download the configuration file from the TFTP server. The configuration file is not available in the installation directory after you start Cisco UC Integration for Microsoft Lync.
Resolution:- Restart your TFTP server.
- Check the name of your configuration file. Remember:
- The name of the configuration file is case sensitive.
- The global configuration filename must be jabber-config.xml.
- Ensure your corporate firewall does not prevent Cisco UC Integration for Microsoft Lync from downloading the configuration file.
- Host the configuration file on your TFTP server as follows:
- Open the Cisco Unified OS Administration interface.
- Select Software Upgrades > TFTP File Management.
- Select Upload File.
- Select Browse in the Upload File section.
- Select the configuration file on the file system.
- Leave the value of the Directory text box empty to host the configuration file in the default directory of your TFTP server.
- Select Upload File.
Cisco UC Integration for Microsoft Lync Does Not Read the Configuration File
Problem description: You host a global or group configuration file on your TFTP server. Cisco UC Integration for Microsoft LyncMicrosoft webdrive mac torrent. downloads the configuration file and saves it in the appropriate installation directory. However, Cisco UC Integration for Microsoft Lync does not apply any settings you specify in the configuration file.
Resolution: Ensure the XML in the configuration file is valid. Cisco UC Integration for Microsoft Lync configuration files must do the following:- Use utf-8 encoding.
- Contain only valid XML character entities. For example, use & instead of &.Open your configuration file in Microsoft Internet Explorer to determine if any characters or entities are not valid. If Internet Explorer displays the entire XML structure, your configuration file does not contain invalid characters or entities. If Internet Explorer displays only part of the XML structure, your configuration file most likely contains invalid characters or entities.
- Contain a valid structure. Ensure parameters are nested under the correct elements. The following XML snippet shows the basic structure of a configuration file:
Cisco UC Integration for Microsoft Lync Uses Old Configuration Settings
Problem description:Cisco UC Integration for Microsoft Lync is not using the current configuration settings. You change settings in a configuration file and host it on your TFTP server. However, Cisco UC Integration for Microsoft Lync uses the settings from the previous version of the configuration file.
Resolution:- Restart your TFTP server.
- Open the configuration file in your browser to verify the settings. Typically, you can access the configuration file at the following URL: http://tftp_server_address:6970/jabber-config.xml
Contacts in Microsoft Outlook Do Not Display in Search
Problem description: Contacts in Microsoft Outlook do not display in search results.
Resolution: Review the following requirements to ensure users can search for and communicate with Microsoft Outlook contacts:
Cisco Uc Integration For Microsoft Lync
- To search for local contacts in Microsoft Outlook using Cisco UC Integration for Microsoft Lync, users must have profiles set in Microsoft Outlook.
- To add local contacts in Microsoft Outlook to contact lists in Cisco UC Integration for Microsoft Lync, user profiles must have email or instant message addresses.
- To communicate with local contacts in Microsoft Outlook using Cisco UC Integration for Microsoft Lync, user profiles must contain the relevant details. For example, to send instant messages to contacts in Microsoft Outlook, the user profiles must have email or instant message addresses. Likewise, to call contacts in Microsoft Outlook, the user profiles must contain phone numbers.
Directory Integration Issues
Cannot Determine If a Directory Connection is Established
Problem description: You specify directory settings in a Cisco UC Integration for Microsoft Lyncconfiguration file. However, you are not sure whether Cisco UC Integration for Microsoft Lync is successfully connected to the directory.
Resolution: Perform the following steps to determine whether Cisco UC Integration for Microsoft Lync is connected to the directory:- Start the client.
- Enter at least three characters in the search field.
If Cisco UC Integration for Microsoft Lync is not successfully connected to the directory, review the configuration settings. By default, the client uses Enhanced Directory Integration and connects to a Global Catalog server.
ADSI Error Codes
Cisco UC Integration for Microsoft Lync uses Microsoft Active Directory Service Interfaces (ADSI) for directory integration. You should refer to the ADSI error codes to help troubleshoot directory integration issues.
See the following Microsoft documentation for information about ADSI error codes:- ADSI Error Codes at http://msdn.microsoft.com/en-us/library/windows/desktop/aa772195(v=vs.85).aspx
- Generic ADSI Error Codes at http://msdn.microsoft.com/en-us/library/windows/desktop/aa705940(v=vs.85).aspx
- Error Codes for ADSI 2.5 at http://support.microsoft.com/kb/242076
Audio, Video, and Device Issues
Microsoft Lync Devices Are Not Available
Note | The section contains information on troubleshooting audio, video, and device issues related to Cisco UC Integration for Microsoft Lync. Refer to the Microsoft Lync documentation for troubleshooting issues related to Microsoft Lync. |
Devices configured in Microsoft Lync must be independently configured in Cisco UC Integration for Microsoft Lync.
Microsoft Lync For Mac Free Download
Audio and Video Communication is Not Available
Problem description: You provision audio and video devices, but Cisco UC Integration for Microsoft Lync cannot connect to the devices.
Resolution: Ensure you set up a CTI gateway and create a CCMCIP profile on Cisco Unified Communications Manager as appropriate.
Voicemail Prompt is Truncated
Problem description: The start of voicemail prompts is truncated.
The start of the audio that prompts users to leave voicemail messages can be truncated in some instances. The result of the truncation is that users do not hear the first second or two of the voicemail prompt.
Resolution
To resolve this issue, set a value for the Delay After Answer field in the Cisco Unity Connection advanced telephony integration settings. See the Cisco Unity Connection documentation at: http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/gui_reference/guide/8xcucgrg120.html#wp1056978
End Users Cannot Retrieve Phone Account Details
Problem description:Cisco UC Integration for Microsoft Lync users cannot retrieve phone account details when they log in to an extension mobility profile. As a result, error messages display in the Phone services section of the Phone accounts tab on the Options dialog box.
The affected users have multiple devices configured on Cisco Unified Communications Manager.
- Disassociate the affected users from all extension mobility profiles.
- Contact your Cisco support representative and request an Engineering Special (ES) to resolve this issue on Cisco Unified Communications Manager.
Off Hook Dialing Does Not Change Presence States
Problem description: A Cisco UC Integration for Microsoft Lync user dials a number directly from the desk phone, or other device. The availability status does not change to indicate the user is on a call.
Resolution: To resolve this issue, do the following:- Ensure the user is associated with the line number.
- Open Cisco Unified Communications Manager and browse to the Phone Configuration window for the device.
- Locate the Association Information section and select the line associated with the device. The Directory Number Configuration window opens.
- Locate the Users Associated with Line section.
- Verify that the user is associate with the line.
- Ensure the SIP trunk exists from Cisco Unified Communications Manager to Cisco Unified Presence.
- Open Cisco Unified Communications Manager.
- Select Device > Trunk.
- Search for a SIP trunk to Cisco Unified Presence.
- Create a SIP trunk if one does not exist.
Calls Drop Intermittently on Network Profile Change
Problem description: Audio and video calls drop intermittently when the network profile changes.
A known bug exists with Microsoft Windows 7 and Microsoft Windows Server 2008 R2 that causes the network profile to change unexpectedly. This change in the network profile closes network ports that Cisco UC Integration for Microsoft Lync requires for calls. As a result, if you are on a call when the network profile changes, that call automatically terminates.
Resolution: Apply the fix available from the Microsoft support site at: http://support.microsoft.com/kb/2524478/en-us
-->Summary: Configure CUCM to work with Skype for Business Server.
Caution
This capability is tested with Cisco Unified Communications Manager (CallManager, or CUCM) version 10.5 using Trunks setup over TCP only. Verify that the CUCM environment meets these criteria before proceeding.
The settings described here are meant only as examples of how CUCM can be configured to work with a VIS. Other settings and/or usages of alternate CUCM functionality could also be used to achieve the same result. No recommendation is implied as to the optimal configuration for a particular scenario.
A number of CUCM settings need to be confirmed or changed for interoperation with the VIS. Follow the procedures below in order to avoid missing required settings.
Configure the CUCM
Log in to CUCM and navigate to Cisco Unified CM Administration->Call Routing->Class of Control->Partition.
In the Partition Configuration screen, enter the partition name and description and click on Add New.
Navigate to Cisco Unified CM Administration->Call Routing->Class of Control->Calling Search Space.
In the Calling Search Space Configuration screen, enter the name for the calling search space, and in Selected Partitions, enter the name of the partition you just created. Click Save when done.
Navigate to Cisco Unified CM Administration->System->Security->SIP Trunk Security Profile.
In the SIP Trunk Security Profile Configuration screen, set the SIP Trunk Security Profile Information options as shown, and click on Add New.
Parameter Recommended setting Name SfBVideoInterop_SecurityProfile Device Security Mode Non Secure Incoming Transport Type TCP + UDP Outgoing Transport Type TCP Incoming Port 5060 Navigate to Cisco Unified CM Administration->Device->Device Settings->SIP Profile.
In the SIP Profile Configuration screen, set the SIP Profile Information options as shown.
Parameter Recommended setting Name SfBVideoInterop_SIPProfile Description SfBVideoInterop_SIPProfile On the same screen, scroll down to the SDP Profile Information section. The SDP Session-level Bandwidth Modifier for Early Offer and Re-invites option is set by default to TIAS and AS. Change this option to TIAS only. If you leave this option at its default setting, Skype for Business Server will not understand the bandwidth modifier information in the SIP message. TIAS means Transport Independent Application Specific while AS means Application Specific. These are SIP options specified in RFC3890.
On the same screen, scroll down further. Under the SIP Profile's Trunk Specific Configuration, select Early Offer Support for voice and video calls and set it to the Mandatory (insert MTP if needed) option. This will enable CUCM to set up an outgoing SIP call with Early Offer. One new feature in CUCM 8.5 and beyond is that it supports outgoing call setup with Early Offer without requiring Media Termination Point (MTP).
Verify that in the SIP Options ping section, the box is checked next to 'Enable OPTIONS Ping to monitor destination status for Trunks with Service Type 'None (Default)'.'
When you are finished, click on Add New.
Navigate to Cisco Unified CM Administration->Device->Trunk.
Set the Device Protocol to SIP and press Next.
Under Device Information, Set the Device Name and Description (probably to something like SfBVideoInterop_SIPTrunk), and set the Media Resource Group List to an MRGL that contains the right media resources.
Scroll down further. Media Termination Point (MTP) is not required for Video Calls, if it is not already unchecked, uncheck it. Check the option to Run on all active Unified CM Nodes. Please note that you should add all CUCM nodes to the Skype for Business Server configuration.
Scroll down further. Set the Inbound Calls and Connected Party Settings options as shown.
Parameter Recommended setting Calling Search Space CSS_SfBVideoInterop AAR Calling Search Space CSS_SfBVideoInterop Connected Party Transformation CSS CSS_SfBVideoInterop Scroll down further. Under the SIP Information Destination section of the SIP Trunk configuration, specify the VIS Pool's FQDN or the IP address of individual VIS servers in the pool (adding multiple entries). In the Destination Port specify the Port that VIS is listening at for connections from CUCM (the default is 6001). Also specify the SIP Trunk security profile and SIP profile you created earlier, as shown.
Parameter Recommended setting SIP Trunk Security Profile SfBVideoInterop_SecurityProfile Rerouting Calling Search Space CSS_SfBVideoInterop Out-of-Dialog Refer Calling Search Space CSS_SfBVideoInterop Subscribe Calling Search Space CSS_SfBVideoInterop SIP Profile SfBVideoInterop_SIPProfile DTMF Signaling Method RFC 2833 Scroll down further. Set the Recording Information as appropriate for your system. It's fine to leave it set to None.
When you are finished, click on Add New.
Navigate to Cisco Unified CM Administration->Call Routing->Route/Hunt->Route pattern.
In the Route Pattern Configuration screen, enter the Pattern definition parameters shown below. Scroll down to the Called Party Transformations section and set the mask as shown, and then click on Add New when finished.
Parameter Recommended setting Route Pattern 7779999 Route Partition SfBVideoInterop_RoutePartition Description Partition for SfBVideoInterop Gateway/Route List SfBVideoInterop_SIPTrunk Called Party Transform Mask +14257779999 Navigate to Cisco Unified CM Administration->Call Routing->SIP Route Pattern.
In the SIP Route Pattern Configuration screen, set the Pattern Definition options as shown, and click on Add New.
Parameter Recommended setting Pattern Usage Domain Routing IPv4 Pattern contoso.com (leave blank if using IPv6) IPv6 Pattern contoso.com (leave blank if using IPv4) Description SIPRoute Pattern to mediarv Route Partition SfBVideoInterop_RoutePartition SIP Trunk/Route List SfBVideoInterop_SIPTrunk Block Pattern checkbox leave unchecked If you have changed the audio or video bit rates from the default settings, you will need to return them to the defaults. To set the bit rate for Audio/Video calls, navigate to Cisco Unified CM Administration->System->Region Information->Region. The defaults are shown below for reference:
Parameter Recommended setting Region Default Audio Codec Preference List System Default Maximum Audio Bit Rate 64 kbps (G.722, G.711) Maximum Session Bit Rate for Video Calls 200000 kbps Maximum Session Bit Rate 2000000000 kbps
At this point the CUCM video gateway is configured to work with the VIS. Corresponding configuration will need to be done on each VTC you wish to integrate.
Note
To improve resiliency, you may want to configure this CUCM gateway to work with a second Video Interop Server or VIS pool. See Resiliency mechanisms for more information.