|
|
microsoft.public.win32.programmer.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.
Best Regards
Andreas Marschall
Microsoft MVP for TAPI / Windows SDK
TAPI / TSP Developer and Tester
My TAPI and TSPI FAQ:
http://www.I-B-A-M.de/Andreas_Marschall's_TAPI_and_TSPI_FAQ.htm
My TotoŽ Tools (a collection of free, mostly TAPI related tools):
http://www.i-b-a-m.de/Andreas_Marschall's_Toto_Tools.htm
TAPI development around the world (Frappr! map):
http://www.frappr.com/TAPIaroundTheWorld
* Please post all messages and replies to the newsgroup so all may
* benefit from the discussion. Private mail is usually not replied to.
* This posting is provided "AS IS" with no warranties, and confers no rights.