< XXXX@XXXXX.COM > schrieb im Newsbeitrag
when you already have notified TAPISRV about the two existing calls (via
LINE_NEWCALL message) you simply need to notify TAPISRV about a new virtual
parent conf call (via LINE_NEWCALL), set its call state to _CONNECTED (via
LINE_CALLSTATE message) and report its LINECALLINFO.dwOrigin as
LINECALLORIGIN_CONFERENCE when queried on it via TSPI_lineGetCallInfo().
After the creation of the parent conference call you need to set the call
states of the conference participants (i.e. the pre existing call handles) to
LINECALLSTATE_CONFERENCED (via LINE_CALLSTATE message). In these last two
LINE_CALLSTATE messages you must set dwParam2 = htCall of the parenbt conf
"If dwParam1 is LINECALLSTATE_CONFERENCED, dwParam2 contains the htCall of the
parent call of the conference of which the subject htCall is a member. If the
call specified in dwParam2 was not previously considered by TAPI to be a
parent conference call, this message causes it to be so treated. The call
specified in dwParam2 must already exist; it was most likely previously
created by a LINE_NEWCALL message and set to LINECALLSTATE_ONHOLDPENDCONF."
Microsoft MVP for TAPI / Windows SDK
TAPI / TSP Developer and Tester
* Please post all messages and replies to the newsgroup so all may
* benefit from the discussion. Private mail is usually not replied to.
* This posting is provided "AS IS" with no warranties, and confers no rights.