Oslec

akroom

Joined
Jun 4, 2009
Messages
61
Likes
0
Points
0
#1
hi guys,

1- i have dahdi 2.2, how do i know that oslec is installed in my system?
2- if not how can i install it?
3- whenever i put the echocanceller line in system.conf all channels don't seem to work.. any clues?

thanks in advance.
 

dicko

Joined
Oct 24, 2008
Messages
4,099
Likes
0
Points
0
#2
1: lsmod|grep oslec (well it will tell if loaded but see next . . .)
2: The elastix dahdi rpm includes and installs it.
3: As it is has a kernel module dependence and you updated it, did you reboot?


4: what channel technologies do you use (elastix version, repositories enabled, etc. etc), it sometimes helps to know WTFYATA :)
 

akroom

Joined
Jun 4, 2009
Messages
61
Likes
0
Points
0
#3
dicko said:
1: lsmod|grep oslec (well it will tell if loaded but see next . . .)
2: The elastix dahdi rpm includes and installs it.
3: As it is has a kernel module dependence and you updated it, did you reboot?


4: what channel technologies do you use (elastix version, repositories enabled, etc. etc), it sometimes helps to know WTFYATA :)
dicko,

it's nice to hear from you again.

--the command lsmod|grep oslec returned nothing!
-- how can i use the rpm to install it, what are the steps?
thanks in advance.
 

dicko

Joined
Oct 24, 2008
Messages
4,099
Likes
0
Points
0
#4
ls /lib/modules/`uname -r`/dahdi/dahdi_echocan*

will show the ec modules available to you, oslec should be among them

if not you might need a yum update dahdi*


see what:

modprobe dahdi_echocan_oslec

does (it should load it if it is there, or report the error otherwise)
 

akroom

Joined
Jun 4, 2009
Messages
61
Likes
0
Points
0
#5
did

yum install dahdi*


but recieved

Transaction Check Error:
file /etc/dahdi/modules from install of dahdi-tools-2.0.0-2.el5.i386 conflicts with file from package dahdi-2.1.99.rc4.xpp.svn.r7138-1.i686
file /etc/dahdi/system.conf from install of dahdi-tools-2.0.0-2.el5.i386 confl icts with file from package dahdi-2.1.99.rc4.xpp.svn.r7138-1.i686
file /etc/modprobe.d/dahdi.blacklist from install of dahdi-tools-2.0.0-2.el5.i 386 conflicts with file from package dahdi-2.1.99.rc4.xpp.svn.r7138-1.i686
file /etc/rc.d/init.d/dahdi from install of dahdi-tools-2.0.0-2.el5.i386 confl icts with file from package dahdi-2.1.99.rc4.xpp.svn.r7138-1.i686
file /usr/sbin/dahdi_cfg from install of dahdi-tools-2.0.0-2.el5.i386 conflict s with file from package dahdi-2.1.99.rc4.xpp.svn.r7138-1.i686
file /usr/sbin/dahdi_genconf from install of dahdi-tools-2.0.0-2.el5.i386 conf licts with file from package dahdi-2.1.99.rc4.xpp.svn.r7138-1.i686
file /usr/sbin/dahdi_hardware from install of dahdi-tools-2.0.0-2.el5.i386 con flicts with file from package dahdi-2.1.99.rc4.xpp.svn.r7138-1.i686
file /usr/sbin/dahdi_monitor from install of dahdi-tools-2.0.0-2.el5.i386 conf licts with file from package dahdi-2.1.99.rc4.xpp.svn.r7138-1.i686
file /usr/sbin/dahdi_registration from install of dahdi-tools-2.0.0-2.el5.i386 conflicts with file from package dahdi-2.1.99.rc4.xpp.svn.r7138-1.i686
file /usr/sbin/dahdi_scan from install of dahdi-tools-2.0.0-2.el5.i386 conflic ts with file from package dahdi-2.1.99.rc4.xpp.svn.r7138-1.i686
file /usr/sbin/dahdi_speed from install of dahdi-tools-2.0.0-2.el5.i386 confli cts with file from package dahdi-2.1.99.rc4.xpp.svn.r7138-1.i686
file /usr/sbin/dahdi_test from install of dahdi-tools-2.0.0-2.el5.i386 conflic ts with file from package dahdi-2.1.99.rc4.xpp.svn.r7138-1.i686
file /usr/sbin/dahdi_tool from install of dahdi-tools-2.0.0-2.el5.i386 conflic ts with file from package dahdi-2.1.99.rc4.xpp.svn.r7138-1.i686
file /usr/sbin/fpga_load from install of dahdi-tools-2.0.0-2.el5.i386 conflict s with file from package dahdi-2.1.99.rc4.xpp.svn.r7138-1.i686
file /usr/sbin/fxotune from install of dahdi-tools-2.0.0-2.el5.i386 conflicts with file from package dahdi-2.1.99.rc4.xpp.svn.r7138-1.i686
file /usr/sbin/lsdahdi from install of dahdi-tools-2.0.0-2.el5.i386 conflicts with file from package dahdi-2.1.99.rc4.xpp.svn.r7138-1.i686
file /usr/sbin/xpp_blink from install of dahdi-tools-2.0.0-2.el5.i386 conflict s with file from package dahdi-2.1.99.rc4.xpp.svn.r7138-1.i686
file /usr/sbin/xpp_sync from install of dahdi-tools-2.0.0-2.el5.i386 conflicts with file from package dahdi-2.1.99.rc4.xpp.svn.r7138-1.i686
file /usr/share/dahdi/xpp_fxloader from install of dahdi-tools-2.0.0-2.el5.i38 6 conflicts with file from package dahdi-2.1.99.rc4.xpp.svn.r7138-1.i686
file /usr/share/man/man8/dahdi_genconf.8.gz from install of dahdi-tools-2.0.0- 2.el5.i386 conflicts with file from package dahdi-2.1.99.rc4.xpp.svn.r7138-1.i68 6
file /usr/share/man/man8/dahdi_hardware.8.gz from install of dahdi-tools-2.0.0 -2.el5.i386 conflicts with file from package dahdi-2.1.99.rc4.xpp.svn.r7138-1.i6 86
file /usr/share/man/man8/dahdi_registration.8.gz from install of dahdi-tools-2 .0.0-2.el5.i386 conflicts with file from package dahdi-2.1.99.rc4.xpp.svn.r7138- 1.i686
file /usr/share/man/man8/dahdi_scan.8.gz from install of dahdi-tools-2.0.0-2.e l5.i386 conflicts with file from package dahdi-2.1.99.rc4.xpp.svn.r7138-1.i686
file /usr/share/man/man8/fpga_load.8.gz from install of dahdi-tools-2.0.0-2.el 5.i386 conflicts with file from package dahdi-2.1.99.rc4.xpp.svn.r7138-1.i686
file /usr/share/man/man8/lsdahdi.8.gz from install of dahdi-tools-2.0.0-2.el5. i386 conflicts with file from package dahdi-2.1.99.rc4.xpp.svn.r7138-1.i686
file /usr/share/man/man8/xpp_sync.8.gz from install of dahdi-tools-2.0.0-2.el5 .i386 conflicts with file from package dahdi-2.1.99.rc4.xpp.svn.r7138-1.i686
file /usr/include/dahdi/user.h from install of dahdi-tools-devel-2.0.0-2.el5.i 386 conflicts with file from package dahdi-2.1.99.rc4.xpp.svn.r7138-1.i686
file /usr/include/dahdi/user.h conflicts between attempted installs of dahdi-t ools-devel-2.0.0-2.el5.i386 and dahdi-devel-2.1.99.rc4.xpp.svn.r7138-1.i686
file /usr/lib/libtonezone.so conflicts between attempted installs of dahdi-too ls-devel-2.0.0-2.el5.i386 and dahdi-devel-2.1.99.rc4.xpp.svn.r7138-1.i686
file /usr/lib/libtonezone.so.1 from install of dahdi-tools-libs-2.0.0-2.el5.i3 86 conflicts with file from package dahdi-2.1.99.rc4.xpp.svn.r7138-1.i686
file /usr/lib/libtonezone.so.1.0 from install of dahdi-tools-libs-2.0.0-2.el5. i386 conflicts with file from package dahdi-2.1.99.rc4.xpp.svn.r7138-1.i686
 

