Summary:ASTERISK-02486: [request] priority of same and next in extensions.conf
Reporter:revk (revk)Labels:
Date Opened:2004-09-27 14:17:41Date Closed:2004-10-02 21:16:12
Versions:Frequency of
Description:I often need a long sequence of commands in extension.conf, and as ever I come along later an need to insert one. A simple way to handle this would be for the parser to handle a priority of "same" and "next" to mean the same as the previous line or the previous line's priority plus one. At the start of a context same and next should both work out as 1 (or perhaps "same" is just stupid there and should be 0).


Currently using CVS-HEAD-09/27/04-19:15:14
Comments:By: Mark Spencer (markster) 2004-09-27 14:24:11

When would "same" ever be used?

By: revk (revk) 2004-09-27 14:33:51

To clarify - this suggestion is ONLY a parsing change, not any change to internal data structures.

By: revk (revk) 2004-09-27 14:35:30

same would be used where you want, e.g.

exten = _./100,next,SetCallerID(fred)
exten = _./101,same,SetCallerID(jim)
exten = _.,same,NoOp ; Other caller IDs not changed
exten = _.,next,Dial(zap/g1/${EXTEN})

Ie.. some times there are several different choices at the same priority.

By: Mark Spencer (markster) 2004-10-02 16:41:04

Added to CVS, also used "s" and "n" as shortcuts.

By: Russell Bryant (russell) 2004-10-02 21:16:12

not included in the 1.0 branch - feature