Recent content by Herbert Whistlefjord

  1. H

    SOLVED Setting line type default to 5061/TLS

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

    Logging when extensions change state

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

    Logging when extensions change state

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

    SOLVED Setting line type default to 5061/TLS

    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?
  5. H

    Difference between "Status UP" and "Status UP (ping)"

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

    Difference between "Status UP" and "Status UP (ping)"

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

    Using FusionPBX as SIPTRUNK server

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

    Using FusionPBX as SIPTRUNK server

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

    Bullseye to Bookworm upgrade

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

    Emails on Event Guard events

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

    Inbound calls to IVR gets routed outside.

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

    Inbound calls to IVR gets routed outside.

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

    Fail2ban not starting after update to 5.2

    [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...
  14. H

    SIP PBX integration

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

    API for enable/disable extension and domain

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