New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash in dns_cache.c with dns_cache_init=off #3350
Comments
Without topoh, calling +437200101011, resolved by the enum module to sip:enum-test@sip.nemox.net, running under valgrind with
I get:
→ CRASHES
→ CRASHES
→ NO CRASH, Kamailio receives “SIP/2.0 488 Not acceptable here” from the remote server. (This is not a problem of Kamailio)
→ NO CRASH, Kamailio receives “SIP/2.0 488 Not acceptable here” from the remote server. (This is not a problem of Kamailio) In each case I have performed the test twice and got consistent results. |
This issue is stale because it has been open 6 weeks with no activity. Remove stale label or comment or this will be closed in 2 weeks. |
Closing valid bugs, without fixing the real problem, results very few current reports for real problems in the software. This practice leads to the wrong impression, that Kamailio has no known problems, and therefore is good software. This is misleading and nobody has interest in having such misleading context. |
See #3475 (comment) . |
/notexpired |
This issue is stale because it has been open 6 weeks with no activity. Remove stale label or comment or this will be closed in 2 weeks. |
This issue is stale because it has been open 6 weeks with no activity. Remove stale label or comment or this will be closed in 2 weeks. |
This issue is stale because it has been open 6 weeks with no activity. Remove stale label or comment or this will be closed in 2 weeks. |
With Kamailio 5.6.3 I add this code
and dial +437200101011 . The code above produces the output “ENUM RESULT 1 :RURI sip:enum-test@sip.nemox.net”.
I have the DNS-related settings:
Kamailio logs during the dial-in process:
The full backtrace is:
111.11.111.11 is the IP address of the server. 22.222.222.222 is my public IP address. 192.168.0.199 is my address behind NAT.
The text was updated successfully, but these errors were encountered: