That is strange. This is added to each tenant. Maybe you deleted it for this particular tenant? I checked a couple of servers, and they all have it. In any case, you can add it based on the screenshot.
You may need to explain to Freeswitch that it is behind NAT. Add these variables. Flush the cache and restart FreeSwitch. Adjust your SIP profile accordingly.
I got it working on my system, but had to push a small fix to make the process user-friendly. SO make sure you have the latest commit.
Stand by while I'm writing the article with instructions. I'll be back shortly
FusionPBX and FS PBX are exactly the same when it comes to SIP profiles. As a matter of fact, SIP profiles are a Freeswitch thing and have nothing to do with either FS PBX or FusionPBX. By default, your external profile uses port 5080 unless you change it. Adrian is correct in pointing out that...
This is a public forum. Don't post your credentials here.
Remote sessions are reserved for customers subscribed to a support plan.
I'm happy to do best effort support on the forum for free, but you need to provide the required logs.
It's fine to use the log viewer, but just don't paste all 59000 lines. The log rotates when it fills up, allowing it to store weeks' worth of calls. If you can isolate just the call in question and paste it here, it would be best. I personally prefer FS CLI because I can start it before the call...
There are 59000 lines in this log. Please isolate the log for one call. I can't possibly read all of those lines. Turn on FS CLI right before the call and turn it off after the call ends. Then copy and paste only those lines.
Yes, you are missing IPv4. Likely misconfiguration in Variables or SIP profiles. It can't properly start. If you watch the Freeswitch CLI while reloading sofia you will see errors that might point you in the right direction.
Use late negotiation. It will negotiate the codec supported by both sides. They will probably decide on G. 711. No transcoding will be needed and it will free up your CPU.