Search results

We've been replicating cross datacenter for years, first using bdr, now moved to pglogical, and @markjcrane now has his own solution using wal to json that is a recently released member feature, I haven't tested that one yet but have no reason to believe it won't be has good as the bdr one was...

I believe its purpose is just to improve the accuracy of the cdr reporting. That for example marks the call as outbound.

If you are running it in tmpfs there is no need to delete anything, it went when the reboot happened

I think kazoo these days is an open source shell to sell commercial addons that give it functionality

So you change a port on your switch and it fixes it? How is this even fusionpbx related?

If it is of importance to you and you do not feel confident try the official fusionpbx support, mark will upgrade it for you.

You won't find anything that matches the capabilities of FusionPBX

Solved by phone

get us a log from the start to the end of a call.

Where did you add the settings?

Just before the bridge in the dialplan set the equivalent ot this: <action application="set" data="sip_h_P-Asserted-Identity=sip:blah@whatever" /> <action application="set" data="sip_cid_type=none"/> The setting cid type to none stops the gateway adding its own pid. Hope this helps

You have a problem with your ACL 1102 <1102>->1103 in context public It looks like you have put your IP addresses in ACL, that is fro providers. Remove them and flush cache and reloadacl.

Really, you need to use fqdn for each tenant, it is far easier this way

All you are seeing is single packets, this is no problem. You cannot stop UDP traffic entering your interface, that is what you are seeing. The only way to block it completely would be on an upstream firewall. What you are seeing shouldn't be causing you any problems, this traffic is not...

Also, no need for you to touch inbound routes generally, the destination should do it for you.

So do you have an inbound route for +16603385111? Look at the log in fs_cli it should help you more.

sngrep for now

Also, for good measure, if you have made changes and they do not seem to be getting applied, do a: rm /var/cache/fusionpbx/* Then restart freeswitch, this will clear your cache.

If you run /usr/bin/freeswitch it will start freeswitch using the current logged in user. If for example it is root, it will now create some files with ownership of root. When you now try and restart using systemd or whatever, it will fail as it cannot create the files it needs to as you have...

Post some logs