Koozali.org: home of the SME Server

Obsolete Releases => SME VoIP (Asterisk, SAIL etc) => Topic started by: apmuthu on March 14, 2013, 06:55:35 AM

Title: SME8 + SAIL v4.0.0-53 + Asterisk 1.8.20 from rpms
Post by: apmuthu on March 14, 2013, 06:55:35 AM
Installed a standard SME 8 and fully yum updated it.
Manually installed smeossec from the rpm in the SAIL ISO but had to manually complete the installation by running sh /usr/src/ossec/ossec-hids-2.4.1/install.sh

Initially used the standard Asterisk rpms from the SAIL ISO image with the updated dahdi kmod drivers and SAIL v4.0.0-43 which had a problematic sarkhpe that had to be corrected with this patch (http://www.apmuthu.com/bugfixes/ExtnPatchForSail4-43only.zip) temporarily to avoid this error:
Code: [Select]
Verbosity was 0 and is now 6
Core debug was 0 and is now 6
  == Using SIP RTP CoS mark 5
    -- Executing [*55*#@internal:1] AGI("SIP/5001-00000003", "sarkhpe,OutCos,*55*#,,") in new stack
    -- Launched AGI Script /var/lib/asterisk/agi-bin/sarkhpe
 sarkhpe,OutCos,*55*#,,: Database connection failed, retval is 14
 sarkhpe,OutCos,*55*#,,: Database connection failed, retval is 14
 sarkhpe,OutCos,*55*#,,: Database connection failed, retval is 14
 sarkhpe,OutCos,*55*#,,: Database connection failed, retval is 14
 sarkhpe,OutCos,*55*#,,: Database connection failed, retval is 14
    -- AGI Script Executing Application: (Set) Options: (AGISIGHUP=no)
 sarkhpe,OutCos,*55*#,,: Database connection failed, retval is 14
 sarkhpe,OutCos,*55*#,,: Database connection failed, retval is 14
    -- AGI Script Executing Application: (NoOp) Options: (NO)
    -- <SIP/5001-00000003>AGI Script sarkhpe completed, returning 0
    -- Executing [*55*#@5001opencos:1] AGI("SIP/5001-00000003", "sarkhpe,OutCluster,*55*#,,") in new stack
    -- Launched AGI Script /var/lib/asterisk/agi-bin/sarkhpe
 sarkhpe,OutCluster,*55*#,,: Database connection failed, retval is 14
 sarkhpe,OutCluster,*55*#,,: Database connection failed, retval is 14
 sarkhpe,OutCluster,*55*#,,: Database connection failed, retval is 14
 sarkhpe,OutCluster,*55*#,,: Database connection failed, retval is 14
 sarkhpe,OutCluster,*55*#,,: Database connection failed, retval is 14
 sarkhpe,OutCluster,*55*#,,: Database connection failed, retval is 14
    -- AGI Script Executing Application: (Set) Options: (CDR(accountcode)=-1)
    -- <SIP/5001-00000003>AGI Script sarkhpe completed, returning 0
[Mar 14 05:41:09] WARNING[4974]: pbx.c:4971 __ast_pbx_run: Channel 'SIP/5001-00000003' sent into invalid extension '*55*#' in context '-1', but no invalid handler

Jeff was quick to remedy it with a later SAIL v4.0.0-53 (http://www.sailpbx.com/sail/sail-4.0-testing/rpms/sail-4.0.0-53.noarch.rpm) that had fixed the sarkhpe issue.

Sark could not be stopped or started using the standard SME method of sv d sark and sv u sark that was coded in /opt/sark/php/sarkglobal/view.php and hence reverted to the old service sark start / stop method using this patch (http://www.apmuthu.com/bugfixes/SarkServicePatch_Sail4-53.zip).

It is fixed to use runit natively in the unreleased sail 4 build 54.

This patch (http://www.apmuthu.com/bugfixes/Sail4-53-StopPatch.zip) needs to be applied and was modelled after the method used in /etc/rc.d/init.d/sark script.

Upgraded to Asterisk v1.8.20 after downloading them from the Asterisk 1.8 repo and executing:
Code: [Select]
yum install bluez-libs
yum remove asterisk18-addons-core asterisk-addons-mysql
yum localinstall \
  asterisk-1.8.20.0-1_centos5.i386.rpm \
  asterisk-addons-1.8.20.0-1_centos5.i386.rpm \
  asterisk-addons-bluetooth-1.8.20.0-1_centos5.i386.rpm \
  asterisk-addons-core-1.8.20.0-1_centos5.i386.rpm \
  asterisk-addons-mysql-1.8.20.0-1_centos5.i386.rpm \
  asterisk-addons-ooh323-1.8.20.0-1_centos5.i386.rpm \
  asterisk-alsa-1.8.20.0-1_centos5.i386.rpm \
  asterisk-configs-1.8.20.0-1_centos5.i386.rpm \
  asterisk-core-1.8.20.0-1_centos5.i386.rpm \
  asterisk-curl-1.8.20.0-1_centos5.i386.rpm \
  asterisk-dahdi-1.8.20.0-1_centos5.i386.rpm \
  asterisk-doc-1.8.20.0-1_centos5.i386.rpm \
  asterisk-ogg-1.8.20.0-1_centos5.i386.rpm \
  asterisk-snmp-1.8.20.0-1_centos5.i386.rpm \
  asterisk-sqlite3-1.8.20.0-1_centos5.i386.rpm \
  asterisk-voicemail-1.8.20.0-1_centos5.i386.rpm

The following warnings arose:
Code: [Select]
warning: /etc/asterisk/chan_dahdi.conf created as /etc/asterisk/chan_dahdi.conf.rpmnew
warning: /etc/asterisk/features.conf created as /etc/asterisk/features.conf.rpmnew
warning: /etc/asterisk/iax.conf created as /etc/asterisk/iax.conf.rpmnew
warning: /etc/asterisk/manager.conf created as /etc/asterisk/manager.conf.rpmnew
warning: /etc/asterisk/queues.conf created as /etc/asterisk/queues.conf.rpmnew
warning: /etc/asterisk/sip.conf created as /etc/asterisk/sip.conf.rpmnew
warning: /etc/asterisk/sip_notify.conf created as /etc/asterisk/sip_notify.conf.rpmnew
They were remedied by uploading the contents of this zip file (http://www.apmuthu.com/bugfixes/ast1820-confs.zip) into the /etc/asterisk folder.
Title: Re: SME8 + SAIL v4.0.0-53 + Asterisk 1.8.20 from rpms
Post by: apmuthu on March 14, 2013, 05:56:34 PM
SAIL 4 Code Changelog (http://www.sailpbx.com/mediawiki/index.php/SAIL_4_Code_Changelog) monitors the code consolidation as SAIL progresses towards production status.