Search results

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

Hence why I said to use the siptrace in sofia.

It should be relatively straightforward, have you contacted @markjcrane about it? He is the most experienced in this?

Freeswitch should definitely send the auth header if challenged. You can check Freeswitch itself is receiving the auth header by doing a: sofia global siptrace on in fs_cli to turn it off again: sofia global siptrace off

I think it largely depends on your customer base too. Between the companies I support there are about 2000 domains and thousands of extensions. I would say that probably 95% of them have never heard of FusionPBX. What I'm saying is that 95% of our customers just want to make phone calls and...

I suspect, without seeing any logs that you have added something to the access control list that you shouldn't have.

Depending on your version, it could be you need to clear the cache. Have a look in /var/cache/fusionpbx and delete any files that exist in there then restart freeswitch.

I've used jaspar reports for this sort of thing for many years: https://community.jaspersoft.com/

Ah, I see, mine is the case where we are the domestic abuse service itself.

Not that this will help you but more than the call actually not being in the billing system, are you actually stopping the agents seeing the caller ID? I just mention it as this was a requirement I had for a client with the same sort of call. I have nothing that will help you though as I did...

That should work, show us the outbound invite in sngrep