[Freeswitch-dev] issue ESL-52: event nitifications filters
Michael Jerris
mike at jerris.com
Tue Nov 23 06:42:26 PST 2010
please see commit 89dbe0b from yesterday.
On Nov 22, 2010, at 4:20 PM, Alex Deiter wrote:
> Hi,
>
> Could you please review issue ESL-52 ?
> We are used FreeSWITCH with BigBlueButton and found problem with ESL events.
> Each new filter loses the previous filter. Example:
>
> % ./fs_cli -H 127.0.0.1 -p ClueCon
> ...
> freeswitch at 127.0.0.1@internal> /event all
> +OK event listener enabled plain
>
> ===> now received ALL events
> Event-Name: HEARTBEAT
> Event-Name: RE_SCHEDULE
> Event-Name: HEARTBEAT
> Event-Name: RE_SCHEDULE
>
> ===> add filter
> ===> now received ONLY HEARTBEAT events
> freeswitch at 127.0.0.1@internal> /filter Event-Name HEARTBEAT
> +OK filter added. [Event-Name]=[HEARTBEAT]
>
> ===> add another filter
> ===> now FreeSWITCH forgotten about the previous filter and used only
> last filter
> freeswitch at 127.0.0.1@internal> /filter Event-Name RE_SCHEDULE
> +OK filter added. [Event-Name]=[RE_SCHEDULE]
> Event-Name: RE_SCHEDULE
> Event-Name: RE_SCHEDULE
> Event-Name: RE_SCHEDULE
>
> This behavior was noted after FreeSWITCH snapshot 12-Nov-2010
>
> FreeSWITCH snapshot 15-Oct-2010 works as it should: each new filter
> was added to the existing filters.
More information about the FreeSWITCH-dev
mailing list