Search results

I am unable to install fusionpbx with the install script. Tried on Debian 11 and 12 with vultr and Linode. I am suspecting that the Postgres library or latest version of Postgres 16.5 is the culprit if anyone can shed some light on this I’d greatly appreciate it

Using it for the past year and a half, as the developer is a personal friend of mine. We have 3000+ endpoints. Very happy with it, and im not saying this in a biased way to favor him. I am very particular, and there’s adjustments he had to make on my behalf in order for me to agree to use it...

I was able to spin up a VM in Vultr and successfully get this installed as well, just make sure to follow the instructions. Also, the cheapest VM with 1 GB of RAM did not work - there was not enough RAM to get it to run. I went one level up on the specs (2GB RAM) and everything worked...

Dexter (@pbxgeek) has been a friend of mine for many years. He introduced me to his code about two years ago and I've been working closely with him to share ideas from a perspective of a VoIP operator handling 3000+ endpoints. When we flipped the switch to his code about a year and a half ago...

That’s the source port, perfectly normal

What version of FS? are you rebooting FS overnight? I notice with polycom the BLF lights will go out of sync if FS is rebooted, until you reboot the polycom phone also, have you tried shortening the subscribe time as well as the registration time under your polycom phone settings?

Sorry to hijack this thread but I found this interesting. For those who have experience, is it better to run the freeswitch database through Postgres, or is setting up SQLite in RAMdrive better? Specifically for high capacity.

Sorry i disagree, Vtiger is super buggy these days, and looks like they want to push everyone to the paid version as there haven’t been any community updates in a while

My best guess is that the install script is not properly installing the components for you. Possibly a bunch of dead CentOS repos causing this. But that’s just a guess.

CentOS is dead. Use Debian 11

I havent had issues after erasing the line. Been few years already

Try adding transcribe_alternate_language = es (or any other language you’d like). I believe that value needs to be filled in order for google to work

Feel free to PM me if you are still interested

You can point fusion1 and fusion2’s databases to the Freeswitch server. Or something to that effect.

If I were you, I would create everyone under a single domain. Extension number will be the 10-digit phone number of the customer. You will have everyone under one domain, and automatically what will happen is “internal” calling will not leave your system. Hopefully this is a good thing and not a...

That has nothing to do with inbound calls. It’s simply the name of your sip profile.

where did i mention anything about inbound? if you follow exactly what i wrote you will get it to work

I have it working - In each of your outbound routes that you want Transnexus to throw the Identity header, add the following, order it at 30: Action: set / clearipsti=1 Action: set / sip_h_Identity=${sip_i_identity} Action: export / sip_h_Identity=${sip_i_identity} - Bridge the call to the...

As of 3/22/2022 they are requiring a token to download Freeswitch https://freeswitch.org/confluence/display/FREESWITCH/HOWTO+Create+a+SignalWire+Personal+Access+Token

If you dont care to have the MWI status on the phones, I have a very simple solution for you. Set up a SIP trunk between both servers. On your outside server, set up call forward no answer to dummy DID numbers in FusionPBX. In FusionPBX, route the dummy DIDs to their respective voice mail boxes.