Defining traffic policies

Article (2)

Pinpoint VoIP call quality issues with smart diagnostics
NetIQ's Hafid Saba explains how to troubleshoot VoIP call quality in this exclusive tip.
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.

Tips (4)

When should a VoIP system be analyzed and with what tools?
We have recently implemented a VoIP network with separate VLANs and QoS. It all seemed to be working fine when it first went in, but recently, certain people have been complaining about sound breakup whilst talking to customers on the phone. I have also had similar problems, but thought it was due to the amount of diagnostics software that I was running on my PC. To check, I moved my phone into its own port and the breakup is still there. Any ideas how we can check to make sure that the network is doing alright? Also are there any software utilities that would help us with day to day analyzing?
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 does the service provider differentiate between data and VoIP as data?
For our mobile devices in trucks, we use GSM/GPRS communication. Our customers are paying for a certain data amount -- depending on the service package to which they subscribe. We use a modem in our device, which can do both data and voice. But as I understand it, with VoIP, everything becomes data. So, is it cheaper for the user if they use VoIP? How will operators handle this from a business model perspective? Will they expand the data amount packages or will they need to differentiate between "regular" data and VoIP data? And a technical question: how much VoIP data am I consuming if I have a one minute voice conversation?
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