CUCIMOC 8.0.1 CTI Issue

Unanswered Question
Jul 7th, 2010
User Badges:

Hi - We are currently piloting CUCIMOC 8.0.1 with AD integrated CUCM 7.1.2 to approx 50 users, and all are working fine (as far as we know) apart from one user who cannot control his desk phone:


The CTI/QBE Server status is shown as "connecting" (with green tick) and the CUCIMOC phone button remains greyed out until we switch to soft phone mode (which works fine).  We have set this user / phone up with the identical .bat file as all other working users and and verified config against all other working users for phone, DN and end user settings.


The issue looks to follow the CUCIMOC device (tried on different PCs / Windows logons). We have also deleted and re-created all config.


The CTI error captured is shown below:


07/06/2010 15:18:02.883 CTI|AuthenticationImpl::setResults daysToExpiry= 0|<CLID::StandAloneCluster><NID::10.x.x.x><LVL::All><MASK::ffff>

07/06/2010 15:18:02.883 CTI|AuthenticationImpl::setResults WarnUser= 0|<CLID::StandAloneCluster><NID::10.x.x.1><LVL::All><MASK::ffff>
07/06/2010 15:18:02.883 CTI|kCtiProviderOpenFailure - CTI application failed to open provider. CTIconnectionId:840  Login User Id:jo.bloggs Reason code.:-1932787616 IPAddress:10.x.x.x IPV6Address: App ID:Cisco CTIManager Cluster ID:StandAloneCluster Node ID:RHBARUCM01|<CLID::StandAloneCluster><NID::10.x.x.1><CT::Alarm><LVL::All><MASK::ffff>
07/06/2010 15:18:02.894 CTI|CTIManager::CtiManager::ready_SdlCloseInd(): Connection closed indication. Shutting down provider. -- Connection Id=13 TcpHandle=[1:200:9:840] PeerIPAddr=10.x.x.x PeerPort=2146 User name=jo.bloggs CtiHandler=[1:200:16:840]|<CLID::StandAloneCluster><NID::10.x.x.1><CT::1,200,15,1.492901><IP::><DEV::><LVL::Error><MASK::0800>
07/06/2010 15:18:03.150 CTI|CTIManager::CtiManager::CleanupProviderInfo(): Provider has been closed -- Connection Id=13 TcpHandle=[1:200:9:840] PeerIPAddr=10.x.x.x PeerPort=2146 User name=jo.bloggs CtiHandler=[1:200:16:840]|<CLID::StandAloneCluster><NID::10.x.x.1><CT::1,200,15,1.492901><IP::><DEV::><LVL::Error><MASK::0800>
07/06/2010 15:20:12.572 CTI|CTIManager: ready_CtiLoginsThrottlingTimer(): login initiated for IPv4 TCP Handle=[1,200,9,841] connection Id=13|<CLID::StandAloneCluster><NID::10.x.x.1><CT::1,200,15,1.492958><IP::><DEV::><LVL::All><MASK::0800>


Could this be an AD password expiry issue?  As the AD admin has confirmed all ok with user account.


Any help is much appreciated.


Thanks

Brian

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
htluo Wed, 07/07/2010 - 16:57
User Badges:
  • Red, 2250 points or more

Could you go to CUCM > System > LDAP Authentication and see what port was being used?


If it was 389, could you change it to 3268 and restart CTIManager?


Thanks!

Michael

http://htluo.blogspot.com

btmulgrew Fri, 07/09/2010 - 01:39
User Badges:

Thanks a lot Michael - I will try this with our customer today and let you know how it goes.


The user account is in the same domain - but have read the GC may contain other properties (cross domain groups etc) which the account may be associated with.


btw - Will the CUCIMOC LDAP port in the admin .bat file / registry  need to be changed also?


thanks again

Brian

htluo Fri, 07/09/2010 - 05:34
User Badges:
  • Red, 2250 points or more

The port configured on CUCM was used by CTIManager (Desk Phone control).


The port configured in BAT fiile was used by CUCIMOC (Directory Lookup).


If you experience poor performance on directory lookup, you should change it to GC port as well.


Thanks!

Michael

Actions

This Discussion