[cisco-voip] Re: QRT - Now what?

[Mike Armstrong]

Took the words out of my keyboard.  I guess we do the same thing we'd do if 
a user called and said they just had a call with X problem, whatever that 
might be.  My experience has been, however, that I'd better do SOMETHING 
pretty quickly, so that the sense of empowerment the user experiences while 
going through the QRT dialog isn't shattered by me saying, "Uuuhhhh... I 
haven't gotten around to looking to see if there are any QRT entries [today, 
this week, this month, yet]".  We run with all traces and logs enabled, so I 
can go back and fetch the applicable diagnostic information pretty easily 
with the Trace Collection Tool.  Unfortunately, it's usually Greek to me, 
but I can send it all off to TAC for translation.  Incidentally, FYI, I just 
did that the other day and was told NOT to collect the traces in XML format 
if I was going to send it to TAC, although I'd read somewhere earlier that I 
should.  Your mileage may vary.

Mike Armstrong
UF/IFAS CREC
Lake Alfred, FL

> From: "King, Jesse" <JKing at thegranitegroup.com>
> Subject: [cisco-voip] QRT - Now what?
> To: <cisco-voip at puck.nether.net>
> Message-ID:
> <80FDD0062521CE4084591182C4DDB6BE7414EF at papaya.thegranitegroup.com>
> Content-Type: text/plain; charset="us-ascii"
>
> Okay, So I have QRT setup now and have had about 5 entries in it for a
> 'other end can't hear me' issue which is sporadic.
>
> I'm looking at the CSV file but don't know what I should do from here.
> Logic tells me to grab the callid number and look somewhere else, but
> where? I also have CDR's setup...
>