From 2856a8e305918c7907adc0a29ce0cbd0d00e447d Mon Sep 17 00:00:00 2001 From: Mike Bradeen Date: Tue, 26 Sep 2023 13:19:27 -0600 Subject: [PATCH] res_pjsip: update qualify_timeout documentation with DNS note The documentation on qualify_timeout does not explicitly state that the timeout includes any time required to perform any needed DNS queries on the endpoint. If the OPTIONS response is delayed due to the DNS query, it can still render an endpoint as Unreachable if the net time is enough for qualify_timeout to expire. Resolves: #352 (cherry picked from commit 4d5b479244f70396d5fb9ab973c75a9641db943e) --- res/res_pjsip/pjsip_config.xml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/res/res_pjsip/pjsip_config.xml b/res/res_pjsip/pjsip_config.xml index 2f4a090f8f..bd60e58727 100644 --- a/res/res_pjsip/pjsip_config.xml +++ b/res/res_pjsip/pjsip_config.xml @@ -1902,7 +1902,8 @@ Timeout for qualify If the contact doesn't respond to the OPTIONS request before the timeout, - the contact is marked unavailable. + the contact is marked unavailable. This includes time spent performing + any required DNS lookup(s) prior to sending the OPTIONS. If 0 no timeout. Time in fractional seconds. @@ -2127,7 +2128,8 @@ Timeout for qualify If the contact doesn't respond to the OPTIONS request before the timeout, - the contact is marked unavailable. + the contact is marked unavailable. This includes time spent performing + any required DNS lookup(s) prior to sending the OPTIONS. If 0 no timeout. Time in fractional seconds.