asterisk users - Sep 2005 - chan_capi-cm-0.6: hangup is detected really late

Hi,

the following szenario leads to a problem:

I connect an CAPI channel to an AGI-Script per Manager API. This Agi 
script starts the MeetMe-Application. The Person on the Capi Channel is 
now able to speak with the other conferess in the MeetMe-Room. But if 
the CAPI channel hangs up, the busy tone is streamed into the MeetMe 
Room for several seconds, until the CAPI HANGUP-Signal is finally send. 
After that the MeetMe-Instance is terminated and the busy tone stops.

If i realize the same szenario with SIP, everthing works fine.

So far i didn't try out ZAP.

Can anybody tell if this is an misbehaviour of chan_capi ? or something 
weird with MeetMe ??

have a nice day

tobias

On Fri, 23 Sep 2005, Tobias Wolf wrote:
> Hi,
> 
> the following szenario leads to a problem:
> 
> I connect an CAPI channel to an AGI-Script per Manager API. This Agi script
> starts the MeetMe-Application. The Person on the Capi Channel is now able
to
> speak with the other conferess in the MeetMe-Room. But if the CAPI channel
> hangs up, the busy tone is streamed into the MeetMe Room for several
seconds,
> until the CAPI HANGUP-Signal is finally send. After that the
MeetMe-Instance
> is terminated and the busy tone stops.
> 
> If i realize the same szenario with SIP, everthing works fine.
> 
> So far i didn't try out ZAP.
> 
> Can anybody tell if this is an misbehaviour of chan_capi ? or something
weird
> with MeetMe ??
This should not happen and is probably triggered by chan_capi. Can you 
please send me a verbose 5 / capi debug log? (at of the hangup sequence).

Armin