Troubleshoot archives - Unified Communications: Click to talk

Unified Communications: Click to talk:

troubleshoot

Sep 24 2009   3:58AM GMT

It (Almost) Never Hurts to Update



Posted by: Tony Bradley
Unified Communications, UC, patch, update, troubleshoot

One of the steps that should be on somewhere in the top 5 troubleshooting steps for virtually any problem is ‘download and apply most current update’ for the software or hardware in question (and/or peripheral software or hardware that could be related to the problem).

Another top 5 step would be to Bing (or Google if you prefer) the issue and see what the vast Interwebs might have to say on the subject. It usually helps to be as specific as possible- like copying and pasting the actual error message you are seeing. Often you will find that this step leads to the first step I mentioned as you encounter comment after comment from users who had the same problem until they applied the latest update.

A recent blog post on the OCS Team blog illustrates how sometimes the latest update may even address issues not specifically called out in the knowledgebase or readme text. If you end up calling for support, applying the latest upates is guaranteed to be one of the top 5 steps the custmer service tech walks you through, so you may as well cut out the middle-man and just do that part before you call.

Bottom line- it never hurts to apply the latest updates…except when it does. There are occasionally patches and updates that break more than they fix, but those are fairy rare these days (at least from estabished / major vendors). The odds of a corrupt patch are probably significantly lower than the odds that applying the latest upate could solve your problem.

Jul 8 2009   8:49PM GMT

Troubleshooting VoIP / UC Issues



Posted by: Tony Bradley
troubleshoot, jitter, latency, dropped packets, VoIP, Unified Communications, UC, colasoft, capsa enterprise, network analyzer, packet sniffer

Networking has always been a more or less imperfect science…perhaps more of an art? The TCP/IP suite of protocols are designed with the base concept that transmitting packets of data is prone to errors and the protocols need to have mechanisms built in to manage dropped packets, latency, and other issues.

With normal data networking it may not be a big deal if packets arrive out of order. As long as the TCP/IP protocols can reassemble them in the proper order there may be a millisecond or two of lag but the data will get there. However, with voice and video a millisecond may as well be a millenia. With VoIP, and audio/video conferencing it is much more important that data arrive quickly and in order.

Microsoft provides a comprehensive amount of guidance and documentation including Troubleshooting Enterprise Voice: Approaches, Procedures, and Tools.

One valuable tool for monitoring and troubleshooting network issues is a network analyzer (also known as a protocol analyzer or packet sniffer). I recently had an opportunity to work with the Capsa Enterprise Network Analyzer and would recommend it as a powerful, cost-effective tool for troubleshooting VoIP / UC, as well as other network issues. You can learn more about Capsa Enterprise from this review (there is also a link to a more extensive product white paper).