[asterisk-dev] i extension does not match on initial context - bug or not?
leif.madsen at asteriskdocs.org
Fri Jan 9 07:54:59 CST 2009
Nir Simionovich wrote:
> Philipp Kempgen wrote:
>> Klaus Darilion schrieb:
>>> Benny Amorsen schrieb:
>>>> Dmitry Andrianov <dimas at dataart.com> writes:
>>>>> There is NO functionality for catch-all currently exist. Extension
>>>>> can be alphanumeric so just [0-9*+] is not enough. The closest
>>>>> pattern would be "_." which matches anything at all but the problem
>>>>> with it is that it also matches "special" extensions like h, i, t,
>>>> It is a bit sad that the special extensions live in the same
>>>> namespace as normal extensions. The reasons are historical, of
>>>> course, from when Asterisk was mostly concerned with connecting to
>>>> the PSTN, but these days it is becoming a problem.
>>> Yes, this should be splitted into separate name spaces. In config we
>>> could use for example @i or @s to address the special extensions.
> Hmmm... well, that's a +1 on my behalf as well.
Let me know when someone writes up a patch and posts it to the bug
tracker, and I'll be sure it takes the necessary steps that all issues
in the tracker take.
More information about the asterisk-dev