This has been discussed before, but here is our experience :
Using globalcall and bayonne 1.2.14 :
When dialing a number, if the called line is busy, we don't get the "^busy" nor "^busytone" event. Instead, we get a "^hangup" event. If we look at what dialogic is sending us, we can see (chronologically) :
- a GCEV_PROCEEDING event, - a GCEV_DISCONNECTED event (which is processed as an incoming call disconnection), AND THEN : - a TDX_CALLP with a CR_STOPD as a ATDX_CPTERM condition (which is not processed)
I think the processing of the event GCEV_DISCONNECTED is not correct in this state : we should not dx_setevtmsk() on the device, as there is still one unprocessed event in the queue (the TDX_CALLP). By the way, if the TDX_CALLP event was processed, the script would get the "^busy" or "^busytone" event.
Am I wrong saying that ?
Julien, didn't you say you had made something about the dx_setevtmsk issue ?
As for your question (Any body is having problem with Dialogic Globalcall Drivers in Bayonne?) I would say, we have some small problems (such as the one described in that mail). We try to manage them, sometimes without alerting the list. Maybe we could mention them more often...
Cheers, FdR/ED
-- Etoile Di�se - www.etoilediese.com
_______________________________________________ Bayonne-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bayonne-devel
