Zaptel g0 rings FXS extensions rather than FXO

[mcbsys]

Just installed PiaF 1.3 / Asterisk 1.4.21.2 / Zaptel 1.4.12.1 with a TDM400P card, 2 FXO and 2 FXS.

Followed jroper's advice in this thread to pull my simplified channel config into zapata.conf. My sole trunk is configured to use 2 channels and group 0 (g0).

Inbound calls work fine, as do calls between SIP phones and FXS extensions. But when I dial out from a SIP phone, the first FXS extension starts ringing! In other words, the group is ringing the wrong channels.

I worked around this by setting up two Zap trunks, one going to channel 3 and one to channel 4, then updating my Outbound Routes. Outbound calls work fine this way, but why don't they work with the g0 configuration?

Thanks,

Mark

zapata.conf:

;
; Zapata telephony interface
;
; Configuration file

[trunkgroups]

[channels]

language=en
context=from-zaptel
signalling=fxs_ks
rxwink=300        ; Atlas seems to use long (250ms) winks
;
; Whether or not to do distinctive ring detection on FXO lines
;
;usedistinctiveringdetection=yes

usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
echotraining=800
rxgain=4.0
txgain=0.0
group=0
callgroup=1
pickupgroup=1
immediate=no

;faxdetect=both
faxdetect=incoming
;faxdetect=outgoing
;faxdetect=no

; MCB 01/10/2009:  Do NOT include zapata-channels.conf, which gets overwritten every time genzaptelconf
;                  is run (including after update-scripts).  Use the custom values below instead.
;                  See http://pbxinaflash.com/community/threads/help-no-incoming-pstn-calls.2877/#post-17061
; #include zapata-channels.conf

;;; Internal extensions (FXS)
signalling=fxo_ks
group=1
context=from-internal
channel => 1
channel => 2

;;;Telco lines (FXO)
signalling=fxs_ks
callerid=asreceived
group=0
context=from-zaptel
channel => 3
channel => 4


;Include AMP configs
#include zapata_additional.conf

 

[jroper]

The "group=0" after txgain and before callgroup is probably not helping.

Remove that, then lets see where you are.

Joe

 

[mcbsys]

Thanks Joe. I noticed that group=0 but thought, it was there by default so maybe there's a reason. To be sure, I temporarily changed my FXO to group=2, and made the corresponding change in the trunk (g2). It still rang the first FXS extension.

By the way when I answer the extension, I hear several more DTMF tones--like it's trying to continue dialing after it reaches the extension picks up.

I can still remove the first group=0 next time I work on it.

Mark

 

[blanchae]

What's in your zapata_additional.conf file? and your /etc/zaptel.conf file?

 

[mcbsys]

Okay I commented out the first "group=0" and it's still ringing the FXS extension. I'm pasting in part of the CLI log below. What is the "|300" near the end of the longest line? I have a ring group 300, but that's for inbound calls, right? The only extension in the ring group is 200, not the FXS that is ringing (298).

    -- Executing [s@macro-dialout-trunk-predial-hook:1] MacroExit("SIP/200-08630e40", "") in new stack
    -- Executing [s@macro-dialout-trunk:17] GotoIf("SIP/200-08630e40", "0?bypass|1") in new stack
    -- Executing [s@macro-dialout-trunk:18] GotoIf("SIP/200-08630e40", "0?customtrunk") in new stack
    -- Executing [s@macro-dialout-trunk:19] Dial("SIP/200-08630e40", "ZAP/g0/18005551212|300|") in new stack
    -- Called g0/18005551212
    -- Zap/1-1 is ringing
    -- Zap/1-1 is ringing

When I change the trunks back to two individual Zap channels (ZAP/3 and ZAP/4), I can dial out fine. This is what the CLI looks like then:

    -- Executing [s@macro-dialout-trunk-predial-hook:1] MacroExit("SIP/200-08630e40", "") in new stack
    -- Executing [s@macro-dialout-trunk:17] GotoIf("SIP/200-08630e40", "0?bypass|1") in new stack
    -- Executing [s@macro-dialout-trunk:18] GotoIf("SIP/200-08630e40", "0?customtrunk") in new stack
    -- Executing [s@macro-dialout-trunk:19] Dial("SIP/200-08630e40", "ZAP/3/18005551212|300|") in new stack
    -- Called 3/18005551212
    -- Zap/3-1 answered SIP/200-08630e40

 

[mcbsys]

zaptel.conf:

# Autogenerated by /usr/local/sbin/genzaptelconf -- do not hand edit
# Zaptel Configuration File
#
# This file is parsed by the Zaptel Configurator, ztcfg
#

# It must be in the module loading order


# Span 1: WCTDM/0 "Wildcard TDM400P REV I Board 1" (MASTER) 
fxoks=1
fxoks=2
fxsks=3
fxsks=4

# Global data

loadzone    = us
defaultzone    = us

.
zapata_additional.conf:

;--------------------------------------------------------------------------------;
; Do NOT edit this file as it is auto-generated by FreePBX. All modifications to ;
; this file must be done via the web gui. There are alternative files to make    ;
; custom modifications, details at: http://freepbx.org/configuration_files       ;
;--------------------------------------------------------------------------------;
;

;;;;;;[298]
signalling=fxo_ks
pickupgroup=
mailbox=298@device
immediate=no
echotraining=800
echocancelwhenbridged=no
echocancel=yes
context=from-internal
callprogress=no
callgroup=
callerid=device <298>
busydetect=no
busycount=7
accountcode=
channel=>1

;;;;;;[299]
signalling=fxo_ks
pickupgroup=
mailbox=299@device
immediate=no
echotraining=800
echocancelwhenbridged=no
echocancel=yes
context=from-internal-courtesy
callprogress=no
callgroup=
callerid=device <299>
busydetect=no
busycount=7
accountcode=
channel=>2