Detecting call state on outbound calls

From: Brett McCoy

On 11/3/2003 2:40:47 PM, Gerry Gilmore wrote:

>1) Don;t rely on the results
>of a call to gc_GetCallState()
>or anything like that. Use the
>logic of your program's state
>machine and the events coming
>through to let you know what
>state you're in.
>
>2) Relevant to 1) above, since
>the call to gc_MakeCall()
>returns immediately, you must
>be using the async model (or
>something is very, very
>wrong..). Again, just track
>the events as they come along
>(Proceeding, etc.)

I suspect something is very, very wrong in our configuration. A very simple test program that does nothing except dial out (using sync model) exhibits this behavior, I can never correctly detect when the outbound call has terminated. I have no problems with inbound calls -- the gc_GetCallState() function tells me the call has disconnected at the point when it really has.

We are using DM/V960-T1 boards, BTW, with pdk_us_mf_io protocol.

-- Brett

To reply: mailto:General.26247@pysdiscussext.py.intel.com
To start a new topic: mailto:General@pysdiscussext.py.intel.com
To login: http://members.support.dialogic.com/wbproxy/wbpx.dll/~general
Received on Mon Nov 03 16:34:07 2003