PCI over Ethernet?
-
@anthonyh I am a FreePBX fan myself. I think others here are too
-
Sure their IVRs are easy to use for the functionality of the switch they were built for (PIAF or FreePBX, etc) but what about extending them? can it done? I'm sure it can, the question is at what cost?
-
Which brings up a great question - how much did that old hardware solution cost you?
-
@scottalanmiller said in PCI over Ethernet?:
@anthonyh said in PCI over Ethernet?:
@aaronstuder said in PCI over Ethernet?:
@anthonyh said:
PBX In A Flash.
Why?
Why not? Except for this very specialized scenario, PIAF has worked beautifully and has saved us a shit ton of $$$$.
Saved you money compared to the standard alternatives of FreePBX or Elastix which are also free and their IVRs are very simple to use?
I'm confused. My understanding is PBX In A Flash is a variant of FreePBX. In fact the web interface says "FreePBX" all over it???
-
@anthonyh said in PCI over Ethernet?:
@scottalanmiller said in PCI over Ethernet?:
@anthonyh said in PCI over Ethernet?:
@aaronstuder said in PCI over Ethernet?:
@anthonyh said:
PBX In A Flash.
Why?
Why not? Except for this very specialized scenario, PIAF has worked beautifully and has saved us a shit ton of $$$$.
Saved you money compared to the standard alternatives of FreePBX or Elastix which are also free and their IVRs are very simple to use?
I'm confused. My understanding is PBX In A Flash is a variant of FreePBX. In fact the web interface says "FreePBX" all over it???
To me that makes me ask - why not just use FreePBX then? what made PIAF better than FreePBX? I'm asking since I have no clue.
-
@anthonyh said in PCI over Ethernet?:
@scottalanmiller said in PCI over Ethernet?:
@anthonyh said in PCI over Ethernet?:
@aaronstuder said in PCI over Ethernet?:
@anthonyh said:
PBX In A Flash.
Why?
Why not? Except for this very specialized scenario, PIAF has worked beautifully and has saved us a shit ton of $$$$.
Saved you money compared to the standard alternatives of FreePBX or Elastix which are also free and their IVRs are very simple to use?
I'm confused. My understanding is PBX In A Flash is a variant of FreePBX. In fact the web interface says "FreePBX" all over it???
Yeah, that's a confusing piece. FreePBX is an interface for Asterisk. There is also a PBX called FreePBX. All made by the same team. So while PIAF, Elastix, TrixBox and FreePBX are all PBXs that use the FreePBX interface.... only one is made by the FreePBX team.
-
Ok, this thread is derailing fast....
-
@Dashrender said in PCI over Ethernet?:
@anthonyh said in PCI over Ethernet?:
@scottalanmiller said in PCI over Ethernet?:
@anthonyh said in PCI over Ethernet?:
@aaronstuder said in PCI over Ethernet?:
@anthonyh said:
PBX In A Flash.
Why?
Why not? Except for this very specialized scenario, PIAF has worked beautifully and has saved us a shit ton of $$$$.
Saved you money compared to the standard alternatives of FreePBX or Elastix which are also free and their IVRs are very simple to use?
I'm confused. My understanding is PBX In A Flash is a variant of FreePBX. In fact the web interface says "FreePBX" all over it???
To me that makes me ask - why not just use FreePBX then? what made PIAF better than FreePBX? I'm asking since I have no clue.
Probably the era when they built it. There was a time like eight years ago when Elastix 2 wasn't established yet and TrixBox was waning that PIAF was pretty viable.
-
@anthonyh Sorry
-
@anthonyh said in PCI over Ethernet?:
Ok, this thread is derailing fast....
So how much did you pay for the old hardware solution and who built it?
Do they have a solution that works directly with today's PBX IVRs?
-
Why change something that we have aboslutely no issues with? It wouldn't save us any money, and we are intimately familiar with how PBX In A Flash is built and are able to adequately support it. So...???
In any rate, I'm going to try to get this back on topic...
-
Let's start with the basic's:
What OS is that last physical server on?
-
Well we don't have a PCE over Ethernet option. I searched and didn't find one. Xen might have the PCI passthrough that you want, but I've never tried it.
Given that we don't have the one and the other would need testing, the obvious answer is to try to solve the goal rather than the proximate, which is best anyway.
Given that, if FreePBX is a drop in replacement for PIAF but does a great IVR, does that not solve several issues rather than just one? In what way is replacing the IVR bad?
-
@anthonyh said in PCI over Ethernet?:
Why change something that we have aboslutely no issues with? It wouldn't save us any money....
Doesn't it? Are the physical IVRs going to be free forever and carry zero risk? If not, it seems like it does save money, at least eventually. It also protects you from something you don't have protection from today AND solves the problem that you are trying to solve here, right?
-
@anthonyh said in PCI over Ethernet?:
Why change something that we have aboslutely no issues with? It wouldn't save us any money, and we are intimately familiar with how PBX In A Flash is built and are able to adequately support it. So...???
In any rate, I'm going to try to get this back on topic...
Sure the question was asked why you used it - but I didn't read anyone suggesting that you should change it.
But - maybe that is one solution for you.
IF you can move to a PBX with built in IVR, that might be the best solution for you.
-
@scottalanmiller said in PCI over Ethernet?:
@anthonyh said in PCI over Ethernet?:
Why change something that we have aboslutely no issues with? It wouldn't save us any money....
Doesn't it? Are the physical IVRs going to be free forever and carry zero risk? If not, it seems like it does save money, at least eventually. It also protects you from something you don't have protection from today AND solves the problem that you are trying to solve here, right?
This assumes he can build a solution based on some free PBX/IVR solution.
-
@scottalanmiller said in PCI over Ethernet?:
@anthonyh said in PCI over Ethernet?:
Why change something that we have aboslutely no issues with? It wouldn't save us any money....
Doesn't it? Are the physical IVRs going to be free forever and carry zero risk? If not, it seems like it does save money, at least eventually. It also protects you from something you don't have protection from today AND solves the problem that you are trying to solve here, right?
Give me a minute to type up a post. I'll explain what this IVR system is and it should make sense after that.
-
@Dashrender said in PCI over Ethernet?:
@scottalanmiller said in PCI over Ethernet?:
@anthonyh said in PCI over Ethernet?:
Why change something that we have aboslutely no issues with? It wouldn't save us any money....
Doesn't it? Are the physical IVRs going to be free forever and carry zero risk? If not, it seems like it does save money, at least eventually. It also protects you from something you don't have protection from today AND solves the problem that you are trying to solve here, right?
This assumes he can build a solution based on some free PBX/IVR solution.
Which is why I asked if it would solve the issue.
-
I think some of you are stuck on "IVR" and thinking "Oh just make your phone system do that." It's more complicated than that and I will explain:
The system I am talking about is an IVR interface for our Jury Management System (I work for a court). It interfaces with said JMS system and allows Jurors to check when they need to report for jury duty and submit any responses requested based on the Juror Summons they received in the mail. They key in their badge number, their last name, and then based on their jury duty history are then presented with various options (check whether or not they need to report for jury duty, request an excuse from jury service if they are eligible for exclusion based on their jury duty history, update their juror information, respond to supplemental juror questions if there are any, etc.).
Hopefully this makes it a little clearer. If it was a simple IVR tree I would have already re-crated it in our PBX.
I'm also going to append this to the OP.
-
Gotcha, so it is not an IVR issue, it is an IVR interface issue.
