Summary:	ASTERISK-01368: Strange behavior with successive Dials
Reporter:	jharragi (jharragi)	Labels:
Date Opened:	2004-04-07 13:44:06	Date Closed:	2011-06-07 14:04:59
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Core/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	It appears that when dial terminates there may still be locks or launched processes yet to complete or release that interferes with the operation of the next priority. (Some of the behavior I'm reporting is from old observations - but I doubt it has been addressed) ****** ADDITIONAL INFORMATION ****** I'm not sure that this should be classified as a bug - but it is not exactly a feature request either. The problem with successive Dials can be fixed by inserting a wait (sometimes longer than 1) between the dials. The first context fails if machine PRI_B is down - the intention is to try machine PRI_C - but priority 2 fails and congestion is played back. [outlocalpri_priority_2_fails] exten => _9NXXXXXX,1,Dial(IAX2/REMOTE_A@PRI_B/${EXTEN}|2) exten => _9NXXXXXX,2,Dial(IAX2/REMOTE_A@PRI_C/${EXTEN}) exten => _9NXXXXXX,3,Congestion ...this version works... [outlocalpri_works] exten => _9NXXXXXX,1,Dial(IAX2/REMOTE_A@PRI_B/${EXTEN}|2) exten => _9NXXXXXX,2,Wait(1) exten => _9NXXXXXX,3,Dial(IAX2/REMOTE_A@PRI_C/${EXTEN}) exten => _9NXXXXXX,4,Congestion exten => _9NXXXXXX,102,Goto(2) exten => _9NXXXXXX,104,Goto(4) ...here is different manifestation of the problem. The caller can't hear ring on the second priority. exten => 6099,1,Dial,Zap/8|20  ; experimental exten => 6099,2,Dial,Zap/7|20  ; experimental Inserting a wait between the two priorities (usually) allows the caller to hear ringing. exten => 6099,2,Wait(1)             ; experimental It appears that when dial terminates there may still be locks or launched processes yet to complete or release that interferes with the operation of the next priority. There may be reasons why dial acts this way. So I figure it is better to ask if this is desired behavior before launching into an investigation or attempting to modify this. At any rate, the workarounds I have found are kind of cumbersome.
Comments:	By: Brian West (bkw918) 2004-04-10 07:01:23 you can indicate ringing: show application Ringing By: exomorph (exomorph) 2004-04-16 01:28:24 Can you please try this slight modification, and tell me if you still have a "no ring" problem? [outlocalpri_priority_2_fails] exten => _9NXXXXXX,1,Dial(IAX2/REMOTE_AA@PRI_B/${EXTEN}|2) exten => _9NXXXXXX,2,Dial(IAX2/REMOTE_A@PRI_C/${EXTEN}) exten => _9NXXXXXX,3,Congestion I want to see if its because asterisk thinks its the same "end point" (IAX2/REMOTE_A in this case) If I do: exten => 99,1,Dial(SIP/REMOTE_A,2) exten => 99,2,Dial(SIP/REMOTE_A) I also see the problem, but changing to: exten => 99,1,Dial(SIP/REMOTE_AA,2) exten => 99,2,Dial(SIP/REMOTE_A) Allows for ringing on the second call. By: exomorph (exomorph) 2004-04-16 01:32:02 Further to this... With my SIP example above, I can not always reproduce this problem. By: Brian West (bkw918) 2004-04-16 15:32:50 Moved to 1434 as they are the same thing almost!