|
|
|
date: Thu, 14 Aug 2008 02:02:41 -0700 (PDT),
group: microsoft.public.win32.programmer.tapi
back
TAPI architecture.
Hello, everybody.
It seems what TAPI developer must go directly to the heaven after
death because of problems while alive :)
I am not sure but I think it is so. Let say there are two processes
using same phisical
line. ( In my case this is cellphone line). Now if one application
( for example MS phone)
gets a handle it becomes like it is written 'sole' owner. Other
application can apply some
functions to this new handle (cause it can take owner rights), but it
seems what not all things
can be done or they cannot be done right at the moment but can be
done later. For example:
App1: makeRequest -> new handle allocated
App2: gets new handle via LINECALLSTATE_APPNEWCALL
if it is try to drop this call no errors occures, (lineDrop called
from app2 ends asynchronously with 0 result)
but call left alive like it is was not droppped.
After app1 establish connection to other part, app2 can drop call and
it will be closed.
In my case I need to drop call before it is becomes connected. I think
I cannot drop call at early
state because I am not 'sole' owner of this call.
Is there any solution how to become full right owner of the call ?
Maybe there some solution how hook system so it call my application to
makeRequest ( I try
lineSetAppPriority, but it was not working for me, it is possible what
I am doing something wrong).
So if somebody see something like this, or maybe already has such
problems or maybe knows
somebody who knows how, give any info.
Normally I would write application which impelemnts all functions
inside. But I need to use some
windows or phone native functions (like speed dial, contact search,
etc.) so I cannot fully disable
native phone processing.
I hope you understand what I write here :)
Respectfully,
Romualdas
date: Thu, 14 Aug 2008 02:02:41 -0700 (PDT)
author: unknown
|
|