Revision as of 18:49, 9 September 2009 by Cchetty
|Problem Summary||When silent monitor fails for any of the reasons described in the PG Error Codes table, the supervisor desktop displays the error number as well as text describing the error.|
|Error Message||IPCC Error  Monitoring request has encountered an error, please make sure that Build-In-Bridge is turned on and the phone has monitoring capability|
|Recommended Action||Theis error occurs when a supervisor attempts to silent monitor an agent using a phone that does not support the silent monitor function.|
|Associated CDETS #||None.|
Supervisor Desktop Log
The error is also logged in the supervisor desktop log.
04/20/07 20:58:11.734 2560 SupervisorSoftphone Thd(3740) CCtiOsSession::OnEvent( eControlFailureConf ), EnablementMask = ffffffff 04/20/07 20:58:11.734 2560 SupervisorSoftphone Thd(3740) CCtiOsSession::OnEvent, (PeripheralID:5000 FailureCode:1 PeripheralErrorCode:13144 AgentID:101 UniqueObjectID:agent.5000.101 MessageID:eControlFailureConf MessageType:eSuperviseCallRequest ErrorMessage:IPCC Error Monitoring request has encountered error, please make sure that Built-In-Bridge is turned on and the phone has the monitoring capability FilterTarget:agent.5000.101 TargetCILClientID:VM3AGENT1-2560-3740)
CTI Server Log
The error is also logged in the CTI Server log.
20:53:23 cg1A-ctisvr Trace: CSTAUniversalFailureConfEvent - InvokeID=0x27000110Error=GENERIC_OPERATION 20:53:23 cg1A-ctisvr Trace: PRIVATE_DATA - PeripheralErrorCode=0x3358(13144) 20:53:23 cg1A-ctisvr Trace:
The JTAPI Gateway logs the error as well. When JTAPI logs the error, it only logs the last 3 digits. For example 13144 is logged as 144.
20:53:22 pg1A-jgw1 Trace: ThreadSuperviseCall::SilentMonitorCall: Call to call.startMonitor([SEP0015FAB8F3EB,30001],[SEP000D2890C160,13004],CiscoCall.Silent_Monitor,CiscoCall.PlayTone_NoLocalOrRemote) encountered exception. com.cisco.jtapi.PlatformExceptionImpl: Monitor req 20:53:22 pg1A-jgw1 Trace: MsgFailureConf: InvID: 197149365 Status: 144