Have you flushed your cache after changes?
I see:
db22fb05-6e98-4d84-823c-eab1230e8d14 Dialplan: sofia/internal/dad@example.domain.com Regex (PASS) [is_secure] ${sip_via_protocol}(tls) =~ /tls|wss/ break=on-false
db22fb05-6e98-4d84-823c-eab1230e8d14 Dialplan...
I see a problem straight away: mod_dialplan_xml.c:639 Processing teste 1 <152>->151 in context public
Context public
For some reason, fusionpbx is processing the inbound dialplan.
This usually comes down to you changing the access control lists when you shouldn't have.
I see the match and bridge: Action bridge(sofia/gateway/343f74f4-773e-401a-bc5a-3e3e3b4b7aa3/5715705843)
Do Telnyx require a prefix of 1 or anything like that?
I don't know of any load balancing solution with fusionpbx other than balancing by domain, ie everything for a single domain ends up on the same fusionpbx server
Google it, its complex to explain but basically circumvents the problem of the app going to sleep. If a call comes in, the push server will wake the app up to take the call.
Check the xml_cdr config file in the /etc/freeswitch/autoload_configs
Modules that are present but won't load usually have a problem with their config file.
I may have read the ACL stuff wrong
Basically you shouldn't have to mess with contexts and profiles at all, it should all be automatic, I'm busy, so I'll take a look later at the whole thread but I can see for example:
Action...