@smititelu I made some changes to better handle the NATS connections and share the connections between publishes and subscribers. This eliminates duplicate connection handling within the module and allows it to extend into independent connection handling (e.g. add/remove/label nats connections while kamailio is running) later.
I've submitted the PR to your fork here so you can review and test.
It's not a common implementation to specify a nats url per publish request therefore the message publish will be sent to a single nats connection (which can container up to 10 nats urls). Also, I did not see the benefit of mixing queue group subjects with publish requests, therefore, I thought it best to also specify subject on publish request. I think there is more to be done here but mostly around testing and fixup of publish parameters.
Please let me know your thoughts, and if you don't mind, let's move this conversation to your fork so we can discuss best path forward before submitting the code to kamailio repo.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.