@oej: it would IMHO only be simple for "static" subscriptions like "kamailio/foo" -> on_mqtt_foo().

But what about wildcard subscriptions like "kamailio/+/unregister" or "kamailio/#" ? I can, of course, forbit these mappings by some validation rule but a cleaner solution would be to pattern-match each incoming message against the wildcard subscription to find the correct route.

It's IMHO a somewhat sophisticated feature for a later version, if the need arises. For now the mapping for incoming messages can be done in script code. We can discuss about it in more detail on the mailing list or some other channel, if you want.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.