Search results

  1. A

    Upgrading from Version 5.0 to 5.2

    1. Create a backup 2. Create a backup 3. Create a backup 4. Restore from backup to make sure you can 5. Version Upgrade — FusionPBX Docs documentation. If you're going from 5 to 5.2 then do the steps in 5 to 5.1 and the steps in 5.1 to 5.2
  2. A

    Public Service Announcement: Message service may lead to increased CPU utilization

    Hello world, Thought I'd post these here as a future note to self and hopefully anyone else who finds themselves in the situation where their CPU utilization is off the charts for no obvious reason. The last time this happened I was experimenting with the messaging service so I knew what...
  3. A

    Reconciling CDR and other changes from Backup

    it was scary in the moment but after thinking of it as a data problem it ended up being an incredibly simple 3 step process: 1) make a csv of yesterday's cdr: copy (select * from v_xml_cdr where date(start_stamp) = current_date - 1) to '/tmp/yesterdayscdr.csv' (FORMAT csv); 2) move that file...
  4. A

    Reconciling CDR and other changes from Backup

    Hello world! I just rolled back to a snapshot from two days ago and am wondering if there are any tools/documentation out there on how to merge yesterday's CDR records and anything else necessary into the currently running instance (we didn't want to risk additional downtime by waiting to...
  5. A

    Stress/Load testing

    Thanks Adrian and DigitalDaz, really appreciate your sharing your insight and experience!
  6. A

    Softphone recommendation

    Read it, didn’t change my mind. The effort required to make it work isn’t worth it because: 1) that only applies to a subset of devices 2) you’re at the mercy Google continuing to support the mechanism, but its a gamble sip predates smartphones by quite a bit, mobile battery/energy efficiency...
  7. A

    Stress/Load testing

    Thanks Adrian, both for highlighing points I hadn't considered and for sharing siege with an example.
  8. A

    letsencrypt install certificate fail

    Start over following the instructions. If it fails, start over following the instructions.
  9. A

    Stress/Load testing

    Hello world, Just wanted to ask here to see what tools the community reccommends for stress/load testing a PBX installation. I'm currently just monitoring, listening to sample calls when load is high, and scaling up vertically as I grow, but I feel that I'm overprovisioned and would like...
  10. A

    anyone deployed on AWS Lightsail

    Thanks for the tip about nftables tracing, I've never encountered/used nftables before but it looks pretty powerful. Regarding the rpi running djangopbx and freeswitch, was it just an experiment or would you actually trust one to run your own phones? I had a pipe dream some time ago about a...
  11. A

    anyone deployed on AWS Lightsail

    You're right, it looks like it was designed to run on an internet facing host but AWS instances aren't exposed to the internet directly by default. Given that you're handling security before passing the traffic you may consider if a host based firewall is even needed in your use case. I still...
  12. A

    anyone deployed on AWS Lightsail

    I had the same issue when I used a bare IP address in the whitelist, changing it to CIDR format resolved that (add a /32 to the end of the ip address) The nftables.conf is pretty restrictive (the internet is a bad neighborhood), you'd need to modify it to be more permissive according to your...
  13. A

    anyone deployed on AWS Lightsail

    Thanks Adrian, haven't made it that far yet but good to know in case it comes up. Restarted from scratch and took notes along the way, was able to reboot and get back in, here's my notes from last night/this morning: # on a fresh install of debian as root: mkdir -p /usr/src/djangopbx-install...
  14. A

    anyone deployed on AWS Lightsail

    I keep speaking too soon, the below config lets me ssh back in but the webui is still blocked, but at least it's been narrowed down to specific configuration, not nftables in general. Oh yeah, to validate that just rename /etc/nftables.conf to something else enable and reboot. It can certainly...
  15. A

    anyone deployed on AWS Lightsail

    edit: I spoke too soon, didn't work after reboot Try during the installation process (or whenever I guess) commenting out the 172.16.0.0/12 subnet from the block whose definition is: Drop IPv4s not in internet (RFC 1918, RFC 5735 etc.) Your line numbers may vary, in my /etc/nftables.conf its...
  16. A

    anyone deployed on AWS Lightsail

    enabling nftables effectively killed the instance, I'll start over and stop there
  17. A

    anyone deployed on AWS Lightsail

    after enabling nftables and rebooting i'm locked out, lets see if I can get back in
  18. A

    anyone deployed on AWS Lightsail

    I'm not able to reproduce following these steps: 1. Install fresh debian 12.5 os-only lightsail instance 2. give it a static ip and configure dns to point to it (not sure about lightsail but with EC2 unless you explicitly assign a static IP every time you reboot you could be assigned a...
  19. A

    anyone deployed on AWS Lightsail

    Thanks for the input about EC2 and sorry I was wrong about lightsail messing with stuff. The problem is that AWS doesn't assign instances public IP addresses, and the djangoPBX install script uses the IP address it detects for configuring nginx. This IP is not routable from outside your VPC...
  20. A

    anyone deployed on AWS Lightsail

    With LightSail you're trading control for convenience, try an EC2 instance and you won't get any surprises or 'help' from an automated admin. Actually, maybe just look in the AWS console instead of on the host itself: Use a launch script to configure your Lightsail instance when it starts up -...