One might think that the COM based API exposed by TAPI v3 would have been an
option with the Runtime Callable Wrappers (RCW) provided by .Net but sadly
that is not a supported scenario:
Just by the way, despite of the official non-support, some posters have
mentioned in the TAPI newsgroup that simple .Net applications can make use
of RCW. FWIW, it might work on the desktop, I wouldn't recommend that in a
server.
Just by the way, the lack of TAPI support in .Net caused one user to write
her own wrapper in C# using interop: