Buy or Renew
Buy or Renew
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
4309
Views
14
Helpful
8
Replies

CtiProviderOpenFailure (After Upgrade to 8.6.2a)

at
Level 1
Level 1

‎07-02-2012 10:32 AM - edited ‎03-16-2019 11:57 AM

Hello,

we upgraded CUCM-Cluster from 6.1.4 to 8.6.2a -

Now the users cannot chooes their Cisco-Lines in Windows dialer - Tapi Driver modified !

I looked to the CUCM-Traces and find Reason Code -1932787595 - on cisoc cco i never find information about such code ...

Anybodey an Idea what kind of problem we have ??

Here some debug output from CUCM

10:52:09.357 |ProviderOpenActivity(): activity: 3, connID: 11667, appID: , ipaddr: , loginID: platju, reason: -1932787595|*^*^*

10:52:09.357 |<--RisCTIManagerAccess::ProviderOpenActivity(...)|*^*^*

10:52:09.358 |CtiProviderOpenFailure - CTI application failed to open provider; application startup failed CTIconnectionId:11667  Login User Id:platju Reason code.:-1932787595 UNKNOWN_PARAMNAME:IPAddress:172.17.40.151 UNKNOWN_PARAMNAME:IPv6Address: App ID:Cisco CTIManager Cluster ID:StandAloneCluster Node ID:rohrpostix|Alarm^*^*

10:52:09.357 |CQBEBuilder::BuildQbeMessage(): objectID=3|*^*^*

10:52:09.357 |CTIHandler::OutputQbeMessage: TcpHand=[1:200:13:11680] QbePref={0x0xa2e193c,0x91} pQbeMsg=0x0xa2e1944 qbeMsgSize=0x91 tmpLen=0x99 msgSize_=0x99|1,200,21,1.77996^*^*

10:52:09.359 |CQBEBuilder::BuildQbeMessage(): objectID=132|*^*^*

10:52:09.359 |CTIHandler::OutputQbeMessage: TcpHand=[1:200:13:11680] QbePref={0x0xa2e193c,0x1c} pQbeMsg=0x0xa2e1944 qbeMsgSize=0x1c tmpLen=0x24 msgSize_=0x24|1,200,21,1.77996^*^*

10:52:09.359 |ready_CtiHandlerShutdownRequest. timer stopped|1,200,21,1.77996^*^*

10:52:09.359 |DBAccess::RemoveUserSubscriptionForChangeNotification|1,200,21,1.77996^*^*

10:52:09.359 |CTIUserCache::RemoveUserSubscriptionForChangeNotification|1,200,21,1.77996^*^*

10:52:09.361 |CTIManager::CtiManager::ready_SdlCloseInd(): Connection closed indication. Shutting down provider. -- Connection Id=5 TcpHandle=[1:200:13:11680] PeerIPAddr=172.17.40.151 PeerPort=57572 User name=platju CtiHandler=[1:200:22:11667]|1,200,21,1.77996^*^*

10:52:09.625 |-->RisCTIManagerAccess::ProviderOpenActivity(...)|*^*^*

10:52:09.625 |ProviderOpenActivity(): activity: 2, connID: 11667, appID: , ipaddr: 172.17.40.151, loginID: platju, reason: 4|*^*^*

10:52:09.626 |<--RisCTIManagerAccess::ProviderOpenActivity(...)|*^*^*

10:52:09.626 |CTIManager: CtiConnections::remove(): TCP Handle=[1,200,13,11680]  total CTI Connections=5|*^*^*

10:52:09.626 |CTIManager: CtiLoginsInProgress::remove(): TCP Handle=[1,200,13,11680]  total CTI Connections=2|*^*^*

10:52:09.626 |CTIManager::CtiManager::CleanupProviderInfo(): Provider has been closed -- Connection Id=5 TcpHandle=[1:200:13:11680] PeerIPAddr=172.17.40.151 PeerPort=57572 User name=platju CtiHandler=[1:200:22:11667]|1,200,21,1.77996^*^*

10:52:09.626 |CTIManager::CtiManager::CleanupProviderInfo():  Total CTI connections=5  Logins in progress=2|1,200,21,1.77996^*^*

10:52:09.725 |CMProcMon - ------Entered Router Verification|*^*^*

