[Home]

Summary:ASTERISK-10736: extensions.conf looks for a [default] context, even if not defined in zapata.conf
Reporter:Des Dougan (ddougan)Labels:
Date Opened:2007-11-10 21:58:15.000-0600Date Closed:2011-06-07 14:08:20
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Core/Configuration
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:Although I can't find it documented anywhere (I have checked both editions of TFOT, as well as searching the wiki), it appears that extensions.conf requires a default context, even if the context defined in zapata.conf has a different name.

****** ADDITIONAL INFORMATION ******

This is the error message displayed in the CLI:

[Nov 10 16:52:24] WARNING[12473]: pbx.c:2450 __ast_pbx_run: Channel 'Zap/4-1' sent into invalid extension 's' in context 'default', but no invalid handler
[Nov 10 16:52:24] WARNING[12473]: pbx.c:2450 __ast_pbx_run: Channel 'Zap/4-1' sent into invalid extension 's' in context 'default', but no invalid handler

Once I defined a context called default in extensions.conf, the messages stopped appearing.

My zapata.conf is as follows:

# more zapata.conf
[trunkgroups]
; Trunk groups are used for NFAS or GR-303 connections.

[channels]
;
; Default context
;
usedistinctiveringdetection=yes
usecallerid=yes
hidecallerid=no
callwaiting=no
threewaycalling=yes
transfer=yes
echocancel=yes
echotraining=yes
faxdetect=both

context=internal        ; Uses the [internal] context in extensions.conf
signalling=fxo_ks       ; Use FXO signalling for an FXS channel
channel => 1            ; Telephone attached to port 1

context=incoming        ; Incoming calls go to this context in extensions.conf
signalling=fxs_ks       ; Use FXS signalling for an FXO channel
channel => 4            ; PSTN attached to port 4
Comments:By: Dmitry Andrianov (dimas) 2007-11-11 05:52:07.000-0600

What is the output of 'zap show channels' command?
By: Tilghman Lesher (tilghman) 2007-11-11 10:39:07.000-0600

I'm guessing that you don't have an "s" extension in the "incoming" context, because that would be why chan_zap is searching for a matching extension in the "default" context.
By: Des Dougan (ddougan) 2007-11-11 16:16:49.000-0600

> zap show channels
  Chan Extension  Context     Language   MOH Interpret
pseudo            incoming                   default
     1            internal                   default
     4                                       default

This is my incoming context:

[incoming]
;
; incoming calls from the FXO port are directed to this context from zapata.conf
;
exten => s,1,Answer()
exten => s,n,Background(custom/welcome-message)
exten => s,n,WaitExten()

exten => 1,1,Goto(internal,6000,1)

exten => 2,1,Goto(internal,6002,1)

exten => 8,1,Directory(internal,internal,f)
exten => 9,1,Directory(internal,internal)

exten => i,1,Playback(pbx-invalid)
exten => i,2,Goto(incoming,s,1)
exten => t,1,Playback(vm-goodbye)
exten => t,2,Hangup()


By: Dmitry Andrianov (dimas) 2007-11-11 16:50:51.000-0600

well, to me it does not look like your Zap/4 is configured for 'incoming' context. According to 'zap show channels', it is configured for 'default'
By: Des Dougan (ddougan) 2007-11-11 17:02:35.000-0600

The "default" you noted is a result of the formatting of what I pasted being crunched together.

The channels show like this:

Chan    Context
pseudo  incoming
    1  internal
    4

So 4 shows blank under the Context label. I have no idea if it should show differently or not, as I have no clue where "pseudo" comes from. I compiled and installed per TFOT, if that's any help.

Is there a Zap setting other than in zapata.conf I might have missed?
By: Tilghman Lesher (tilghman) 2007-11-11 17:48:44.000-0600

Okay, so then something is wrong with your zapata.conf.  Care to paste the non-commented lines?

More particularly, I suspect that you have another "context=" line before your "channel => 4" line.


By: Des Dougan (ddougan) 2007-11-11 18:05:09.000-0600

The code I posted originally is my entire zapata.conf - I cleaned out the remaining comments and sample code when I was trying to debug the problem. Here it is again:

hudson:/etc/asterisk # more zapata.conf
[trunkgroups]
; Trunk groups are used for NFAS or GR-303 connections.

[channels]
;
; Default context
;
usedistinctiveringdetection=yes
usecallerid=yes
hidecallerid=no
callwaiting=no
threewaycalling=yes
transfer=yes
echocancel=yes
echotraining=yes
faxdetect=both

context=internal        ; Uses the [internal] context in extensions.conf
signalling=fxo_ks       ; Use FXO signalling for an FXS channel
channel => 1            ; Telephone attached to port 1

context=incoming        ; Incoming calls go to this context in extensions.conf
signalling=fxs_ks       ; Use FXS signalling for an FXO channel
channel => 4            ; PSTN attached to port 4
hudson:/etc/asterisk #

I originally had the last three lines (context=incoming, etc.) prior to the context=internal lines, and switched them after some snippet I read while Googling. And just to confirm, I can make and receive PSTN calls OK.
By: Tilghman Lesher (tilghman) 2007-11-12 10:38:18.000-0600

Ah, if you can make and receive PSTN calls, then zapata.conf is not the issue.  You probably have another channel starting in the [default] context, then.  Could be as simple as omitting the context= line in iax.conf or sip.conf in the appropriate section.  You could probably fix this issue by setting another context line in the [general] section of sip.conf or iax.conf.  "default,s,1" is the extension/priority that the PBX core searches for if you start in a nonexistent context.

In any case, I'm confident that this is a configuration error, although you may not have found where that is yet.  If you want further assistance, please come on the #asterisk-bugs channel on irc.freenode.net and ask a bug marshal for assistance.  Be prepared to give remote root access to your machine, and we'll find the configuration error in fairly short order.