> I am stumped as well, you don't have any extension defined for either
> 0, _0X, or _0X.
> So I got no clue why *you* are stumped, in fact 1625 is treated
> special, because it got an extension.
Okay; thanks! I mis-understood the mechanism. I didn't think
extensions.conf actually came into pla
On 1/7/06, Ken D'Ambrosio <[EMAIL PROTECTED]> wrote:
> > Post your extensions.conf and what's on the CLI (asterisk -r)
>
> As requested:
>
> # cat /etc/asterisk/extensions.conf
> [incoming]
> exten => s,1,Answer()
> exten => s,n,NoOp(CallerID is ${CALLERID})
> exten => s,n,NoOp(DID is ${DNID})
> ex
> Post your extensions.conf and what's on the CLI (asterisk -r)
As requested:
# cat /etc/asterisk/extensions.conf
[incoming]
exten => s,1,Answer()
exten => s,n,NoOp(CallerID is ${CALLERID})
exten => s,n,NoOp(DID is ${DNID})
exten => s,n,Background(enter-ext-of-person)
exten => 1625,1,Playback(di
Ken D'Ambrosio wrote:
I've got a T1 (E&M wink). Our four-digit inbound DNIS numbers are in the
range of 0600 - 1699. However, the second that the "0" is seen on an
in-bound 06xx call, it stops listening for any more digits, and
immediately tries to route the call. My 16xx numbers wait for all
I've got a T1 (E&M wink). Our four-digit inbound DNIS numbers are in the
range of 0600 - 1699. However, the second that the "0" is seen on an
in-bound 06xx call, it stops listening for any more digits, and
immediately tries to route the call. My 16xx numbers wait for all four
digits before tryin
