Recent content by Adrian Fretwell

Internal and External profiles cannot be on the same port unless they have different IP addresses.

Yes, go for it. I am hopeless with GUI design. The only thing I will ask is that is MUST be self-contained, your own work and not AI generated. I do not want to see DjangoPBX calling out to CDNs or any other third party website.

@nickbh I have now created a Grandstream gxp2170 provision template for you. It was committed to the repo this evening. I have yet to write some documentation on the Provision system but will do so soon. Firmware locations are specified in the relevant default settings for the vendor I.E...

I just checked and we do have two Grandstream templates on the system a WP810 and a WP820. Leave it with me I will see if I can create a gxp2170 template and I will also try to write up some documentation on creating your own templates.

Don't believe that AI nonsense. DjangoPBX is very much alive and in production for our own VoIP services. I don't post much one here because someone started to behave aggressively towards it. We have a good number of organisations that are using it and a few more using it purely for it API, so...

You could set a channel variable in the outbound route. You can see all the channel variables listed in the json field of the xml_cdr. If you are not using the accountcode variable for anything else you could set that in the OB route, accountcode is an actual field in the v_xml_cdr table...

Any collaboration/help is greatly appreciated. How you would help depends more on the type of things you enjoy doing and the skills you have. For coding work, a knowledge of Python and the Django project is essential, and some knowledge of FreeSWITCH will also be helpful. The main project...

Quite a lot has been happening with the DjangoPBX project, but I don't write about it very much on here. We do need help with improving and updating the documentation so any collaboration is welcome. We are doing a lot of work to provide the facility for dedicated reporting servers to really...

Possibly something like this? ^(?:(?!somedomain\.pbx\.com).)*$

For a single box standard install all recordings, voicemails etc. will be stored under /home/django-pbx/media/fs/. It is also possible to configure a separate file store, if required for larger installations.

Ah, I have just realised your issue. You are connecting to port 8009, this is a second backup connection from where FreeSWITCH can fetch it's configuration. You should be pointing your web browser at https://<your box's IP>. In other words port 80 or port 443 should get you to the right...

You may need to run manage.py collectstatic More information can be found here: https://www.djangopbx.com/static/documentation/commandline/django_management_commands.html

As I say this is uncharted territory, can you show me one of the errors?

I think we should modify the installer script so it pauses after cloning the repository to allow for the database settings to be manually changes before continuing. I will have a look at this. To answer your question you should carry on from line 1088 in the install script. Another workaround...

Make sure all instances of uWSGI are stopped. You need python manage.py migrate not makemigrations. Once this is done you will need to manually perform all of the steps that the installer does after the DB creation.