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

Silent Monitor error code = 0x00000005

don_crowder
Level 1
Level 1

Greetings,

Running CTIOS 6.0 and are having problems montitoring about a dozen or so agents. Last week, I visited a site that was experiencing the issue and performed the following:

Verified port was spanned with WireShark

Uninstall / re-install CTIOS client from admin login.

Updated / NIC drivers on the agents desktop (Broadcom NetXtreme Gig)

After completing this, I returned to the office and was able to monitor the agent with no problems. Today, I am getting the aforementioned error code as I was previously. Does anyone have an idea on what might be the problem? Any troubleshooting suggestions would be greatly appreciated. BTW, I am very new to the contact center world, so please don't use too many big words .

Thanks in advance,

Don

1 Reply 1

Kris Lambrechts
Level 1
Level 1

By 'checked with Wireshark' I assume you've ran Wireshark on the PC and you could see RTP / Skinny traffic ?

That's indeed typically the biggest hurdle, either due to the PC not being daisy chained to the phone and/or NICs that do not support monitor mode.

Some other causes that you may want to check to could 'pop up' without making any real changes :

1) If the PCs are laptops with wireless NICs or have a 2nd NIC for some other reason you'll want to check from Network Connections - Advanced - Advanced Settings that the NIC connected to the phone is on top, if it isn't, CTI OS SM service will be listening on another IP than is advertised to the Supervisor client;

2) Some firewall / AV software causes WinPCAP to not be able to switch the NIC into monitor mode, so try to disable that;

3) If you tested with other user ids than the agents actually use, make sure the agents have enough permissions to set their NICs in monitor mode.

Mind you, step 1 can also apply to your supervisor PC, i.e. if you've got a wireless NIC or VPN adapter active and prioritized over whatever interface you use to reach the CTI OS server that can cause the same problem.

Cheers,

Kris