Hello,
I have an anomoly that I am unable to explain.
My entire extensions.conf is attached. You can see that the [from-sip] and
[internal] dial plans are identical, each including 4 other contexts in the
same order:
[internal]
include => extensions
include => outbound
include => invalid
include
Brian Candler wrote:
Hello,
I have an anomoly that I am unable to explain.
My entire extensions.conf is attached. You can see that the [from-sip] and
[internal] dial plans are identical, each including 4 other contexts in the
same order:
[internal]
include => extensions
include => outbound
inc
On Thu, Sep 28, 2006 at 09:44:07AM -0500, Eric ManxPower Wieling wrote:
> You need the [general] and [global] sections
Well, if you read the attachment, you would see that I had a [general]
section:
[general]
autofallthrough=no
In what way would adding an empty [global] section alter the anomoly
Not having a [globals] section (even if it is empty) has caused Asterisk
to screw things up in the past. I think it causes contexts to not be found.
Brian Candler wrote:
On Thu, Sep 28, 2006 at 09:44:07AM -0500, Eric ManxPower Wieling wrote:
You need the [general] and [global] sections
Well
On Thu, 2006-09-28 at 15:05 +0100, Brian Candler wrote:
> I have an anomoly that I am unable to explain.
> ...
>
> [invalid]
> exten => _X!,1,Answer()
> exten => _X!,2,Background(pbx-invalid)
>
> [test]
> exten => 611,1,Answer()
> exten => 611,2,Playback(hello-world)
> exten => 611,3,Hangup()
>
>
On Fri, Sep 29, 2006 at 07:49:00PM +0200, Michael Neuhauser wrote:
> The order of include statements is important in 1.2, I don't know if
> this still holds for trunk/1.4. Could you please try to include the
> 'invalid' context as the last one (i.e., AFTER "include => test", not
> before) in both i
[invalid]> exten => _X!,1,Answer()> exten => _X!,2,Background(pbx-invalid)Are you sure that your invalid context is correctly written?I've never heard about this pattern match _X!As far as i know the wild card is the "."
So your invalid context should be: [invalid]exten => _X.,1,Answer()
exten =>
On Sun, Oct 01, 2006 at 03:55:45PM +0100, Marco Mouta wrote:
>
>[invalid]
>> exten => _X!,1,Answer()
>> exten => _X!,2,Background(pbx-invalid)
>Are you sure that your invalid context is correctly written?
>I've never heard about this pattern match _X!
>As far as i know the
