[Home]

Summary:ASTERISK-17731: Command "Show Channels" reports incorrect number of active calls in comparison to active channels
Reporter:Pedro Guillem (pguillem)Labels:
Date Opened:2011-04-20 14:50:16Date Closed:2011-06-07 14:01:03
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Channels/General
Versions:1.4.38 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:Version: Asterisk 1.2.32 - 1.2.40
(It occurs in every version i try from this branch)

The service is running sweet... at some point without any notice, asterisk stops recording CDRs in mySql and the CLI command "show channels" reports the correct number of "active channels", however the "active calls" counter keeps rising per every call completed.


Here is the output:
cl-t184-070cl*CLI> show channels

Channel              Location             State   Application(Data)
SIP/XX.XX.XX.XX-023a7 (None)               Down    AppDial((Outgoing Line))
SIP/900904-e8037c00  52701675@default Ring    Dial(SIP/2153#573152701675@216
SIP/XX.XX.XX.XX-0242f (None)               Down    AppDial((Outgoing Line))
SIP/telnicsipbx-e807 05579488@default Ring    Dial(SIP/2153#573005579488@216
SIP/XX.XX.XX.XX-023ed (None)              Up      Bridged Call(SIP/900904-e80642
SIP/900904-e80642e0  6455618@default Up      Dial(SIP/2153#573106455618@216
SIP/XX.XX.XX.XX-023dc (None)              Up      Bridged Call(SIP/900904-0242be
SIP/900904-0242be50  573145699581@default Up      Dial(SIP/2153#573145699581@216
SIP/XX.XX.XX.XX-023fd (None)              Up      Bridged Call(SIP/900904-023cd2
SIP/900904-023cd250  573126230201@default Up      Dial(SIP/2153#573126230201@216

10 active channels
513 active callsI>

In thic ase 513 would be the number of calls processed since asterisk stopped recording CDRs (a major symptom the problem is happening).


****** ADDITIONAL INFORMATION ******

This did not happen before in ANY 1.2 installation i've ever seen, nor in 1.4 or 1.6.

Questions:
1) Are this two things related somehow?? (activa call cunter and CDR subsystem)??
2) Are there system variables that could possibly affect this behaviour?
3) Is it maybe a compilation issue due to updated libraries in the Debian repos?
Comments:By: Paul Belanger (pabelanger) 2011-04-20 14:53:30

Thanks for your comments. This does not appear to be a bug report and we are closing it. We appreciate the difficulties you are facing, but it would make more sense to raise your question in the support tracker, http://www.asterisk.org/support