You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Kamailio goes unresponsive when it cannot resolve a DNS from siptrace
We are using siptrace to integrate Kamailio with Homer and we have a DNS on the duplicate_uri field. We noticed that when Kamailio cannot resolve this domain it freezes and stops responding to SIP requests.
Reproduction
You can reproduce the issue by:
1) Enabling siptrace
2) Populating the duplicate_uri field with a non-existing domain
3) Sending test calls
Log Messages
1(1164) CRITICAL: <core> [core/proxy.c:264]: mk_proxy(): could not resolve hostname: "homer7-hep.query.consul"
1(1164) ERROR: siptrace [siptrace_hep.c:177]: trace_send_hep3_duplicate(): bad host name in uri
DNS is a blocking operation. If it takes long to get the reply from the dns server, then the Kamailio worker is blocked. Look on the wiki at the core cookbook, there are several core parameters related to dns, try to adjust them. Also, there are config options of the operating system for dns queries (preferences, timeout), you should check them as well and change the values to fit better your needs.
Now, to clarify, after you get the error message that the domain/hostname cannot be resolved, is Kamailio still not handling SIP requests?
Thanks for your response, we'll try to adjust the DNS parameters.
When we have this DNS issue Kamailio is unable to handle most of the SIP requests, the ones that Kamailio was able to handle had a significant delay (about 2-3 seconds)
Description
Reproduction
Log Messages
Additional Information
The text was updated successfully, but these errors were encountered: