login | register
Sat 17 of May, 2008 [06:30 UTC]

voip-info.org

Search with Google
Search this site with Google. Results may not include recent changes.
 
Google Ads
Shoutbox
  • Juan Ortega, Thu 15 of May, 2008 [10:33 UTC]: Hi everybody, I'm Juan, an ITCom student, and I need to know what basic elements I need to create a VoIP network. Can anybody helpme, please?,Thank you very much
  • gineta, Wed 14 of May, 2008 [03:58 UTC]: any here not fine the configuration of firewall juniper -screem for VOIP asterisk????
  • Anoop Prabhakaran, Tue 13 of May, 2008 [12:16 UTC]: I am developing Asterisk IVR, Whenever i make a internation call to the IVR system, the DTMF is not getting detected properly, this happens only for the first time, second call onwards system works fine. why this is happening
  • joe, Mon 12 of May, 2008 [04:27 UTC]: Is there an opensource browser based softphone, or a system like Busta where everything is not manages through their website?
  • Nick Barnes, Fri 09 of May, 2008 [11:36 UTC]: Christopher - yesterday I tried an Asterisk install on a CentOS 5.1 box with stock GUI and it all worked fine. Sorry I can't help.
  • aero, Fri 09 of May, 2008 [08:20 UTC]: can someone help me out on this, i tried to play some sound files on my asterisk box and this is the error message i got. WARNING[4429]: format_wav.c:169 check_header: Unexpected freqency 22050 May 8 11:17:39 WARNING[4433]: codec_gsm.c:194 gsmtolin_fra
  • Christopher Faust, Thu 08 of May, 2008 [14:15 UTC]: I beleive that I may have to change something in the xserver configuration. Please advise
  • Christopher Faust, Thu 08 of May, 2008 [14:14 UTC]: Everything was perfect. In the bios I have increased the memory allocated Still receive input not supported on my display.
  • Christopher Faust, Thu 08 of May, 2008 [14:13 UTC]: This would not be my main box. I am doing some testing to see if I can install zaptel and asterisk 1.4 on a full centos 5.1 box with development software Its bizzare, because before I went through the asterisk and zaptel installation everything was perfe
  • Nick Barnes, Thu 08 of May, 2008 [13:44 UTC]: Christopher - I can't see any way in which an Asterisk installation would muck your GUI, but remember that it is advised not to use a GUI on an Asterisk box anyway.
Server Stats
  • Execution time: 0.41s
  • Memory usage: 2.18MB
  • Database queries: 31
  • GZIP: Disabled
  • Server load: 0.45

BlueWave Telecom's VoIPFlow 2.0

For more information see:
VoIPFlow 2.0 Product page

BlueWave Telecom's VoIPFlow 2.0
Our premier product is VoIPFlow 2.0, a software platform that allows service providers to provision and manage thousands of virtual PBXs, thereby enabling a new revenue stream for their business. With features such as One Click PBX Deployment (tm) and the concept of hardware nodes as compute resources, VoIPFlow has the most advanced architecture on the market for managing many virtual PBXs at once. We make Asterisk industrial strength. This software is not geared for the single PBX install, but rather for the service provider who must maintain hundreds or even thousands of virtual PBXs. Our user interface is abstracted away from the underlying open PBX config files and allows the user to completely provision and manage the PBX via a simple and intuitive user interface. System wide settings are available to manage your entire PBX inventory. VoIPFlow runs on commodity Intel or AMD servers and you may host the solution yourself in your own data center, or you may choose to have us host it as an on-demand solution.
                                                                                                                              
Architecture
VoIPFlow is built on a custom 64bit Linux kernel called the BlueWave kernel. We hand build our Linux kernel so that we know exactly what is inside…nothing extra…just the core of what we need to provide a screaming fast OS. Next, we utilize a custom virtualization layer that allows every PBX that we spin up to believe it is running on its own server, complete with a Linux process 1. The overhead for our custom virtualization layer is less than 2%...very efficient. On top of that we layer our security and licensing modules. These modules protect our intellectual property and provide us a secure and undeniable way to do accurate billing, inventory, and software updates to our licensed systems. Then we layer on a pluggable PBX module. We have built the system so that it may take advantage of any open PBX system on the market that supports open standards. In this release we have chosen to include Asterisk in our distribution. Next, we hand build the custom logic necessary to provide fail-over, load-balancing, and auto-leveling. Finally we layer in a beautiful, CSS-based user interface to tie it all together. Our architecture is built for scalability. In order to scale, you simply plug in another hardware node and the system can be rebalanced. You can run several hundred of our virtual PBXs on a single hardware node.



For more information see:
VoIPFlow 2.0 Product page
Created by Ken Burge, Last modification by Ken Burge on Sat 18 of Nov, 2006 [00:07 UTC]

Please update this page with new information, just login and click on the "Edit" or "Add Comment" button above. Get a free login here: Register Thanks! - support@voip-info.org

Page Changes | Comments

Sponsored by:

Terms of Service Privacy Policy
© 2003-2008 VOIP-Info.org LLC

Powered by bitweaver