akroom

Joined
Jun 4, 2009
Messages
61
Likes
0
Points
0
#6
when modprobe dahdi_echocan_oslec
FATAL: Module dahdi_echocan_oslec not found.
 

dicko

Joined
Oct 24, 2008
Messages
4,099
Likes
0
Points
0
#7
That would seem to indicate you are using Xorcom xpp hardware if so you need to follow xorcom's directions as to the elastix.repo edits/dahdi install intructions

Further I suggest you need to contact xorcom for more authoritative
 

akroom

Joined
Jun 4, 2009
Messages
61
Likes
0
Points
0
#8
no i don't think it refers back to Xorcom, but it does refer to ill configured setting files.

i still can't run fxotune, knowingly that i always stop asterisk before applying it.

the thing is, fxotune points to zaptel folder while it should point out to a dahdi folder to prevent this dreaded errrrror

/dev/zap/155 absent: No such file or directory
/dev/zap/156 absent: No such file or directory
/dev/zap/157 absent: No such file or directory
/dev/zap/158 absent: No such file or directory
/dev/zap/159 absent: No such file or directory
/dev/zap/160 absent: No such file or directory
/dev/zap/161 absent: No such file or directory
/dev/zap/162 absent: No such file or directory
/dev/zap/163 absent: No such file or directory
/dev/zap/164 absent: No such file or directory
/dev/zap/165 absent: No such file or directory
/dev/zap/166 absent: No such file or directory
/dev/zap/167 absent: No such file or directory
/dev/zap/168 absent: No such file or directory
/dev/zap/169 absent: No such file or directory
/dev/zap/170 absent: No such file or directory
/dev/zap/171 absent: No such file or directory
/dev/zap/172 absent: No such file or directory
/dev/zap/173 absent: No such file or directory
/dev/zap/174 absent: No such file or directory
/dev/zap/175 absent: No such file or directory
/dev/zap/176 absent: No such file or directory
/dev/zap/177 absent: No such file or directory
/dev/zap/178 absent: No such file or directory
/dev/zap/179 absent: No such file or directory
/dev/zap/180 absent: No such file or directory
/dev/zap/181 absent: No such file or directory
/dev/zap/182 absent: No such file or directory
/dev/zap/183 absent: No such file or directory
/dev/zap/184 absent: No such file or directory
/dev/zap/185 absent: No such file or directory
/dev/zap/186 absent: No such file or directory
/dev/zap/187 absent: No such file or directory
/dev/zap/188 absent: No such file or directory
/dev/zap/189 absent: No such file or directory
/dev/zap/190 absent: No such file or directory
/dev/zap/191 absent: No such file or directory
/dev/zap/192 absent: No such file or directory
/dev/zap/193 absent: No such file or directory
/dev/zap/194 absent: No such file or directory
/dev/zap/195 absent: No such file or directory
/dev/zap/196 absent: No such file or directory
/dev/zap/197 absent: No such file or directory
/dev/zap/198 absent: No such file or directory
/dev/zap/199 absent: No such file or directory
/dev/zap/200 absent: No such file or directory
/dev/zap/201 absent: No such file or directory
/dev/zap/202 absent: No such file or directory
/dev/zap/203 absent: No such file or directory
/dev/zap/204 absent: No such file or directory
/dev/zap/205 absent: No such file or directory
/dev/zap/206 absent: No such file or directory
/dev/zap/207 absent: No such file or directory
/dev/zap/208 absent: No such file or directory
/dev/zap/209 absent: No such file or directory
/dev/zap/210 absent: No such file or directory
/dev/zap/211 absent: No such file or directory
/dev/zap/212 absent: No such file or directory
/dev/zap/213 absent: No such file or directory
/dev/zap/214 absent: No such file or directory
/dev/zap/215 absent: No such file or directory
/dev/zap/216 absent: No such file or directory
/dev/zap/217 absent: No such file or directory
/dev/zap/218 absent: No such file or directory
/dev/zap/219 absent: No such file or directory
/dev/zap/220 absent: No such file or directory
/dev/zap/221 absent: No such file or directory
/dev/zap/222 absent: No such file or directory
/dev/zap/223 absent: No such file or directory
/dev/zap/224 absent: No such file or directory
/dev/zap/225 absent: No such file or directory
/dev/zap/226 absent: No such file or directory
/dev/zap/227 absent: No such file or directory
/dev/zap/228 absent: No such file or directory
/dev/zap/229 absent: No such file or directory
/dev/zap/230 absent: No such file or directory
/dev/zap/231 absent: No such file or directory
/dev/zap/232 absent: No such file or directory
/dev/zap/233 absent: No such file or directory
/dev/zap/234 absent: No such file or directory
/dev/zap/235 absent: No such file or directory
/dev/zap/236 absent: No such file or directory
/dev/zap/237 absent: No such file or directory
/dev/zap/238 absent: No such file or directory
/dev/zap/239 absent: No such file or directory
/dev/zap/240 absent: No such file or directory
/dev/zap/241 absent: No such file or directory
/dev/zap/242 absent: No such file or directory
/dev/zap/243 absent: No such file or directory
/dev/zap/244 absent: No such file or directory
/dev/zap/245 absent: No such file or directory
/dev/zap/246 absent: No such file or directory
/dev/zap/247 absent: No such file or directory
/dev/zap/248 absent: No such file or directory
/dev/zap/249 absent: No such file or directory
/dev/zap/250 absent: No such file or directory
/dev/zap/251 absent: No such file or directory
/dev/zap/252 absent: No such file or directory
[root@elastix ~]#
 

