Created by: Christopher Nagel on 21-10-2010 05:30:10 PM Hi, I'm getting OnControlFailureConf messages two in a row, one with info and one without. Here is a sanitized version of the log: 10/21/2010 11:11:12.0666 OnControlFailureConf: (CallType:2 FailureCode:13 PeripheralErrorCode:0 EnablementMask:0xBF01A6 UniqueObjectID:call.1029.34226497.1 CallStatus:eCallConnectionConnect MessageID:eControlFailureConf ErrorMessage:The connection identifier is not valid. EventType:1 ICMEnterpriseUniqueID:swm.14222.2593 DeviceUniqueObjectID:device.1029.1) 10/21/2010 11:11:12.0666 CtiOsSession(9486447).ReportError, Code: -903, Msg: An object for this call is already set as current in the session 10/21/2010 11:11:12.0666 OnEvent (DEBUG) - Initial receive, EventID(536870924) and Args: : (EnablementMask:0xBF01A6 UniqueObjectID:call.1029.34226497.1 MessageID:eControlFailureConf) 10/21/2010 11:11:12.0666 OnButtonEnablementChange: (EnablementMask:0xBF01A6 UniqueObjectID:call.1029.34226497.1 MessageID:eControlFailureConf) 10/21/2010 11:11:12.0666 Current CallID: call.1029.34226497.1 10/21/2010 11:11:12.0682 Got mask -->12517798 10/21/2010 11:11:12.0682 OnControlFailureConf: (EnablementMask:0xBF01A6 UniqueObjectID:call.1029.34226497.1 MessageID:eControlFailureConf) The first and last lines show the difference between the two messages. The dev docs indicate that there should be some reliance upon the args array containing values like ErrorMessage. Of course I can code defensively, but what I really wonder is if the missing args are indicative of some other error upstream? Thanks, Chris
Subject: RE: New Message from Christopher Nagel in Computer Telephony Integration Ob Replied by: David Lender on 22-10-2010 01:51:52 PM Under what scenario(s) do you receive the 2nd onControlFailureConf? I would ignore the one without a FailureCode. If you want to report the 2nd one as a bug, open a Service Request and provide a full set of CIL and CTIOS Server logs demonstrating the issue and include a description of the scenario.
Subject: Re: Same message, different args Replied by: Christopher Nagel on 03-11-2010 08:33:55 PM
Under what scenario(s) do you receive the 2nd onControlFailureConf? I would ignore the one without a FailureCode. If you want to report the 2nd one as a bug, open a Service Request and provide a full set of CIL and CTIOS Server logs demonstrating the issue and include a description of the scenario.
We were running into resource allocation errors - we'd reached (and passed) our max concurrent call volume. Under those circumstances, I'm not sure I can rightly call it a bug as much as "whaddayaspekt?" :-) The weird thing is, the code first checks if the error message value is null and then tries to use it. Somehow it seems to have been getting GC'ed between the check and the access, and throwing an NPE. For now, it's thankfully "just gone" - I cannot reproduce it. Thanks, Chris
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:
