Search results

One more thought: Set up a second gateway to your provider and an outbound route with non-dial-plan-conflicting prefix digits like 9900. Set the new gateway CODEC to PCMU only. Then you can dial 9900 + the number you want to fax to. I haven't tried this since my provider supports T.38 protocol.

Advanced > Default Settings > FAX If your provider supports t.38, enable that feature. Otherwise, I see no way to set fax speed via the GUI. On FusionPBX they show a way to do some manual XML programming to set some variables and also insure that the fax transmits at PCMU instead of G.722...

Interesting. When I did the FreeSwitch upgrade on my FusionPBX test system, I had to restart Sofia. I did not have to do that on the FS PBX upgrade and my SIP profiles came up on their own.

@pbxgeek The other good thing is that the upgrade did not clobber my custom LUA scripts and so far has not affected my custom XML coding.

The FS PBX and subsequent FreeSWITCH upgrade worked like a champ. No issues to report. :) Kudos @pbxgeek !

Thanks Mark! That should help others doing the upgrade.

On FusionPBX upgrading FreeSWITCH was a royal pain. The upgrade would abort on the configure first because spandsp was not the correct version and then because sofia was not the correct version. I would have expected the upgrade script for FreeSwitch to handle bringing the dependencies up to...

Upgrading FreeSWITCH was a royal pain. The upgrade would abort on the configure first because spandsp was not the correct version and then because sofia was not the correct version. I would have expected the upgrade script for FreeSwitch to handle bringing the dependencies up to correct...

Or their inactions and lack of adequate support for the community.

The git pull doesn't seem to be getting it. git stash git pull No local changes to save Already up to date. > version FreeSWITCH Version 1.11.1-release+git~20260526T204126Z~c2c59645f6~64bit (git c2c5964 2026-05-26 20:41:26Z 64bit)

I've been on version 5.5.x for several months without issue. You can run it on Debian 12 or Debian 13. Also, FreeSWITCH has been upgraded as well so check the forums to see if you need to upgrade it. On a fresh install, you'll get the new version.

AI Says: To configure a Polycom digit map for FS PBX (a modern FreeSWITCH-based platform), you need a dial plan that properly aligns with your system’s internal extension length and standard North American or regional dialing rules. [1] Because FS PBX relies on a clean, immediate routing...

If you make any manual changes to FS PBX or FreeSWITCH or config files, you need to git stash. This is the script I use: cd /var/www/fspbx git stash git pull php artisan app:update php artisan migrate

@pbxgeek SIP ALG is disabled and due to the new router firmware, everything works well without it. I was happy to see all of my phones are displaying the local IP.

Its a mystery to me but in my case, I'm sure SIP ALG was deliberately making sure the external IP was being sent. Now with latest router firmware on my TP-Link M707v2 router, and SIP ALG turned off, the local IP's are definitely being sent in the registration header contact. Every single device...

That was exactly it. My router had that turned on so that Smartphone wifi calling could work. I have since had a router firmware upgrade. I just turned off the SIP ALG and now I see the local IP addresses and Smartphone wifi calling works now. I still wonder why it worked on FusionPBX but...

Here is the recommendation from Ward Mundy at NerdVittles.com:

If you don't have Status > Fax Queue then you don't have permissions set up correctly. I'm on version 1.9.7.

OK. Explain for the class what you did.

I'm looking at registrations of several different phones and only a few include the local LAN IP in the call-id string. Some include some hex hashed string that I have no idea how to decode. Most don't include anything that would indicate local LAN IP. Like you said, its is something we all...