dicko

Joined
Oct 24, 2008
Messages
4,099
Likes
0
Points
0
#9
Well Yosarian you got yourself in a catch 22.

the fxotune binary you have is from the old setup, proof is in man fxotune will refer to zap
fxotune is in the dahdi-tools package.

You did indeed install the Xorcom drivers, from http://updates.xorcom.com/astribank/elastix/repo/) but didn't install the dahdi-tools from them. Unless you do the Xorcom .repo thing you are stuck without yum for dahdi*. and will have to get the Xorcom dahdi-tools rpm package.

So having chosen the Xorcom path, the ball is now between you and them.

sorry dude

dicko
 

akroom

Joined
Jun 4, 2009
Messages
61
Likes
0
Points
0
#10
dicko said:
1: lsmod|grep oslec (well it will tell if loaded but see next . . .)
2: The elastix dahdi rpm includes and installs it.
3: As it is has a kernel module dependence and you updated it, did you reboot?


4: what channel technologies do you use (elastix version, repositories enabled, etc. etc), it sometimes helps to know WTFYATA :)
as to 1 no it's no installed
as to 2 what's the command to install it from there?
as to 3 i will
as to 4 elastix version 1.5-2.3, e1 module + 1 fxo all run under asterisk 1.4.2 ( i think) + dahdi 2.2
 

Members online

No members online now.

Latest posts

Forum statistics

Threads
30,913
Messages
130,917
Members
17,589
Latest member
cristian.saiz
Top