Search results

Faxing is a huge part of my setup and I added export variables to ensure t38 support at every leg of the fax call using FusionPBX/Freeswitch both incoming and outgoing. Combine this with a Netgen ATA and it is as reliable as POTS and WILL use t38 whenever the other end supports it. Although...

I'd wait until Freeswitch is actually ported to Bullseye since this is the basis of the system as I am sure there will be dependency problems. Since I do have one instance of FusionPBX running on a VPS, I'll take a snapshot of that, then try to update but I expect it to run into dependency...

The biggest factor for Bullseye is waiting for Freeswitch to have a bullseye branch. As of this minute, Freeswitch 1.8 does not have a Bullseye branch. http://files.freeswitch.org/repo/deb/freeswitch-1.8/dists/

Oh I have run into the NAT issue. My static IP for my Firewall/Router is on the same subnet as the the other four IP addresses. Whenever I try to run my FusionPBX/Freeswitch box on one of the static IPs, I can register sip clients from behind my firewall as usual but the registrations do not...

If you do not use backports this will not affect you since the last security update for ibcurl3-gnutls that is not backported works fine. The solution for me was to do an # apt install libcurl3-gnutls=7.64.0-4+deb10u2 and then add a block in the update for that package by running # apt-mark hold...

You need to do a lot of homework before anything, you need to learn how to do a distro update which is well documented at the debian website and elsewhere. Once the distro is updated cleanly to buster including freeswitch, then it's quite easy to deal with fusionpbx. Most of it is in /var/www...

I believe that you cannot transcode g.729 since it is passthrough only as are all non-free codecs. The only benefit at all for using this codec is to save on bandwidth, it is inferior in every other way, even packet loss and it does add extra milliseconds to the latency. In my own setup, I go...

Is this the same Polyphase that makes excellent albeit expensive, 75 ohm gas filled lightning arrestors?

I have always gotten a backup and that script is already in daily cron on my Debian installation however, it does not contain the commented out restore script posted by another poster and reposted here: #!/bin/sh #now=$(date +%Y-%m-%d) #remote_server=162.208.16.3 #delete freeswitch logs...

Yes I see the actual page but no mailboxes. They all exist and work just as I left them, just no gui access. Executing app defaults does nothing and yes I do log out and back in. Edit: What had happened is that I had the entire superadmin group permissions protected from when I added the field...

I hope I am not hijacking this thread but I have the same issue with voicemail as far as seeing it in the GUI. It actually works fine, I can still receive messages and access them by phone. If I go into the database I can see that everything reflects what is actually there and when I added a...

I know this is an old thread but CSF on a PBX is like using a garden rake to comb your hair, leave it to Red Hat to come up with such a thing. It is called ConfigServer Security and Firewall. It is here: https://www.configserver.com/cp/csf.html This is gross overkill and interfering for a PBX...

I was wondering about the security implications of adminer and you answered that. As far as records, I was sure there were good reasons, I would imagine that in some use cases call records would need to be available for review without an easy way to cover tracks by simply deleting them. In...

Without adding it to the database hence "permission if it exists" as it is stated in xml_cdr.php, you cannot tick the box and have it save that permission in the gui alone, I tried it on a second installation on a separate device as well. Same for archive, this is all in the master branch in...

In case anyone was wondering, the actual file xml_cdr_delete.php was deprecated and the function moved over the xml_cdr.php file a few months back. It still looks for the same permission xml_cdr_delete if it exists, well one can make it exist by adding it to the database.

Ah I see what you may have meant, the xml_cdr_delete field was removed from the database so by adding the permission as you say it has to be added back into the database as an added line and superuser as the user. It works perfectly now.

I was beginning to wonder about the same method of cleaning out anything via sql that is only pointed at my ip. I once had reverse lookup enabled on my domain, once I saw a mischievous attempt point to my domain I quickly decided that it was a bad idea.

OK, this is a good explanation and I am glad to see you chime in Mark. This may help the OP provided he is still watching the thread. I found that you have to find it in the Group Permissions under advanced however when I check the delete function, it does not save after hitting the save button.

I don't want to get rid of legitimate calls made and received, just the bogus hack call attempts.

The removal of the radio buttons beside each call detail record as well as a select all radio button is very irritating. Anyone who has seen junk records added from sql injection attempts or other override attempts to place calls knows what I am talking about. If it is still in work and a date...