Search results

I have done some more testing over the weekend, and always come up to the same conclusion, the ring group creates a channel in the external profile, looping the call back, eventually creating a busy message. FusionPBX is a great tool but documentation is so much restricted to trivial config...

Doing some more testing, when inbound call is transferred to an extension, an internal channel is created However, when the call is transferred to a ring group, an external channel is created instead: Is this the way it should be?

Looking at the log, when having a ring group (ext. 400), I get the impression that the switch is trying to route the incoming call back as an outbound call? Could someone take a look at the below and confirm? TIA,

I decided to do a fresh install of 5.1 to a very basic FusionPBX setup (1 POTS, 2 extensions). Inbound calls work only if the endpoint is a single extension. If I create a ring group with the 2 extensions and route the inbound call to the ring group, I get a 486 error. Internal calls work...

I am trying to untangle a seemingly straightforward setup to no success. Simple home setup with 1 FXO gateway (Grandstream HT813) and some SIP phones. Inbound and outbound destinations are defined based on this gateway. ACL node is defined in domains, to allow the gateway, per the docs. Inbound...

Hello All, seems like I have messed up a small install I have at home, trying to setup a new carrier. Most probably has to do with ACLs, which arguably is the least documented part in freeswitch/fusionpbx and a major pain. Is there a way to reset the install to vanilla settings and redo the...

Many Thanks for the quick feedback. I am also expecting their support to get back to me. Cheers,

Hi, I am facing exactly the same behaviour with Groundwire. @Deezer could you please let me know if/how this was resolved?

Looking to implement this, yet sofia.conf.lua contains no such code? Has it been implemented some other way in the latest code?

Ended up working with self-signed certificates...

curling https://valid-isrgrootx1.letsencrypt.org/ worked; however, last evening I started looking at the pems created by the dehydrated script. The all.pem stored in /etc/freeswitch/tls was missing both the ISG Root X1 certificate as well the chain in the header. So I was getting the following...

eval $${certs_dir} evals correctly to /etc/freeswitch/tls. When I created them with letsencrypt scrip per the docs, no error was thrown. permissions look OK as well. # ls -la /etc/freeswitch/tls total 44 drwxr-x--- 2 www-data www-data 4096 Dec 22 17:19 . drwxr-xr-x 13 www-data www-data 4096...

At this point I have pretty much exhausted the places I can look into. I have wildcard Let's Encrypt cert issued, /etc/freeswitch/tls contains the certs, owned by www-data yet, when I try to connect from remote on the tls port I get the following: # openssl s_client -tls1_2 -connect...

Trying to get some remote Yealink phones as well as mobile phones (Groundwire) to use TLS instead of openVPN I am using a non-default port for the internal profile (i.e. non 5061). Connections are incoming in the FusionPBX box, can see them with netstat however they get stuck in TIME_WAIT state...

I see. Need to add that changing the domain name DOESN'T work. It has messed up the installation. I have gone back to using the IP domain but somewhere in the system the FQDN has stuck and now incoming calls from the SIP gateway are dropped as looking to come from FQDN. I have cleared cache and...

is there a way to handle this by adding an alias to the sip profile?

/var/cache/fusionpbx doesn't exist? (I am on 4.4.3) cleared cache thru UI I have saved the gateway again and rebooted as well

Sure, but this is an external call coming in and looks like domain is set wrongly? The trunk gateway definition contains the FQDN domain in it...

Trying to debug; my sip trunk registers with provider, but when an incoming invite happens I see the following in the logs that the domain is set using the IP, not the FQDN (i.e. the "old" IP domain 192.168.0.10) : 09249af9-8e8c-401b-bbc9-815b1690a5ad Dialplan...

Just tried to rename the domain name. Although the FQDN is shown in the various forms instead of the IPs... Phones lost registration, SIP trunks the same. rebooted and checked again but still the same