Cisco Bug: CSCtd34220 - Partition change on CTI Port yields CtiLineOpenLineRes Result=0x8ccc0005
Feb 22, 2014
- Cisco Unified Communications Manager (CallManager)
Known Affected Releases
Symptom: IPCC Mobile Agent login may fail with "Timeout limit was exceeded" even though the given LCP/RCP CTI Ports show registered within the CCMAdmin web page. The following signature may be found the CTI SDL traces. ===== 021262694| 2009/11/13 01:29:48.073| 007| SdlSig-O | CtiLineOpenLineReq | NA RemoteSignal | CTIRegistrar(7,100,*,*) | CTIDeviceLineMgr(7,200,18,1) | (0,0,0,0).0-(*:*) | [R:NP - HP: 0, NP: 0, LP: 0, VLP: 0, LZP: 0 DBP: 0] mAsyncResponse = 805626 Name=LCP5000F66001 LH=7|375 Line=66001 Partition=PREVIOUS-PARTITION TimeOut=0 FilterBitmap=0x98 Auto Accept Status=0 ===== Note: The Partition value shown in the above signal will indicate the name of the previous partition assigned to the CTI Port line/DN. And there is never another attempt by the application or CTI Manager to open the line with the newly configured partition. This results in the following error response. ===== 021262695| 2009/11/13 01:29:48.074| 007| SdlSig-I | CtiLineOpenLineRes | ready | CTIDeviceLineMgr(7,200,18,1) | CTIRegistrar(7,100,45,1) | (0,0,0,0).0-(*:*) | [R:NP - HP: 0, NP: 0, LP: 0, VLP: 0, LZP: 0 DBP: 0]AsyncResponse=805626 Name=LCP5000F66001 LH=7|375 Result=0x8ccc0005 Auto Accept Status=0 ===== The following two error signals may also be found in the CTI SDL trace. The second error signal listed below may also be thrown as a system alarm in the CUCM application event log and as a SyslogSeverityMatchFound alert in RTMT with corresponding email notification if email notification is configured. ===== 021262699| 2009/11/13 01:29:48.074| 007| AppError | | | CTIDeviceLineMgr(7,200,18,1) | | | LineOpen failed. Removing Lines 021262705| 2009/11/13 01:29:48.102| 001| AlarmErr | | | | | | AlarmClass: CtiManagerAlarmCatalog, AlarmName: kCtiLineOpenFailure, AlarmSeverity: Error AlarmMessage: , AlarmDescription: Unable to open the line, AlarmParameters: UNKNOWN_PARAMTYPE:CTI Connection Id:1, DeviceName:LCP5000F66001, DirNum:66001, Partition:PREVIOUS-PARTITION, UNKNOWN_PARAMTYPE:Reason .:-1932787707, AppID:Cisco CTIManager, ClusterID:StandAloneCluster, NodeID:taclab9cucm, ===== Conditions: This problem may occur if the partition on the line of a CTI Port (LCP or RCP) is changed to a new value while the CTI Port is currently registered/InService and working problem. The PG may not receive notification of the partition change. This may allow the "device" to be in a registered/InService state, but the "line" may be stuck in an "OutOfService" state.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases