I very happy to announce the 1.4 final version released. After hours, and many new stuffs, this version is available in the PyFreeBilling Bitbucket repos.
The installation documentation is hosted on PyFreeBilling ReadTheDocs repos.
If you see any bugs, please report in PyFreeBilling bug tracker.
The change log :
Version 1.4
New features
- New customer portal
- HTTPS access only
- Reload Fs config via button in admin panel
- Currency management
- Database size monitoring – new panel (in admin menu)
- Sofia Gateway : add new choose lists for selecting codecs
- Add sip profile DTMF options (pass-rfc2833)
- Add new rtp_rewrite_timestamps sofia profile option
- Visitors and web interface use stats
- Admin CDR panel : show minutes / sell / cost / margin corresponding to selection
- New dashboard : revenue / cost / minutes / calls stats
- documentation update for installation of 1.4 freeswitch version
- web country blocker based on visitor’s ip. Databases : freegeoip.net and/or maxmind
- detailed customers, providers and destinations stats
Modifications
- Django 1.6 migration
- All dependencies are up to date
- Optimisation of customer sip parameter and customer sip UA codecs selection
Bug corrections
- Add new codec options in Customer sip accounts and sip profiles : G711u&G711a and G711a&G711u
- Destination number is checked before LUA
- Recurrent tasks working with new chronicler version
Matt,
Thanks for the work you’ve done. What is the best way to upgrade a production system to PFB-1.4 and Freeswitch-1.4. I currently have PFB-1.3 and FS-1.2, respectively.
Mike
Hi Mike,
Thanks.
You can update a current installation by doing :
git pull
check your local_settings.py file and see the diff between the doc one (you need to add some settings)
pip install -U -r requirements/requirements.txt
python manage.py syncdb
python manage.py initcurrencies
python manage.py migrate
python manage.py loaddata country_dialcode.json
python manage.py loaddata switch 0001_fixtures.json
python manage.py loaddata 0001_initial_SipProfile.json
python manage.py loaddata 0001_initial_ReccurentTasks.json
python manage.py loaddata country.json
python manage.py updatecurrencies (if you have set your Openexchange API key)
python manage.py collectstatic (answer ‘yes’)
That’s done.
If you have some question, please use the bitbucket issue tools.
BR
Matt
Matt,
I’ve emailed out put from pip.log where I got an error while running:
pip install -U -r requirements/requirements.txt
I’m currently running PFB-1.3 and FS-1.2
The machine has all latest apt updates
Here is the error
Found existing installation: distribute 0.6.24dev-r0
Uninstalling distribute:
Successfully uninstalled distribute
Running setup.py install for distribute
Running setup.py install for pyPdf2
Traceback (most recent call last):
File “”, line 1, in
ImportError: No module named setuptools
Complete output from command /usr/bin/python -c “import setuptools;__file__=’/usr/local/venv/pyfreebilling/build/pyPdf2/setup.py’;exec(compile(open(__file__).read().replace(‘\r\n’, ‘\n’), __file__, ‘exec’))” install –single-version-externally-managed –record /tmp/pip-JqfiNc-record/install-record.txt:
Traceback (most recent call last):
File “”, line 1, in
ImportError: No module named setuptools
—————————————-
Command /usr/bin/python -c “import setuptools;__file__=’/usr/local/venv/pyfreebilling/build/pyPdf2/setup.py’;exec(compile(open(__file__).read().replace(‘\r\n’, ‘\n’), __file__, ‘exec’))” install –single-version-externally-managed –record /tmp/pip-JqfiNc-record/install-record.txt failed with error code 1
Hi,
Please, could you open a ticket in Bitbucket.
It is not easy to support via comments.
Thx
Matt
Sorry, I’ve created an issue in Bitbucket.
it will make easy for users if you have installation script
sam
we appreciate what you doing for Community, i like to give advise Please add Retail service for ANI & Calling Card Shadow Billing multi reseller and easy installation step or script on new version.
Sameer
@sam I am working on the installation script.
Oh yeah, so far I have had three unsuccessful installations. And 1 successful but never able to route call through.
Hi Chris,
Do not hesitate to use the question section. Also, if you want some help, post some details. This version is used by many providers in production with success.