Search results

This would pretty much be entirely within the nginx configuration, remove the server block for the hostname, reload nginx and that should do it I should imagine.

Nah, it's not like that. It's more for a residential use case, in that a person calls a charity for domestic abuse, and the abuser sees the call in the logs or bills; Ofcom regulation in the UK. The billing systems we have a fine for it, it's just allowing users to see the FusionPBX CDRs as well...

Anyone got any ideas on how to stop specific calls (vulnerable people charities, police, domestic abuse, etc) being logged in the CDRs? I'm not sure this functionality exists in the xml_cdr module for freeswitch.

These settings should help you out. Contacts can now be done with groups and user permissions (bit cumbersome, the device and extension needs to be assigned a user). Disabling that should give you three addressbooks as long as you enable them, extensions, groups and users. If you're like me...

I don't know about the extra 16 seconds, but is it because the two extensions have a timeout of 30 seconds?

Forgive me if I'm wrong, but I think it's so your outbound calls are correctly marked as such for CDR/Dialplan purposes. In previous releases, a few clients used to complain that outbound calls had the wrong 'arrow' in the CDRs.

What does it show in the logs when it hits this dialplan entry?

Would love this to be a built-in feature of FusionPBX. It's one of the few reasons we have to lose revenue and put them on a 3CX instead (the other being the proprietary desktop/phone app that does advanced presence, queues, etc)

Bit of a sanity check here, is the logic backwards for BLFs for the queues? Say I have the 3 agents: Agent Name Agent ID Contact adam 2001 2001 beth 2002 2002 chris 2003 2003 I was experimenting with a queue toggle button on the phones, ideally with a BLF just to emulate what they...

What you want is the Yealink Administrator Guide for your model of phones. It has the full list of variables to define Action URLs with so you could: Event: IncomingCall Action URL: https://172.16.0.1/help.xml?remote=$remote This will then send the remote SIP URI when it receives a call. You...

https://www.fusionpbx.com/app/tickets/public.php?type=bug I might take a pop at it when I've got the time. Plates pretty full at the moment.

If you mean you want the number displayed as a name, 3 options: 1. VOIP providers can sometimes do this for you. 2. Remote address books like the Yealinks. 3. Utilise the cidlookup.lua script: https://www.pbxforums.com/threads/running-a-script-on-an-inbound-call.6367/#post-26114

It's a big fat PHP class that takes a HTTP request, checks for things like user-agent, MAC address, and builds files appropriately. It's quite a difficult one to pin-point issues as so much happens at once. The index.php returns a 'dummy' 404 error for a few things that are wrong like if...

If you're going to do a pull request and submit it, then yes that would be the correct thing to do. This was just a fast and dirty personal patch.

Ah yes, it's taken straight from the DB: /var/www/fusionpbx/app/xml_cdr/xml_cdr_inc.php $sql .= "to_char(timezone(:time_zone, start_stamp), 'DD Mon YYYY') as start_date_formatted, \n"; $sql .= "to_char(timezone(:time_zone, start_stamp), 'HH12:MI:SS am') as...

Is it enabled?

Not in FusionPBX, out of the box it should allow for UDP SIP. Perhaps you have a conflict with another program? Might have to do some troubleshooting with tools like: 'ss' and 'sngrep'. Might even be an iptables rule.

Default Setting: domain --> time_format --> text --> 24-Hour or 12-Hour

Out of the box, external calls should be on 5080 and internal on 5060, then only use the ACL on the external profile?

Don't forget to think about emergency phone numbers too. Making people do wacky stuff like prefixing 9 before 911 or 999 is usually against the law, or frowned upon in some countries.