All;
I'm pulling my hair out here trying to setup two POTS lines with a 4 port card. It just should not be this difficult. It had worked previously when it was a Trixbox setup. Now of course, its a Thirdlane setup. All I want to do is have the line pickup and dial an IP phone, thats all. This is what I have:
/etc/zaptel.conf
# Span 1: WCTDM/0 "Wildcard TDM400P REV I Board 1" (MASTER)
fxsks=3
fxsks=4
# Global data
loadzone = us
defaultzone = us
/etc/asterisk/zap.conf
[G4]
qualify=no
nat=no
context=from-outside
type=friend
;=description=410-766-4040
[G3]
qualify=no
nat=no
context=from-outside
type=friend
;=description=410-766-1100
/etc/asterisk/zapata.conf
[channels]
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
busydetect=yes
rxgain=0.0
txgain=0.0
group=g1
callgroup=1
pickupgroup=1
immediate=no
callreturn=yes
echocancel=yes
echocancelwhenbridged=no
echotraining=400
;;; line="3"
signalling=fxo_ks
callerid="Channel 3 <410-766-1100>"
mailbox=20
context=from-outside
channel => 3
mailbox=20
group=G3
context=from-outside
;;; line="4"
signalling=fxo_ks
callerid="Channel 4 <410-766-4040>"
mailbox=20
context=from-outside
channel => 4
mailbox=20
group=G4
context=from-outside
I am using Thirdlane release 70 STE. Any insight at all would earn my undying gratitude.
FSD
Ok, I have 2 POTS lines
Ok, I have 2 POTS lines coming in on ports 3 and 4. For incoming calls, I simply want to route them to an extension (SIP). For outbound, perhaps preface one line with a 9, the other an 8, I really dont care. The most important thing is inbound calls. ztcfg -v gives the following:
Zaptel Version: 1.4.12.1
Echo Canceller: MG2
Configuration
======================
Channel map:
Channel 03: FXS Kewlstart (Default) (Slaves: 03)
Channel 04: FXS Kewlstart (Default) (Slaves: 04)
2 channels to configure.
/etc/dahdi/system.conf loadzo
/etc/dahdi/system.conf
loadzone = us
defaultzone = us
fxsks=3-4
echocanceller=mg2,3-4
/etc/asterisk/chan_dahdi.conf
[channels]
language=en
usecallerid=yes
hidecallerid=no
echocancel=yes
echocancelwhenbridged=yes
echotraining=no
relaxdtmf=yes
jbenable = yes
jbmaxsize = 200
jbresyncthreshold = 1000
jbimpl = fixed
jblog = no
context=from-outside
signalling=fxs_ks
group=1
txgain=0.0
rxgain=0.0
usecallerid=yes
echocancel=yes
echocancelwhenbridged=yes
echotraining=no
callerid=asreceived
channel => 3-4
you do understand that
you do understand that analog lines ring to extension 's' and you have to have that inbound route set up right?
what does /prod/dahdi/1 show?
Yes, I've set up analog
Yes, I've set up analog lines before. I'm not even seeing the line ring from the CLI. I've called your support line but I guess he's out for the day. I'm testing now on a different server that has POTS lines in the first two ports instead of the last two above.
cat /proc/dahdi/1
Span 1: WCTDM/4 "Wildcard TDM400P REV E/F Board 5" (MASTER)
1 WCTDM/4/0 FXSKS (SWEC: MG2)
2 WCTDM/4/1 FXSKS RED(SWEC: MG2)
3 WCTDM/4/2 FXOKS
4 WCTDM/4/3 FXOKS
your module is showing the
your module is showing the opposite of what you described.. this config is showing
lines 1 & 2 with FXO modules
lines 3 and 4 with FXS modules
the signalling is always opposite what the module itself is.
in that case you would just change the port assignments in the configs I gave you to 1-2 instead of 3-4
zaptel is no more, you should be using dahdi
which ports have which modules in them
your whole config is a terrible mess btw. tell me which ports have which modules, what echo canceller you want to use and how you want them to operate when dialing out.