mirror of
https://github.com/signalwire/freeswitch.git
synced 2026-10-04 02:03:59 +00:00
Dmitry Verenitsin
f390069308
A client message can select which chat proto handles it, and the `api` proto runs the address as a FreeSWITCH API command. That route does not pass through `verto.fsapi`, so the per-user fsapi permission does not apply to it. The new per-profile `enable-chat-api-proto` param controls the route and is off unless set; a message selecting the proto without it is refused and logged. The proto compare is case-insensitive, matching the chat interface registry, which is created with `switch_core_hash_init_nocase()`. Only the `api` proto is gated. A message carrying no proto selector, or one naming any other chat proto, routes exactly as before. The param ships commented out in both vanilla verto profiles.