Search results

As of the following commit today, the checking of allowed IP addresses has moved away from simple string comparisons to use the python ipaddress module. https://github.com/djangopbx/djangopbx/commit/5eb6649337baefa8c6d4e6a51e750eda4719e004 This is a breaking change because single IP addresses...

If I'm reading this tread correctly, the only things you haven't changed out are the handsets? I have seen faulty network switches intermittently send RTP streams to the wrong MAC addresses, but I doubt this is happening in your case because the base unit only has one MAC address.

It's a long while since I looked at Fusion, but I'm pretty sure it is hard coded into the code that creates the statement to bridge all the destinations. It's a channel variable called group_confirm_file that is normally set to "ivr/ivr-accept_reject.wav" This may have changed in the later versions?

Correct me if I'm wrong. rport helps in the correction of bad headers caused by NAT, but freeswitch will still report the endpoint as UDP-NAT. If the end point itself is aware of NAT and does not send any headers containing RFC1918 addresses then freeswitch will report the endpoint as UDP.

If you mean "How do you make your endpoint NAT aware" You can configure STUN, ICE or TRUN, if you endpoint device supports one of those protocols.

I'm sure you are getting confused somewhere. Moving FreeSWITCH DB from SQLLite into PostgreSql, has nothing to do with registering extensions and it is not specific to DjangoPBX. In fact for someone new to FreeSWITCH and/or DjangoPBX I would recommend leaving the FreeSWITCH DB in SQLite.

Happy to help, but you need to be more specific. To say "encountered issues with Linphone connectivity" is like me saying to you "My car engine won't start, what could be wrong?" Try to get a packet capture of the connection attempt, sngrep is a good tool. Is there anything in the Freeswitch...

Absolutely true and exactly what we find in production. I completely understand why people ask the question, but there aren't any good answers and what works for one person may not work for someone else. I'm not going to get into it here, there are may other threads that discuss this. You can...

There are several ways you can do it. You can also do it by booting to something like a sys rescue USB stick and then mount your HDD partition to change the root password. https://www.system-rescue.org/

If I remember correctly from my Fusion days, you can't override a setting to false in that way. Because you have set Enabled to False, it just means that setting is not enabled at the user level in which case the underlying default setting will be used. You also have the added complexity that...

I'll pick up on this as no one else has. I have little or no experience of load testing. I do know that it is quite a complicated art to get it right and produce meaningful results. You have to load test in a way that simulates exactly the scenario that you wish to test. Handling X calls per...

If it is a local machine and you can get to the boot loader screen when the machines starts up, then the procedure is pretty much the same for most Linux distributions. The following web page may help: https://linuxconfig.org/recover-reset-forgotten-linux-root-password

For the benefit of others reading this thread, we got to the bottom of it. The DNS provider had not set the sub-domains to the same IP address as the main FusionPBX server, despite them saying they had. The dig command proved very useful in diagnosing the issue: https://linux.die.net/man/1/dig

You have two capturing groups there so the contents of \d* will end up in $2. The first alternative of your first capturing group will always match nothing (a zero length string), that may be why you are seeing the INVALID_NUMBER_FORMAT error. You can make your first group non-capturing with...

nft delete chain inet filter trace_chain That should do it.

Ok, so do all the subdomain names point to the same IP address? and is this the IP address of your FusionPBX box?

The system is designed to be run on an internet facing machine, I've even got it running on a Raspberry Pi connected directly to the internet. There is no reason why you can't use the nftables firewall behind a NAT, all you need do is comment out the whole section: # Drop IPv4s not in internet...

Why do you need such short registration times? In most cases 1800 or 3600 seconds is fine. Short registration times can seriously increase the workload on you server if you have subscriptions and BLFs etc. A push server being static will generally want a 3600 second registration or even...

I have seen your PM, we will work through what you need and post back here for the benefit of others. I will pick this up in the (UK) morning.

I'm not sure what "set them up through GoDaddy" means here. Do you understand A records and CNAME? An A record associates your domain name with an IP address: mypbx.com 1800 IN A 1.2.3.4 A CNAME allows you to reference the A record: customer-1 1800...