Search results

Hi Chris, I understand your view. I have not played with Asterisk for over twenty years, so I struggle to remember what ti was like. I did like the IAX phone protocol, it just seemed to work and did not get broken by NAT in the same way that SIP does. But the whole world went SIP shaped and...

I have never used the ping option on the extension record, but I always use the KeepAlive(OPTIONS) on the phone. The OPTIONS/NOTIFY ping is only ~500 bytes in each direction every 30 seconds, it's not a big deal.

Yes, by default, nginx has a certificate key pair called snakeoil which are merely self signed certificates, nothing wrong with using them. #ssl on; ssl_certificate /etc/ssl/certs/ssl-cert-snakeoil.pem; ssl_certificate_key...

Unless Letsencrypt can access your DNS records via a public DNS server like 8.8.8.8, dns-01 validation is not going to work. I use the term zone file because the most popular dns server on the internet is called bind, and bind stores it's configuration in zone files that are located in...

In order for the dns-01 to work, letsencrypt gives you a text based token that you must add to the zone file on your dns server. Letsencrypt then makes a request to lookup the dns record for the domain you are trying to obtain the certificate for. If it see the token you have put there, then it...

Many Linux systems use /etc/resolv.conf to determine which DNS server to use.

It is not feasible to list every possible channel variable, for two good reasons: 1. There are an awful lot of them 2. You may have created some of your own within your dialplan.

We use mod_bcg729 with no issues. currently using the build from here: https://github.com/djangopbx/djangopbx-install.sh/tree/main/binaries

For the benefit of anyone reading this thread, nftables had not been installed. apt-get install nftables fixed the problem. Although nftables is supposed to be the default firewall on Debian12, we have found it missing one some cloud and VPS builds. The install script has now been modified to...

Logging in as the django-pbx user try issuing a /usr/local/bin/fw-show-ipv4-white-list.sh This should return some json showing the IPs in the list

NFT looks fine what about the output of the shell command?

This regex will work for you: ^(?:\+?62|0)(\d+)$ This will strip +62 or 62 or 0 returning the rest of the number in $1 All you need to do is add the 0 in front of your $1 in the bridge statement. This is how the regex works: ^ anchors the beginning of the line. (?: starts a non-capturing group...

I assume there is more that what you have shown. Logging in as the django-pbx user try issuing a /usr/local/bin/fw-show-ipv4-white-list.sh This should return some json showing the IPs in the list

What do you see with an nft list ruleset

This does look more like an ssl error, but it is worth checking the following: Check your /home/djangp-pbx/pbx/pbx/settings.py file. See what you have in the ALLOWED_HOSTS list. It should look have in there: '127.0.0.1', 'Your server IP', 'Your FQDN' at the very least. You can do a wildcard...

Currently only PostgreSQL is integrated into the core of FreeSWITCH - hence it is native. Other DBs can be used via ODBC but that would not be my choice.

You are very welcome.

There are no firewall rules that affect codecs. RTP traffic is accepted on ports 16384-32768.

@simonjw Add the IP address(es) of your SIP provider in Admin->Switch->Access Controls. Set the type to "allow" Set the CIDR to <ip>/32 for a single address or you can specify a subnet 192.168.88.0/24 Leave domain blank Then in Utilities->Reload XML/ACL check the ACL box and click the...

@simonjw You can download the royalty free mod_bcg729 form here: wget https://raw.githubusercontent.com/djangopbx/djangopbx-install.sh/master/binaries/mod_bcg729.so Copy this file to /lib/freeswitch/mods/ Go to Status->Switch Modules and stop the pass thorough G729 Then in Status->switch...