Koozali.org: home of the SME Server
Obsolete Releases => SME VoIP (Asterisk, SAIL etc) => Topic started by: domainwizard on April 30, 2008, 08:41:57 PM
-
following your excellent tutorials on adding non standard cards to the database, i probed and added the following to try to make my lowly x100p cheep clone card work....
all is well, being that following a commit in globals and a probe with the pci panel finds the card and loads it, however , if i do a initialize, the card disappears from the pci panel and obviously does not work.
am i missing something?
Version: sail-2.2.1-603
many regards on your excellent product and support
00:0e.0 Communication controller: Motorola Wildcard X100P
Subsystem: Efar Microsystems: Unknown device 0000
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (250ns min, 32000ns max)
Interrupt: pin A routed to IRQ 81
Region 0: I/O ports at b800 [size=256]
Region 1: Memory at e4802000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI+ D1- D2+ AuxCurrent=55mA PME(D0+,D1-,D2+,D3hot+,D3cold+)
00:0e.0 Class 0780: 1057:5608
Subsystem: 1055:0000
Flags: bus master, medium devsel, latency 32, IRQ 81
I/O ports at b800 [size=256]
Memory at e4802000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [40] Power Management version 2
# /sbin/e-smith/db selintra-work set pci:1057:5608:1055:0000 sysdev
# /sbin/e-smith/db selintra-work setprop pci:1057:5608:1055:0000 probe wcfxo zzeor EOR
-
Hello
This is all fine. An initialise is supposed to clear out all of the card infor from the database prior to doing a re-probe. You would normally only do this if you were adding a new card to an existing system. Once your card has been probed and committed then there is nothing further to do (at least as far as the card is concerned).
The X100P works OK as long as you have the bristuff release of asterisk. This loads the OSLEC echo canceller which has some special code in it just for the X100P.
Kind Regards
S
-
ok, but when a ring/tip comes in the analog line connected to the card, the asterisk cli is silent... and no come say hello
and on a totally different note what is the state of cdr affairs these days?
-
the asterisk cli is silent...
Probably because you didn't restart asterisk after you did the probe/commit. Do zap show channels at the asterisk cli. This will show if the card is being recognised by asterisk itself.
You can stop and start asterisk from Globals by pressing "STOP" and then "START"
what is the state of cdr affairs
I don't understand what you mean. CDR works as it always has, either direct to /var/log/asterisk only or also to mySQL if you have that option enabled.
Kind Regards
S
-
i got distracted but am back onto this...
although the card appears configured in the gui, no come zap in the cli
is there a location i should check to see zap loadz?
thanks
-
lsmod should show if wcfxo and zaptel are loaded
cat /proc/zaptel/1 should show the card details
zap show channels (from the asterisk console) should show the zap channel.
Kind Regards
-
cat /proc/zaptel/1
Span 1: WCFXO/0 "Wildcard X100P Board 1" (MASTER)
zap show status
Wildcard X100P Board 1 UNCONFIGUR 0 0 0
ZTDUMMY/1 (source: Linux26) 1 UNCONFIGUR 0 0 0
zap restart
== Parsing '/etc/asterisk/zapata.conf': Found
[May 13 22:39:04] WARNING[5330]: chan_zap.c:903 zt_open: Unable to specify channel 1: No such device or address
[May 13 22:39:04] ERROR[5330]: chan_zap.c:7164 mkintf: Unable to open channel 1: No such device or address
here = 0, tmp->channel = 1, channel = 1
[May 13 22:39:04] ERROR[5330]: chan_zap.c:10471 build_channels: Unable to register channel '1'
[May 13 22:39:04] WARNING[5330]: chan_zap.c:9768 zap_restart: Reload channels from zap config failed!
Module Size Used by
ztdummy 6724 0
tulip 47073 0
8139too 27585 0
ipt_ULOG 11845 1
ipt_REJECT 10689 1
ipt_MASQUERADE 8001 1
ipt_state 5953 1
ip_nat_ftp 9009 0
ip_conntrack_ftp 76529 1 ip_nat_ftp
iptable_mangle 6849 0
iptable_nat 27613 3 ipt_MASQUERADE,ip_nat_ftp
ip_conntrack 46085 5 ipt_MASQUERADE,ipt_state,ip_nat_ftp,ip_conntrack_ftp,iptable_nat
iptable_filter 6977 1
ip_tables 22720 7 ipt_ULOG,ipt_REJECT,ipt_MASQUERADE,ipt_state,iptable_mangle,iptable_nat,iptable_filter
uhci_hcd 33241 0
wcfxo 14240 0
zaptel 189828 4 ztdummy,wcfxo
crc_ccitt 6209 1 zaptel
mii 9281 1 8139too
bonding 68200 0
floppy 58193 0
dm_snapshot 21221 0
dm_zero 6337 0
dm_mirror 31301 0
ext3 119497 2
jbd 59865 1 ext3
raid1 19777 2
dm_mod 66665 8 dm_snapshot,dm_zero,dm_mirror
aic7xxx 146425 0
sd_mod 20545 0
scsi_mod 120269 2 aic7xxx,sd_mod
i am thinking the error messages make forno come answer
thanks for your help
-
when i do a commit, i get this error
== Parsing '/etc/asterisk/zapata.conf': Found
[May 15 00:01:39] WARNING[5703]: chan_zap.c:11231 process_zap: Ignoring signalli ng
[May 15 00:01:39] ERROR[5703]: chan_zap.c:10582 build_channels: Unable to reconf igure channel '1'
[May 15 00:01:39] WARNING[5703]: chan_zap.c:11549 reload: Reload of chan_zap.so is unsuccessful!
-
I've looked at this and I think maybe your card is not running correctly. Try this...
/etc/init.d/sark stop
Now do..
modprobe wcfxo
ztcfg -vv
Then
cat /proc/zaptel/1
Post the output.
Best
S
-
my impatience overwhemed me and i blew the whole thing away and started over, in which everything worked exactly as expected, however the x100 has a bit of static and echo on it, i noticed you do not support hem, and i assume this to be why, but is there anything that can be done to address the echo,
ztmonitor shows ./ztmonitor 1 -v
Rx #################################* Tx ###
do you think it would help to add in zapata.conf
rxgain=10.5
txgain=-3.5
or just throw the cheep thing away?
-
s there anything that can be done to address the echo,
Yes, we have had good results with OSLEC softecho canceller. However, it isn't available with ATrpms so you either have to compile your own version of zaptel or download our SARK BRIstuff .iso, which is a complete SME Server/SAIL build.
Kind Regards
S
-
:music:
where did the bristuff iso go?
:music:
-
:) It was an old one. We're just about to load a more up-to-date version...
Courage mon brave.
Best
S
-
and i had just figgured the old one out ;-p
thanks and many regards
-
along the way i figgured out the answer for the original post, i had been using the bristuff, and then did a yum, which delivered me a new kernel, which did not methinks support oslec, and left everything working in the gui, once i turned back the kernel, to the original, everything worked happy,
i was able to replicate this theory, the x100 worked very well with the original kernel and oslec, but looked ok in the gui but no come work with the newer kernel
looking forward to the updated iso
cheers ! :pint: