FreePBX 2.4.0 incoming call being dropped

hi There, I have a fresh centos 5, FreePBX latest installed. I have two X100P analog cards installed and Already created extensions, an ivr, and some other things. I can dial out perfectly, but when i dial in, freepbx gets the call and plays a “goodbye” message and then hangs up.
I have no idea where is this context going to play that message. This is the call coming in:

In this example im using the second trunk to call the first trunk (i have tried calling from my cellphone but it’s too expensive)
First trunk is g1 with phone number 3918174, second trunk is g2 with phone number 3918175. Im using extension 101 to dial.

– Called g2/3918174
– Zap/2-1 answered SIP/101-09691d60
– Starting simple switch on ‘Zap/1-1’
– Executing [[email protected]:1] Playback(“Zap/1-1”, “vm-goodbye”) in new stack ****WHY IS THIS BEING PLAYED???
– <Zap/1-1> Playing ‘vm-goodbye’ (language ‘en’)
– Executing [[email protected]:2] Macro(“Zap/1-1”, “hangupcall”) in new stack
– Executing [[email protected]:1] ResetCDR(“Zap/1-1”, “w”) in new stack
– Executing [[email protected]:2] NoCDR(“Zap/1-1”, “”) in new stack
– Executing [[email protected]:3] GotoIf(“Zap/1-1”, “1?skiprg”) in new stack
– Goto (macro-hangupcall,s,6)
– Executing [[email protected]:6] GotoIf(“Zap/1-1”, “1?skipblkvm”) in new stack
– Goto (macro-hangupcall,s,9)
– Executing [[email protected]:9] GotoIf(“Zap/1-1”, “1?theend”) in new stack

I have setup an incoming route that matches any / any and it should go to an IVR. So I really have no idea why is playing that message.

Thanks for your help.

Erick.

your zapata.conf configurations are wrong, you need context=from-zaptel for your trunks. Note this line:

-- Executing [[email protected]:1] Playback("Zap/1-1", "vm-goodbye") in new stack ****WHY IS THIS BEING PLAYED???

There is no “default” context in FreePBX.

Indeed going to /etc/asterisk/zapata.conf fixed the issue. Just one question, Why freepbx did not took care of it? or…was the centos 5.1 howto manual i used to install it…incomplete?

Thanks a lot for pointing right to the configuration issue!!!

FreePBX does not setup zapata.conf. It has a sample configuration. And the defaults typically used in various genzaptelconf scripts are usually wrong.

Hi,

I have read this post a few times, it fixed my problem at least once! So, thanks for that.

I am now getting the same issue again, but I can not find anywhere that the context=default in my config files.

Asterisk 1.4.21.2
FreePBX 2.6.0.0

The CLI output:

== Starting Zap/1-1 at DID_trunk_1,s,1 failed so falling back to exten ‘s’
== Starting Zap/1-1 at DID_trunk_1,s,1 still failed so falling back to context ‘default’
– Executing [[email protected]:1] Playback(“Zap/1-1”, “vm-goodbye”) in new stack
– <Zap/1-1> Playing ‘vm-goodbye’ (language ‘en’)
– Executing [[email protected]:2] Macro(“Zap/1-1”, “hangupcall”) in new stack
– Executing [[email protected]:1] GotoIf(“Zap/1-1”, “1?skiprg”) in new stack
– Goto (macro-hangupcall,s,4)
– Executing [[email protected]:4] GotoIf(“Zap/1-1”, “1?skipblkvm”) in new stack
– Goto (macro-hangupcall,s,7)
– Executing [[email protected]:7] GotoIf(“Zap/1-1”, “1?theend”) in new stack
– Goto (macro-hangupcall,s,9)
– Executing [[email protected]:9] Hangup(“Zap/1-1”, “”) in new stack
== Spawn extension (macro-hangupcall, s, 9) exited non-zero on ‘Zap/1-1’ in macro ‘hangupcall’
== Spawn extension (macro-hangupcall, s, 9) exited non-zero on ‘Zap/1-1’
– Hungup ‘Zap/1-1’

zapata.conf:
;# Flash Operator Panel will parse this file for zap trunk buttons
;# AMPLABEL will be used for the display labels on the buttons

;# %c Zap Channel number
;# %n Line number
;# %N Line number, but restart counter
;# Example:
;# ;AMPLABEL:Channel %c - Button %n

;# For Zap/* buttons use the following
;# (where x=number of buttons to dislpay)
;# ;AMPWILDCARDLABEL(x):MyLabel

[channels]
language=en

; include zap extensions defined in AMP
#include zapata_additional.conf

; XTDM20B Port #1,2 plugged into PSTN
;AMPLABEL:Channel %c - Button %n
context=from-zaptel
signalling=fxs_ks
faxdetect=incoming
usecallerid=yes
echocancel=yes
echocancelwhenbridged=no
echotraining=800
group=0
channel=1

I can make outbound calls no problem, but incoming as you see gets “hung up” on. This was working and then we added a second X100P card to the system and I couldn’t get it to work again. Zapata.conf did get rebuilt and “context=default” was inserted, I have removed it and still no joy.

Please let me know if there are any other files or information required.

Appreciate any assistance.

–Pete