Search results

Browser-Phone does look better on mobile, but if its not going to work as expected as-is without significant effort on my end I'd rather start from scratch.

Thanks for the offer to contribute, and you do make a valid point about the constant OS updates potentially requiring new builds, hopefully maintenance of the mobile apps (Android, ios) would be minimal given core functionality exists in the webapp which the mobile app is just a wrapper to.

Never take anything at face value, especially not crap from a plagerism machine. "Hard to maintain" is relative, I think the problem with the world in general, not just in tech, is that we have the wrong people assigned to the job, and that's why they find things hard. iOS does a pretty good job...

Didn't mean to imply anything about anyone's gitbilities, the talk around it just reminded me of the xkcd comic that still stings (as I'm no gitxpert).

https://xkcd.com/1597/

The mobile app will essentially be opening a browser pointed at the phone, basically option 1 from this copilot answer: https://copilot.microsoft.com/shares/Wq2iuEMxzKeZDaA5NyQ5Q

Hello world, After succesfully getting LinPhone for iOS to build then compiling MicroSip to provision with a hacky provision server I set my sights on MacOS and thought what a mess, multiple codebases (with various original authors in a hodgepodge of languages), why not write a single...

AI slop will keep us employed for years to come. I asked it for help coding session invalidation for a login workflow and it suggested I drop the user table and clear my redis cache. Redis didn't exist in my infra and thankfully I think before I execute commands.

Could this have happened to someone on a cut branch (a branch other than master/main)?

No need to explain further, thanks for the detailed reasoning around why you created event gaurd. I do recall the frustrations with fail2ban’s trigger happiness in my early days, actually had my customer get static IPs at all his locations so I could whitelist them. Nice to know that’s no longer...

Thanks, thankfully I haven’t touched that. Is fail2ban still recommended or is event guard enough?

Maybe the upgrade takes care of permissions, personally I’ve been prepending my Fusion related git operations with sudo -u www-data To avoid the warning and ensure permissions aren’t changed to root

Woot woot, gotta love open source! It’s been a few days since I applied your fix and removed my authentication proxy and just checked on it, working like a charm! Thanks for the contribution.

Glad it worked out, heaven knows I’ve over complicated stuff myself so totally get the lols!

I feel like your approach is over complicating it, I just downloaded a random VM greeting from the internet (mp3 format), then went to Applications > Voicemail > Greetings and uploaded it, then went to Applications > Voicemail > Extension to validate, and when I called in it just worked. That...

Thanks, I still need to work around or remove my authentication proxy likely stipping headers and/or rewriting requests, but I can confirm that after a reboot my permissions to /var/run/fusionpbx had reverted to root:root. Made the change you suggested but haven't rebooted yet.

I see there's some significant changes from 5.3 to 5.4, and like many others I'm facing issues with the websockets, though I've yet to open a ticket as I'm far from a vanila configuration. The first issue I faced was repeated service restarts due to failed authentication handshakes: while true...

Thanks, I'll upgrade this weekend and if I run into it will report, thanks for the feedback.

Thanks whut, greycom, and RTL. The permissions on /var/run/fusionpbx sound like a recurring theme in 5.4 (I have yet to upgrade) has this been reported to the maintainers via a bug ticket at fusionpbx.com?

Thanks for chipping in greycom, Tuly sounds pretty confident a restore which would restore permissions and certificates has nothing to do with it though. Tuly, your vibe is wasted as a tech practitioner, perhaps you should consider politics or management.