Koozali.org: home of the SME Server
Obsolete Releases => SME VoIP (Asterisk, SAIL etc) => Topic started by: saleh on June 28, 2009, 12:32:14 PM
-
When i run the selintra command this error occurs
[root@sme ~]# /var/lib/asterisk/agi-bin/selintra
/var/lib/asterisk/agi-bin/selintra: error while loading shared libraries: libmysqlclient_r.so.14: cannot open shared object file: No such file or directory
[root@sme ~]# locate libmysqlclient_r
/usr/lib/mysql/libmysqlclient_r.a
/usr/lib/mysql/libmysqlclient_r.so
/usr/lib/mysql/libmysqlclient_r.so.15
/usr/lib/mysql/libmysqlclient_r.so.15.0.0
-
we haven't tested on 8.0 yet.
I'm sure there will be changes we have to make.
For now, you shouldn't run Sail on 8.0
Best
S
-
I have tested sail-2.3.1-20 on the SME Server 8.0 Beta 4 and now the problem with the libmysqlclient_r.so.14 resolved and work well, but i see that the analogue Extensions not displayed on the Operator Panel, i have TDM400 with 2 FXS and one FXO
5000 default DAHDI Ext(FXS)1 AnalogFXS NA Analogue
5001 default DAHDI Ext(FXS)2 AnalogFXS NA Analogue
5002 default ext5002 Grandstream GXP 2000
Thanks and Best Regards
Saleh
-
Hello Saleh,
Do you mean the Flash Operator Panel?...
Best
S
-
Yes, i mean the Flash Operator Panel.
Best Regards
Saleh
-
Ah OK, you'll need to modify it if you want to see analogue extensions. It is specifically set-up to show SIP extensions and SIP/IAX/TDM trunks. It doesn't look for analogue extensions. In fact, I'm not even sure if we've done the work to convert it for DAHDI trunks yet - I think it may still be looking for Zap Trunks.
It's easy enough to change. The code fragments are in
/etc/e-smith/templates/usr/local/operator/op_buttons.cfg/
Thanks for your input and let us know if you find any glitches in 8.0. You don't say which version of Asterisk you have installed, but we'd be pleased if you would test with 1.6.1.
Kind Regards
S
-
Version of Asterisk: 1.4.25.1
Version of DAHDI: 2.1.0.4
Best Regards
Saleh
-
Syntax error on the /etc/dahdi/system.conf
Current Contents of /etc/dahdi/system.conf
# Autogenerated by /usr/sbin/dahdi_genconf on Wed Jul 1 09:06:00 2009 -- do not hand edit
# Dahdi Configuration File
#
# This file is parsed by the Dahdi Configurator, dahdi_cfg
#
# Span 1: WCTDM/4 "Wildcard TDM400P REV I Board 5" (MASTER)
fxoks=1
echocanceller=oslec,1
fxoks=2
echocanceller=oslec,2
# channel 3, WCTDM/4/2, no module.
fxsks=4
echocanceller=oslec,4
# Global data
loadzone = uk
defaultzone = uk
Loading DAHDI hardware modules:
wct4xxp: [ OK ]
wcte12xp: [ OK ]
wct1xxp: [ OK ]
wcte11xp: [ OK ]
wctdm24xxp: [ OK ]
wcfxo: [ OK ]
wctdm: [ OK ]
wcb4xxp: [ OK ]
wctc4xxp: [ OK ]
xpp_usb: [ OK ]
opvxa1200: [ OK ]
ystdm8xx: [ OK ]
ystdm16xx: [ OK ]
ap400: [ OK ]
dahdi_dynamic_eth: [ OK ]
dahdi_dynamic_ethmf: [ OK ]
Running dahdi_cfg: Notice: Configuration file is /etc/dahdi/system.conf
line 14: Syntax error. Should be <keyword>=<value>
line 16: Syntax error. Should be <keyword>=<value>
2 error(s) detected [FAILED]
I think that the "SARKPCI - Discover Hardware" add wrong lines on the /etc/dahdi/system.conf file.
But when i run /usr/sbin/dahdi_genconf manually the problem does not appear and the problem occur only in blank lines
Loading DAHDI hardware modules:
wct4xxp: [ OK ]
wcte12xp: [ OK ]
wct1xxp: [ OK ]
wcte11xp: [ OK ]
wctdm24xxp: [ OK ]
wcfxo: [ OK ]
wctdm: [ OK ]
wcb4xxp: [ OK ]
wctc4xxp: [ OK ]
xpp_usb: [ OK ]
opvxa1200: [ OK ]
ystdm8xx: [ OK ]
ystdm16xx: [ OK ]
ap400: [ OK ]
dahdi_dynamic_eth: [ OK ]
dahdi_dynamic_ethmf: [ OK ]
Running dahdi_cfg: [ OK ]
Best Regards
Saleh
-
Interesting....
We know about the two space lines causing a problem. WE weren't aware that it doesn't happen if you run dahdi_genconf on its own.
All sark does is execute dahdi_genconf so I'm not sure why there should be a difference in outcome.
Thanks for this Saleh.
Best
S
-
The Problem is on your
sub commitLines ($)
{
my ($q) = @_;
my $gonogo = ();
my $dahdi_system = $q->param ('dahdi_system');
my $dahdi_channels = $q->param ('dahdi_channels');
open OUT, ">/etc/dahdi/system.conf";
print OUT $dahdi_system;
close OUT;
..............
Example:
PCI Cards => Press Initialise => Press ReGen
then start dahdi manually the problem does not appear.
Other Example: PCI Cards => Press Initialise => Press ReGen => Commit
then start dahdi manually the problem appear.
Loading DAHDI hardware modules:
wct4xxp: [ OK ]
wcte12xp: [ OK ]
wct1xxp: [ OK ]
wcte11xp: [ OK ]
wctdm24xxp: [ OK ]
wcfxo: [ OK ]
wctdm: [ OK ]
wcb4xxp: [ OK ]
wctc4xxp: [ OK ]
xpp_usb: [ OK ]
opvxa1200: [ OK ]
ystdm8xx: [ OK ]
ystdm16xx: [ OK ]
ap400: [ OK ]
dahdi_dynamic_eth: [ OK ]
dahdi_dynamic_ethmf: [ OK ]
Running dahdi_cfg: Notice: Configuration file is /etc/dahdi/system.conf
line 14: Syntax error. Should be <keyword>=<value>
line 16: Syntax error. Should be <keyword>=<value>
2 error(s) detected [FAILED]
Best Regards
Saleh
-
Nice
We'll follow it up.
Best
S
-
There are some non-*nix characters creeping in from somewhere.
Here is a bandaid
open OUT, ">/etc/dahdi/system.conf";
print OUT $dahdi_system;
close OUT;
#
# bandaid
#
system "/usr/bin/dos2unix", "/etc/dahdi/system.conf";
#
#
#
Kind Regards
S
-
Thanks, now works well after your changes
Best Regards
Saleh