DjangoPBX Beginners

The gui is very configurable, i don’t recall anything about changing anything other than the whitelist IP during install

I need to look at ufw, the install script need to make sure it is not installed or if it is, disable it.

@chris021 Addition to SIP Customer List and SIP Gateway List will not survive a reboot or even a nftables reload but there are some options:
You can of course save the rules with nft list ruleset > my_firewall_rules
You can add your gateways and other important IPs to the defines at the top of /etc/nftables.conf
SIP Customer lists can be restored in the GUI Admin->Switch->IP Register and choose the action "Re-instate SIP Customer Firewall List"

I'm pretty sure standard Debian12 does not install ufw by default. Maybe it is installed by default in some cloud versions.

If you have ufw, it is better to remove or disable it for DjangPBX:
Run the following command to remove ufw:


OR
Run the following commands to disable ufw:

A description of the Firewall operation is given here:
https://www.djangopbx.com/static/documentation/architecture/firewall.html

I rebuilt cloud server from Vultr and yes ufw is installed, removed it then did the install of Djangopbx and it works.

Thanks, to all for the help.

For those playing with the Debian 12 release, be advised that there was a missing Freeswitch piece using the src build for FreeSwitch (now fixed). Here are our notes on what worked using a SignalWire Personal Access Token.

First, you must have a public-facing FQDN for your server. It's the only way to login to the GUI (similar to iPBX PUBLIC).

Second, set up an account at Signalwire.com and obtain a Personal Access Token after you login (bottom left link)

Third, login to your Debian 12 server as root using SSH and issue the following commands:


Fourth, once the installer script opens, make these entries. Then SAVE file: Ctrl-X, Y, ENTER...


Fifth, run the script: ./install.sh and type y at all prompts. Be sure to whitelist your client PC's public IP address. Use default user account: django-pbx.

When the script finishes, enter the following commands BEFORE rebooting. Second command only required if nginx doesn't start on reboot.


Finally, using browser, navigate to https://django.somebody.com and login as django-pbx with your password.

A word of warning about the firewall. Adding Firewall-> Add Whitelist entries in the GUI do NOT get preserved on reboot.
Instead, login via SSH and issue the following commands to whitelist additional IP address (12.34.56.78):

Just a note about the post above, whilst it is very helpful, I must state that changes to /usr/lib/systemd/system/nginx.service are NOT required on many Debian12 installations. If your NGINX works fine, leave it alone. I have seen the issue on some cloud and vps deployments.

Building FreeSWITCH from source is fine with the latest installer.

Details about the firewall and how it works are given here:
https://www.djangopbx.com/static/documentation/architecture/firewall.html

Wow, I recall following documentation by NerdUno over a decade ago when I was messing with Asterisk, its kind of cool how the community evolves!

Sorted out getting a VoIP.ms trunk registered with bug fix from @Adrian Fretwell. Thanks!!

Now if only we could make an outbound call. Both djangopbx and voip.ms show the trunk registered, and Status->Registrations shows the softphone registered. We then created an outbound route to VoIP.ms using the following settings;

Order: 100
Number: ^(\+1|1)?(\d{10})$
Destination: True
Hostname: my.djangopbx.domain
Domain: my.djangopbx.domain
Enabled: True
Description: voipms
Continue: True

But I get a 488 Not Acceptable error dialing either 10-digit or 11-digit NANPA number. No idea what Destination and Continue mean either but True or False doesn't seem to matter. Same result.

488 normally indicates "no codec intersection" i.e. the two endpoint could not agree on a codec.
You will need to find out what codecs your softphone is offering and what codecs your SIP provider is willing to accept.

You should not have anything in Hostname, unless you are running multiple freeswitch instances. Continue should absolutely be false in this particular case.
You can find out about dialplans here:
https://developer.signalwire.com/freeswitch/FreeSWITCH-Explained/Dialplan/XML-Dialplan/

NerdUno said:

Sorted out getting a VoIP.ms trunk registered with bug fix from @Adrian Fretwell. Thanks!!

Now if only we could make an outbound call. Both djangopbx and voip.ms show the trunk registered, and Status->Registrations shows the softphone registered. We then created an outbound route to VoIP.ms using the following settings;

Order: 100
Number: ^(\+1|1)?(\d{10})$
Destination: True
Hostname: my.djangopbx.domain
Domain: my.djangopbx.domain
Enabled: True
Description: voipms
Continue: True

