[asterisk-bugs] [JIRA] (ASTERISK-24208) Channels with CDR Information Remain Active Even After ConfBrige Is Ended

[Frankie Chin (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-24208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Frankie Chin updated ASTERISK-24208:
------------------------------------

    Description: 
I have one Asterisk running on a physical Ubuntu machine, and 20 other Asterisks running on virtual Ubuntu machines. The virtual Asterisks are registered to the physical Asterisk using IAX. 

AMI is used to originate calls to all the virtual Asterisks and join them into a conference bridge hosted in the physical Asterisk. Once all the participants join the conference, the physical Asterisk will be taking up close 90% of the CPU usage.

The real concern is that.... even after ending the conference (using "confbridge kick [ID] all" CLI command), the channels with CDR information will still remain active (as indicated by the "cdr show active" command). Also, the physical Asterisk will still be taking 90% of the CPU usage. If I type the "cdr set debug on" in the CLI console, the screen will be loaded with seemingly endless loop of activities (Please see my comment).

This issue was first found when I was using Asterisk Version 12. I just tested it using Version 13 Beta 1 and the problem persists.

The AMI Originate Action (for one virtual Asterisk):
Action: Originate
Channel: IAX2/vm1/1001
Exten: 1
Priority: 1
Context: conference
Async: true
CallerID: AMI

The dial plan at the physical asterisk looks like this:
[conference]
exten => 1,1,ConfBridge(1234,,,conf_menu)

The dial plan at the virtual asterisk looks like this:
[internal]
exten => 1001,1,Answer
exten => 1001,n,Wait(180)
exten => 1001,n,Hangup()


  was:
I have one Asterisk running on a physical Ubuntu machine, and 20 other Asterisks running on virtual Ubuntu machines. The virtual Asterisks are registered to the physical Asterisk using IAX. 

AMI is used to originate calls to all the virtual Asterisks and join them into a conference bridge hosted in the physical Asterisk. Once all the participants join the conference, the physical Asterisk will be taking up close 90% of the CPU usage.

The real concern is that.... even after ending the conference (using "confbridge kick [ID] all" CLI command), the channels with CDR information will still remain active (as indicated by the "cdr show active" command). Also, the physical Asterisk will still be taking 90% of the CPU usage. If I type the "cdr set debug on" in the CLI console, the screen will be loaded with seemingly endless loop of activities (Please see attached screen shot).

This issue was first found when I was using Asterisk Version 12. I just tested it using Version 13 Beta 1 and the problem persists.

The AMI Originate Action:
Action: Originate
Channel: IAX2/vm0/1000
Exten: 1000
Priority: 1
Context: conference
Async: true
CallerID: AMI

The dial plan at the physical asterisk looks like this:
[conference]
exten => _XXXX,1,ConfBridge(${EXTEN},,,conf_menu)

The dial plan at the virtual asterisk looks like this:
[internal]
exten => _1XXX,n,Answer
exten => _1XXX,n,Wait(180)
exten => _1XXX,n,Hangup()



> Channels with CDR Information Remain Active Even After ConfBrige Is Ended
> -------------------------------------------------------------------------
>
>                 Key: ASTERISK-24208
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24208
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_confbridge
>    Affects Versions: 13.0.0-beta1
>         Environment: Ubuntu 10.04
>            Reporter: Frankie Chin
>            Severity: Critical
>
> I have one Asterisk running on a physical Ubuntu machine, and 20 other Asterisks running on virtual Ubuntu machines. The virtual Asterisks are registered to the physical Asterisk using IAX. 
> AMI is used to originate calls to all the virtual Asterisks and join them into a conference bridge hosted in the physical Asterisk. Once all the participants join the conference, the physical Asterisk will be taking up close 90% of the CPU usage.
> The real concern is that.... even after ending the conference (using "confbridge kick [ID] all" CLI command), the channels with CDR information will still remain active (as indicated by the "cdr show active" command). Also, the physical Asterisk will still be taking 90% of the CPU usage. If I type the "cdr set debug on" in the CLI console, the screen will be loaded with seemingly endless loop of activities (Please see my comment).
> This issue was first found when I was using Asterisk Version 12. I just tested it using Version 13 Beta 1 and the problem persists.
> The AMI Originate Action (for one virtual Asterisk):
> Action: Originate
> Channel: IAX2/vm1/1001
> Exten: 1
> Priority: 1
> Context: conference
> Async: true
> CallerID: AMI
> The dial plan at the physical asterisk looks like this:
> [conference]
> exten => 1,1,ConfBridge(1234,,,conf_menu)
> The dial plan at the virtual asterisk looks like this:
> [internal]
> exten => 1001,1,Answer
> exten => 1001,n,Wait(180)
> exten => 1001,n,Hangup()



--
This message was sent by Atlassian JIRA
(v6.2#6252)