Vicibox ver 4 and https://

[bghayad]

Hello Gardo;

Vicibox version 5 has been released and it is using asterisk 1.8, when do you expect that goautodial will release new version that use asterisk 1.8 and vicidial 2.8?

Regards
Bilal

[gardo]

We will be using Asterisk 1.8 on the next major release (v4.0). Most probably next year.

As of now there really is no point in switching to Asterisk 1.8. Since almost all the features of Vicidial doesn't rely on Asterisk 1.8 features.

[williamconley]

Most clients who want 1.8 want to use modules available for 1.8, not related to Vicidial itself.

[mflorell]

We have noticed better SIP carrier support with Asterisk 1.8, as well as the fact that Sangoma CPD(Lyra) seems to work better under Asterisk 1.8 in production. For new clients Asterisk 1.8 is now what we install by default.

[bghayad]

That is correct what Matt said and there are some problems faced with asterisk 1.4 which is related to answering the call from the queue (the call was in the queue and it sent for the agent and the agent pressed answer, but it is dropped), this happened with some kind of phones. Also, asterisk 1.8 is better SIP carrier support.

Really it is important to go for asterisk 1.8 and I am sure it will be also important to use the newer incoming asterisk generation and this will be effecting in SIP protocol itself.

Regards
Bilal

[gardo]

Better SIP carrier support and Sangoma CPD is still less than 1% of the tonnes of features available in Vicidial. Asterisk 1.4.X (patched for Vicidial) is rock solid. We've been using this version with really no issues. Our enterprise services and cloud call center infrastructure is based on Asterisk 1.4.

The only compelling reason for us to switch to Asterisk 1.8 is that Asterisk 1.4 is EOL (end of life) and won't compile on CentOS 6 (which GOautodial CE v4 will be based from).

[bghayad]

When do you expect goautodial v4 will be ready?

Regards
Bilal

[gardo]

Most probably 3rd quarter next year.

[williamconley]

Following up for a client:

Generate Self-Signed Cert

Code: Select all

gensslcert -n server.FQDN.com

/etc/apache2/vhosts.d/vhost-ssl.conf
Please replace FQDN above and below with the Fully Qualified Domain Name of the server. It will still work on the IP and other names.

Code: Select all

    <IfDefine SSL>
    <IfDefine !NOSSL>
    <VirtualHost *:443>
            DocumentRoot "/srv/www/htdocs"
              ServerName server.FQDN.com:443
              ServerAdmin admin@FQDN.com
              ErrorLog /var/log/apache2/ssl_error_log
              TransferLog /var/log/apache2/ssl_access_log
            SSLEngine on
            SSLProtocol all -SSLv2 -SSLv3
            SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL
             SSLCertificateFile /etc/apache2/ssl.crt/server.crt
             SSLCertificateKeyFile /etc/apache2/ssl.key/server.key
             SSLCertificateChainFile /etc/apache2/ssl.crt/ca.crt
             SSLCACertificateFile /etc/apache2/ssl.crt/ca.crt
           <Files ~ "\.(cgi|shtml|phtml|php3?)$">
                SSLOptions +StdEnvVars
            </Files>
            <Directory "/srv/www/cgi-bin">
                SSLOptions +StdEnvVars
            </Directory>
            CustomLog /var/log/apache2/ssl_request_log   ssl_combined
    </VirtualHost>
    </IfDefine>
    </IfDefine>


/etc/sysconfig/apache2

Code: Select all

 nano +115 /etc/sysconfig/apache2

modify APACHE_SERVER_FLAGS="SSL"

Code: Select all

APACHE_SERVER_FLAGS="SSL"

Restart Apache

Code: Select all

rcapache2 restart

or

Code: Select all

service apache2 restart