Users report slrange behaviors when Ihey call external numbers from the company phone system. The company is using Cisco 8865 phones with Cisco UCM connected to a gateway with two T1 circuits. There is no indication of the possible problem, but the connection seems to be established Which command meets the requirement to capture all the data needed to debug the problem?
Suggested Answer: D
Get Premium 300-815 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
30 comments · newest first
DA
Dacia
11 months ago
D is too low, we need critical level for debugging.
LU
Luann
11 months ago
Wait, why would we need verbose? Isn’t that overkill?
LA
Lashawnda
11 months ago
I’m not so sure, C seems sufficient too.
DE
Delpha
11 months ago
Definitely agree with B, more verbose is better!
MO
Moon
12 months ago
I think option B is the best choice for detailed info.
TR
Tracey
12 months ago
I vaguely remember that "debug mgcp media tracelevel critical all" was mentioned in class, but I’m not sure if it applies here. I think "critical" is definitely the right choice, though.
CA
Caprice
1 year ago
I’m a bit confused about the difference between "critical" and "moderate." I feel like "critical" is the way to go, but I can't recall if verbose is really needed.
LE
Lenny
1 year ago
I think we practiced a similar question where we had to choose between critical and moderate levels. I feel like "critical verbose" might give us the most information.
CR
Craig
1 year ago
I remember we discussed the importance of capturing detailed logs for debugging, but I'm not sure if "verbose" is necessary here.
DU
Dustin
1 year ago
I'm a little confused by the wording of the question. It says "the connection seems to be established", so I'm not sure if the issue is with the call setup or the media itself. I might try option C, "debug mgcp media tracelevel critical", to start and see if that provides any clues before going for the more verbose option.
IV
Ivette
1 year ago
Okay, let me think this through. The issue is with external calls, so I'd want to capture as much detail as possible. I'm leaning towards option B - the "critical verbose" level should give me the full picture to identify what's causing the strange behaviors.
KA
Katie
1 year ago
Hmm, I'm a bit unsure about this one. The question mentions "no indication of the possible problem" so I'm not sure if the "critical" level is necessary. Maybe option D, "debug mgcp media tracelevel moderate", would be a better choice to start with and see if that provides enough information.
SU
Sue
1 year ago
This seems like a pretty straightforward question. I'd go with option B - "debug mgcp media tracelevel critical verbose" since it looks like the most comprehensive command to capture all the relevant data for debugging the issue.
TH
Thad
2 years ago
Haha, 'slrange' behaviors? Sounds like someone needs to spell-check their question. But seriously, I agree with Eric. The 'critical verbose' command seems like the best way to go here.
BU
Buddy
2 years ago
I'm with Martina on this one. When you're dealing with a mysterious issue, you can never have too much information. Going with the 'critical all' option seems like the safest bet to me.
MA
Mayra
2 years ago
I'm not sure, maybe 'critical' is enough to debug the problem.
MA
Marci
2 years ago
I think 'critical verbose' might be better, it gives detailed information.
TI
Tien
2 years ago
I agree with Martina, 'critical all' will give us the most information.
ET
Ettie
2 years ago
I'm not sure, but I think C) debug mgcp media tracelevel critical could also work to capture the necessary data.
BA
Basilia
2 years ago
I agree with Janine, because setting the tracelevel to critical all will capture all the data needed for debugging.
MA
Martina
2 years ago
Hmm, I'm not sure about that. Wouldn't the 'debug mgcp media tracelevel critical all' command be better? It seems to capture more information, and we need all the data we can get to figure out this strange behavior.
GL
Glendora
2 years ago
Let's go ahead and use 'debug mgcp media tracelevel critical all' to capture all the necessary data for troubleshooting.
KR
Kristal
2 years ago
I agree, we need as much information as possible to debug this issue. 'debug mgcp media tracelevel critical all' seems like the right choice.
CA
Caitlin
2 years ago
I think 'debug mgcp media tracelevel critical all' would be the best command to use. It captures all the data we need.
ER
Eric
2 years ago
I think the correct answer is B. The 'debug mgcp media tracelevel critical verbose' command will capture all the necessary data to debug the issue, including critical and verbose level details.
TA
Taryn
2 years ago
I believe option B is the best choice for capturing all the necessary data.
WI
Willetta
2 years ago
I'm not sure, but I think option B makes sense.
FL
Floyd
2 years ago
Yes, I agree. 'debug mgcp media tracelevel critical verbose' will provide detailed information.
PH
Phyliss
2 years ago
I think the correct answer is B.
JA
Janine
2 years ago
I think the answer is A) debug mgcp media tracelevel critical all.