Created by: David Noble on 06-04-2011 06:17:50 AM Hi everyone, I am developing a component to enable integration of a .NET 3.5 solution written in C# with the Cisco Unified Communications Manager 8 - which uses Tapi 2.1. My initial investigations seem to show that Tapi 2.1 cannot be called from managed code - so it seems I'll have to write a wrapper in C++ that I will then in turn call from my C# code - can anyone verify that this is definatley what I'll have to do? Is there absolutley no way to call Tapi directly from C#, there would be no way for .Net to automatically generate interop classes ect? Alternatively, if there are other mechanisms with which to integrate with Cisco Unified Communications Manager 8 which are easier to use from .NET it would be interesting to know about them. Thanks, David
Subject: RE: Calling Tapi 2.1 From .NET 3.5 Replied by: Jaime Bennett on 06-04-2011 03:32:17 PM David,
Mark Smith of Julmar Technology has released his C++ wrappers for both TAPI 2.X and 3.X. They both require .NET 2.0 but they might be a good place to start for what you're looking to do. Check out: http://www.julmar.com/tapi/ for the source code and examples. I've run into a few gotchas that you might want to be aware of:
1. The Cisco TSP for CUCM vesions 8.0 and below only works on 32 bit operating systems
2. I haven't been able to find a way to remove a call from a conference using TAPI and CUCM
3. In my opinion, the Julmar 3.X wrapper is much nicer to use than the 2.X (and seems to work fine with CUCM v 8.0). The only issue i've seen is that it doesn't appear you can start a conference with two connected calls. If you start a conference with a non-connected call, you can't remove it and if it isn't answered it just continues to ring or goes to voicemail.
If you provide more info on what you're trying to acomplish, I might be able to help.
Jaime
Subject: RE: Calling Tapi 2.1 From .NET 3.5 Replied by: David Noble on 07-04-2011 03:17:31 AM Jamie,
Thanks for the reply, much appreciated.
The Julmar wrappers do look like a good starting point; however I think we plan to deploy to a 64 bot OS so your first point is a very important one so thanks for mentioning that.
In terms of what I'm trying to achieve, it's basically simple third party control for a call centre app; answer/hold/disconnect/transfer and reading incoming call data - we've already done this for another platform and I need to quickly write a plugin to achieve the same thing with Cisco.
However yesterday I found something that may mean that I don't need to use TAPI:
I'm currently trying to confirm whether on not we can use this, but it seems more suited to what we need to do.
Subject: RE: Calling Tapi 2.1 From .NET 3.5 Replied by: Jaime Bennett on 07-04-2011 10:47:12 AM David,
Thanks for the info. From what I've read, the 64 bit version of the TSP may only work on CUCM 8.5+. If you try it with a lower version, let me know how it goes. Good luck with your project!
Thanks, Jaime
Subject: RE: Calling Tapi 2.1 From .NET 3.5 Replied by: David Noble on 07-04-2011 10:25:32 AM ..looks like CTIOS is not an option, so it's back to TAPI.
By the way Jame, a colleague informed me that a 64bit TSP has been released recently, just letting you know in case it's of any use to you:
Subject: RE: Calling Tapi 2.1 From .NET 3.5 Replied by: E Daniel Christoff on 09-04-2011 10:14:04 AM David,
You can use ExceleTel TeleTools SDK within a .NET 3.5 application to access TAPI 2.1. This will work on Win 7 64-bit OS, but currently your application will need to be compiled as a 32-bit application.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
