Hi, everyone, have a nice day,
Sorry to bother you, but I have some question about the use of TAPI.
My work is to develop a CSD-trans app on PPC Phone Edition(WM 5
kernel), but actually the PDA is not bought yet: this is because my
project manager wanted to reduce the risk of our project and he told
me to develop an app using TAPI in windowsXP at first for testing, and
the test use TWO normal 56k modem(V.90 OR V.92) and TWO PCs instead of
the original TWO GSM Modem, one PDA and one PC. The TAPI is of ver2.0.
My question is:
1. In MSDN, I found that TAPI2.0 need UNIMODEM to work and the actual
modem must be "Hayes-compatible". I understand what's "Hayes-
compatible", but how can I judge whether a modem is "Hayes-
compatible" ? Is there some trade-mark or some verification mark or
something like this on the modem ? I think the RS232 56k modem must be
"Hayes-compatible", am I right ?
2. If I connect the RS232 modem to the PC, how can I make the TAPI to
use this modem OR how can the TAPI entity "discover" the modem ? Maybe
it's some confusing, let me explain more: when you need to use
TAPI ,firstly you may use lineInitialize() to get the total number of
TAPI supported device, then negotiate the version of TAPI and so on.
Before calling lineInitialize(), there must be some information of
modem devices stored at somewhere in the OS, then the lineInitialize()
function could be possible to return the information. If what I said
is right, how to make the TAPI entity to know there is a modem on the
commport ? So after calling lineInitialize() the TAPI entity will
found the special modem.
3. Is it possible to translate the app to Windows Mobile without much
work ? Is there no question if the normal modems are replaced by the
GSM modem (both use hayes AT set)?
Thanks your precious help ahead. ^_^
Best Wishes,
skovano