Hi,
Thanks for the reply,
The dispatcher params we are using are as below:
#--- Dispatcher params ----
modparam("dispatcher", "db_url", DBURL_LOCAL)
modparam("dispatcher", "flags", 2)
modparam("dispatcher", "xavp_dst", "ds_dst")
modparam("dispatcher", "ds_probing_mode", 1)
modparam("dispatcher", "ds_ping_interval", 30)
modparam("dispatcher", "ds_ping_from", "sip:proxy@VAR_LOCAL_IP")
The version of the kamailio is 5.4.7.
Above are the details which was asked, Please let me know if any thing is needed.
Hi,
Check the options you have set for the dispatcher params and then if you have any logic to mark dispatcher destination as IP on any timeout, or error response would be my first checks.
Specifically - "ds_probing_threshold" and the "ds_inactive_threshold" params (first takes it out after x failed, second adds it back in after x successful.) We would need to see the kamailio version, dispatcher params and the dispatcher logic to help further though.
Thanks,
John.
HI,
Scenario:
We possess 2 proxies and 2 registrar servers equipped with dmq functionality. Unexpectedly, one of the Proxy IP addresses was marked as inactive (FLAG: IP) in the dispatcher list, causing the proxy to cease responding. Simultaneously, Kamailio logs stopped recording any activity.
Upon restarting the Kamailio service, the problem was resolved, and the proxy resumed normal operation, with the Flag changing back to AP (ACTIVE).
The sudden occurrence of this issue is not clear, and due to the cessation of logs during the incident, we lack information for the investigation.
Any suggestions on how to address this issue would be appreciated.
And is this scenario happened to any one in your experience?
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-leave@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe: