| Summary: | ASTERISK-06661: ChanIsAvail always uses priority juming even if the option is not set explicitly | ||
| Reporter: | Kai Militzer (kmilitzer) | Labels: | |
| Date Opened: | 2006-03-30 05:06:44.000-0600 | Date Closed: | 2011-06-07 14:07:23 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | ChanIsAvail should, according to the helptext, only support priority jumping, if the option "j" is used. This is not the case, ChanIsAvail always uses priority jumping (even if not set with the option) if the result is negativ (= no channel is available) it jumps to +101 resulting in an error if this priority does not exist. | ||
| Comments: | By: BJ Weschke (bweschke) 2006-03-30 08:15:29.000-0600 I just double checked the code in both places. (1.2 and /trunk). It will not app_chanisavail will not attempt to jump w/o the 'j' option OR if you have priorityjumping=yes in extensions.conf. If you have priorityjumping=yes in extensions.conf, the global option then gets set, and it doesn't matter whether you specify 'j' or not. If you're still having trouble with this, please reopen and post a DEBUG / VERBOSE trace of this call and we'll have another look. | ||