AppNeta | The Path

Arming the “voice” guy

Posted on: October 28, 2010

We get it, traditional telephony is perfect. Nobody ever dropped a call, nobody ever heard echo, and it only cost about as much as a small island in the south pacific per month to run.

“I’m just an old phone guy; I don’t get these network issues.” This is a common line I hear when working through a VoIP deployment issue where the telephony vendor/MSP has become suspect and needs some help in the network arena.

Well, hold on to your MOS scores, because we are on the case.

Our Partner was in the midst of a VoIP deployment at a multi-site financial institution. Three sites out of 27 were known to be experiencing call quality issues and so they enlisted PathView to help solve the problem.  In about 20 minutes worth of monitoring data those same suspect sites were identified and another three that were experiencing the same issue.

Diagnostics were run, providers called, problem solved?? Keep dreaming.

The providers ensured nothing was different about these six sites (except for the fact that the route happened to change for all six shortly thereafter, eliminating the loss found on the path – did I mention we track route history?)

Seemed like we were winning – but then the phone rang with tales of rolling waves of destruction from the central site out to ALL remote offices.  The client of our MSP was outraged.  He swore that this VoIP deployment was a nightmare, and our Partner had their back up against the wall once again.

“Now there is loss everywhere!” Our partner exclaimed.  “What do all these results mean?!”  – I wasn’t scared.

I took a stroll back through the monitoring data collected and found the beginning traces of the loss. I calmly stated, “Looks like something changed on August 25th at around 1:00 in the morning.” (This was clear to me from the spike in loss and a change in route at the core of the network).

Indeed, something did happen on August 25th around 1:00 in the morning. The client was responsible for a swap in network gear that had caused the issue in the first place.  Apparently the client and MSP shared a good laugh about it after the client realized the MSP clearly had all the facts even before the boss did.

But something bigger happened on the follow-up call I had with our Partner – he realized that the “voice guy” in him had just become data-dangerous.  Armed now with enough to diffuse issues from both providers and the end clients alike.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Follow us on Twitter!

Error: Twitter did not respond. Please wait a few minutes and refresh this page.

%d bloggers like this: