[asterisk-dev] dvossel: trunk r315856 - /trunk/apps/app_confbridge.c

Tony Mountifield tony at mountifield.org
Thu Apr 28 10:07:17 CDT 2011


In article <4DB97AEA.4040602 at asteriskdocs.org>,
Leif Madsen <leif.madsen at asteriskdocs.org> wrote:
> On 11-04-28 10:00 AM, Russell Bryant wrote:

> >>>  	case CONF_SOUND_ERROR_MENU:
> >>>  		return S_OR(custom_sounds->errormenu, "conf-errormenu");
> >>>  	case CONF_SOUND_JOIN:
> >>> - return S_OR(custom_sounds->join, "beep");
> >>> + return S_OR(custom_sounds->join, "confbridge-join");
> >>>  	case CONF_SOUND_LEAVE:
> >>> - return S_OR(custom_sounds->leave, "beeperr");
> >>> + return S_OR(custom_sounds->leave, "confbridge-leave");
> >>>  	}
> >>
> >> A very minor nit to pick, but all the other sounds have conf- as the
> >> prefix rather than confbridge-, so perhaps conf-join and conf-leave
> >> might be more consistent...
> > 
> > Good point.  +1 from me.  :-)
> > 
> 
> Actually these were named with confbridge specifically to not overlap with the
> existing conf sounds, which are more to do with MeetMe() and not ConfBridge().
> The point was made that we wanted to avoid overwriting any custom sounds other
> people may have already created.

I see the logic, but having just checked both the core and extra sounds,
there are no files already called conf-join or conf-leave, so there should
not be any conflict, should there? And all the other sounds used by
Confbridge are the standard conf-xxx sounds from Meetme anyway.

Anyway, it's no big deal to me - I just thought it might have been an
oversight.

Cheers
Tony
-- 
Tony Mountifield
Work: tony at softins.co.uk - http://www.softins.co.uk
Play: tony at mountifield.org - http://tony.mountifield.org



More information about the asterisk-dev mailing list