Topic: [Announce]SAIL 2.1.10-115/Asterisk-SME7 i386

[SARK devs]

SME7rc1 breaks Zaptel due to the new kernel 2.6.9-34.EL.

Hi

We've just put a 7.0rc1 compliant version of asterisk-SME7 up onto our ftp server.

asterisk-SME7rc1-1.2.3-137.i686.rpm


Kind Regards

Selintra

[JonB]

Hi Selintra,

Unfortunately the new build does not work for me.

ztdummy module does not load, mind you on this server I have always had to manually modprobe ztdummy.

In this case

Code: [Select]

[root@heathcliff Asterisk]# modprobe ztdummy
WARNING: /etc/modprobe.conf line 58: ignoring bad line starting with 'post-install'
WARNING: /etc/modprobe.conf line 59: ignoring bad line starting with 'post-install'
WARNING: /etc/modprobe.conf line 60: ignoring bad line starting with 'post-install'
WARNING: /etc/modprobe.conf line 61: ignoring bad line starting with 'post-install'
WARNING: /etc/modprobe.conf line 62: ignoring bad line starting with 'post-install'
WARNING: /etc/modprobe.conf line 63: ignoring bad line starting with 'post-install'
WARNING: /etc/modprobe.conf line 64: ignoring bad line starting with 'post-install'
WARNING: /etc/modprobe.conf line 65: ignoring bad line starting with 'post-install'
WARNING: /etc/modprobe.conf line 66: ignoring bad line starting with 'post-install'
WARNING: /etc/modprobe.conf line 67: ignoring bad line starting with 'post-install'
WARNING: /etc/modprobe.conf line 68: ignoring bad line starting with 'post-install'
WARNING: /etc/modprobe.conf line 69: ignoring bad line starting with 'post-install'
WARNING: /etc/modprobe.conf line 70: ignoring bad line starting with 'post-install'
WARNING: /etc/modprobe.conf line 71: ignoring bad line starting with 'post-install'
FATAL: Module ztdummy not found.


/etc/modprobe.conf has the following

Code: [Select]

post-install tor2 /sbin/ztcfg
post-install torisa /sbin/ztcfg
post-install wcusb /sbin/ztcfg
post-install wcfxo /sbin/ztcfg
post-install wctdm /sbin/ztcfg
post-install wctdm24xxp /sbin/ztcfg
post-install ztdynamic /sbin/ztcfg
post-install ztd-eth /sbin/ztcfg
post-install wct1xxp /sbin/ztcfg
post-install wct4xxp /sbin/ztcfg
post-install wcte11xp /sbin/ztcfg
post-install pciradio /sbin/ztcfg
post-install ztd-loc /sbin/ztcfg
post-install ztdummy /sbin/ztcfg

Editing post-install to install results in the following error when running modprobe ztdummy

Code: [Select]

[root@heathcliff Asterisk]# modprobe ztdummy
Notice: Configuration file is /etc/zaptel.conf
line 0: Unable to open master device '/dev/zap/ctl'

1 error(s) detected

FATAL: Error running install command for ztdummy


Running selsniff produces

Code: [Select]

[root@heathcliff Asterisk]# perl /etc/selintra/selsniff

modprobing for Telephony boards - do a restart if this hangs....

FATAL: Module zaptel not found.
FATAL: Module wctdm not found.
FATAL: Error running install command for wctdm
FATAL: Module wctdm not found.
FATAL: Error running install command for wctdm
Finished Probes...

        No Telephony boards found...

        no boards found - loading ztdummy
FATAL: Module ztdummy not found.
FATAL: Error running install command for ztdummy

Probe ends...

Rebuilding Asterisk configuration....
Done

On-board channel summary follows:-
Notice: Configuration file is /etc/zaptel.conf
line 0: Unable to open master device '/dev/zap/ctl'

1 error(s) detected


Asterisk PBX Board Probe and Configure: complete



Jon

[psoren]

SME7rc1 breaks Zaptel due to the new kernel 2.6.9-34.EL.

Hi

We've just put a 7.0rc1 compliant version of asterisk-SME7 up onto our ftp server.

asterisk-SME7rc1-1.2.3-137.i686.rpm


Kind Regards

Selintra

Well well, everything was going quite well here until i upgraded my server. So now i can just hope for the i386 version
It looks like these threads are getting mixed between i386 and i686 now.....

Per

[JonB]

True, looks like time for a bug tracker.

Jon

[SARK devs]

Unfortunately the new build does not work for me.

ztdummy module does not load, mind you on this server I have always had to manually modprobe ztdummy

Hi Jon,

modprobe.conf is corrupt.  Give us a few hours to try and understand why.  In the meantime, if you're in need of asterisk up and running, completely remove it with rpm -e.  Re-install 137 from scratch.  This should cure it.    If you want to have a go at patching modprobe manually (it should work - we've tried it), then do this...

