asterisk users - Sep 2006 - extensions.conf strangeness

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 => test

[from-sip]
include => extensions
include => outbound
include => invalid
include => test

I can place calls between extensions as expected.

Now here's the problem. If I dial '611' on a zaptel line (context
"internal"), I get the "Hello World" message from the
"test" context as
expected. However if I dial '611' on a SIP phone (context
"from-sip"), I get
"I am sorry, that is not a valid extension"

If I modify extensions.conf as follows:

[from-sip]
include => extensions
include => outbound
;include => invalid       <<< comment out this line
include => test

then it works: dialling 611 from a SIP phone gives "Hello World".

Could someone please explain to me why the dialplan seems to behave
differently for calls originating from SIP and zaptel lines in this instance?

I am running Asterisk from SVN trunk, compiled two weeks ago (September
13th)

Thanks,

Brian Candler.
-------------- next part --------------
[general]
autofallthrough=no

[incoming]
; incoming calls from the FXO port are directed to this context from zapata.conf
include => extensions

exten => s,1,Answer()
exten => s,2,Wait(1)
exten => s,3,Background(enter-ext-of-person)
exten => i,1,Background(pbx-invalid)
exten => t,1,Playback(vm-goodbye)
exten => t,2,Hangup()

[macro-ext]
exten => s,1,Dial(${ARG1},10)
exten => s,2,Playback(vm-nobodyavail)
exten => s,3,Hangup()
exten => s,102,Playback(tt-allbusy)
exten => s,103,Hangup()

[extensions]
exten => 101,1,Macro(ext,Zap/1)
exten => 102,1,Macro(ext,Zap/2)
exten => 301,1,Macro(ext,SIP/test301)

[outbound]
exten => _9.,1,Dial(Zap/4/${EXTEN:1})
exten => _9.,2,Congestion()
exten => _9.,102,Congestion()

[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()

[internal]
include => extensions
include => outbound
include => invalid
include => test

[from-sip]
include => extensions
include => outbound
include => invalid
include => test

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
> include => invalid
> include => test
> 
> [from-sip]
> include => extensions
> include => outbound
> include => invalid
> include => test
> 
> I can place calls between extensions as expected.
You need the [general] and [global] sections

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 I am
seeing?

Thanks,

Brian.

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, 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 I am
> seeing?
> 
> Thanks,
> 
> Brian.
>

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()
> 
> [internal]
> include => extensions
> include => outbound
> include => invalid
> include => test
> 
> [from-sip]
> include => extensions
> include => outbound
> include => invalid
> include => test
> 
> ...
> [summary of cut text: 611 from SIP -> invalid; 611 from zaptel line
-> test]
>
>I am running Asterisk from SVN trunk, compiled two weeks ago (September
>13th)
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 internal and from-sip and then test again?
-- 
Dr. Michael Neuhauser                              mailto:mike@firmix.at
Firmix Software GmbH                                  sip:mike@firmix.at
Vienna/Austria/Europe                               tel:+43-1-7890849-30
Linux Development and Services                     http://www.firmix.at/