Hybrid PBX systems

Article (5)

Cisco knocks out Avaya as IP PBX heavyweight
IP PBX adoption is rising as Cisco and Avaya square off for market dominance.
Network configuration management key to VoIP success
While companies spend millions on upgrading infrastructure for VoIP, little attention is given to solving the largest source of downtime â€“ configuration-related outages due to human error. A well-defined change management process built around a configuration management system can virtually eliminate the "self-inflicted" errors, which currently account for about 60% of all network outages.
How is average repair time determined for both a TDM PBX and a VoIP system?
I am trying to find some statistics on average time to repair or troubleshoot VoIP and TDM PBX. We heard PBX takes 30 minutes versus VoIP at 4.5 hours -- is this true?
VoIP convergence: Managing staffing issues
Companies making the transition to IP telephony must find a way to converge their voice and data networks -- and the employees who work on them.
Managing converged networks: The next challenge
Enterprises are well-versed managing separate voice and data infrastructures, but they do not have the tools and training necessary to manage SIP-based VoIP and multimedia applications. To take advantage of this technology, a new breed of IP expert must be trained to architect, implement and troubleshoot the converged IT environment at the session layer.

Tips (2)

How can VoIP be integrated into an existing PBX system?
I am trying to integrate VoIP into my existing PBX system. I have a Talkswitch 48CVA which supports both PSTN and VoIP lines. My main phone number is a landline which forwards calls to my VoIP line when my status is busy or I do not answer. When my first VoIP line is busy/no answer, it is, in turn, set to forward to my second VoIP line. If my landline is in use, the second call will forward to my VoIP line without a problem. However, if my landline and my first VoIP line are both in use, the next call into my landline merely receives a busy signal. In theory I should not have a busy signal since my first VoIP line should forward to the second VoIP line. The phone company said they only forward one call at a time. If they were all landlines or all VoIP lines I could do hunt/rollover. But since they are a hybrid of both, it seems neither provider wants to accommodate the situation. Do you have any suggestions on how a small business can integrate incoming calls into both landlines and VoIP lines?
How can choppiness during a phone call be eliminated?
I have a WAN that consists of two LANS. On that network there are two Toshiba phone switches. I wouldn't say that it is a VoIP system as the individual terminals are digital. For some reason we sporadically experience some choppiness in the calls from node to node; the choppiness is not quite a delay or an echo -- it seems more like a broken call. I have verified the priority of voice on the routers as well as the timing. But the problem still occurs and it is frustrating when it occurs on conference calls. Is there anything else that we may be missing that could be improved on this situation?

© 2010 TechTarget ANZ. All Rights Reserved. Designated trademarks and brands are the property of their respective owners. Use of this website constitutes acceptance of the TechTarget ANZ Terms and Conditions and Privacy Policy.

TechTarget ANZ sites: SearchCIO.com.au | SearchNetworking.com.au | SearchSecurity.com.au | SearchStorage.com.au | SearchVoIP.com.au