But I get a 488 Not Acceptable error dialing either 10-digit or 11-digit NANPA number. No idea what Destination and Continue mean either but True or False doesn't seem to matter. Same result.

Click to expand...

Please share the bug fix, I have been trying to get voipms working as well.

I found that my Yealink phone would not work with Ulaw I had to use Alaw

ou812 said:

Please share the bug fix, I have been trying to get voipms working as well.

Click to expand...

It wasn't really a bug fix. The user had deleted their selected domain and then tried to create a gateway - effectively with a non existent domain. The fix was just a test to stop someone deleting the domain they are currently working on.

I'm sorry I know nothing about voipms.

Hey everyone.

So I am very new to Freeswitch and want to learn. I usually use 3CX or something that has a single install command and a GUI that just works. I installed it on a Vultr instance with Debian and it comes with UFW preinstalled. Removing UFW first and installing and vice versa stops the ability to connect to the VM via SSH and the web portal after adding my static IP and rebooting. I have not found a workaround yet, but I have not rebooted and it does work.

Moving past that, I have watched some Freeswitch videos, and it's "relatively" simple to set up the XML files for gateways, dial plans, and extensions. I have a few domains set up and working on internal calls, however, I cannot seem to get my gateways registered to my Porta instances as well as the dial plans to receive and make calls.

Is there anyone who may be able to assist me in setting it up? I only need to see it once and I should be good thereafter.

I would like to use this in production with the API and integrate it into my (all-in-one) portal which offers clients and partners all my services.

Thanks guys

Hi Simon, happy to help if I can.
Yes, UFW does need to be removed. The Django-PBX installer does attempt to remove it if it exists.
Django-PBX uses nftables for it's firewall and the is a point in the install script that prompts you to enter your IP address into a whitelist for service like sh.

I don't know anything about Porta instances but I'm sure will can work through Gateways and dialplans.

There is a documentation page for Gateways here:
https://www.djangopbx.com/static/documentation/admin/accounts/gateways.html

If you have any specific questions it may be better to start a new thread then it makes any solutions easier to find for others.

Adrian Fretwell said:

Hi Simon, happy to help if I can.
Yes, UFW does need to be removed. The Django-PBX installer does attempt to remove it if it exists.
Django-PBX uses nftables for it's firewall and the is a point in the install script that prompts you to enter your IP address into a whitelist for service like sh.

I don't know anything about Porta instances but I'm sure will can work through Gateways and dialplans.

There is a documentation page for Gateways here:
https://www.djangopbx.com/static/documentation/admin/accounts/gateways.html

If you have any specific questions it may be better to start a new thread then it makes any solutions easier to find for others.

Click to expand...

Thanks for the reply.

Weirdly it didn’t remove UFW and I had to do it manually. During the install when it asks to put in my IP it doesn’t actually save it so I did it manually with the command and then set the config and do the reboot and I get no joy as it just hangs. I’ll try do another install and see if it still does the same thing. So far working without setting the firewall and no reboot and doesn’t seem like any rogue connections.

I’ll take a look at the documentation and see where I may be going wrong. It’s a simple IP, username and password SIP trunk so it should work with a default setup.

I’ll let you know how it goes

@Adrian Fretwell has obviously invested an enormous amount of effort in getting DjangoPBX out the door. The problem for beginners (like me) is there is virtually no documentation on how to do even the basics, i.e. set up an extension, set up a working trunk, set up an inbound and outbound route, and make a call. By my estimate, there are close to a thousand moving parts in DjangoPBX and without something that at least gets users to the point of making a successful call, the rest of the effort is of little value. Just my $.02.

Truth be told, I'm not quite a beginner. I've been using, developing, and writing about Asterisk for almost 20 years.

Documentation is an ongoing project in itself. It keeps getting moved forward as time allows. The documentation Repo is given below, if you wish to help contribute, pull requests are always welcome:
https://github.com/djangopbx/djangopbx-docs

Thanks for all the information guys.

So a second installation and the whole UFW saga and being locked out is over and the install runs perfectly. Additionally, I didn't realize that I had to reload the gateway which I did and it registered. I assumed it would be done automatically. The issue I am having is I cannot get my inbound and outbound working and I think it may be the regex for South African numbers that I am not getting correct and I've spent the last 16 or so hours trying to figure it out.

Is it possible, anyone here might know how to assist me?

Yes, post your regex and I will have a look at it, or tell me what pattern you are trying to match and I'll have a go at writing it for you.
Also you may find this site very useful for prototyping regex https://regex101.com/