Raw Caller ID format
- From: "Tal.k." <tal_2k@xxxxxxxxxxx>
- Date: Fri, 2 Sep 2005 03:04:16 +0200
Hi, I have a very annoying problem,
I have a zoltrx smart spirit voice modem,
And I'm developing a tapi software running on windows xp.
The problem is that it is missing the caller id information almost every
second call, one time it's working and the next call I don't get any caller
id,
I've checked everything, HyperTerminal, Fax software, the modem log, they
all act alike, and I've checked it with 2 more modems: one that is not a
voice modem, get the caller id perfectly, and another voice modem (apache)
that has the same problem. And also I've checked it on other phone lines, at
several locations. (So it's not my noisy line that causing the problem).
After days of checking, I found out that the problem is that sometimes the
caller id information is not coming correctly, more accurate, the checksum
is wrong.
So, I've used the at+vcid=2 command, which switches to caller id raw mode.
Now I can see that there is a caller id coming every call, but sometimes the
checksum is wrong so the message is coming with more unwanted information,
but I can still decipher it.
My questions are:
1. Does tapi can work in unformatted - raw caller id mode? And if so how can
I configure it?
2. Can I listen to the port while tapi is initialized, and read the data
coming from it? (Maybe using some tapi api to directly access the port)
4. is there a problem with windows xp and caller id?
3. If the first 2 can not be done, how can I solve this problem?
Thanks in advance, Tal .
.
- Follow-Ups:
- Re: Raw Caller ID format
- From: Alex Feinman [MVP]
- Re: Raw Caller ID format
- Prev by Date: Re: Newbie question
- Next by Date: Re: Raw Caller ID format
- Previous by thread: Re: Busying Out TAPI for incoming H.323 call
- Next by thread: Re: Raw Caller ID format
- Index(es):
Relevant Pages
|
