cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2348
Views
0
Helpful
7
Replies

CUCI Lync deskphone control don't work

                 Hello!

I try configure CUCI Lync (Installation Guide for Cisco UC Integration for Microsoft Lync Release 8.5), but

deskphone control don't work, CUCI don't see deskphone which is assosiated to user.

7 Replies 7

Chris Deren
Hall of Fame
Hall of Fame

What type of phone is it?

Is the user assigned to Allow Control of Device from CTI group?

If it is 69XX/89XX/99XX model is the user assigned to Standard CTI Allow Control of Phones supporting Connected Xfer and conf group and  Standard CTI Allow Control of Phones supporting Rollover Mode group?

Chris

I try use 6941 and Cisco IP Communicator.

User is assigned to following group:

Allow Control of Device from CTI group

Allow Control of Phones supporting Connected Xfer and conf group

Allow Control of Phones supporting Rollover Mode group

But CUCI see only CUCSF device (softphone).

Hi

Have you associated the 6941 handset to the user?

Where do you see the CUCSF device?

Is the central 'softphone/deskphone' toggle button active in the GUI?

Aaron

Aaron Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!

Hi Aaron!

Yes 6941 (SCCP protocol) is associated to the user.

I see CUCSF device in configuration window of CUCI.

Central 'softphone/deskphone' button is active, but when i try to switch to deskphone i see error.

Have you applied registry settings or group policy settings to configure CTI on the PC?

Aaron

Aaron Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!

Yes, i have applied following settings on the PC:

T f t p S e r v e r 1 = 10.3.10.21

T f t p S e r v e r 2 = 10.3.10.22

C t i S e r v e r 1 = 10.3.10.21

C t i S e r v e r 2 = 10.3.10.22

C c m c i p S e r v e r 1 = 10.3.10.21

C c m c i p S e r v e r 2 = 10.3.10.22

C c m c i p S e r v e r V a l i d a t i o n = 0

P.S.

10.3.10.21 - PUB

10.3.10.22 - SUB

I've found what is problem:

This problem is normally associated with using

port 389 for your LDAP authentication in CUCM.  To check this go to

System->Server->LDAP->LDAP Authentication.  This port would need to be

changed to 3268 and CTI Manager restarted on all nodes for this change

to go into effect.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: