Search results

So if you do not have names for the ACLs then how possibly can you distinguish between them?

I can answer that for you the answer is 100% no.

I'll marked this solved and close it so other can find it easily.

You can add a prefix when creating the outbound route, there is a box for it on the form.

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

So what are you trying to achieve? Why do you think you need an SBC?

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.

Once you have a bit of volume, give me a shout our base rates are a little higher for mobile but we charge per second.

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...

You need an app that uses push notifications, see the paid. for version of zoiper for example

The master/master documentation is a part of the fusionpbx basic membership unfortunately and cannot be shared on these forums. Personally, I do not use the method described in that documentation and instead use pglogical, search google for pglogical master/master replication and you will find...

It looks to me like you are getting yourself in a real mess here and from a quick glance it looks like the source of your problem is the ACL, it looks like you have added your own IP to the providers list? Are you a voip carrier? No, so who ever told you to do that? Once you have done that you...

Where have you seen the current recommended configuration that you say has recently changed?

If it is UDP frag, then very much so a solution and that is TCP.

It is very possible that your UDP packets are being fragmented because they are too big and that is why the calls are not working. TCP will not suffer from this problem. Using TCP for SIP is not a problem, all the media streams, eg audio/video still use UDP anyway.

What is your destination entry for this look like? The answer would appear to be here: a1a63f08-cb55-4a47-8a3e-3eaa43db4cbb 2023-09-14 03:43:30.980362 99.07% [ERR] switch_core_session.c:2760 Invalid Application It looks like it is trying to call an invalid application.

So freeswitch is clearly listening there on UDP on the internal profile: udp 0 0 172.26.9.223:5060 Are you saying the phones register OK with UDP? On another note, why are you not using TCP anyway?

What does this command show? If netstat is not installed, use: apt install net-tools netstat -antup | grep freeswitch