Summary:	ASTERISK-01260: manager and outgoing calls via CAPI are not cancelled if immediately hung up
Reporter:	mmenaz (mmenaz)	Labels:
Date Opened:	2004-03-21 12:45:43.000-0600	Date Closed:	2011-06-07 14:10:49
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Core/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	It works when the parameter are passed to asterisk manager for the call, my extensions rings, I pick up, wait some time, I hear the other ringing, now I can hang-up to cancel the call. But if instead pick up the extension, and hang up BEFORE hearing the call going, the call goes all the same (not cancelled)! And I can't cancel it with a subsequent "hangup" action :( I must wait that it timeouts :( ****** ADDITIONAL INFORMATION ****** The commands I use are like: Action: Login Username: dialout Secret: mysecret Action: Originate Channel: SIP/bt101 Context: default Exten: 03393188823 Priority: 1 Action: logoff
Comments:	By: James Golovich (jamesgolovich) 2004-03-21 14:33:18.000-0600 I really don't understand what your saying here.  Can you find one of the bug marshals on irc and describe it to them so they can update this info? By: James Golovich (jamesgolovich) 2004-03-21 16:45:54.000-0600 I got together with markit and from what I can tell it looks like a potential problem with chan_capi. What is happening here is the manager originate command is used to originate a call to the SIP phone with the extension/context/priority set to something that will Dial(CAPI, ...)  If the SIP phone gets hungup in a short amount of time, then the CAPI dial continues until the timeout passed (in his case 60 seconds) I suspect that chan_capi needs to call ast_check_hangup during the call setup to make confirm that it should continue with the dialing.  I had markit try dialing another SIP channel and it works as expected By: Brian West (bkw918) 2004-04-17 23:46:56 I agree with james, we need to have Kapejod look at chan_capi. bkw