cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
368
Views
0
Helpful
1
Replies

CTI Issue

Not applicable

I am currently trying to assist an installation of a third party call center software called Apropos. This will connect to our are Call Manager running 3.3(2). We basically set up 10 Cti route points and created a user with the devices under it. Apropos can control the phones it has under it but when we try and call the route point it just goes down the hunt group and then gives us a fast busy. It looks like it might be an issue with the CTI routing. We our not sure if it is on the call manager side or the Apropos side. Apropos system does show the call coming in but thats it.I have looked into the trace logs in our call manager and this is what I see:

CTI Trace log:

10/28/2003 11:31:32.242 CTI|kCtiProviderOpenFailure - CTI application failed to open provider CTIconnectionId:64 Login User Id:ac UNKNOWN_PARAMNAME:ReasonCode:2362179680 IPAddress:192.168.10.4 App ID:Cisco CTIManager Cluster ID:StandAloneCluster Node ID:C3ICM1|<CLID::StandAloneCluster><NID::C3ICM1><CT::Alarm>

10/28/2003 11:31:32.242 CTI|-->RisCTIManagerAccess::ProviderOpenActivity(...)|<CLID::StandAloneCluster><NID::C3ICM1>

10/28/2003 11:31:32.242 CTI|<--RisCTIManagerAccess::ProviderOpenActivity(...)|<CLID::StandAloneCluster><NID::C3ICM1>

10/28/2003 11:32:32.478 CTI|pAlarmInstance: a30d270|<CLID::StandAloneCluster><NID::C3ICM1>

10/28/2003 11:32:32.494 CTI|kCtiProviderOpenFailure - CTI application failed to open provider CTIconnectionId:65 Login User Id:ac UNKNOWN_PARAMNAME:ReasonCode:2362179680 IPAddress:192.168.10.4 App ID:Cisco CTIManager Cluster ID:StandAloneCluster Node ID:C3ICM1|<CLID::StandAloneCluster><NID::C3ICM1><CT::Alarm>

10/28/2003 11:32:32.494 CTI|-->RisCTIManagerAccess::ProviderOpenActivity(...)|<CLID::StandAloneCluster><NID::C3ICM1>

10/28/2003 11:32:32.494 CTI|<--RisCTIManagerAccess::ProviderOpenActivity(...)|<CLID::StandAloneCluster><NID::C3ICM1>

CCM:

10/28/2003 11:31:32.242 CTI|kCtiProviderOpenFailure - CTI application failed to open provider CTIconnectionId:64 Login User Id:ac UNKNOWN_PARAMNAME:ReasonCode:2362179680 IPAddress:192.168.10.4 App ID:Cisco CTIManager Cluster ID:StandAloneCluster Node ID:C3ICM1|<CLID::StandAloneCluster><NID::C3ICM1><CT::Alarm>

10/28/2003 11:31:32.242 CTI|-->RisCTIManagerAccess::ProviderOpenActivity(...)|<CLID::StandAloneCluster><NID::C3ICM1>

10/28/2003 11:31:32.242 CTI|<--RisCTIManagerAccess::ProviderOpenActivity(...)|<CLID::StandAloneCluster><NID::C3ICM1>

10/28/2003 11:32:32.478 CTI|pAlarmInstance: a30d270|<CLID::StandAloneCluster><NID::C3ICM1>

10/28/2003 11:32:32.494 CTI|kCtiProviderOpenFailure - CTI application failed to open provider CTIconnectionId:65 Login User Id:ac UNKNOWN_PARAMNAME:ReasonCode:2362179680 IPAddress:192.168.10.4 App ID:Cisco CTIManager Cluster ID:StandAloneCluster Node ID:C3ICM1|<CLID::StandAloneCluster><NID::C3ICM1><CT::Alarm>

10/28/2003 11:32:32.494 CTI|-->RisCTIManagerAccess::ProviderOpenActivity(...)|<CLID::StandAloneCluster><NID::C3ICM1>

10/28/2003 11:32:32.494 CTI|<--RisCTIManagerAccess::ProviderOpenActivity(...)|<CLID::StandAloneCluster><NID::C3ICM1>

Any help would be much appreciated.

Greg

1 Reply 1

Not applicable

I think there is some memory leak issue related to call manger. I doubt if you are running into the same. Check this out:

http://www.cisco.com/warp/public/707/callmanager-ctifw-leak-pub.shtml