10:52:09.725 |CMProcMon - ----Exited Router Verification|*^*^*

10:52:11.370 |CtiManager::ready_SdlDataInd(): ConnHandle=[1:200:13:11415] TCP message length=0x20|1,200,13,11415.320^*^*

10:52:11.370 |SdiStats: #Lines: 55 Free HWM: 8 Free HWM(total): 160|*^*^*

10:52:11.370 |CQBEParser::ParseQbeMessage: PDU#=120|*^*^*

10:52:11.729 |CMProcMon - ------Entered Router Verification|*^*^*

10:52:11.729 |CMProcMon - ----Exited Router Verification|*^*^*

10:52:13.101 |CQBEBuilder::BuildQbeMessage(): objectID=179|*^*^*

10:52:13.101 |CTIHandler::OutputQbeMessage: TcpHand=[1:200:13:135] QbePref={0x0xb45a1d4,0x18} pQbeMsg=0x0xb45a1dc qbeMsgSize=0x18 tmpLen=0x20 msgSize_=0x20|1,200,21,1.435^*^*

10:52:13.101 |CQBEBuilder::BuildQbeMessage(): objectID=179|*^*^*

10:52:13.101 |CTIHandler::OutputQbeMessage: TcpHand=[1:200:13:64] QbePref={0x0xb409b54,0x18} pQbeMsg=0x0xb409b5c qbeMsgSize=0x18 tmpLen=0x20 msgSize_=0x20|1,200,21,1.178^*^*

10:52:13.197 |CQBEBuilder::BuildQbeMessage(): objectID=179|*^*^*

10:52:13.197 |CTIHandler::OutputQbeMessage: TcpHand=[1:200:13:11681] QbePref={0x0xb389cac,0x18} pQbeMsg=0x0xb389cb4 qbeMsgSize=0x18 tmpLen=0x20 msgSize_=0x20|1,200,21,1.77999^*^*

10:52:13.288 |CtiManager::ready_SdlDataInd(): ConnHandle=[1:200:13:11681] TCP message length=0x20|1,200,13,11681.8^*^*

10:52:13.288 |CQBEParser::ParseQbeMessage: PDU#=120|*^*^*

10:52:13.366 |CtiProviderOpenFailure - CTI application failed to open provider; application startup failed CTIconnectionId:11668  Login User Id:beckma Reason code.:-1932787595 UNKNOWN_PARAMNAME:IPAddress:172.21.3.157 UNKNOWN_PARAMNAME:IPv6Address: App ID:Cisco CTIManager Cluster ID:StandAloneCluster Node ID:rohrpostix|Alarm^*^*

10:52:13.367 |-->RisCTIManagerAccess::ProviderOpenActivity(...)|*^*^*

10:52:13.367 |ProviderOpenActivity(): activity: 3, connID: 11668, appID: , ipaddr: , loginID: beckma, reason: -1932787595|*^*^*

10:52:13.367 |<--RisCTIManagerAccess::ProviderOpenActivity(...)|*^*^*

10:52:13.366 |CQBEBuilder::BuildQbeMessage(): objectID=3|*^*^*

10:52:13.366 |CTIHandler::OutputQbeMessage: TcpHand=[1:200:13:11681] QbePref={0x0xb389cac,0x91} pQbeMsg=0x0xb389cb4 qbeMsgSize=0x91 tmpLen=0x99 msgSize_=0x99|1,200,21,1.77999^*^*

10:52:13.366 |CQBEBuilder::BuildQbeMessage(): objectID=132|*^*^*

10:52:13.366 |CTIHandler::OutputQbeMessage: TcpHand=[1:200:13:11681] QbePref={0x0xb389cac,0x1c} pQbeMsg=0x0xb389cb4 qbeMsgSize=0x1c tmpLen=0x24 msgSize_=0x24|1,200,21,1.77999^*^*

10:52:13.366 |ready_CtiHandlerShutdownRequest. timer stopped|1,200,21,1.77999^*^*

10:52:13.367 |DBAccess::RemoveUserSubscriptionForChangeNotification|1,200,21,1.77999^*^*

10:52:13.367 |CTIUserCache::RemoveUserSubscriptionForChangeNotification|1,200,21,1.77999^*^*

