Any news for this problem.
Who has this problem

Why you don’t answer.

Any news for this problem.
Who has this problem

Hello my friends,

Previously, we developed fastagi application with Erlang to run on asterisk
1.4, it run very well.

But when we try to migrate this application to interface with asterisk
1.6.2.13( the same with 1.6.1 or 1.6.0),
We found the hangup issue there, the hangup event will delayed a few minutes
when callee hangup , or make an hangup
request on cli. The channel be hungup don’t release at once on hangup action
performed. And on AMI , there is also no
hangup event output at once. So my fastagi application hold there too.
It’ll delay a few minutes until the hangup
event output from cli or AMI.we tried dial over dahdi and sip channel, the
result
is same.

This issue don’t happen on 1.4, has anyone here experienced the same issue?
And share the resolving experiences here ?
Is there any special configuration to control this hangup delay behavior?

Thank you in advance!

Best Regards,

Thomas Liu

My application fires several calls thru AMI ORIGINATE command.

For example if I have 3 operators I do 3 ORIGINATEs.

My trouble is when one operator quit for some reason, I should kill the
corresponding ORIGINATE.

Of course, I could let the call ring and hangup after the customer pick-up.

But this is not the case, I do have to kill the corresponding ORIGINATE.

I could execute a soft hangup, but I am not aware the channel that ORIGINATE
is using until customer either pick-up or not answer – generating a
OriginateResponse event.

I have tried to send a STATUS command on the ActionId, but the answer is
assync and I can’t trust on it.

I would appreciate any help.

Thanks,

Valter

Hi,

I have this on an Aastra phone:

Button 1: Login English Queue
Button 2: Login French Queue
Button 3: Logout both English and French

I am out of buttons and using only three buttons I want my third button to
be smarter. Currently the third button does a QueueRemoveMember to both
English and French Queue at the same time. I want this button to be smarter
to and to check and see if the Agent is logged into only English to only do
a Remove on English or if the Agent is only logged into French to only log
out French. Same goes for both, if both are logged in to log out both.

Currently I have this for Third Button:

exten => 999999,1,Answer
exten =>
999999,n,RemoveQueueMember(900|Local/${CALLERID(num)}@from-internal/n)
exten =>
999999,n,RemoveQueueMember(899|Local/${CALLERID(num)}@from-internal/n)
exten => 999999,n,Hangup

900 is English and 800 is Spanish Queue numbers.

P.S. Is there a way to do exten = s rather than exten = 999999 as someone
from outside might find out about the 999999 extension and try to log into
it? This is for an Aastra phone with XML support.

Thanks