The good news here, though, is that the vast majority of VoIP problems are because of front-line service providers (like your ISP). In many cases, the use of any server can work, but this will only identify problems with your ISP - not with your VoIP provider. If you called your VoIP provider and they asked you to collect PingPlotter data, they may have given you a server to use. Ideally, this would be the actual VoIP server of your VoIP provider, or something on the same area of the network. We cover some of these topics in earlier manual entries, so we won't cover *details* of how to set things up here.įirst, we need a target server to monitor. Collecting data with PingPlotterīefore we can do much analysis, we need some data to analyze.
PingPlotter can offer a lot of insight into all of these questions. When you call them, how do you convince them it's their problem to fix?.If you need to call someone else, who do you call? Your ISP? Your VoIP provider?.Can you fix the problem or do you need to call someone else to fix it?.PingPlotter has some unique capabilities in its ability to help you track down the source of network problems. Using PingPlotter to identify the source of network problems Inability to connect a call to some users while you can call others.This can be exacerbated by network problems, but constant echo is usually not caused by network problems. In particular, if the symptom *always* happens, any time of the day, any day of the week, then there's a decent chance it's not a network problem. Other symptoms might not be network related. You start talking not realizing that the other party has started talking already too, and you talk over each other for a few seconds.Delays between the time you talk and the other side hears you (and vice versa).Gaps where the other side is talking, but you don't hear any of it.Garbled words ("blips" and clicks mixed in with the words).Here are some examples of symptoms that are often network related: Many symptoms of VoIP problems are network related (although certainly not all of them). This article will talk about some basic troubleshooting techniques that can be used to locate where the problem is occurring so you can make good decisions about how to solve the problem. If you're having voice quality problems, the problem is often related to the network - maybe your internet provider or maybe some other component between you and the called party. The underlying technology for VoIP is extremely network dependent. It can be inexpensive and relatively reliable.It can, however, also be challenging - with poor voice quality, the inability to hear and communicate, delays and other problems. Using an IP Network (like the internet) to conduct a voice conversation ( VoIP) is becoming easier and easier for people to do.
0 kommentar(er)
