Logging PRI activity - Failed calls

Unanswered Question
May 2nd, 2007

I am having the occational issue with failed calls from and to the PSTN from clients. The hard part is I cannot recreate the issue and so I cannot get a capture of the failed calls.

Does anyone know of a way to log calls so that I can look for failed ones? I am running a 3825 with two pri modules on it and the latest voice IOS.


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 3.8 (3 ratings)
Paolo Bevilacqua Wed, 05/02/2007 - 14:11


Are you using CCM ? Which is 'the latest IOS' you are using ? You can enable "debug isdn q931" , log to a buffer or host.

davecisco Wed, 05/02/2007 - 14:25

No CCM, this is the gateway for all our client sites. I was hoping to do some logging, not debuging. If I debug isdn q931 on our gateway with in a few minutes I will have a pretty massive file.

Paolo Bevilacqua Wed, 05/02/2007 - 15:56

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!

davecisco Wed, 05/02/2007 - 21:03

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.

Currently we run c3825-ipvoice-mz.123-14.T6.bin


Paolo Bevilacqua Thu, 05/03/2007 - 04:09


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.

jarogers2 Fri, 05/04/2007 - 12:39

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.

jarogers2 Mon, 05/07/2007 - 14:47

#show voice dsp

This is the easiest way to check your dsps.

#debug dspfarm

if you have a farm of dsps.

#debug voice dsp

could also help


This Discussion