"Riber" <riber @ RemoveSpacesAndThis mail.com> schrieb im Newsbeitrag
I guess you didn't take telephony devices into account that are not POTS
related, e.g. ISDN phones or digital system phone connected to a PBX. They are
using interfaces like S0, Up0, or Uk0 partly with proprietary protocols on it.
In thoses cases there is no "raw Hex Caller ID data" like modems use it.
As I said "TAPI is an abstraction layer for all kind of telephony equipment".
One may regard this as prime directive.
It is the goal of TAPI to provide a standardized mechanism for accessing the
Any TAPI app (not only those focussing on modems!) should be able to get this
info in the same way.
Of course TAPI offers ways to access proprietary info or functions via
Extended Services (DevSpecific stuff) but this is only designed for features
that are not provided by the common parts of TAPI (Basic and Supplementary
So if a TSP provides raw data although there is well defined way in TAPI to
provide the same info in a way that all(!) TAPI app can understand then this
would be regarded a violation of the prime directive (s.a.).
Microsoft MVP for TAPI / Windows SDK
TAPI / TSP Developer and Tester
* 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.