Recent content by Herbert Whistlefjord

Whether this is the right way to do it or not I don't know, but the Extension Enter the extension number. field in the IVR settings actually accepts a name. Changed it from a number to a name, now it works, cannot match numeric outbound route.

I have an IVR 1234 that plays a message. I have an outbound route for 3+ digits to out to SIP provider. I have a Destination for a direct dial. If I assign an inbound route for this direct dial to an extension, it works [Note that the extensions are not numeric, so cannot accidentally match...

[From the other post that I can't reply to Because Reasons]: This was with an install of Debian 12 with just the SSH "task" chosen, using the stock 12.5 ISO downloaded from the Debian project - doesn't pull in rsyslog, so it's not just a cloudy thing. If FusionPBX depends on rsyslog then it...

1003$1 will evaluate to 1003101, if your user dialled 999101. Is that what you're intending?

But the official FusionPBX documentation isn't one of those many places. This forum is the first hit on Google when one searches for "fusionpbx api", the official FusionPBX documentation is second and the actual answer [the "members" page] is 8th, or 12th, if you count those "snippets" of things...

Bit odd that there's more information about the Bing API here: https://docs.fusionpbx.com/en/latest/search.html?q=api&check_keywords=yes&area=default than there is about the FusionPBX API! Even just a note saying that exists but you have to pay for it, would be a start.

allowipv6 is 'warning' not 'error'. 'error'-level events prevent the service from starting, 'warning' does not. I "fixed" the fusionpbx jail by commenting out the logfile and setting backend=systemd just to get fail2ban running BUT I don't know if this is the correct thing to do. If fusionpbx...

Something else, I can't see how sip-auth-ip relates to fail2ban? Maybe it doesn't! root@ukwpbx:/etc/fail2ban# grep sip-auth-ip `find -type f` root@ukwpbx:/etc/fail2ban#

I think this started happening after 5.1->5.2 update yesterday, as I still have a banned IP listed so definitely was working: Chain sip-auth-ip (1 references) target prot opt source destination DROP 0 -- 193.107.216.241 0.0.0.0/0 but today I am unable...

Can't reply to this: https://www.pbxforums.com/threads/xml_cdr-not-working-after-update.7284/ Trying to troubleshoot why no CDRs are shown on a new install. I have found with an install of 5.1.0 on Debian 12 in Azure that cron isn't installed. I don't know if this is a "feature" of Azure's...

Was all working Monday morning after they told me they couldn't see anything wrong. I'm blaming the carrier!

I have passed this to the carrier as a SIP trunk from them on a different SBC cluster behaves as expected, with an identical configuration. So pretty sure this is their issue.

I am using inbound routes with a regex to catch the destination number and then bridge the call to a downstream PBX, like this: action bridge sofia/internal/$1@172.18.20.5 I have found that there is no ringback in this scenario. I just get silence from the outside, then it...

Is it? To me, the most readable approach would be one inbound route for each thing that I want to route calls to, with one number per line. It sounds like agree's approach would achieve this. For some context, this is a PBX and SIP trunk consolidation project. The inbound route is not sending...

I need to apply a destination number condition to route a long list of numbers with no obvious pattern. So I could cram them all in to a single regex like condition destination_number ^(01324334832|01742743501|01550239421)$ but it's going to be unreadable [at least 15 numbers...