|Summary:||ASTERISK-02845: 'i' extension doesnt match invalid dialled extensions, only menu responses|
|Date Opened:||2004-11-17 17:59:11.000-0600||Date Closed:||2011-06-07 14:10:09|
|Description:||When I dial an invalid extension I get the congestion tone, even with an 'i' extension in the current context. This happens at least with a DISA and SIP calls, a user on irc reports this happens too with his PRI connection.|
If I include a context with _. at the end of the local context, It matches on invalid numbers, but causes an undesireable 5 second delay in dialled numbers from being processed, probably because they match both the correct dialplan entry and _.
This may be a misunderstanding on my part or a deliberate design decision to have 'i' for incorrect menu responses only. It seems natural to have it match invalid extensions called too.
|Comments:||By: Brian West (bkw918) 2004-11-17 18:07:08.000-0600|
This is a config issue post your extensions.conf
By: Mark Spencer (markster) 2004-11-17 18:13:20.000-0600
"i" is only for invalid extensions dialed at WaitExten or similar, not for channel drivers, etc. where there is established behaviors for that. IF you want a match all, use _X.
By: darkskiez (darkskiez) 2004-11-17 18:33:21.000-0600
If I include a context with _X. at the end of the local context, It matches on invalid numbers, but causes an undesireable 5 second delay in correctly dialled numbers from being processed. Setting the digit timeout shorter is also undesireable as it does not allow enough time for correct entry to occur.
Asterisk does not detect that a valid extension has been dialled and execute it instantly as it is waiting for that extension to match the longer _X. sequence. There seems to be no way to specify matching of shorter sequences first. The downside of that would be you couldn't have extensions say "444" and "4446" as 444 would match first, but I would have expected that as default behaviour.
By: Mark Spencer (markster) 2004-11-17 18:47:29.000-0600
Well, "i" isn't supposed to work that way, so you can either come up with the appropriate patterns you want to match or... well... i don't know, you can make another suggestion, but it shouldn't be "run i whenever somebody enters an invalid extension."