asterisk users - Jul 2005 - [Asterisk-Dev] CVS HEAD behavior change: Beware!

I have just committed some changes to CVS HEAD that make the effort to 
eliminate 'priority jumping' applications sooner vs. later...

Basically, there is now a global option, settable in extensions.conf, to 
disable all priority jumping. The only application that has been updated 
to respect this option is app_dial, but I will update the "janitor 
project" list to reflect what needs to be done. The 'j' option to
Dial()
now has the exact opposite behavior it had before: if priority jumping 
has been disabled globally, the 'j' option will cause that instance of 
Dial() to do jumping. This will be the model for all applications to be 
converted over to.

Anyone who does not change the global setting in extensions.conf (it 
defaults to 'on' in the source code) will not experience any change in 
behavior unless they were using 'j' to suppress jumping in Dial(). In 
that case, you will need to global suppress jumping, and then enable it 
in any Dial() calls where you need it. As more applications get 
converted to use this new option, you may need to add more 'j' options 
in different parts of your dialplan.

New users of CVS HEAD (anyone who uses the 'make samples' starter 
configuration file) will not have priority jumping on by default, since 
it is explicitly turned off in the sample configuration file. We will 
try to get the remaining apps converted over as quickly as possible, so 
that their behavior will be consistent.
_______________________________________________
Asterisk-Dev mailing list
Asterisk-Dev@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-dev
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev

Just wondering... what is the idea behind this change?
And what should we use instead of jumping?
Can you give an example?


-----Oorspronkelijk bericht-----
Van: asterisk-users-bounces@lists.digium.com
[mailto:asterisk-users-bounces@lists.digium.com] Namens Kevin P. Fleming
Verzonden: dinsdag 26 juli 2005 19:30
Aan: Asterisk Developers Mailing List; Asterisk Users Mailing List -
Non-Commercial Discussion
Onderwerp: [Asterisk-Users] CVS HEAD behavior change: Beware!

I have just committed some changes to CVS HEAD that make the effort to 
eliminate 'priority jumping' applications sooner vs. later...

Basically, there is now a global option, settable in extensions.conf, to 
disable all priority jumping. The only application that has been updated 
to respect this option is app_dial, but I will update the "janitor 
project" list to reflect what needs to be done. The 'j' option to
Dial()
now has the exact opposite behavior it had before: if priority jumping 
has been disabled globally, the 'j' option will cause that instance of 
Dial() to do jumping. This will be the model for all applications to be 
converted over to.

Anyone who does not change the global setting in extensions.conf (it 
defaults to 'on' in the source code) will not experience any change in 
behavior unless they were using 'j' to suppress jumping in Dial(). In 
that case, you will need to global suppress jumping, and then enable it 
in any Dial() calls where you need it. As more applications get 
converted to use this new option, you may need to add more 'j' options 
in different parts of your dialplan.

New users of CVS HEAD (anyone who uses the 'make samples' starter 
configuration file) will not have priority jumping on by default, since 
it is explicitly turned off in the sample configuration file. We will 
try to get the remaining apps converted over as quickly as possible, so 
that their behavior will be consistent.
_______________________________________________
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

TWV wrote:
> Just wondering... what is the idea behind this change?
> And what should we use instead of jumping?
> Can you give an example?
Jumping to a specific priority is both confusing and limiting. 
Applications are now starting to set variables instead of jumping.  For 
exmaple Dial would jump to the current priority + 101 when it got a BUSY 
and jump to the current priority + 1 on ANY other condition.  Very 
limiting.  If instead Dial always went to the next priority, but set a 
variable, maybe called DIALSTATUS, to provide information about the 
result of the call, then we have a MUCH more flexible method to handle 
the various results of a Dial.

-- 
Eric Wieling * BTEL Consulting * 504-210-3699 x2120

Eric Wieling aka ManxPower wrote:
> TWV wrote:
> 
>> Just wondering... what is the idea behind this change?
>> And what should we use instead of jumping?
>> Can you give an example?
> 
> 
> Jumping to a specific priority is both confusing and limiting. 
> Applications are now starting to set variables instead of jumping.  For 
> exmaple Dial would jump to the current priority + 101 when it got a BUSY 
> and jump to the current priority + 1 on ANY other condition.  Very 
> limiting.  If instead Dial always went to the next priority, but set a 
> variable, maybe called DIALSTATUS, to provide information about the 
> result of the call, then we have a MUCH more flexible method to handle 
> the various results of a Dial.
There is always DIALSTATUS...


-- 
Kristian Kielhofner