Hi everyone,
I have installed Asterisk 1.0.9 on FC3. I have recently installed a Digium
TDM400P and a red Digium FXO module, which I hope to connect to the PSTN so
I can make outbound calls. The FXO card is installed in port 1, and the
telephone jack is inserted into port 1.
No matter how I try, I cannot get Asterisk to dial out. Please could someone
point me in the right direction.
Here are a bit of information on how my system is configured:
/proc/interrupts
cat /proc/interrupts
CPU0
0: 536844 XT-PIC timer
1: 8 XT-PIC i8042
2: 0 XT-PIC cascade
3: 0 XT-PIC ehci_hcd:usb1
4: 0 XT-PIC ohci_hcd:usb3
8: 1 XT-PIC rtc
9: 0 XT-PIC acpi, ohci_hcd:usb2
10: 504097 XT-PIC wctdm
11: 2963 XT-PIC eth0
12: 110 XT-PIC i8042
14: 4313 XT-PIC ide0
NMI: 0
ERR: 0
/etc/zaptel.conf
fxsks=1
loadzone=za
defaultzone=za
/etc/asterisk/zapata.conf
[channels]
language=en
immediate=no
context=default
usecallerid=yes
callprogress=no
transfer=yes
threewaycalling=yes
callwaitingcallerid=yes
callwaiting=yes
cancallforward=yes
musiconhold=default
pridialplan = local
prilocaldialplan = local
nationalprefix = 0
internationalprefix = 00
;Echo control
echocancel=yes
echotraining=yes
echocancelwhenbridged=yes
;Adjust Volume
rxgain=0.0
txgain=0.0
; This is for the FXS Digium card
signalling=fxs_ks
echocancel=yes
echocancelwhenbridged=yes
echotraining=400
callerid=asreceived
group=1
context=default
channel => 1
/etc/asterisk/extensions.conf
[general]
static=no
writeprotect=no
[globals]
TRUNK=Zap/1
include => daytime|9:00-17:00|mon-fri|*|*
[local]
ignorepat => 0
include => sip
[default]
include => sip
exten => _X.,1,wait(1)
exten => _X.,2,Answer()
exten => _X.,3,Goto(default,s,1)
exten => s,1,Answer()
exten => s,2,NoOp(${CALLERID})
exten => s,3,Goto(sip,2100,1)
exten => t,1,Goto(default,s,4)
exten => i,1,Playback(invalid)
[sip]
exten => 2100,1,Answer
exten => 2100,2,wait(1)
exten => 2100,3,Dial(SIP/2101,20,tr)
exten => 2100,4,Voicemail(u2100)
exten => 2100,103,Voicemail(b2100)
exten => 2100,104,hangup
exten => 2101,1,Answer
exten => 2101,2,wait(1)
exten => 2101,3,Dial(SIP/2101,20,tr)
exten => 2101,4,Voicemail(u2101)
exten => 2101,102,Voicemail(b2101)
exten => 2101,103,hangup
; This is where we handle the outgoing calls
exten => _0.,1,Dial(${TRUNK}/${EXTEN:1},70,T,t)
exten => _0.,2,Hangup
Now because ZAPTEL moans on boot-up, I have removed ZAPTEL from the startup
services and edited my /etc/rc.d/rc.local file to load everything.
/etc/rc.d/rc.local
#!/bin/sh
#
# This script will be executed *after* all the other init scripts.
# You can put your own initialization stuff in here if you don't
# want to do the full Sys V style init stuff.
touch /var/lock/subsys/local
/sbin/modprobe zaptel
/sbin/modprobe wctdm ; I have also tried wcfxs
/sbin/service zaptel start
sleep 1
/sbin/service asterisk start
sleep 1
lsmod
Module Size Used by
wcfxs 32288 0
zaptel 208388 1 wcfxs
md5 4033 1
ipv6 262977 10
autofs4 28229 0
dm_mod 57333 0
video 15685 0
button 6609 0
battery 9285 0
ac 4805 0
ohci_hcd 26081 0
ehci_hcd 40013 0
i2c_sis96x 5445 0
i2c_core 21313 1 i2c_sis96x
hisax 598301 0
crc_ccitt 2113 2 zaptel,hisax
isdn 148673 1 hisax
slhc 6849 1 isdn
r8169 29005 0
ext3 130633 2
jbd 83161 1 ext3
Now Asterisk starts up fine, and when I dial, using X-Ten Lite, Asterisk
shows that it is dialling the ZAP/1, but the number I am dialling never
rings.
I am probably doing something stupid, so if anyone can shed some light, I
will appreciate it.
Kindest regards,
Jacques Beyers
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.362 / Virus Database: 267.12.8/165 - Release Date: 2005/11/09
-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 4392 bytes
Desc: not available
Url :
http://lists.digium.com/pipermail/asterisk-users/attachments/20051111/44b76a62/winmail.bin
On Friday 11 November 2005 02:25, Jacques Beyers wrote:> I have installed Asterisk 1.0.9 on FC3. I have recently installed a Digium > TDM400P and a red Digium FXO module, which I hope to connect to the PSTN so > I can make outbound calls. The FXO card is installed in port 1, and the > telephone jack is inserted into port 1. > > No matter how I try, I cannot get Asterisk to dial out. Please could > someone point me in the right direction. > > Here are a bit of information on how my system is configured:[ very useful, concise and correct data snipped ] Jaques, your post should be bronzed and placed at the desk of anyone subscribed to this channel. You've created what I consider the perfect "help, I can't get something working" email suitable for a mailing list such as this one. Now I only hope that my help does indeed help you. :-)> pridialplan = local > prilocaldialplan = local > nationalprefix = 0 > internationalprefix = 00None of that matters, as you don't have a PRI.> exten => _0.,1,Dial(${TRUNK}/${EXTEN:1},70,T,t)I don't think this is killing you, but the "T,t" should be "Tt" -- all flags just get lumped together, as you did with your SIP example above. Also, if you want people you call to be able to transfer (very odd scenario, but possible), then leave the 't' in there. Most people don't allow the people they've called to be able to use their transfer function.> Now because ZAPTEL moans on boot-up, I have removed ZAPTEL from the startup > services and edited my /etc/rc.d/rc.local file to load everything.What do you mean that zaptel moans on boot-up? What's the exact error message?> hisax 598301 0I've noticed that a lot of Asterisk boards get mistakenly identified as hisax boards by the hotplug subsystem, and is likely why zaptel is 'moaning' on boot-up. I would either remove the hisax driver or try to put it in your hotplug blacklist (/etc/hotplug/blacklist) so that it does not automatically load. This *could* be the source of your dialout troubles.> Now Asterisk starts up fine, and when I dial, using X-Ten Lite, Asterisk > shows that it is dialling the ZAP/1, but the number I am dialling never > rings.I imagine that you are dialing 0{telephone number} then, correct?> I am probably doing something stupid, so if anyone can shed some light, I > will appreciate it.Nothing stupid... just a couple of other questions: Do you use any wctdm kernel options? I see that you're from South Africa, so wctdm may need a different country identification in order to properly interface to your telephone network? (opermode kernel module parameter, and also 'loadzone' in zaptel.conf.) Does the system work correctly when people call in on the line that the FXO module is plugged in to? When you attempt to call out, do you hear Asterisk trying to dial if you "listen in" on another regular phone extension connected to the same FXO port? Again, thank you so much for providing a *shining* example of how to write an email to a large mailing list asking for help. You described your problem clearly, provided the RIGHT information concisely and were generally all-around polite. Thank you. -A.
> I have installed Asterisk 1.0.9 on FC3. I have recently installed a Digium > TDM400P and a red Digium FXO module, which I hope to connect to the PSTN so > I can make outbound calls. The FXO card is installed in port 1, and the > telephone jack is inserted into port 1. > > No matter how I try, I cannot get Asterisk to dial out. Please could someone > point me in the right direction. > > Here are a bit of information on how my system is configured: > > /proc/interrupts > cat /proc/interrupts > CPU0 > 0: 536844 XT-PIC timer > 1: 8 XT-PIC i8042 > 2: 0 XT-PIC cascade > 3: 0 XT-PIC ehci_hcd:usb1 > 4: 0 XT-PIC ohci_hcd:usb3 > 8: 1 XT-PIC rtc > 9: 0 XT-PIC acpi, ohci_hcd:usb2 > 10: 504097 XT-PIC wctdm > 11: 2963 XT-PIC eth0 > 12: 110 XT-PIC i8042 > 14: 4313 XT-PIC ide0 > NMI: 0 > ERR: 0 > > /etc/zaptel.conf > fxsks=1 > loadzone=za > defaultzone=za > > /etc/asterisk/zapata.conf > [channels] > language=en > immediate=no > context=default > usecallerid=yes > callprogress=no > > transfer=yes > threewaycalling=yes > callwaitingcallerid=yes > callwaiting=yes > cancallforward=yes > > musiconhold=default > pridialplan = local > prilocaldialplan = local > nationalprefix = 0 > internationalprefix = 00 > > ;Echo control > echocancel=yes > echotraining=yes > echocancelwhenbridged=yes > > ;Adjust Volume > rxgain=0.0 > txgain=0.0 > > ; This is for the FXS Digium card > signalling=fxs_ks > echocancel=yes > echocancelwhenbridged=yes > echotraining=400 > callerid=asreceived > group=1 > context=default > channel => 1 > > /etc/asterisk/extensions.conf > [general] > static=no > writeprotect=no > > [globals] > TRUNK=Zap/1 > > include => daytime|9:00-17:00|mon-fri|*|* > > [local] > ignorepat => 0 > include => sip > > [default] > include => sip > > exten => _X.,1,wait(1) > exten => _X.,2,Answer() > exten => _X.,3,Goto(default,s,1) > > exten => s,1,Answer() > exten => s,2,NoOp(${CALLERID}) > exten => s,3,Goto(sip,2100,1) > > exten => t,1,Goto(default,s,4) > exten => i,1,Playback(invalid) > > [sip] > exten => 2100,1,Answer > exten => 2100,2,wait(1) > exten => 2100,3,Dial(SIP/2101,20,tr) > exten => 2100,4,Voicemail(u2100) > exten => 2100,103,Voicemail(b2100) > exten => 2100,104,hangup > > exten => 2101,1,Answer > exten => 2101,2,wait(1) > exten => 2101,3,Dial(SIP/2101,20,tr) > exten => 2101,4,Voicemail(u2101) > exten => 2101,102,Voicemail(b2101) > exten => 2101,103,hangup > > ; This is where we handle the outgoing calls > exten => _0.,1,Dial(${TRUNK}/${EXTEN:1},70,T,t) > exten => _0.,2,Hangup > > Now because ZAPTEL moans on boot-up, I have removed ZAPTEL from the startup > services and edited my /etc/rc.d/rc.local file to load everything. > > /etc/rc.d/rc.local > #!/bin/sh > # > # This script will be executed *after* all the other init scripts. > # You can put your own initialization stuff in here if you don't > # want to do the full Sys V style init stuff. > > touch /var/lock/subsys/local > > /sbin/modprobe zaptel > /sbin/modprobe wctdm ; I have also tried wcfxs > /sbin/service zaptel start > > sleep 1 > /sbin/service asterisk start > sleep 1 > > lsmod > Module Size Used by > wcfxs 32288 0 > zaptel 208388 1 wcfxs > md5 4033 1 > ipv6 262977 10 > autofs4 28229 0 > dm_mod 57333 0 > video 15685 0 > button 6609 0 > battery 9285 0 > ac 4805 0 > ohci_hcd 26081 0 > ehci_hcd 40013 0 > i2c_sis96x 5445 0 > i2c_core 21313 1 i2c_sis96x > hisax 598301 0 > crc_ccitt 2113 2 zaptel,hisax > isdn 148673 1 hisax > slhc 6849 1 isdn > r8169 29005 0 > ext3 130633 2 > jbd 83161 1 ext3 > > Now Asterisk starts up fine, and when I dial, using X-Ten Lite, Asterisk > shows that it is dialling the ZAP/1, but the number I am dialling never > rings. > > I am probably doing something stupid, so if anyone can shed some light, I > will appreciate it.Based on what you are showing above, the lsmod Module Size Used by wcfxs 32288 0 zaptel 208388 1 wcfxs does not make sense. Your script does /sbin/modprobe wctdm, but the lsmod shows wcfxs. The wctdm driver _is_ required for the red fxo module to function, and the wcfxs is associated with the green fxs module. It would appear your problem is associated with this driver load stuff. Do the modprobes by had (not a script) and watch the results. If I do a 'modprobe zaptel' followed by a 'modprobe wctdm', I see: Module Size Used by wctdm 33728 0 zaptel 209540 1 wctdm indicating the zaptel driver is used by one wctdm driver. The do a 'ztcfg -vv' and you should see something like: Zaptel Configuration =====================Channel map: Channel 01: FXS Kewlstart (Default) (Slaves: 01) Channel 02: FXS Kewlstart (Default) (Slaves: 02) Channel 03: FXS Kewlstart (Default) (Slaves: 03) Channel 04: FXS Kewlstart (Default) (Slaves: 04) 4 channels configured. (The above is for a TDM card with four fxo modules installed.) If you don't see something like this, then resolve that before you do anything with the asterisk application. Once the above is loading correctly, run zttool to see if any issues are displayed. If everything looks okay at that point, then start asterisk using something like 'asterisk -cvvvvdddd' and scan back over the hundreds of lines of output looking for errors. If you still have problems loading wctdm, you might take a look at the output from 'dmesg' and look for the line that says: Found a Wildcard TDM: Wildcard TDM400P REV H (4 modules) If the revision number of your TDM card is 'H', 'I', etc, (a later version of the card), then consider updating the asterisk/zaptel code to something later then v1.0.9 as that old of code did not have the pci numbers in it to recognize the newer TDM card revisions. One way or another, you "have to" get wctdm to load properly before the fxo module is going to function properly. Assuming you still have problems with the above, then give us a clue which distro your using, TDM card revision, output from 'ztcfg -vv', etc.
Hi everyone, Thank you to Andrew Kohlsmith and Rich Adamson for their input.>> Do you use any wctdm kernel options? I see that you're from SouthAfrica, so>> wctdm may need a different country identification in order to properly >> interface to your telephone network? (opermode kernel module parameter,and>> also 'loadzone' in zaptel.conf.)I have tried adding in the opermode, but I think I did something wrong. Here is a copy of my unmodified /etc/modprobe.conf file. [root@voip ~]# cat /etc/modprobe.conf alias eth0 r8169 install snd-intel8x0 /sbin/modprobe --ignore-install snd-intel8x0 && /usr/sbin/alsactl restore >/dev/null 2>&1 || : alias usb-controller ehci-hcd alias usb-controller1 ohci-hcd options torisa base=0xd0000 alias char-major-196 torisa install tor2 /sbin/modprobe --ignore-install tor2 && /sbin/ztcfg install torisa /sbin/modprobe --ignore-install torisa && /sbin/ztcfg install wcusb /sbin/modprobe --ignore-install wcusb && /sbin/ztcfg install wcfxo /sbin/modprobe --ignore-install wcfxo && /sbin/ztcfg install wcfxs /sbin/modprobe --ignore-install wcfxs && /sbin/ztcfg install ztdynamic /sbin/modprobe --ignore-install ztdynamic && /sbin/ztcfg install ztd-eth /sbin/modprobe --ignore-install ztd-eth && /sbin/ztcfg install wct1xxp /sbin/modprobe --ignore-install wct1xxp && /sbin/ztcfg install wct4xxp /sbin/modprobe --ignore-install wct4xxp && /sbin/ztcfg install wcte11xp /sbin/modprobe --ignore-install wcte11xp && /sbin/ztcfg alias wctdm wcfxs alias wct2xxp wct4xxp alias eth3 hisax [root@voip ~]# Where do I make the changes, and how should they look?>> What do you mean that zaptel moans on boot-up? What's the exact error >> message? >> >> hisax 598301 0This is because I also have a HFC ISDN card in the Asterisk box. I used to first make and receive calls through it before I got the Digium card.>> Does the system work correctly when people call in on the line that the >> FXO module is plugged in to?No, when I dial the number, I get a "number busy" signal.>> When you attempt to call out, do you hear Asterisk trying to dial if you >> "listen in" on another regular phone extension connected to the same FXO >> port?No, I hear soft "bee bah bee bah bee bah" tones. Here is a capture of what Linux returns whilst trying to load and start the Digium devices One error [root@voip etc]# modprobe zaptel [root@voip etc]# modprobe wctdm Notice: Configuration file is /etc/zaptel.conf line 3: Unable to open master device '/dev/zap/ctl' [root@voip etc]# Although when I run modprobe wctdm again, the error message does not repeat itself. Listing of /dev/zap* [root@voip dev]# ls -la zap total 0 drwxr-xr-x 2 root root 200 Nov 13 21:47 . drwxr-xr-x 9 root root 5400 Nov 13 21:47 .. crw------- 1 root root 196, 1 Nov 13 21:47 1 crw------- 1 root root 196, 2 Nov 13 21:47 2 crw------- 1 root root 196, 3 Nov 13 21:47 3 crw------- 1 root root 196, 4 Nov 13 21:47 4 crw------- 1 root root 196, 254 Nov 13 21:47 channel crw------- 1 root root 196, 0 Nov 13 21:47 ctl crw------- 1 root root 196, 255 Nov 13 21:47 pseudo crw------- 1 root root 196, 253 Nov 13 21:47 timer [root@voip dev]# Here is what LSMOD shows after having loaded the WCTDM driver. lsmod [root@voip dev]# lsmod Module Size Used by wcfxs 32288 0 zaptel 208388 1 wcfxs md5 4033 1 ipv6 262977 12 autofs4 28229 0 dm_mod 57333 0 video 15685 0 button 6609 0 battery 9285 0 ac 4805 0 ohci_hcd 26081 0 ehci_hcd 40013 0 i2c_sis96x 5445 0 i2c_core 21313 1 i2c_sis96x hisax 598301 0 crc_ccitt 2113 2 zaptel,hisax isdn 148673 1 hisax slhc 6849 1 isdn r8169 29005 0 ext3 130633 2 jbd 83161 1 ext3 [root@voip dev]# /var/log/messages Nov 13 21:47:11 voip kernel: Zapata Telephony Interface Registered on major 196 Nov 13 21:47:16 voip kernel: ACPI: PCI Interrupt 0000:00:08.0[A] -> Link [LNKD] -> GSI 10 (level, low) -> IRQ 10 Nov 13 21:47:16 voip kernel: Freshmaker version: 73 Nov 13 21:47:16 voip kernel: Freshmaker passed register test Nov 13 21:47:16 voip kernel: Module 0: Installed -- AUTO FXO (FCC mode) Nov 13 21:47:16 voip kernel: Module 1: Not installed Nov 13 21:47:16 voip kernel: Module 2: Not installed Nov 13 21:47:16 voip kernel: Module 3: Not installed Nov 13 21:47:16 voip kernel: Found a Wildcard TDM: Wildcard TDM400P REV I (4 modules) ztcfg -vvvv [root@voip dev]# ztcfg -vvvv Zaptel Configuration ===================== Channel map: Channel 01: FXS Kewlstart (Default) (Slaves: 01) 1 channels configured. [root@voip dev]# Any pointers? Kindest regards, Jacques Beyers (MCP, MCSE) Beyers Squared Integrated Solutions Mobile: +2782 566-4381 Facsimile: +2782 131-566-4381 E-mail: jacquesb@b-squared.co.za Skype: jdbeyers Linux registration number: 353934 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.362 / Virus Database: 267.12.8/165 - Release Date: 2005/11/09 -------------- next part -------------- A non-text attachment was scrubbed... Name: winmail.dat Type: application/ms-tnef Size: 4740 bytes Desc: not available Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20051113/f4ad8d7f/winmail.bin