lineGetCallInfo CallerID

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hi!
I'm surely not the first one with this problem.
So a link to a good archiv answer would be fine enough.

My problem: Tapi 2.0
I'm trying to get the callerId of a call (how extraordinary...)
with the LINECALLINFO i get the offset of a DWORD array of size x.
Im my case x=4 mostly. This is a fine array, but it contains some "mystic things", but def. not the CallerID.

Here is the code. My language is c by the way...

HCALL *hCalls;
hCalls=(HCALL *)calloc((*lpCallList).dwCallsNumEntries,sizeof(HCALL));
hCalls=&(*lpCallList).dwCallsOffset;
getMessage();

for (byte i=1;i<=(*lpCallList).dwCallsNumEntries;i++)
{
LINECALLINFO *lpCallInfo;
lpCallInfo=malloc(1000);
memset(lpCallInfo, 0,1000);
(*lpCallInfo).dwTotalSize =1000;
lResult=lineGetCallInfo(hCalls[i],lpCallInfo);

DWORD *lpCallerID;
lpCallerID=(DWORD *)calloc((*lpCallInfo).dwCallerIDSize,sizeof(DWORD));
memset(lpCallerID, 0,(*lpCallInfo).dwCallerIDSize);
lpCallerID=&(*lpCallInfo).dwCallerIDOffset;
for (byte j=1;j<=(*lpCallInfo).dwCallerIDSize;j++)
{ printf(" %d",*lpCallerID[j]);}

I think it has something to do with DWORD and bytes.
But becaus of being a total newbie in c (and ++) i don*t understand, what the matter is.
Kind regards
Martin
.

Relevant Pages

  • Re: Question about OffloadModExpo() Function
    ... It seems to me that you're interpreting the length values as the DWORD count ... It might be helpful if you were to create a private key whose structure you ... > memcpy(base, pbBase, cbMod); ... > It's 'big number' params are DWORD array, ...
    (microsoft.public.platformsdk.security)
  • RE: Question about OffloadModExpo() Function
    ... I'm sorry to disturb you again.Because I really have no idea about it. ... BOOL OffloadModExpo( ... DWORD cbExpo, // in ... It's 'big number' params are DWORD array, ...
    (microsoft.public.platformsdk.security)