cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
968
Views
0
Helpful
3
Replies

Unable to silent monitor agent with CTIOS 6.0

fbushiri1
Level 1
Level 1

Hello,

I'm unable to monitor an agent using CTIOS 6.0. The logs show the following error:

From Supervisor:

01/12/11 08:20:43.459  260724  SupervisorSoftphone  Thd(00263472)  CSilentMonitorManager::HandleStatusReportForMonitoringMode( SMSessionKey=101,
  UOID = agent.5000.7169), Silent monitor session termination (Status=0x5)
01/12/11 08:20:43.459  260724  SupervisorSoftphone  Thd(00263704)  CUDPPort(03BE2BC0)::ReceiveData, recvfrom, Blocking call interrupted by
  WSACancelBlockingCall. (WSAEINTR), Error Number(10004).

From Agent:

01/12/11 08:19:57.010  4524  CTIOSSoftphone  Thd(00004740)  CSilentMonitorManager::CacheStartRequest(...)
01/12/11 08:19:57.057  4524  CTIOSSoftphone  Thd(00004740)  CCtiOsSession::MakeRequest(eReportSilentMonitorStatusRequest)
01/12/11 08:19:57.057  4524  CTIOSSoftphone  Thd(00004740)  CSilentMonitorManager::DiscardStartRequest(...)
01/12/11 08:20:43.120  4524  CTIOSSoftphone  Thd(00003904)  CUDPPort(017B4770)::ReceiveData, recvfrom, Blocking call interrupted by
  WSACancelBlockingCall. (WSAEINTR), Error Number(10004).
01/12/11 08:20:43.120  4524  CTIOSSoftphone  Thd(00003228)  CCtiOsSession::MakeRequest(eReportSilentMonitorStatusRequest)

Any assistance will be appreciated.

Thanks,

MB

3 Replies 3

Ian Meyers
Level 1
Level 1

MB,

    I've seen some issues on 6.0 with silent monitoring. What you describe sounds a little like CSCsa69519, except it doesn't sound like your desktop has been locking up.  Have you patched it at all, or is IPCC on base version?

David Patterson
Level 1
Level 1

I'm experiencing a similar situation with the Blocking call interrupted by WSACancelBlockingCall on silent monitoring and am curious if you identified the source of your problem.  Thank you.   DBP

Hi David,

Sorry for the late response... but I upgraded to WinPcap 4.1.2 (http://www.winpcap.org/install/default.htm) and that seemed to fix the problem.

Thanks,

MB