[asterisk-bugs] [JIRA] (ASTERISK-30175) Channels in ConfbridgeWelcome contains wrong information

[Joshua C. Colp (JIRA)]

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

Joshua C. Colp updated ASTERISK-30175:
--------------------------------------

    Attachment:     (was: confbridgewelcome_patch.txt)

> Channels in ConfbridgeWelcome contains wrong information
> --------------------------------------------------------
>
>                 Key: ASTERISK-30175
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30175
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_confbridge
>    Affects Versions: 18.8.0
>         Environment: AlmaLinux 8.4
>            Reporter: Oskar Nyberg
>         Attachments: confbridgewelcome_patch.txt
>
>
> When using ConfBridge the ConfbridgeWelcome message will contain incorrect channel information for channels of other participants in the conference.
> How to reproduce:
> 1. Join a conference (Which is configured to have events enabled)
> 2. Mute yourself (Can be done easily through the CLI with the confbridge command)
> 3. Join the same conference with another participant. (Make sure send_events=yes in confbridge.conf for the joining user)
> 4. Observe the ConfbridgeWelcome MESSAGE that is sent to the new participant. The muted attributed of the channel json will be "false" for the first participant even though it is muted.
> The issue lies in /apps/confbridge/confbridge_manager.c. The method "conf_send_event_to_participants" incorrectly uses the "extras" variable to create JSON data for all active channels in the conference. The problem is that the extras variable contains data specific to the joining channel, which means all channels in the conference will show whatever values the joining channel has stored in the extras variable. At the moment the extras variable also includes the "admin" value.
> I attached a file containing a patch the seems to solve the issue.



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