I'm trying to write an app to manage conference calls. I can create the conference calls and add as many parties as UCM is configured to allow. The problem is that I can only see the first two parties and the conference call itself in the calls collection. I have tried looking at the line's call array, the address call array, and the output of the lineGetConfRelatedCalls function. In each case, it only displays 3 calls. Now if I disconnect the first two parties from the call reverting it to a non-conference call to the 3rd party and look at the call collection again, my 3rd parties call shows up, but doesn't have a valid callOrigin or callReason. There are also dead calls hanging around in the collection at this point with their call state set to idle. If I create new calls now, the collection grows past 3 calls(with the idle calls still hanging around) but I still can't see more than two parties and the root conf call when I add the 3rd party to the conference.

I'm accessing TAPI via julmar.com's atapi.net library in VS2005. Mark Smith over there has been extremely helpful. The TSP version is 6.1(0.10).

Any ideas?

Jun will only monitored devices be represented as call instances in the conference? Are the two lines in this example monitored, and the others unmonitored..?

lineGetNewCalls returned SUCCESS
LINECALLLIST
dwTotalSize=x1000
dwNeededSize=x28
dwUsedSize=x28
dwCallsNumEntries=x4
dwCallsSize=x10
dwCallsOffset=x18
00010106 0001014a 0001016c 000101d1 ....J...l.......
Monitored call x10106 deallocated on IDLE
lineGetConfRelatedCalls returned SUCCESS
LINECALLLIST
dwTotalSize=x1000
dwNeededSize=x24
dwUsedSize=x24
dwCallsNumEntries=x3
dwCallsSize=xc
dwCallsOffset=x18
0001016c 000101d1 0001014a xxxxxxxx l.......J...

As you can see from the TB20 trace, only 3 calls are being reported by the TSP driver, when there are 4 calls legs(3 remote participants, and the parent conf call).

Jeremy Sanders, CCIE #12332(R&S and Voice)
Solutions Architect
TekLinks, Inc.
c205-249-5988
w205-314-6630