It is not much output actually, you can limit to one pri if you want and will let you know who is closing the call and the reason code. Which IOS are you running? Chances are that upgrading to latest maintenance would also fix it.
As a courtesy to those providing answers, please rate all useful posts!
Thanks I will look at that one for sure then. The IOS we are running is pretty much were we are stuck for now. The last time we tried to upgrade the IOS it broke our SIP voice. I am no SIP expert but our guy in charge of that said he found allot of info on the web that the newer IOS's broke a certain important aspect of SIP.
Yes it true that sometime you upgrade and something breaks, however do not assume it is a common or permanent situation, there are many releases after the one you are using and you will have to upgrade anyway soon or later.
Also it's important to get to know what exactly was the bug and when it has been fixed, else you remain in the uncertainty and biten by other bugs in the menawhile.
Not that it helps with the logging question, but you might check your dsp resources to see if any of them have gone bad. I have seen in the past where they may become unresponsive and cause intermittent call failure.
Introduction: The "external-out enable" command is available for
configuration under the "router ospf process" in case of the IOS-XR
operating system. This command basically enables advertisement of
intra-area routes on the device as external routes in th...
IntroductionIn this article we'll discuss how to troubleshoot packet
loss in the asr9000 and specifically understanding the NP drop counters,
what they mean and what you can do to mitigate them. This document will
be an ongoing effort to improve troublesh...