Asterisk Insall, Codec Install, Vicidial Install.
All in One
Vicidial, Asterisk, Web-MeetMe, MySQL, OTRS
Vicidial, Asterisk, Web-MeetMe, MySQL, OTRS.
Vicidial, Asterisk, Web-MeetMe, MySQL, OTRS.
Frontend::Agent::Ticket::ViewNote
Then --> Ticket::Frontend::AgentTicketNote###State: "YES" --> Update
After adding this, you will have the otion to change the state of a ticket
under notes.
Run the below command
SELECT table_schema "Data Base Name", sum( data_length + index_length) / 1024 / 1024
"Data Base Size in MB" FROM information_schema.TABLES GROUP BY table_schema ;
In /etc/my.cnf
server-id=2
replicate-same-server-id = 0
auto-increment-increment = 2
auto-increment-offset = 2
replicate-do-db = databasename
Mysql> Show slave status;
Above command will show the status of replication. we see two column -- value for both should be 'Yes'.
a. SlaveIORunning -- 'Yes'
b.SlaveSQLRunning --'Yes'
Incase of replication failure value for the columns will be 'No'.
If value is 'No' look for the error. Note the logfile and logposition being read.
Stop slave. First Diagnose error and resync replication from the log position it broke.
Deleting Binlogs of mysql. ----->
Log into Secondary Server
mysql> show slave status;
Above command will give the file name being read by slave machine.
Go to master and execute--->
mysql> purge binlogs to 'file_name_got_from_above_command'
In case of master to master replication we have to delete binlog from both machines. Do the same as above on both machines.
My.ini/My.cnf configuration for Master
-------------------------------
log-bin=mysql-bin
server-id=1
--------------------------------
INNODB Specific options
--------------------------------
innodb_flush_log_at_trx_commit=1
sync_binlog=1
--------------------------------
Restart MySql Service
FLUSH PRIVILEGES;
-----------------------------------------
mysql>USE exampledb;
mysql>FLUSH TABLES WITH READ LOCK;
Take a backup (or MYSQLDUMP) of the DB to be replicated
Restore DB on Slave
************************************************** *********************************
Step 2 – Configure the Slave Server(Windows XP)
Edit the my.ini/my.cnf
server-id=2
replicate-do-db = exampledb
Step 3 – Restart Mysql Service
Restart mysql Service
mysql > Stop slave;
mysql>CHANGE MASTER TO MASTER_HOST='master_IP', MASTER_USER='user', MASTER_PASSWORD='password',MASTER_LOG_FILE='mysql-bin.000006',MASTER_LOG_POS=183;
mysql > Start slave;
mysql > show slave_status; [This command will show whether your replication is running fine.]
To know if your replication is working check output of above command.
IN Out put of above command value of these two running status should be yes.
Slave_IO_Running | Slave_SQL_Running
Yes | Yes |
If any of these is NO than your replication is not working. To resynchronize DB and start replication again contact your MYSQL DBA.
Install And Maintain Kamailio (OpenSER) v3.0.x From GIT on CentOS 5.x
Main author:
Elena-Ramona Modroiu <ramona (at) asipto.com>
This is a step by step tutorial about how to install and maintain Kamailio (OpenSER) using the sources from GIT on CentOS 5.x.
Using the GIT, you get access to the latest code very quickly.
This document focuses on Kamailio (OpenSER) v3.0.x with MySQL support, using CentOS 5.5 system - should works more or less in the same way with CentOS 5.3 or 5.4.
Kamailio 3.0.0 was released on January 11, 2010:
You need git 1.5.x at least and might not be available on your CentOS installation, if it is too old. In case git is not available on your yum repository, then install Fedora repository for enterprise release.
On CentOS i386, do:
rpm -Uvh http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-3.noarch.rpm
On CentOS x86_64, do:
rpm -Uvh http://download.fedora.redhat.com/pub/epel/5/x86_64/epel-release-5-3.noarch.rpm
Then install suing yum:
yum install git
Of course, as alternative, you can install it from sources, download it from:
Then compile and make install.
Create the directory on the file system where to store the sources.
mkdir -p /usr/local/src/kamailio-3.0
cd /usr/local/src/kamailio-3.0
Download the sources from GIT using the following commands.
git clone --depth 1 git://git.sip-router.org/sip-router kamailio
cd kamailio
git checkout -b kamailio_3.0 origin/kamailio_3.0
Generate the config for Makefile system and include MySQL connector module for installation:
make include_modules="db_mysql" cfg
If you want other modules which are not enabled by default to be compiled, add them in include_modules, separated by whitespace.
Compile and install:
make all
make install
The binaries and executable scripts were installed in:
/usr/local/sbin
These are:
To be able to use the binaries from command line, make sure that '/usr/local/sbin' is set in PATH environment variable. You can check that with 'echo $PATH'. If not and you are using 'bash', open '/root/.bash_profile' and at the end add:
PATH=$PATH:/usr/local/sbin
export PATH
Kamailio (OpenSER) modules are installed in:
/usr/local/lib/kamailio/modules/
/usr/local/lib/kamailio/modules_k/
The documentation and readme files are installed in:
/usr/local/share/doc/kamailio/
The man pages are installed in:
/usr/local/share/man/man5/
/usr/local/share/man/man8/
The configuration file was installed in:
/usr/local/etc/kamailio/kamailio.cfg
To create the MySQL database, you have to use the database setup script:
/usr/local/sbin/kamdbctl create
In order to create the database you need to specify the wanted db type (DBENGINE=MYSQL) in the
/usr/local/etc/kamailio/kamctlrc
file. Call this script without any parameter to get some help for the usage. You will be asked for the domain name Kamailio (OpenSER) is going to serve (e.g., mysipserver.com) and the password of the 'root' MySQL user. The script will create a database named 'openser' containing the tables required by Kamailio (OpenSER). You can change the default settings in the kamctlrc file mentioned above.
The script will add two users in MySQL:
- openser - having the password 'openserrw', user which has full access rights to 'openser' database
- openserro - having the password 'openserro', user which has read-only access rights to 'openser' database
Do change the passwords for these two users immediately after the database is created.
To fit your requirements for the VoIP platform, you have to edit the configuration file.
/usr/local/etc/kamailio/kamailio.cfg
Follow the instruction in the comments to enable usage of MySQL. Basically you have to add several lines at the top of config file, like:
#!define WITH_MYSQL
#!define WITH_AUTH
#!define WITH_USRLOCDB
The init.d script can be used to start/stop the Kamailio (OpenSER) server in a nicer way. A sample of init.d script for Kamailio (OpenSER) is provided at:
copy the init scripts :
#cp /usr/local/src/kamailio-3.1.2/pkg/kamailio/rpm/kamailio.init /etc/init.d/kamailio
#chmod 755 /etc/init.d/kamailio
#cp /usr/local/src/kamailio-3.1.2/pkg/kamailio/rpm/kamailio.default /etc/default/kamailio
#vi /etc/default/kamailio and set RUN_KAMAILIO=yes
#vi /etc/init.d/kamailio and update :
KAM=/usr/local/sbin/kamailio
/usr/local/etc/kamailio/kamailio.cfg edit this file to fit your requirements.
For WEB-Interface please install siremis http://techgobind.blogspot.com/2011/11/siremis-open-source-web-management.html
SIREMIS: Open Source Web Management Interface for SIP Routing Engines:
Latest version of SIREMIS 2.x is available at:
Untar the archive on the local file system (e.g., in your web server root folder):
If you want to setup an alias for Apache 2.x, you can run 'make apache-conf' and you get the config snippet printed:
siremis-2.0# make apache-conf
# siremis apache conf snippet ...
Alias /siremis "/var/www/siremis-2.0/siremis"
<Directory "/var/www/siremis-2.0/siremis">
Options Indexes FollowSymLinks MultiViews
AllowOverride All
Order allow,deny
Allow from all
<FilesMatch "\.xml$">
Order deny,allow
Deny from all
</FilesMatch>
<FilesMatch "\.inc$">
Order deny,allow
Deny from all
</FilesMatch>
</Directory>
You can copy&paste it to Apache conf file (e.g., for Apache2 on Debian/Ubuntu: /etc/apache2/sites-available/default).
This will make SIREMIS available under http://yourwebserver.com/siremis/. If you want to use a different alias, edit Makefile and change the value of URLBASE
Next step is to create .htaccess and Siremis configuration files, you have to run 'make prepare':
siremis-2.0# make prepare
updating htaccess file...
updating app.inc file...
done
Make sure that following directories have write access for web server user:
Do not forget to restart the web server after doing the changes in its configuration file.
Database server to be used is MySQL.
You have to create a MySQL user that has access to Siremis database, for example:
GRANT ALL PRIVILEGES ON siremis.* TO siremis@localhost IDENTIFIED BY 'siremisrw';
This user will be needed later during the installation, of course, you can use an existing MySQL user that has enough privileges.
Also, you have to create Kamailio database with kamdbctl tool, if you don't have it already:
kamdbctl create
You don't need to do anything else to setup the database of Siremis 2.0, the rest of the process is down via web installation wizard.
Once you have done the steps above, access the web page:
First step shows the status of required items. You have to update local configuration until all the items are checked ok.
Step 2
In the second step you have to introduce the details to access Kamailio and Siremis database.
When you install Siremis first time, you probably have to check:
This page presents a status report of installation, showing whether the required directories have writable access and summary of database access details.
This is the end of installation, presenting the username and password to login to Siremis. This page is automatically redirected to login page after a short period of time.
The login page has a protection for blocking login bots, asking to enter a code printed in an image.
After first login, do not forget to update the password for user admin.
If you want to run again installation wizard:
