Search results

Thanks, that has worked. I guess I was over-thinking it!

Is there a way to pipe the output of a fs_cli /event subscription? I have this: /event plain CHANNEL_CREATE CHANNEL_DESTROY CUSTOM sofia::register sofia::unregister but it produces a crazy amount of output, about 60 line for every event. I can't do it with fs_cli -x , that just claims that...

I feel like the information I am after is probably all "in there" somewhere, because we have a Registrations table and we have Event Guard watching for failed logins. I am interested in extensions change state, ie register, unregister or expire. But when I look in the logs, I don't see events...

Where can I change the line provisioning globally so that 5061/TLS is used? In Default Settings we have "line_sip_port", that can easily be set to 5061. But line_sip_transport is "tcp" and looking at account.X.sip_server.Y.transport_type, the valid values are 0 - 3, so how do these interact?

I am inferring from this: https://github.com/signalwire/freeswitch/issues/2489 that "UP (ping)" means that FreeSWITCH has sent an OPTIONS ping but has not yet received [or perhaps, processed] a response, but the previous response was UP. But that's just a guess.

What's the difference between these two statuses? They were run 60s apart: ================================================================================================= Name e90a3575-fdbf-4c03-8a93-cf0c889fe64f ... Ping 1742483830 PingFreq 60 PingTime...

Yeah, that's the other half of the solution I use, for the outbound dialling.

I have something like this working for giving multiple phone systems access to a single SIP trunk. No registration involved at all, all IP-based. Multiple inbound routes looking like the attached.

A colleague updated the OS of a FusionPBX system from Debian 11 to 12 last year. The upgrade process did not update the release in /etc/apt/sources.list.d/php.list accordingly so the system is still using the Sury 8.1 PHP packages. Everything looks to be fine but PHP 8.1 is approaching EOL so I...

Is it possible to get FusionPBX to send an email on Event Guard events?

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