[cisco-voip] How to monitor dropped Calls

[Dennis Weikel]

The following should be verified if the problem happens regularly.

Verify QoS is applied end-to-end

1.    Make sure voice gateways classify\police traffic at egress
2.    Confirm and then reconfirm that your service provider (SP) is
applying the correct CoS profile.
3.    Make sure the switches are honoring the DSCP values assigned by
phones.



On Mon, Jan 30, 2012 at 8:25 AM, Nick Matthews <matthnick at gmail.com> wrote:

> Be wary - 'dropped calls' are some of the vaguest problem descriptions.
>
> Things that classify as a 'dropped call' - one way audio, no way
> audio, actual call drop with abnormal cause code, phone failover, lack
> of patience in queue, people who have walked away from their phone by
> the time it's answered, transfer failures, cell phone drops, and
> probably a few more.
>
> Even then, the one-way/no-way audio can be intermittent, mid call, or
> for the whole call.  Those are tons of fun.
>
> Even if you set up a trap for abnormal cause codes it's still likely
> users will report call drops you can't monitor, unless you're
> currently having call drops and already know you're seeing abnormal
> cause codes.
>
> -nick
>
> On Mon, Jan 30, 2012 at 10:48 AM, Dennis Heim <Dennis.Heim at cdw.com> wrote:
> > I would think it would be more important to monitor call quality.
> Latency,
> > jitter, mos scores. There are some monitoring products out of the box
> that
> > can do this, solarwinds, CUOM/SM. This can also to a degree be
> accomplished
> > with elbow grease and opensouce solutions(Nagios, cacti, pick your
> poison)..
> >
> >
> >
> > Thanks,
> >
> >
> >
> > Dennis Heim
> > Senior Engineer (Unified Communications)
> > CDW  Advanced Technology Services
> > 10610 9th Place
> > Bellevue, WA 98004
> >
> > 425.310.5299 Single Number Reach (WA)
> >
> > 317.569.4255 Single Number Reach (IN)
> > 317.569.4201 Fax
> > dennis.heim at cdw.com
> > cdw.com/content/solutions/unified-communications/
> >
> >
> >
> > From: cisco-voip-bounces at puck.nether.net
> > [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ryan Ratliff
> > Sent: Monday, January 30, 2012 7:07 AM
> > To: Robert Schuknecht
> > Cc: cisco-voip at puck.nether.net
> > Subject: Re: [cisco-voip] How to monitor dropped Calls
> >
> >
> >
> > You can monitor CDRs for "abnormal" disconnect codes.  There's nothing
> out
> > of the box that will do this for you.
> >
> >
> >
> > -Ryan
> >
> >
> >
> > On Jan 30, 2012, at 9:48 AM, Robert Schuknecht wrote:
> >
> >
> >
> > Hi List,
> >
> >
> >
> > Is there a way  to monitor dropped Calls in a CUCM environment? Our
> customer
> > wants to get informed by RTMT (Perfmon), Networkmanagement (SNMP)
> Systems or
> > E-Mail when dropped Calls are occurring. Especially for IP-Phone to
> IP-Phone
> > and IP-Phone to MGCP-Gateway Calls.
> >
> >
> >
> > Any hint is welcome!
> >
> >
> >
> > /Robert
> >
> > _______________________________________________
> > cisco-voip mailing list
> > cisco-voip at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-voip
> >
> >
> >
> >
> > _______________________________________________
> > cisco-voip mailing list
> > cisco-voip at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-voip
> >
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120130/03a74ac0/attachment.html>