[asterisk-bugs] [JIRA] (ASTERISK-20898) sound_only_one parameter will be ignored in confbridge.conf

[Stephan (JIRA)]

Stephan created ASTERISK-20898:
----------------------------------

             Summary: sound_only_one parameter will be ignored in confbridge.conf 
                 Key: ASTERISK-20898
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20898
             Project: Asterisk
          Issue Type: Bug
      Security Level: None
          Components: Applications/app_confbridge
    Affects Versions: 11.1.2, 11.1.1, 11.1.0
         Environment: centOS 6.3 64Bit
            Reporter: Stephan
            Severity: Minor


The Parameter sound_only_one set in confbridge.conf does not have any effect.
The patch https://issues.asterisk.org/jira/browse/ASTERISK-20404
is not been fully added on asterisk version 11 yet.

part of conf file
; --- ConfBridge Bridge Profile Options ---
[basic_bridge]
type=bridge
sound_only_person=audioplace/conf_only_person
sound_wait_for_leader=audioplace/wait_for_moderator
sound_place_into_conference=audioplace/silence-500ms
sound_only_one=audioplace/conf_many_person
sound_leader_has_left=audioplace/moderator_has_left_conference


With help of issue ASTERISK-20404 I have modified the source like:

edit ./asterisk-source/apps/confbridge/conf_config_parser.c

   * structure of a dynamic profile will need to be altered, a completely new sounds structure must be
   * created instead of simply holding a reference to the one built by the config file. */
   ast_string_field_set(sounds, onlyperson, b_profile->sounds->onlyperson);
+  ast_string_field_set(sounds, onlyone, b_profile->sounds->onlyone);
   ast_string_field_set(sounds, hasjoin, b_profile->sounds->hasjoin);
   ast_string_field_set(sounds, hasleft, b_profile->sounds->hasleft);

This will fix the issue in my case. But someone has to do it properly in the source code system. And I'm not sure of side effects on this change.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira