Hi,
Very new to VB. I've been thrown in at the deep end at the start of a
univeristy placement.
I think I have the problem described, while going through some rather more
complex stuff in the background, so please bear with me while I describe
it, in case the problem is actually something else entirely.

I'm using the MS TAPI3 COM objects to set up, call and answer a phone call
over two 56K modems.
I've selected a modem, set up the call to be made, and set up an event on
the second modem to answer when it registers an incoming call on its line.
I've tested these things seperately and they seem to work.
Then I send the following line:

Call objCallControl.Connect(True)

Which starts a call object, which is set not to return until the call is
answered, or it times out.
Because the exact same software is the software that's trying to answer
the call, it can't respond to the call to answer until this outgoing call
has "finished", i.e. until it has failed to be answered and processed
through to its two-minute timeout.
This then starts the slightly surreal situation where the line picks up,
dials, fires a "Call incoming" event which it blocks, times out, then
allowing the incoming call event to answer the other modem on the other
(now closed) line.

There is a simple workaround in TAPI that I've used for the moment, which
is to send:

Call objCallControl.Connect(False)

which just sends out a call event and returns immediately, regardless of
whether it's been answered or not.

I'm not sure this is safe, but at the moment, I don't know how to allow
that event to fire and answer the call while the call is still valid to be
answered.

Any ideas?

--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

Archived from group: microsoft>public>vb>syntax