@tim_g said in What Are You Doing Right Now:

@eddiejennings said in What Are You Doing Right Now:

@jaredbusch Apparently doing updates on FreePBX broke everything, and my dumbass didn't take a snapshot before installing the updates. So I'm restoring from one of the Vultr backups.

That doesn't sound like a good solution to use if you can't update without things breaking...

I think you just have to know what you are doing, dont feel bad @EddieJennings because most of my FreePBX broke from updates. I think someone thats worked with it for a while just knows what to do and what not to do.

@naammeinkyahai Ah, gotcha. I would still just directly call the billing department. If you explain the renewal is coming they will extend your grace period.

We have google music family (which gives you tube red for family) but previously had thousands and thousands of iTunes purchases.

Anymore it’s rare I find a song that isn’t on play, and I sync my playlists offline in iOS. If I Shazam something on the road (rare these days) I add to playlist and let it download immediately.

So basically I now use music.google.com for everything.

Have used plesk and did a lot of ripping in the 2000’s for music and video, but with the kids I finally switched to google.

I have to admit I never thought I would find myself doing this and like everything else these days we are hopelessly at the mercy of our cloud overlords.

@dbeato they should extend it and the reseller will then be abel to apply the license. Could be different in different countries but the billing department is definitely easier to deal with than support.

You will probably have to wait for a call back though.

Also, my email worked for 2 weeks past due before I had to call billing. Maybe I just got lucky though...

http://linuxbsdos.com/2015/12/01/chrome-remote-desktop-is-used-on-deepin-15-for-remote-assistance/

@scottalanmiller said in Issabel PBX " Elastix Alternative ":

@alyragab said in Issabel PBX " Elastix Alternative ":

Is there anyone who checked and worked with Issabel "the alternative application of Elastix "

Elastix has been dead for so long, and FreePBX picked up the space from it. What's even the purpose of Issabel at this point? I appreciate wanting PBX alternatives, but we already have a few. Is another one needed, especially one that is basically just copying FreePBX?

I'm not opposed to it, and maybe I'll give it a try at some point. But it seems like an odd project to have out there splintering the support community even further. Do they add a twist on to the Asterisk + FreePBX space that makes them important in some way? Wazo does some really different stuff from FreePBX. But FreePBX is the definitive Asterisk + FreePBX distro these days, so Issabel has a pretty up hill battle to relevance.

Hopefully someone from Issabel will hop in here and talk about goals and value proposition. I'm certainly interested, but my interest in it is certainly behind FreePBX and Wazo which are established as the leaders.

Yeah, I was trying not to be rude as I know people are trying to make that a go, but it reminds me of the BeOS project, Haiku or whatever. I stopped giving money 10 years ago when I realized it wasnt going to get anywhere like BeOS did. Also Q#$%#$ to Palm for ruining BeOS.

@scottalanmiller Just started this thread https://mangolassi.it/topic/14480/let-s-convince-someone-to-release-a-foss-pbx and looking for some support/feed back. I think we can convince someone to do this with a current production product. I have several ideas.

@restoronixsean The reason nothing ends up decentralized anymore, outside of investor interests, has a lot to do with the fact that it's just easier to control a closed ecosystem. Its harder to build compatible moving parts and keep them upgrade.

The biggest recent thing in memory would be Open Whisper Systems.

@scottalanmiller said in Let's Convince Someone to release a FOSS PBX:

@dashrender said in Let's Convince Someone to release a FOSS PBX:

@scottalanmiller said in Let's Convince Someone to release a FOSS PBX:

@dashrender said in Let's Convince Someone to release a FOSS PBX:

@scottalanmiller said in Let's Convince Someone to release a FOSS PBX:

Given that open source costs less to make, and as there is nothing in this model that would increase the support costs, why would it cost any more to support if given away than under the current model?

Giving it away wouldn't increase their costs but making/selling "cheap" support could drive their costs through the roof. Could be the operative word.

Why would they make "cheap" support. What does that portion mean?

A price that entices SMBs to buy it but the cost would be that SMBs using that support so much to overcome the income from the support contract. No clue how often that happens.

But none of that is needed. They don't have to change a single pricing thing. I think that you are assuming that they will change all kinds of things and get screwed. SUre, they can if they want to, but they can just as easily do that today without being open source and they have not. Going open source would not influence that in any meaningful way. Those are unrelated decisions. If they have a logical pricing model today, they would logically keep it exactly as it is.

Right, the product is already developed. It just get downloaded and used more. More opportunities to showcase other products. More opportunities to sell modules. More people in your forums trying things, asking questions, etc.

Just please no banner ads across the web interfaces. Please no proprietary hardware offerings. And instead of CAPEX for add-on modules at least offer a month to month version.

I've been thinking about how these conversations go online and searching throughout SW posts where the typical OP is looking for a good pbx, hosted, but no one wants to pay the $20 to $30 per user anymore. Then they are shown FreePBX, where you end up seeing them on freepbx forums getting their ass owner for not being a life long asterisk guru. Exchange server was this way for a while then hosted exchange went from $16/mailbox down to $4/mail per month. FOSS didn't fix this, economy of scale did. And for some reason Hosted PBX hasn't reached this.

