I was wondering why *...@default should match '_*[0-9a-zA-Z].*0.'
in 1.6.13. Who is making the parse error, * or me?
CLI dialplan show *...@default
'_*[0-9a-zA-Z].*0.' =
1. NoOp(${EXTEN}) [pbx_config]
2. Set(accountcode=${CUT(EXTEN,*,2)})
On 12/20/2010 11:35 AM, Daniel Tryba wrote:
I was wondering why *...@default should match '_*[0-9a-zA-Z].*0.'
in 1.6.13. Who is making the parse error, * or me?
CLI dialplan show *...@default
'_*[0-9a-zA-Z].*0.' =
1. NoOp(${EXTEN}) [pbx_config]
2.
On Monday 20 December 2010 11:35:21 Daniel Tryba wrote:
I was wondering why *...@default should match '_*[0-9a-zA-Z].*0.'
in 1.6.13. Who is making the parse error, * or me?
CLI dialplan show *...@default
'_*[0-9a-zA-Z].*0.' =
1. NoOp(${EXTEN}) [pbx_config]
On Mon, Dec 20, 2010 at 12:27:46PM -0600, Jason Parker wrote:
'_*[0-9a-zA-Z].*0.'
'.' stops further matching. Your extension ends up being (effectively)
shortened to _*[0-9a-zA-Z].
That explains a lot, never read it this way before. Thanks for the eye
opener.
What I'm looking for is a
