@surendratiwari3 - we do not use issue tracker for discussions to give ideas of how to configure kamailio for specific cases. The description of the field in database is not saying that it must use that socket only. Once discussions on mailing list conclude on ways to do it using the current version or what new feature has to be implemented, then an issue here can be open for feature request and the discussion on tracker can focus on implementation details, c code review, etc ...

Everyone tends to open issue on the tracker for something they need in their config/deployment, hoping to get help here. It is not what we use the tracker for. Discuss always on sr-users mailing list if you are not sure it is a bug. And connecting many instances to the same database, expecting that one instance behaves different that the others is definitely not a clear bug. When many instances share database, they are expected to behave more or less the same.

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