Re: <HEX to HEX> instead of <Hex - People - Hex>
From: Andreas Marschall [MVP TAPI] (Andreas.Marschall_at_I-B-A-M.de)
Date: 07/22/04
- Next message: Andreas Marschall [MVP TAPI]: "Re: Modifying Calling Party Number and Name Information"
- Previous message: FCTOM: "Modifying Calling Party Number and Name Information"
- In reply to: Riber: "<HEX to HEX> instead of <Hex - People - Hex>"
- Next in thread: Riber: "Re: <HEX to HEX> instead of <Hex - People - Hex>"
- Reply: Riber: "Re: <HEX to HEX> instead of <Hex - People - Hex>"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 22 Jul 2004 18:07:23 +0200
"Riber" <riber @ RemoveSpacesAndThis mail.com> schrieb im Newsbeitrag
news:qkHLc.45$A37.2299@nnrp1.ozemail.com.au...
> Give Tapi Developers more Power!
>
> The raw Hex Caller ID data is not hard to understand at all, and it contain
> all the information a developer would need.
>
> I think it is plain stupid to translate a good Hex Caller ID Signal into
> "People Language" and then translate it back to Hex in unimodem.
>
> Whoever though out this stupid idea doing this <people translation> do not
> deserve a medal.
> However they possibly didn't know what they were doing. Maybe it looked
> fancy at the time.
>
> I say, get the Raw Hex to Tapi Developers!! The Tapi developers have plenty
> of brain to make good use out of this data, and can make any Caller ID
> application compatible with any kind of Telco.
Jack,
please note that TAPI is not equal to modem! TAPI is an abstraction layer for
all kind of telephony equipment.
The "raw Hex Caller ID data" you are referring to is only modem related and
not relevant for any other kind of TAPI devices. So IMO it is not TAPI
relevant. TAPI (not restricted to modems!) has a well defined way of
presenting CallerID in LINECALLINFO.dwCallerIDxxx.
Admittantly there are modem related issues presenting CallerID via TAPI but
these have several causes: TelCo signalling, signal processing by modem
hardware, modem.INF file, and UniModem.TSP.
I'm under the impression that you are focussed on blaming almost solely
UniModem.TSP for this situation.
But AFAIK TAPI is presenting CallerID correctly if UniModem.TSP is provided
with the information it expects. So one can say that it is the task of the
underlaying layers to provide this info correctly and conform to UniModem's
specifications. It seems that a lot of TelCos over the world feel the need to
define proprietary CallerID signalling protocols and that modem manufacturers
are not able to handle all these protocols and provide a valid signalling to
UniModem. Even if UniModem will be enhanced to process all these proprietary
(or malformatted) signallings it won't take long until a new TelCo or modem HW
is available that comes with an additional variant that won't work...
So IMO there is a clear priorisation of responsibilities for these issues:
1. TelCo CallerID signalling "standards"
2. modems (HW, .INF)
3.UniModem.TSP.
(4.)TAPI itself (as part of the OS) has absolutely nothing to do with it
because it solely depends on the info provided by the TSP.
Possible solutions:
A. Address the issues in priority of responsibility.
B. Write your own Modem.TSP: anybody (in theory) is able to write a TSP. The
specifications are available via MSDN and there is a sample code for AT
command based TSP available (ATSP32). Any modem manufacturer could deliver a
well tailored TSP for their modems but apparently the choose to do not. Even
every developer may try to develop a better TSP for modems.
C. If you want modem proprietary data like "raw Hex Caller ID data" you may
always choose to develop a modem proprietary (non-TAPI) app accessing the
modem directly.
-- Best Regards Andreas Marschall Microsoft MVP for TAPI / Windows SDK TAPI / TSP Developer and Tester http://www.I-B-A-M.de/Andreas_Marschall's_TAPI_and_TSPI_FAQ.htm * 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.
- Next message: Andreas Marschall [MVP TAPI]: "Re: Modifying Calling Party Number and Name Information"
- Previous message: FCTOM: "Modifying Calling Party Number and Name Information"
- In reply to: Riber: "<HEX to HEX> instead of <Hex - People - Hex>"
- Next in thread: Riber: "Re: <HEX to HEX> instead of <Hex - People - Hex>"
- Reply: Riber: "Re: <HEX to HEX> instead of <Hex - People - Hex>"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
