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...
-
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.
-
What about the PCI passthrough for Xen? Did that look promising?
-
@scottalanmiller said in PCI over Ethernet?:
Gotcha, so it is not an IVR issue, it is an IVR interface issue.
Exactly - He needs a new system basically, to become modern and no longer rely on hardware IVR
-
@Dashrender said in PCI over Ethernet?:
hate to suggest it - why not do VMWare for that one box? You could use the free version, and if you have a client based Backup solution you can do backups.
I thought about this. It's an option. Not ideal, but definitely on the list.
-
@anthonyh said in PCI over Ethernet?:
@Dashrender said in PCI over Ethernet?:
hate to suggest it - why not do VMWare for that one box? You could use the free version, and if you have a client based Backup solution you can do backups.
I thought about this. It's an option. Not ideal, but definitely on the list.
How long since you check on Xen doing this? I think that it has had what you need for a little while now.
-
@scottalanmiller said in PCI over Ethernet?:
Hmm. This looks intimidating (but that has never stopped me). I wonder how well this would translate to the XenServer world though. What would happen when I deploy patches? Hmm. Something to check out though.
-
@anthonyh Can you at least get a backup of the physical server?
-
@Dashrender said in PCI over Ethernet?:
Who wrote the IVR interface? Do they offer other non PCI options in light of PBX IVR solutions these days?
20 years ago, Nuance sold hardware solution IVR cards, today they sell IVR software that does the same thing and ditches the hardware requirement.
Of course management says - hey why do I have to spend money replacing something that works perfectly well - so good luck with that.
On my list is to query the vendor to see if they have a VoIP based solution. The system isn't as old as you may think. It's victim to the niche market which usually aren't up to snuff when it comes to modern technologies (hence the analog voice cards to ATA MacGuyvering :D).
I suspect if they have a solution it'll be expensive, but if it's our only option I'll push for it.
-
@Dashrender said in PCI over Ethernet?:
@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?
Good question. This system was implemented before my time. No clue what it cost. Definitely going to query the vendor if it's looking like my only option.
-
@aaronstuder said in PCI over Ethernet?:
Let's start with the basic's:
What OS is that last physical server on?
This server is running Server 2008 R2 I believe.
-
@anthonyh said in PCI over Ethernet?:
@scottalanmiller said in PCI over Ethernet?:
Hmm. This looks intimidating (but that has never stopped me). I wonder how well this would translate to the XenServer world though. What would happen when I deploy patches? Hmm. Something to check out though.
DO you need pathces wtih XS 7? I've not looked. It is very current, though.
