Chris,
The JavaCil does not support the silent monitoring objects needed for CTIOS based silent monitoring. Nor does the .NET Cil.
David,
Thank you so much for this response. However, I need to find a way to enable client side silent monitoring **somehow**. I cannot rewrite the entire custom client, so whatever I do will need to be either kludge or genius! :-)
I am not asking for you to design the solution, but if there were some additional detailed guidance you could provide I would be very grateful. I can open case if you think it is a valid Development Support issue that would yield concrete technical results.
I am thinking that if the COM CIL supports those objects, perhaps I can develop a native bridge to utilize the COM objects that are required. Would it require multiple logins for the agent at the ICM side? Is there any reason why it would not be possible? In my experience, there is nothing that cannot be done in Java (especially given JNI); it's typically just an engineering challenge.
If I understand how SM works, the winPcap application transmits voice packets off the PC<->Phone link to a remote address. I'd guess the setup/teardown trigger events would come from CTIOS, and this would cause the client app to instantiate a session in winPcap using the endpoint provided in the OnSilentMonitorStartRequestedEvent event. Is there any reason why the event received in Java cannot trigger objects in the COM CIL? I'm not sure what is accomplished by session.SetCurrentSilentMonitor().
Another possible solution would be to switch to the COM CIL for CTIOS events and recast the GUI as a shell over the COM CIL's event mechanism. The multi-threaded approach (listener / gui) lends itself to refactoring across a wider gulf than just 2 in-process threads, so I suppose that'd be a decent solution if I can't mix in the SMM objects to the existing session.
I will look through the sample code to see if there's anything I can come up with on my own. Would the Dev Support team be able to support a request like this? Can you share with me the principle impediment to a Java+COM solution?
Thanks,
Chris