Star2Billing S.L. offers consultancy including installation, training and customisation
All the logs are centralized into one single directory /var/log/newfies/
newfies-django-db.log : This contains all the Database queries performed by the UI
newfies-django.log : All the logger events from Django
err-apache-newfies.log : Any apache errors pertaining to Newfies-Dialer
celery-newfies-node1.log : This contains celery activity
newfieslua_logs_%%.log.log : This contains the phone system logs
Newfies-Dialer configuration file is located by default at /usr/share/newfies-dialer/newfies_dialer/settings_local.py
settings_local.py contains all the local changes specific to your installation, this file is inherited from /usr/share/newfies-dialer/newfies_dialer/settings.py, therefore you can copy settings to settings_local.py and overwrite the default configuration.
When you get a message “Server Error, You’ve encountered an error!”, you might want to enable the debugger to get a full traceback of the error.
To enable the debugger, edit the file /usr/share/newfies-dialer/newfies_dialer/settings_local.py and set those settings as follow:
DEBUG = True TEMPLATE_DEBUG = DEBUG
Note that you should be able to get the traceback in /var/log/newfies/err-apache-newfies.log
Go on the admin panel and check if there is any call request that has been spooled.
If there are no calls queued, this means that the campaign is not properly configured.
- Check if the campaign is started that the “Start time”, “Finish Time” and server time are correct.
- Make sure that you configured a Dialer Setting for the user running the campaign, although there will be a warning for this on the Customer UI : http://your-ip:8008/admin/dialer_settings/dialersetting/
If there is an existing Call Request, check the status, and check the Celery log stored in /var/log/newfies
Make sure you stop the services first:
$ /etc/init.d/newfies-celeryd stop
Then run in debug mode:
$ workon newfies-dialer $ cd /usr/share/newfies/ $ python manage.py celeryd -EB --loglevel=DEBUG
Although installing and running Newfies-Dialer on EC2 should work flawlessly, you will need to update the settings ALLOWED_HOSTS manually as the install script won’t be able to detect the public IP address of your EC2 Instance.
Edit /usr/share/newfies/settings_local.py and ensure that your public IP is set in ALLOWED_HOSTS, ie. ALLOWED_HOSTS = [‘XXX.YYY.ZZZ’]
Further information about ALLOWED_HOSTS: https://docs.djangoproject.com/en/1.5/ref/settings/#allowed-hosts
Running the monitor :
- Start celery with the –events option on, so celery sends events for celerymon to capture::
- $ workon newfies-dialer $ cd /usr/share/newfies/ $ python manage.py celeryd -E
Run the monitor server:
$ workon newfies-dialer $ cd /usr/share/newfies/ $ python manage.py celerymon
However, in production you probably want to run the monitor in the background, as a daemon:
$ workon newfies-dialer $ cd /usr/share/newfies/ $ python manage.py celerymon --detach
For a complete listing of the command line arguments available, with a short description, you can use the help command:
$ workon newfies-dialer $ cd /usr/share/newfies/ $ python manage.py help celerymon
Now you can visit the webserver celerymon starts by going to: http://localhost:8989
You can use the celery purge command to purge all configured task queues. http://docs.celeryproject.org/en/latest/faq.html?highlight=purge#how-do-i-purge-all-waiting-tasks
Entering the Freeswitch CLI shold indicate whether it is running by typing fs_cli at the console. Once logged in, you can check the trunk registration by typing sofia status at the Freeswitch CLI. CTRL-D exits the Freeswitch CLI.
If the Freeswitch CLI cannot be launched, then the status of freeswitch can be checked with:
$ ps aux | grep freeswitch or $ /etc/init.d/freeswitch status
If Freeswitch is not running, then it can be started with
$ /etc/init.d/freeswitch start
The step by step checklist below should be used to validate that all components of the platform are running.
User interface :
- Dialer Gateway matching a configured trunk is set up in the UI
- Dialer Settings configured and attached to the appropriate user
- Phonebook Created with contacts attached to the phonebook
- Configured voice application
- Campaign created, and started, with a phone book attached, and the campaign schedule current
- Celery Monitor Running
- Freeswitch running
If there are still problems, then raise a support question on the mailing-list http://groups.google.com/group/newfies-dialer or our forum, http://forum.newfies-dialer.org/, alternatively, contact firstname.lastname@example.org for commercial support.