Topic: Solved: asterisk CLI not loading

[compsos]

Hi
On a new install of asterisk we were unable to load the cli. Note also the stop/start button in the Globals page did not work properly.
Installed 7.4
asterisk-1.4.21.1-65.el4.i386.rpm
libpri1-1.4.7-21.el4.i386.rpm
libpri-1.4.7-21.el4.i386.rpm
sme-ast-en-uk-gpl-sounds-1.0.0-3.noarch.rpm
zaptel-1.4.12.1-54.99.el4.i386.rpm
zaptel-kmdl-2.6.9-78.0.8.ELsmp-1.4.12.1-54.99.el4.i686.rpm
sail-2.2.1-716.noarch.rpm

asterisk -rvvv failed with
Unable to connect to remote asterisk (does /var/run/asterisk/asterisk.ctl exist?)
asterisk -cvvvv returned
symbol lookup error: /usr/lib/asterisk/modules/codec_speex.so
speex installed version
speex-1.0.4-4.el4_6.1
yum update -y speex --enablerepo=atrpms
returned speex.i386 0:1.2-0.2.beta1
and now the cli loads

Hope this helps someone else.

[SARK devs]

HI Gordon

I believe thgat speex should be loaded as an asterisk dependancy.  Did you yum install asterisk or rpm it?

Best

S
 

[compsos]

Hi Jeff

Yes yum installed. It certainly sent us in a loop trying to understand why it did not run properly and then to have had the newer asterisk that does not run zap correctly.

Should we update the wiki to indicate the pitfalls in the current versions of asterisk/sail combinations?

[David Harper]

The issue is only temporary (it will be resolved when SAIL is updated for Dahdi and SME Server goes to the -78.0.13 kernel).

But yes, I think a notice on the Selintra wiki would be a good idea.

[SARK devs]

We'll do a "state of the union" in the next few days when we've worked out exactly how we are going to move forward.  However, bearing in mind the fact that Digium have never been great respecters of upward/backward compatibiliy between releases, we would not ever recommend "routine" yum update of Asterisk or its components.  The whole DAHDI episode is typical of this.  It isn't transparent and it isn't (as they initially claimed) just a name change.  There are all sorts of other subtle differences in trhe DAHDI release.

S   

[David Harper]

Ian Wells has just started the ball rolling on releasing the -78.0.13 kernel update (and a lot of other updates unrelated to these issues), so we may at least get the atrpms Zaptel drivers working again soon.

[compsos]

And I just thought I was going crazy especially following vmware/bridge issue by not have a physical layer working on eth0. The joys of software.