I wonder if the solutions is about FOSS, or if it's not more about why there isn't a "voip.ms or flowroute for Hosted PBX"

Something simple, per device or extension at a bare bones cost. Perhaps bring your trunk from major providers that are peered in (voip.ms, twilio, telnyx)

If you could get something cheap and reliable on Hosted PBX that didn't force you to give up your control over your trunks, and was a la cartel monthly service like the new trunk providers are, would they negate the need for FreePBX?

So finding a FOSS pbx is the much better alternative, not getting a "flowroute for PBX"?

I've been playing with FusionPBX all day. I do wish Monster UI from a kazoo was built for a single server deployment...

I love the videos,

I hate that everything is VPN

@dafyre its definitely the best looking interface I have ever seen.

Installed FusionPBX and am actually going to cut over a friend's business next week after another day of testing from a $5 FreePBX isntance. They have about 4 locations and 60 phones. Lots of issues here lately with phones losing registration and having to be defaulted and reconfigured. They run their own instance so I am not sure if it is a FreePBX issue or something they did.

At least on all the phones I am testing Freeswitch certainly is faster, but that has always been the case in my experience over asterisk. I am running it on Jessie and I believe I could host a dozen tenants and hundreds of phones off a $5 or $10 vultr instance.

Also, no banner ads and no questions around the FOSS and licensing. Has an easy way to add your own CSS, GUI and Branding as well.

It's come a LONG way.

And I will add, I would never had suggested this before the hard fork and wouldnt suggest it 6 months or so from now.

But at this very moment things are going to be at its worst, a last for a few weeks til we get to block 479808. And still, there are going to be issues and people losing there coins. And I am watching closely to see what everyone not signed on to the NYA is going to do.

Just wanted to clarify why I am making a suggestion I otherwise would never make.

I would almost guess BTC is going to shoot up even more after this, because I feel like big money now owns BTC. We could see $30,000 for a BTC inside 12 months. Some people think it will peek at $40,000.

Have you ever installed Clip Studio Paint on a linux distro. Its available for Mac and Windows so Im hoping I could get it on Deepin for my older daughter who uses it for her drawings.

@dashrender This is my immediate thesis, I will be sure to share any pros/cons that come from real world use.

1.) Freeswitch is faster and IMHO better than Asterisk. Just park a call and pick it back up for a real world example.

2.) FusionPBX is multi-tenant, rebrandable, true open source. Can run a simple single server install and be expanded to multiple servers. No licenses or add on modules. True FOSS.

3.) I get mod_sofia instead of pjsip, and I ditch all my yealink ghost transfer and ghost call issues.

4.) Better provisioning and its also free. Using Yealink RPS and FusionPBX provisioning you can drop ship a phone to your customer and it will automatically configure itself out of the box.

You can also have a Yealink customer default their existing phone and Yealink RPS will send it new provisioning info when it reboots. So even a customer switching to you with existing phones could default their phones and be up on their new system with you instantly.

Also FusionPBX has templates for all major brands and models for easy provisioning.

4.) No banner ads for SIP Station, Proprietary phone hardware or links that would otherwise send your customers around you to Sangoma.

@markjcrane said in Replacing FreePBX with FusionPBX:

Another thing you can do for increased security is use domain names and don't register phones to IP addresses as the authentication realm.

Reason for this is when anyone attempts to register to the IP address we know they are not a customer. We have a fail2ban rule that can be enabled

Edit file /etc/fail2ban/jail.conf find enabled = false and set it to true the two sections that should be enabled are:

[freeswitch-ip-tcp]
[freeswitch-ip-udp]

service fail2ban restart

It pains me a bit to have these disabled but currently they are disabled as we need to inform the user to use domain names instead of IP addresses if they want tighter security. When we can educate users enough we may default these to enabled.

@markjcrane I really appreciate you coming online and sharing that tip. One of the problems in FreePBX is IP addresses getting banned when and brief internet outage occurs on the client side. Its nearly impossible to roam with Bria on your smartphone for all the constant banning that occurs when you go from cellular to wifi, etc.

For anyone following along he is referring to the server address you use to connect from the endpoint. I create an A record in my DNS (for example *.sip.domain.com and then you can create subdomains on the fly for new tenants (customer1.sip.domain.com, customer2.sip.domain.com).

I am still trying to figure out the best order to create user/device/extensions. It seems like devices would be created automatically when they auto-provision, but I assume the username/extension should be created manually.

I agree with a lot of what you are saying. Containers seem to be better for scale-out scenarios for fluctuating demand is critical. I am limited to only seeing containers deployed for VOIP/SIP carrier situations.

I have seen FS Logix talk a lot about their container based solution for One Drive and hosting true Office 2016 Outlook connections on VDI. I have absolutely no idea how this provides any advantage but its all over their website. I came across it while playing with RDSH and trying to find a reasonable sync/cloud drive solution.

I would be interested in hearing more about scenarios where this Containers have offered big advantages over automatically spinning up new VM's from a golden image.