ThousandEyes announced something they called “new and shiny” at Networking Field Day 8 and it definitely caught my attention – not just because the word shiny was used* – but also because voice was the target of the announcement. I am quite used to being the literal and figurative red headed stepchild at networking events due to my involvement in that oh-so-unsavory world of voice** – but this Networking Field Day, voice got some well deserved attention.
ThousandEyes makes a product that via the use of Enterprise and Cloud Agents – those are active probes set out and about in your network, SaaS networks, and around the globe, you can gather some extremely detailed information regarding network performance, even when you don’t own all the pieces of the infrastructure along the path.
ThousandEyes is now leveraging that capability to ease the pain that is voice troubleshooting. Using probes that emulate RTP traffic, you can gather data that can be used for capacity and voice quality planning purposes, as well as for troubleshooting voice performance issues.
Say you are planning to bring a new site online and route voice to and from this new branch. Now you can collect detailed information that shows you how much this will suck (or perhaps not suck) *before* you go and purchase all the equipment for your design.
Say you are having trouble with voice between already established sites. This solution can help you identify capacity issues, jitter issues, and even DSCP remarking issues. That last one really makes me smile. How often is voice wrecked just because consistent QoS isn’t applied across all devices in the network? No need to answer that out loud, we all know…
So here’s an idea of what a voice test creation would look like. You can see there is a codec selection option, DSCP setting, and even a de-jitter buffer option that can be tweaked for the testing.
Below is an idea of what kind of data is being presented back. I really like that you can jump to the BGP path visualization and other layer tools just as usual with the product. Feel free to watch the short video here for the full show and tell.
Now it’s important to remember that this isn’t actually running tests on “real” calls being made in your network. While ThousandEyes makes a point of crafting probes to look and feel as much like actual application traffic as possible, it’s still not a live call. I did ask about workflow integration with some tool like Wireshark or something similar and got a to-be-continued type answer. In my vision, you would set alerts when thresholds were met that would kick off capture processes of live calls. Then you would correlate the .pcap files with this data to get a complete picture of the network. That way when the Director’s call to his beloved Aunt Erna drops and he wants to blame your really expensive phone system, you will have plenty of evidence to suggest that Aunt Erna just hasn’t mastered the art of speaker phone on her cell. Talk about a happy world.
*using the word shiny is a pretty good way to get my attention. Using actual things that are shiny, even better.
**hating on voice is a well-known pastime for those engineers too afraid to touch it. 😉
Disclaimer: While Networking Field Day, which is sponsored by the companies that present, was very generous to invite me to this fantastic event and I am very grateful for it, my opinions are totally my own, as all redheads are far too stubborn to have it any other way.