Skip to main content

VOIP Monitoring Project

Initially we deployed VOIP as a interoffice communication savings. With the presence in India we have, and its growth it has some huge savings attached to it. We then decided to modernize the call centers that we have deployed. That meant we were deploying Cisco solutions that were very network centric to function using call manager, and the rest of the suite.

In the next phase we realized that we were spending a huge amount of money on conference calling services. We use a LOT from every vendor you can think of. We even max out some of our vendors when we run conference calls for earnings periods. We started to implement Cisco Meetingplace. The product has been working well, and we are monitoring the same way we monitor any set of cisco devices, and a few windows machines.

One of our CEOs was on a conference call and it started to have voice quality issues. That they brought up the fact that we are missing a whole bunch of ways to debug and fix issues relating to voice and overall network quality. We came up with the following criteria, and set of vendors we are looking at:


 

Metrics

These metrics must apply across anywhere that KPI is used : Jitter Delay, R-Factor, MOS, Cocec Transcoding, QOS (load, cpu, memory)

Monitoring and Packet Capture

  

Network General

NetQOS

Wildpackets

General

Must Provide 7 days at 4gb/s of buffered capture of full packet data

  

  

  

Monitoring

Provide network and service monitoring based on metrics defined above

  

  

  

Operations

Provide Real-time network packet capture to monitor and troubleshoot problems quickly

  

  

  

Design and Planning

Ability to conduct VOIP quality testing and simulate traffic to measure and fix potential problems

  

  

  

Design and Planning

Provide MOS scores as well as R-Factor values for each call.

  

  

  

Operations

Analyze and track against PKIs to ensure voice quality and performance

  

  

  

Operations

Ability to provide per call analysis and support multiple signaling protocols for voice

  

  

  

Operations

Analyze packet level details of RTP, RTCP, MGCP, SIP, H323 streams

  

  

  

Operations

Evaluates packet delay variations, packet loss, jitter,

  

  

  

Operations

Provide Application Response Time (ART) analysis

  

  

  

Operations

Provide full 7-layer decodes, alarms, triggers

  

  

  

Design and Planning

Provide call playback or replay of captured data to hear and see VOIP impairments

  

  

  

Operations

Ability to extend monitoring and troubleshooting at remote locations

  

  

  

Operations

Perform analysis of mission critical applications both in real-time and post capture.

  

  

  

Operations

Provide Efficient per-call filtering to expedite problem resolution and minimizes packet transfer

  

  

  

Operations

Provide clear identification marking of VOIP calls, video conference calls and other services

  

  

  

Operations

Utilize standard SNMP and RMON probes. Ability to monitor relevant OIDs

  

  

  

Operations

Capable of importing or exporting file to standard formats

  

  

  

Monitoring

Monitor CISCO and other telephony devices from AVAYA or NORTEL.

  

  

  

Operations

Analyze call setup protocol of SCCP

  

  

  

Design and Planning

Measure network performance of RTP, MGCP, H323.

  

  

  

Display Web Reporting \ Dashboard view of information and events

  

  

  

  

Executive

Reports generated in HTTP web format for easy viewing. No use of plug-ins or Java on the client.

  

  

  

Executive

Reports can be formatted or imported into a dashboard style display

  

  

  

Executive

Provide Canned and Custom Reports

  

  

  

Executive

Historical data archived or saved for 1 year, and exportable via automated manner to standard DB platforms, MSSQL, Oracle, or MySQL

  

  

  

Executive

Able to import or export files from third party or freeware monitor tools to create reports

  

  

  

Executive

Report on Key performance indicators and measurements

  

  

  

Executive

Provide measurement of SLA levels

  

  

  

  

  

  

  

  

Comments

Anonymous said…
look at f5.com
Monday, December 17, 2007 9:56:00 AM
Post a Comment

Popular posts from this blog

Dynatrace Growth Misinformation

For my valued readers: I wanted to point out some issues I’ve recently seen in the public domain. As a Gartner analyst, I heard many claims about 200% growth, and all kind of data points which have little basis in fact. When those vendors are asked what actual numbers they are basing those growth claims on, often the questions are dodged. Dynatrace, recently used the Gartner name and brand in a press release. In Its First Year as an Independent Company, Gartner Ranks Dynatrace #1 in APM Market http://www.prweb.com/releases/2015/06/prweb12773790.htm I want to clarify the issues in their statements based on the actual Gartner facts published by Gartner in its Market Share data: Dynatrace says in their press release: “expand globally with more than three times the revenue of other new generation APM vendors” First, let’s look at how new the various technologies are: Dynatrace Data Center RUM (DCRUM) is based on the Adlex technology acquired in 2005, but was cr...
10 comments
Read more

Misunderstanding "Open Tracing" for the Enterprise

When first hearing of the OpenTracing project in 2016 there was excitement, finally an open standard for tracing. First, what is a trace? A trace is following a transaction from different services to build an end to end picture. The latency of each transaction segment is captured to determine which is slow, or causing performance issues. The trace may also include metadata such as metrics and logs, more on that later. Great, so if this is open this will solve all interoperability issues we have, and allow me to use multiple APM and tracing tools at once? It will help avoid vendor or project lock-in, unlock cloud services which are opaque or invisible? Nope! Why not? Today there are so many different implementations of tracing providing end to end transaction monitoring, and the reason why is that each project or vendor has different capabilities and use cases for the traces. Most tool users don't need to know the implementation details, but when manually instrumenting wi...
2 comments
Read more

IBM Pulse 2008 - Review

I spent Monday-Wednesday at IBM Pulse in Orlando. It was a good show, but quite a few of the sessions were full when I arrived. It was frustrating because they didn't offer them more than once. The morning sessions were mostly pie in the sky, and not very useful to me. I got to spend a lot of time with senior people in engineering, architecture, and acquisitions/strategy. I also got to meet people I knew from online or other dealings with IBM. Overall, the show was a good use of my time, and I found it enjoyable. Here are some of my highlights: ITM 6.2.1 improvements including agentless capabilities and such. New reporting framework based on BIRT which will be rolling forward. New UI which is being pushed and was on display from TBSM 4.2. Hearing about what other customers are up to (mostly bad decisions from what I've seen). Affirmation of ITNM (Precision) as a best of breed tool, with a excellent roadmap. Some things which are bad and make no sense: Focus on manufactur...
6 comments
Read more