Re: Caller ID question - no caller ID after first call

Andreas Marschall [MVP TAPI] wrote:
"Jim D" <jfd@xxxxxx> schrieb im Newsbeitrag
news:eQgAYr5KHHA.4460@xxxxxxxxxxxxxxxxxxxxxxx
I have a TAPI 2.x app that I'm using to get the Caller ID and display
it. I'm using an Intel 537 modem. On openLine, I'm using
LINECALLPRIVILEGE_OWNER and LINEMEDIAMODE_INTERACTIVEVOICE. I get the
LINECALLINFOSTATE_CALLERID events just fine, but only on the first call.
I'm not answering the call, I just let it ring. Then on
LINECALLSTATE_IDLE, I call lineDeallocateCall. That all seems fine.
But then on the next call (from the same phone), I only get
LINEDEVSTATE_RINGING events and no others.

What could be causing that?

Jim,
some TSP like UniModem.TSP only support one call handle at a time.
If you don't deallocate _any_ call related resources from the 1st call you
won't be notified on further calls.

Thanks for the reply. I did some more debugging and discovered that due to a condition that was failing, it wasn't really calling lineDeallocateCall. Now that I've fixed that problem, Caller ID is working correctly.

I do have another related question. Now that caller ID is working, I'm getting 2 LINECALLINFOSTATE_CALLERED events in a row. So I've gone from not enough caller ID, to too much caller ID.

Is that normal? If so, is there some difference between the 2 events?

Thanks,
Jim
.

Loading