Dear all,
I have a problem to verify the correct RFC 3263 behavior of Kamailio SIP Server v4.1. I have a basic configuration of two SIP servers one domains "net1.test" and the other for domain "net2.test". When I now setup a session between both domains (from sip:alice@net1.test to sip:bob@net2.test) I expect a NAPTR-, SRV- and A-query before forwarding the INVITE to the (inbound) proxy server of net2.test. But I instead get an error: 0(3994) ERROR: <core> [resolve.c:1733]: sip_hostport2su(): ERROR: sip_hostport2su: could not resolve hostname: "net2.test"
The trace-protocol shows only two A-queries - A-query for net2.test - A-query for net2.test.net1.test
Why do I not get the NAPTR- and SRV-queries?
BR Franz
Hello,
naptr is not tried by default, you have to enable it via global parameter:
- http://www.kamailio.org/wiki/cookbooks/4.1.x/core#dns_try_naptr
Then be aware of the other rules, e.g., if the uri has a port, there is no SRV done.
Cheers, Daniel
On 09/02/14 14:25, Franz Edler wrote:
Dear all,
I have a problem to verify the correct RFC 3263 behavior of Kamailio SIP Server v4.1. I have a basic configuration of two SIP servers one domains "net1.test" and the other for domain "net2.test". When I now setup a session between both domains (from sip:alice@net1.test to sip:bob@net2.test) I expect a NAPTR-, SRV- and A-query before forwarding the INVITE to the (inbound) proxy server of net2.test. But I instead get an error: 0(3994) ERROR: <core> [resolve.c:1733]: sip_hostport2su(): ERROR: sip_hostport2su: could not resolve hostname: "net2.test"
The trace-protocol shows only two A-queries
- A-query for net2.test
- A-query for net2.test.net1.test
Why do I not get the NAPTR- and SRV-queries?
BR Franz
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hi Daniel,
naptr is not tried by default, you have to enable it via global parameter:
Then be aware of the other rules, e.g., if the uri has a port, there is no
SRV
done.
Thank you for the very quick answer. Sorry I did not look at the numerous DNS parameters in the core cookbook. Now it works as expected - compliant to RFC 323.
BR Franz