I am planing the network for a large VoIP provider and have been looking at Xen and VMWare. I have tested our VoIP applications such as BroadSoft on Xen and ran into some big problmes such as duble page fault that kills the whole box. I have talked with VirtualIron and they have found the same issues with Xen and say they have patches for their implimentation, but their beta is full and I can't test for 30 days. I have tried to get a VMware sales guy to call me, left 2 messages and emailed twice with no responce, funney since they want about 4X the cost of VirtualIron.
I am working on a new VoIP startup and looking at virtualization. I looked at VMware, but the preformance sucked big time. Xen may not have the nice management interface (yet), but the approach gives far far better preformance. I just don't see why you would be willing to pay a 20 - 40% hit using VMware vs Xen.
Most switches will accept caller ID digits, and pass them, however names are normally from CNAM via line information database base (LIDB). If you are the CLEC of record you can update LIDB to be whatever you want. CNAM filed is 15 char long and only (A-Z) and ",".
Hmm, how would this work? Again, CID is something that is passed, caller name (CNAM) is not. The end switch will do a CNAM lookup for caller ID with name. Does your VoIP provider publish the data in the LIDB?
I just finsihed building the caller ID with name system for BroadVoice. I built a gateways system to a CNAM provider with a SIP stack on the other end to talk to our application servers. I now am looking into what I should do next in this area. Going to add the ability to add custom names to incoming calls so your CID text could be "Dad" vs PATRICK STRATTON or someting like that, but since we are not a CLEC we could offer Caller ID spoofing also as an option, but are worried about many of the donwsides.
Slashdot Mirror
I am planing the network for a large VoIP provider and have been looking at Xen and VMWare. I have tested our VoIP applications such as BroadSoft on Xen and ran into some big problmes such as duble page fault that kills the whole box. I have talked with VirtualIron and they have found the same issues with Xen and say they have patches for their implimentation, but their beta is full and I can't test for 30 days. I have tried to get a VMware sales guy to call me, left 2 messages and emailed twice with no responce, funney since they want about 4X the cost of VirtualIron.
I do actually, I guess what I don't understand is now that XEN is also supporting full virtualization why one would go with VMWare.
I am working on a new VoIP startup and looking at virtualization. I looked at VMware, but the preformance sucked big time. Xen may not have the nice management interface (yet), but the approach gives far far better preformance. I just don't see why you would be willing to pay a 20 - 40% hit using VMware vs Xen.
-Nathan
Ya, it is odd that BroadVoice was not mentioned at all, oh well. There is always next time.
Na, I gave him free US and International, we can't do 900. -Nathan
Most switches will accept caller ID digits, and pass them, however names are normally from CNAM via line information database base (LIDB). If you are the CLEC of record you can update LIDB to be whatever you want. CNAM filed is 15 char long and only (A-Z) and ",".
Hmm, how would this work? Again, CID is something that is passed, caller name (CNAM) is not. The end switch will do a CNAM lookup for caller ID with name. Does your VoIP provider publish the data in the LIDB?
I just finsihed building the caller ID with name system for BroadVoice. I built a gateways system to a CNAM provider with a SIP stack on the other end to talk to our application servers. I now am looking into what I should do next in this area. Going to add the ability to add custom names to incoming calls so your CID text could be "Dad" vs PATRICK STRATTON or someting like that, but since we are not a CLEC we could offer Caller ID spoofing also as an option, but are worried about many of the donwsides.