Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CUSTOM events are not produced when filter is set #14

Closed
gmarsico opened this issue Nov 24, 2024 · 2 comments
Closed

CUSTOM events are not produced when filter is set #14

gmarsico opened this issue Nov 24, 2024 · 2 comments

Comments

@gmarsico
Copy link

gmarsico commented Nov 24, 2024

Hi, I trying to set the event-filter to get only custom events, like vm::maintenance or other. If no filter are applied, custom events are normally produced, but if the filter is set to CUSTOM, or the sub-paths combinations of CUSTOM, like CUSTOM::vm::maintenance, no events are produced.
It is easly reproduced setting this line on the config file:
<param name="event-filter" value="CUSTOM"/>

Thanks

@gmarsico
Copy link
Author

More strangely, if the event-filter is set to:
<param name="event-filter" value="MESSAGE_WAITING,HEARTBEAT,MESSAGE-WAITING"/>
The CUSTOM events start to appear. Note the invalid MESSAGE-WAITING.

@kingster
Copy link
Member

I don't think CUSTOM is a valid event name. Based on the freeswitch documentation the closed match that I can see is SWITCH_EVENT_CUSTOM.

@kingster kingster closed this as completed Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants