Hi L0ki,
I came across your post via google and thought I would reply to save you having a heart attack on this.
We have just completed weeks of work developing an interface to the UCA SDK from a non .NET CRM application (written in pure C++) - to say it has been a nightmare is underselling it.
The main issue is that TelephonyProxy.dll is not a true COM entity because it provides no method for you to access the events connect, disconnect, offering and ringback. This is because those events are actually .NET events and are not accessible via an iConnectionPointContainer interface.
So to answer your question, there is no REFIID - I know I was shocked as well given it was promoted as being a COM interface.
Our solution was to create a native <-> NET interop bridge/wrapper sending back the Event information to our application via a WM_COPYDATA Window message. The advantage of this approach is that we do not have to mess around with regasm which I feel is an amateur thing to have to do. The disadvantage is that we now have to install the Visual C++ Runtime Libraries because you cannot statically link CLI to those libraries which is annoying.
Anyway, our mitel update has just been rolled out to one Client at this stage and we have Dial Out and Caller ID working.
But here we have hit a snag.....
The Caller ID application is maintaining a log file so that we can see the firing sequence of the events. And there we have a problem - the sequence is not logical. We are seeing random disconnect events for which there is no connect event and sometimes the ringback and offering phone numbers are not provided at all.
So, what I am after is some documentation explaining the events in detail describing basic things like what to expect when a call is transferred from another extension or placed on hold. Anyone ?
Of course I am happy to share with others trying to get what is the worst SDK I have come across in 30 years operational. I mean if you are not going to use TAPI but provide your own interface, surely you would make sure that what you supply is superior to TAPI.
This is certainly not the case in this instance and I would sack the developers of this monstrosity in a blink of an eye.
Leslie.