|
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
 |
Newsgroups: microsoft.public.win32.programmer.tapi
From: "Andreas Marschall [MVP TAPI]" <Andreas.Marsch...@I-B-A-M.de>
Date: Thu, 19 Jun 2008 13:54:35 +0200
Local: Thurs, Jun 19 2008 9:54 pm
Subject: Re: Future of TAPI
"Brent" <notha...@noemail.com> schrieb im Newsbeitrag
news:eqwYVyH0IHA.2068@TK2MSFTNGP05.phx.gbl... > Andreas, thanks for the reply. Seems like unless you are dealing with one Brent, you are welcome. > manufacturer and phone system, it can get a little hairy. I will keep > digging and see if it's a viable project. In theory TAPI is an abstraction layer between the device and the app, but this concetpt actually works only for basic features. Advanced features that are more or less unique to a device / PBX may need special handling, at least special attention. In all cases it is highly recommended to test and a TAPI with all relevant TSPs (devices / PBXs). > By the way, most of the links on your site that link to Microsoft have Thanks for the hint with MS link issue within my FAQ. > changed. If I do a search, I can find the referenced pages, but the links > are broken. I will address this with the next update. -- 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.
| |||||||||||||