Detecting call state on outbound calls

From: General Listmanager <General.listmanager@pysdiscussext.py.intel.com>
Date: Tue Nov 04 2003 - 11:55:08 EST

From: Brett McCoy

On 11/4/2003 4:09:53 AM, Martin Steer wrote:

>I wouldn't advise using sync
>model - instead use async and
>then process the incoming
>events to see what is
>happening. If your makecall
>block parameters don't match
>the configuration your CO is
>expecting the CO will reject
>(drop) the call without
>actually dialling out.

The issue is that the call *is* still dialing out, we just can't ever detect when it has disconnected because we get an initial disconnect state after gc_MakeCall() returns so the application thinks the call is in the disconnected state and proceeds to issue a gc_DropCall() and gc_ReleaseCall() for the outbound linedevice.

-- Brett

To reply: mailto:General.26259@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 Tue Nov 04 12:02:18 2003

This archive was generated by hypermail 2.1.8 : Sat Jul 16 2005 - 03:48:30 EDT