Gmail Calendar Documents Reader Web more »
Recently Visited Groups | Help | Sign in
Google Groups Home
microsoft.public.win32.programmer.tapi
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Message from discussion Future of TAPI
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Angus  
View profile  
 More options Jun 14 2008, 8:07 pm
Newsgroups: microsoft.public.win32.programmer.tapi
From: "Angus" <nos...@gmail.com>
Date: Sat, 14 Jun 2008 11:07:13 +0100
Local: Sat, Jun 14 2008 8:07 pm
Subject: Re: Future of TAPI
Reply to author | Forward | Print | View thread | Show original | Report this message | Find messages by this author
The thing you have to consider is that if you don't offer a TAPI interface
what alternatives do you have?

CSTA is one option.

Another option is to provide a proprietary interface.  for example, Mitel
provide an SDK which developers can purchase and develop CTI programs - but
obviously they will only work with Mitel PBX's.

It depends where you anticipate your market.  If your PBX is destined to be
used in call centres then CSTA could be a good option.  If your PBX is
general purpose then I would advise TAPI is the way to go.

Or if you want to make the interface to your PBX closed then a proprietary
interface.

The proprietary interfaces tend to be C API's.

Note that none of these options tend to be .NET friendly.  .NET developers
would need a wrapper around all these interfaces.  As would Java developers.

There is often a disparity between what developers want (flexibility, easy,
low cost) and what PBX vendors want (making money out of developers, tie
developers in, etc).

Angus

"Brent" <notha...@noemail.com> wrote in message

news:eKekwUWzIHA.2184@TK2MSFTNGP02.phx.gbl...
> I am looking into TAPI-enabling our software application that we develop
and
> sell. I am a little hesitant to jump into this since it appears that TAPI
> hasn't moved forward in awhile. Is Microsoft going to move TAPI to .NET or
> continue its development at all? I would hate to start a major project
like
> this to have it end up dead.

> Thanks for any insight.
> Brent


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google