This page describes the VoipNow services available on your server.
Kamailio
The main purpose of this service is to receive and send calls from your server. If this service does not work, no calls will be possible on your server.
Kamailio log messages are stored in the /var/log/kamailio/kamailio.log
file.
The default log level is set to 1, but in case you need to debug a problem, you can increase the log level using the following command:
kamctl fifo debug 9
kamctl fifo debug 1
/etc/init.d/kamailio restart
During restart, active calls will not be dropped, but you will not be able to receive or make new calls until the service is up again.
Asterisk
Asterisk turns your computer into a powerful communication server.
Based on the actual configuration, Asterisk routes calls between extensions, from your providers to your extensions or from extensions towards your providers.
Asterisk log files are located in /var/log/asterisk
folder.
By default, Asterisk can send logs in two locations, in the messages log file and in its console.
To access the console, use the following command:
asterisk -rcvvvvvvvv
If you want to see more detailed information, you can enable SIP debug and increase the verbose and the debug level. You can do that either from within the Asterisk console or from outside.
asterisk -rx 'sip set debug on' asterisk -rx 'core set debug 1111' asterisk -ex 'core set verbose 1111'
sip set debug on core set debug 1111 core set verbose 1111
asterisk -rcvvvvvvvvvvvvvvvvvvvvv > asterisk.log
/etc/init.d/asterisk restart
When Asterisk is restarted, all calls are dropped until the service is up again.
Hubring
Hubring is the cache system on your Voipnow server. For quick access, a lot of information is stored in the cache.
For debugging purposes, all messages from Hubring are stored in /var/log/hubring/hubring.log.
To restart Hubring, use the following command:
/etc/init.d/hubring restart
Ejabberd
Ejabberd is an XMPP application server used for internet messaging. You can use a jabber client to create IM communication between your extensions. IM services can be restarted using this command:
/etc/init.d/ejabberd restart
RabbitMQ
RabbitMQ is the message broker service from your server. If this service is not initiated, you will most probably see an error message on the Call Flows page. You can restart the service using this command:
/etc/init.d/rabbitmq restart
Postfix
The e-mail server from your VoipNow box. This service sends and receives e-mail messages on your server. All notifications are sent by Postfix. In some cases, you should make some small changes in its configuration. For instance, when you want to use the Email 2 fax feature.
If you need to restart Postfix, you can use the command below.
/etc/init.d/postfix restart
VoipNow
VoipNow is the web service of your box. To access the web interface, you need to make sure that Voipnow is started. In fact, when VoipNow services is started, two other services will be started: httpsa
and php-fpm
. The log files are kept in two locations, depending on what you are searching for:
- /usr/local/httpsa/log/voipnow - this is where the access log and error log of the web service are
- /usr/local/voipnow/admin/log/ - this is where the log file for the error generated by the web interface are
In case you need to restart the web services, you can use the command below:
/etc/init.d/voipnow restart
Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 4.0 International.