10:52:13.386 |CTIManager::CtiManager::ready_SdlCloseInd(): Connection closed indication. Shutting down provider. -- Connection Id=6 TcpHandle=[1:200:13:11681] PeerIPAddr=172.21.3.157 PeerPort=7659 User name=beckma CtiHandler=[1:200:22:11668]|1,200,21,1.77999^*^*

10:52:13.629 |-->RisCTIManagerAccess::ProviderOpenActivity(...)|*^*^*

10:52:13.630 |ProviderOpenActivity(): activity: 2, connID: 11668, appID: , ipaddr: 172.21.3.157, loginID: beckma, reason: 4|*^*^*

10:52:13.630 |<--RisCTIManagerAccess::ProviderOpenActivity(...)|*^*^*

10:52:13.629 |CTIManager: CtiConnections::remove(): TCP Handle=[1,200,13,11681]  total CTI Connections=4|*^*^*

10:52:13.629 |CTIManager: CtiLoginsInProgress::remove(): TCP Handle=[1,200,13,11681]  total CTI Connections=1|*^*^*

10:52:13.629 |CTIManager::CtiManager::CleanupProviderInfo(): Provider has been closed -- Connection Id=6 TcpHandle=[1:200:13:11681] PeerIPAddr=172.21.3.157 PeerPort=7659 User name=beckma CtiHandler=[1:200:22:11668]|1,200,21,1.77999^*^*

regards

alex

2 people had this problem
Labels:
0 Helpful
8 Replies 8

ronpatel
Level 8
Level 8

‎07-02-2012 07:47 PM

Hi

See restart of tomcat service helps you. We have seen this message when tomcat service takes more memory and gets hang.

Regards

Ronak patel

Rate helpful posts.

Regards Ronak Patel Rate all helpful post by clicking stars below the answer.
0 Helpful

Kapil Atrish
Level 3
Level 3

‎10-23-2012 12:32 PM

Hi,

Did you get the solution to this issue?

I am experiencing exactly the same on my 8.6.2a cluster. All TSP clients have stopped working and I don't see Cisco Line in windows dialer.

CUCM detailed CTI Trace shows the same error which you highlighted above.

Let me know if you ever got to the solution of this.

thanks,

Kapil

0 Helpful

at
Level 1
Level 1
In response to Kapil Atrish

‎11-08-2012 10:11 AM


Hi
Yes I resolved the problem -changing ldap authentication on cucm to global catalog port 3268 instead of port 389 !!
Regards Alex
Sent from Cisco Technical Support iPhone App

0 Helpful

peterputt
Level 1
Level 1
In response to at

‎01-21-2014 09:06 AM

Hi Alex

You saved my live!

Regards,

Peter

0 Helpful

Robert Thomas
Level 7
Level 7

‎10-23-2012 03:53 PM

You are looking at CTI Manager SDI traces with QBE protocol, that won't give you information.

The CTI Manager SDL traces will revel much more information, and hopefully the source of the problem.

Get the CTI Manager SDL traces uploaded to the thread and we will try to help.

0 Helpful

Kapil Atrish
Level 3
Level 3
In response to Robert Thomas

‎10-23-2012 05:40 PM

Pl find attached CTI Manager SDI/SDL traces.

137363-cti.rar.zip
0 Helpful

Kapil Atrish
Level 3
Level 3
In response to Kapil Atrish

‎10-25-2012 08:44 AM

I engaged TAC and the engineer pinpointed following error from the CTI Logs:

Login User Id:platju Reason code.:-1932787595

This is the Cisco documentation on this error code:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/jtapi_dev/8_6_1/constantfieldvalues.html

The engineer suspected LDAP server is not able to authenticate CTI based connections correctly although HTTP based connections (CCMUSER Web Page access) or JTAPI based connections (UCCX) are working fine.

We created an application user in CUCM and the Dialer.exe showed Cisco Line as expected. The engineer did assign all CTI roles (Not only Standard CTI Enabled) except Secure CTI ones. The End User didn't work no matter what we try.

As of now, I've asked the AD team to look at their side or engage Microsoft to debug it at their end. Hopefull that'll resolve the issue.

issofunky
Level 1
Level 1
In response to Kapil Atrish

‎10-23-2015 08:05 AM

I MEANT to rate that response 5 starts, but my mouse did not cooperate.

 

0 Helpful
Customers Also Viewed These Support Documents