Yeah we have a couple other clients who have used them and never had an issue. The one particular customer needs and exorcism of their environment everything that can possibly go wrong will. NexVortex is just in a long line of things right now.

@FiyaFly said:

@coliver We're using Yealink phones. I'll take a look into it. Thanks!

I'm thinking the hardest part will be setting up the VPN on the PBX side.

@FiyaFly said:

Well, they send the notification as though they are getting a channel unavailable response from the PBX. I'm looking to call them tomorrow but wanted to see if anyone had seen this before. I do not think it is the PBX either.

Everything about this screams "hiccup in Vitelity" but of course, they'll pass it off as a PBX problem unless you can prove definitively otherwise.

@scottalanmiller said:

Elastix has been keeping VERY up to date on Asterisk, just not other packages.

They just rub me the wrong way with the support cycle anymore. Really regretting using Elastix back in March for this last roll out.

Well in a hosted system you don't have analogue lines so that isn't a factor for us.

Thanks guys, I missed the fact that this was a 'soft phone'

@IT-ADMIN said:

don't you use windows IP PBX like 3CX

No. We can if customers want to work with it. We've have experience with 3CX but it is not cost nor feature equivalent to Elastix, FreePBX, PIAF and others. The use if Windows as a base severely limits it's applicability.

Thanks @JaredBusch I will reach out to you on Monday to discuss the details!

We use an international blocking trunk provider. It's great peace of mind.

@scottalanmiller greaaaaaaaaaaaaaaaaaaaaaaaat, that's what i'm looking for, a bunch of experts willing to help and share their knowledge with other people,
really people will appreciate your work, thanks

@FiyaFly said:

I was recently doing a PBX install for someone and they were using a Sangoma Gateway. At first, it looked pretty simple and straightforward. The instructions to configure it with Elastix were about as straightforward as can be. If only it worked that way...

I ran into many little obstacles that I didn't expect to see with this setup. First, we couldn't get a SIP account to register as the instructions told us to do. Then, fax information seems to be stuttering and not passing through the way it's supposed to. DTMF tones transmit in a way that is completely arbitrary to the settings that are mentioned. As icing on the cake, for some reason it felt the need to strip the first character of the CID off as well.

Am I just severely unlucky or has anyone else had troubles like these with gateway devices for a PRI?

I have never used these PRI gateways. I have only had to deal with FXO/FXS interconnections. I have read mixed reviews on the Sangoma brand. Generally, once up and working they are great, but sometimes people cannot make them work. Again I have no personal experience with them though.

@Katie said:

What are the pros and cons of implementing an open-source PBX as opposed to a proprietary system?
I've worked in shops that ran Cisco Unity, and after that - Shoretel. I found Shoretel to be a great deal easier to learn over the Cisco system and had a fairly easy time administering it.
How do these compare to something like Elastix or Asterisk?
3CX is also a good solution, but it is not an open source one. I personally do not prefer it, but if you have a windows license to spare for a VM, it is quite easy to setup and not nearly as expensive as other options.
I use PBX in a Flash simply because I do not need the simplified Elastix interface and I want more up to date versions. If the Elastix team put more effort into staying updated I would use it everywhere.

You hit the nail on the head about the true cost of switching the phone system though. No matter what you go to, if it is not a true upgrade,you will have to redesign all of the call handling from scratch. The thing you need to validate with you upgrade is whether or not it is a 100% no reconfig needed upgrade. If there is time not accounted for to do something like that, then you just leveled the playing field again.

@NetworkNerd said:

This was something @FiyaFly and I worked on together, and I believe he was the one who fully resolved it by changing the baud rate settings on the physical fax machine. But I can say for a fact that this setup worked and is still working today at the site in question.

good job 🙂

@scottalanmiller Correct. Windstream, Patech, Cavelier all the same shiz. and shiz they are.