[Home]

Summary:ASTERISK-05113: no jump to n+101 when busy
Reporter:David Trcka (dtrcka)Labels:
Date Opened:2005-09-19 09:04:44Date Closed:2011-06-07 14:02:37
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:Dial application doesn't jump to n+101 priority after getting 'busy' state from called party.

Example part of extensions.conf:

[klienti]
exten => 597579111,1,NoOp(incoming call 597579111)
exten => 597579111,2,Dial(SIP/597579111,10)
exten => 597579111,3,NoOp(priority 3)
exten => 597579111,103,NoOp(priority 103)
exten => 597579111,104,Dial(SIP/597579111,30)
exten => 597579111,105,NoOp(priority 105)
exten => 597579111,106,Hangup
exten => 597579111,205,NoOp(priority 205)
exten => 597579111,206,Hangup

CLI output:

-- Accepting overlap call from '597578000' to '597579111' on channel 0/2, span 1
-- Starting simple switch on 'Zap/2-1'
-- Executing NoOp("Zap/2-1", "incoming call 597579111") in new stack
-- Executing Dial("Zap/2-1", "SIP/597579111|10") in new stack
-- Called 597579111
-- Got SIP response 486 "Busy Here" back from 85.135.1.186
-- SIP/597579111-0998 is circuit-busy
== Everyone is busy/congested at this time (1:0/1/0)
-- Executing NoOp("Zap/2-1", "priority 3") in new stack
== Auto fallthrough, channel 'Zap/2-1' status is 'CONGESTION'
-- Channel 0/2, span 1 got hangup request
-- Hungup 'Zap/2-1'
Comments:By: David Trcka (dtrcka) 2005-09-19 09:07:22

This setup worked fine before we updated to latest CVS-HEAD last weekend. Previous version was CVS-HEAD from Feb. 2005.

By: Clod Patry (junky) 2005-09-19 09:08:05

which date?
which Revision of app_dial.c?
We added that field, please use it.

You can use the following flag:
      'j' -- Jump to n+101 if all of the channels were busy.

By: David Trcka (dtrcka) 2005-09-19 09:18:14

Revision of appdial.c is 1.167. I really don't know the last used revision it worked fine. We have upgraded several times and noticed this (maybe) bug just today.

'j' flag is fine, works ok. Is it known change to dialplan behaviour? If it is, I will have to re-check all my dialplans according to this feature.

By: Clod Patry (junky) 2005-09-19 09:34:39

You will have to do one day or another, cause the N+101 behavior will disapear in the future.
You should check the DIALSTATUS instead.

By: paradise (paradise) 2005-09-19 11:20:24

have you set "priorityjumping=yes" in extension.conf?

By: Tilghman Lesher (tilghman) 2005-09-19 11:36:01

This is not a bug; it is a planned behavior change.  Please see the file UPGRADE.txt in your asterisk/ directory.  You need to specify the j option to Dial to get the old behavior.