"failed so falling back to exten 's'"

Asterisk Asterisk Support
1

I have just finished installing and configuring a TDM11B card on Asterisk 1.4. I’ve tested an inbound PSTN call using this extensions.conf section:

[from-pstn]
; incoming calls from the FXO port are directed to this context from zapata.conf
exten => s,1,Answer( )
exten => s,2,Echo( )

The corresponding zapata.conf configuration is:

[channels]
;
; Default context
;
context=from-pstn

When I call, Asterisk answers and I can hear the echo (if somewhat faint). However, in the CLI, I see this:

-- Starting simple switch on 'Zap/4-1'
-- Detected ring pattern: 0,0,0
-- Checking 0,0,0
-- Distinctive Ring matched context

== Starting Zap/4-1 at ,s,1 failed so falling back to exten ‘s’
== Starting Zap/4-1 at ,s,1 still failed so falling back to context ‘default’
[Sep 8 14:27:10] WARNING[4610]: pbx.c:2450 __ast_pbx_run: Channel ‘Zap/4-1’ sent into invalid extension ‘s’ in context ‘default’, but no invalid handler
– Hungup ‘Zap/4-1’
– Starting simple switch on ‘Zap/4-1’
[Sep 8 14:27:19] NOTICE[4613]: chan_zap.c:6367 ss_thread: Got event 18 (Ring Begin)…
[Sep 8 14:27:19] ERROR[4613]: callerid.c:564 callerid_feed: fsk_serie made mylen < 0 (-1)
[Sep 8 14:27:19] WARNING[4613]: chan_zap.c:6399 ss_thread: CallerID feed failed: Success
– Detected ring pattern: 205,0,0
– Checking 0,0,0
– Checking 0,0,0
– Checking 0,0,0
[Sep 8 14:27:19] WARNING[4613]: chan_zap.c:6499 ss_thread: CallerID returned with error on channel ‘Zap/4-1’
– Executing [s@from-pstn:1] Answer(“Zap/4-1”, " ") in new stack
– Executing [s@from-pstn:2] Echo(“Zap/4-1”, " ") in new stack
== Spawn extension (from-pstn, s, 2) exited non-zero on ‘Zap/4-1’
– Hungup ‘Zap/4-1’

If I place include => from-pstn in the otherwise blank default context, I see a shorter log cycle, but still with the failed messages:

-- Starting simple switch on 'Zap/4-1'
-- Detected ring pattern: 0,0,0
-- Checking 0,0,0
-- Distinctive Ring matched context

== Starting Zap/4-1 at ,s,1 failed so falling back to exten ‘s’
== Starting Zap/4-1 at ,s,1 still failed so falling back to context ‘default’
– Executing [s@default:1] Answer(“Zap/4-1”, " ") in new stack
– Executing [s@default:2] Echo(“Zap/4-1”, " ") in new stack
== Spawn extension (default, s, 2) exited non-zero on ‘Zap/4-1’
– Hungup ‘Zap/4-1’

Why do I get the failed messages? This is a simple test, and the two contexts match.

Thanks,

Des

2

Hi
Could you post the zapata.conf as it looks as if its set to context=default and from what you have posted you havent got one.

Ian

3

Ian,

See below for the current zapata.conf I have:

Thanks,

Des

[trunkgroups]
;
; Trunk groups are used for NFAS or GR-303 connections.
;
[channels]
;
; Default context
;
context=from-pstn
;
signalling=fxs_ks
;
;
; Whether or not to do distinctive ring detection on FXO lines
;
usedistinctiveringdetection=yes
;
; Whether or not to use caller ID
;
usecallerid=yes
;
; Whether or not to hide outgoing caller ID (Override with *67 or *82)
;
hidecallerid=no
;
; Whether or not to enable call waiting on internal extensions
;
callwaiting=no
;
; Support three-way calling
;
threewaycalling=yes
;
; Support flash-hook call transfer (requires three way calling)
; Also enables call parking (overrides the ‘canpark’ parameter)
;
transfer=yes
;
; Stutter dialtone support: If a mailbox is specified without a voicemail
; context, then when voicemail is received in a mailbox in the default
; voicemail context in voicemail.conf, taking the phone off hook will cause a
; stutter dialtone instead of a normal one.
;
; If a mailbox is specified with a voicemail context, the same will result
; if voicemail received in mailbox in the specified voicemail context.
;
; for default voicemail context, the example below is fine:
;
;mailbox=1234
;
; for any other voicemail context, the following will produce the stutter tone:
;
;mailbox=1234@context
;
; Enable echo cancellation
;
echocancel=yes
;
echotraining=yes
;
faxdetect=both
;
channel => 4

4

I’ve been running asterisk -r with verbose set to 3, and saw this today when a PSTN call came in:

-- Starting simple switch on 'Zap/4-1'
-- Detected ring pattern: 0,0,0
-- Checking 0,0,0
-- Distinctive Ring matched context

== Starting Zap/4-1 at ,s,1 failed so falling back to exten ‘s’
== Starting Zap/4-1 at ,s,1 still failed so falling back to context ‘default’
– Executing [s@default:1] Answer(“Zap/4-1”, “”) in new stack

The context seems to be null in the first “Starting Zap/4-1” line, which I hadn’t noticed before. I do have it set in zapata.conf, per one of the earlier messages in this thread. Can anyone suggest why there is no value being picked up?

Thanks,

Des

5

I’ve been running asterisk -r with verbose set to 3, and saw this today when a PSTN call came in:

-- Starting simple switch on 'Zap/4-1'
-- Detected ring pattern: 0,0,0
-- Checking 0,0,0
-- Distinctive Ring matched context

== Starting Zap/4-1 at ,s,1 failed so falling back to exten ‘s’
== Starting Zap/4-1 at ,s,1 still failed so falling back to context ‘default’
– Executing [s@default:1] Answer(“Zap/4-1”, “”) in new stack

The context seems to be null in the first “Starting Zap/4-1” line, which I hadn’t noticed before. I do have it set in zapata.conf, per one of the earlier messages in this thread. Can anyone suggest why there is no value being picked up?

Thanks,

Des