The "s" extension did not catch the incoming call. It was only when I
added a specific 366 or the _. wildcard that I was able to capture the
incoming call.
Mitch
On 10/12/2012 10:18 AM, A J Stiles wrote:
If (and only if) all the extensions you are using in all your contexts are
numeric, t
On Friday 12 October 2012, Mitch Claborn wrote:
> Converting this customer from a MiTel system to asterisk. Discovered
> that the inbound calls from the T1 are going to extension 366. (This
> was mapped in the MiTel for some arcane purpose.) The dial plan I am
> currently using is shown below. W
On Fri, Oct 12, 2012 at 9:10 AM, Mitch Claborn wrote:
> Converting this customer from a MiTel system to asterisk. Discovered that
> the inbound calls from the T1 are going to extension 366. (This was mapped
> in the MiTel for some arcane purpose.) The dial plan I am currently using
> is shown be
Converting this customer from a MiTel system to asterisk. Discovered
that the inbound calls from the T1 are going to extension 366. (This
was mapped in the MiTel for some arcane purpose.) The dial plan I am
currently using is shown below. When loading the dial plan, I get this
warning:
WA