ERRATA - we changed the following at 10:30 Zulu 22nd March (previous version hadn't formatted correctly in the BB).

To fix modprobe.conf....

Open the file and delete everything AFTER the line which reads

alias char-major-196 torisa

Then append

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 wctdm /sbin/modprobe --ignore-install wctdm && /sbin/ztcfg
install wctdm24xxp /sbin/modprobe --ignore-install wctdm24xxp && /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


Save the module and run depmod

depmod

then

modprobe zaptel



CAUTION, if this fails, you will likely have to re-install 7.0 from scratch.

Sorry about this guys, we were caught on the back-foot with the kernel change in rc1.  We will sort this today.  We'll also put up an i386 release for you Per.   In the meantime, we've pulled 137 from ftp until we know what's what.

[psoren]

Thanks Selintra,

These Mini-ITX boards are quite popular for small servers, so i'm sure it's not just me who needs the i386 RPM...

Per

[SARK devs]

Unfortunately the new build does not work for me.

ztdummy module does not load, mind you on this server I have always had to manually modprobe ztdummy

Hi all,

We've just put asterisk-SME7rc1-1.2.3-142.i686.rpm up onto ftp.  There are a few caveats.  Make sure you remove any previous asterisk-SME7 installs  with rpm -e before you install this one (it's fine to leave sail as-is).

Once installed do a modprobe for zaptel.  It may well fail at first attempt. this is due to the fact that udev has to build the device trees and it can take up to 30 or 40 seconds to do so.  You can check they're built by doing ls -l /dev/zap.

Once you see this...

ls -l /dev/zap

crw-rw----  1 root root 196, 254 Mar 22 18:55 channel
crw-rw----  1 root root 196,   0 Mar 22 18:55 ctl
crw-rw----  1 root root 196, 255 Mar 22 18:55 pseudo
crw-rw----  1 root root 196, 253 Mar 22 18:55 timer

then you've cracked it.

Now run etc/selintra/selsniff to set up your tdm boards (if you have any)

Finally start asterisk with /etc/init.d/start asterisk, or just

asterisk  -vvvc

If asterisk fails to come up, check the module load it failed on.  It will probably be chan_zap.  If so, you probably didn't configure your TDM boards.

Kind regards

Selintra

[JonB]

Ok, this works on a clean install of SME7rc1.

Tonight I will blow my other server away and rebuild as SME7pre3 and use the yum updates to upgrade to SME7rc1. I will try the new RPM on that and let you know what happens.

Jon

[JonB]

After re-installing my server multiple times and different configurations and upgrading to RC1 I can say that if you have asterisk-SME7-x.x.x-xxx installed on your server then remove it before upgrading to SME7RC1. If you still have asterisk installed when you upgrade then on reboot the server will hang on starting the asterisk service.

So in a nutshell, before upgrading your server to RC1

uninstall asterisk-SME7

Code: [Select]

rpm -e asterisk-SME7

go ahead and do the upgrade

then install asterisk-SME7rc1-1.2.3-147.i686.rpm

Code: [Select]

rpm -Uvh asterisk-SME7rc1-1.2.3-147.i686.rpm
modprobe zaptel

If you do not have a zaptel card then you may also need to do

Code: [Select]

modprobe ztdummy

When you do lsmod you should see something like

Code: [Select]

ztdummy                 3540  0
wcfxo                  12576  0
wctdm                  34368  0
zaptel                206212  5 ztdummy,wcfxo,wctdm
crc_ccitt               2113  1 zaptel


You will then need to re-create the asterisk config files which is easiest done by going into Extensions, pick any extension and hit CHG, just hit update without making any changes.

restart asterisk

Code: [Select]

service asterisk restart

Jon

[SARK devs]

Perfect write-up Jon,

We spent all day yesterday installing and un-installing and we have nothing to add to this.  

Asterisk-SME7rc1 is now available on sourceforge.  You can get it at

http://sourceforge.net/projects/asterisk-sme7

Downloads are MUCH faster than from our ftp server

The Sourceforge release is designated 143 and you should safely be able to install it over any previous SME7rc1 release (but not - as Jon points out -  over an SME7 release).  The rc1 designation is the key.  If you have an asterisk-SME7 which is not designated rc1 then you must follow Jon's instructions below.

We'll put all this onto the docs site later today.

Thanks again Jon, it's very much appreciated.


Kind Regards

Selintra

[psoren]

Hi Selintra,

I don't hope you gave up on the i386 version, did you?  

Per

[SARK devs]

I don't hope you gave up on the i386 version, did you?

Hello Per

No we haven't given up on it.  However, you have to draw the distinction between SAIL and the asterisk-SME7 rpm.  SAIL will run NOW on i386, or any other chip you care to mention.  It's the Asterisk rpm that's causing the problem.

Right now the i586 7.0 rc1 version is being a pig.   The bottom line is that zaptel (the asterisk tdm driver) doesn't compile properly on the latest Redhat/CentOS kernel.  We're working on it but it may take a few days.

Kind Regards

Selintra

[psoren]

No we haven't given up on it.  However, you have to draw the distinction between SAIL and the asterisk-SME7 rpm.  SAIL will run NOW on i386, or any other chip you care to mention.  It's the Asterisk rpm that's causing the problem.

Hi Selintra,

I'm happy to hear that, it did look promising and i even got it to register to my VoIP provider, but never managed to recieve calls. Is that due to the port opening?
I understand the difference of the two RPM's and i can certanly wait for a couple of days for the updated i386.

Per