06-18-2012 04:28 PM - edited 03-16-2019 11:43 AM
A user used the QRT button to report an issue with their phone call after it happened. I used RTMT to open up the log file that was submitted and the choice they selected (ie, choppy noise). The issue was that it happened on a call about 5 minutes earlier and for another extension that was listening in on the call. I see all the results, but am not sure what to look for or could identify anything that stood out. I read through some Cisco docs, but nothing really explained what to look for in these reports. Also, does the user need to use the QRT button during the call for best results and are there any good docs out there that would help with troubleshooting these results aside from the standard Trace log and/or Serviceability admin guides? Any help would be appreciated. Thanks!
Solved! Go to Solution.
06-18-2012 05:04 PM
Hi Eric,
The QRT log usually gives general information of the call such as the priblem reported (choppy voice), if it is an internal or external call, whcih gateway was used in case of external call, the codec used, IP addresses involved, jitter info, packets received and packets lost.
For example, the log wil begin with the date when the QRT button was pressed, category (problem call), the call state which was connected (talking), the call manager server ID that the phone is registered to (ID 2, server name CUCMSUB1), sample frequency in sec (30), calling number (XXXX), the called party number (YYYY), the device name, device IP, type of phone (79XX), protocol (SCCP), receive port number (26080), call codec (g.711).
Then the
Here's the QRT guide for your reference:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/8_6_1/ccmfeat/fsqrt.html
Regards,
Tere.
If you find this post helpful, please rate!
06-18-2012 05:04 PM
Hi Eric,
The QRT log usually gives general information of the call such as the priblem reported (choppy voice), if it is an internal or external call, whcih gateway was used in case of external call, the codec used, IP addresses involved, jitter info, packets received and packets lost.
For example, the log wil begin with the date when the QRT button was pressed, category (problem call), the call state which was connected (talking), the call manager server ID that the phone is registered to (ID 2, server name CUCMSUB1), sample frequency in sec (30), calling number (XXXX), the called party number (YYYY), the device name, device IP, type of phone (79XX), protocol (SCCP), receive port number (26080), call codec (g.711).
Then the
Here's the QRT guide for your reference:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/8_6_1/ccmfeat/fsqrt.html
Regards,
Tere.
If you find this post helpful, please rate!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide