<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi,<br>
<br>
I made some progress. As I stated before, I made a patch and
submitted to git branch misi/dns_srv.<br>
I tested with dns cache. It works for me.<br>
<br>
I made it also available for case if "no dns cache" is used too,<br>
but it isn't tested yet.<br>
<br>
Please review my commit, and let me know if any corrections needed.
<br>
Any suggestion, comment highly appreciated!<br>
<br>
Please also let me know even if you find my code OK and i can merge
it to the master.<br>
<br>
Current status: <br>
If there is no NAPTR record then based on the dns_<i>protocol</i>_pref
scores it sort the list of the sr supported protocols, and it tries
protocols to resolve SRV. <br>
It stops the loop and returns, if it founds the first most preferred
and available/so DNS SRV exists for the protocol/ record.<br>
<br>
I will appreciate if anyone can help me to explain how can i made
future progress with this SRV issue. <br>
My problem is, that i don't know how to iterate and fallback to
other preferred and available protocols, so keep the state of the
failed protocols. <br>
How can i save state and fallback if the access the remote side with
the currently selected SRV protocol failed so fall back to
second,third.. available and preferred protocol.<br>
<br>
Many thanks,<br>
Misi<br>
<br>
On 2012-11-05 15:03, Klaus Darilion wrote:
<blockquote cite="mid:5097C719.2010308@pernau.at" type="cite">Indeed,
this is not implemented correctly.
<br>
<br>
If you fix it, the question is: what should be used if there are
SRV records for UDP and TCP?
<br>
<br>
AFAIK there is already a configuration option to choose the
respective NAPTR records according to local priority. These config
options could be reused.
<br>
<br>
See dns_udp_pref/dns_tcp_pref/... options in doc/dns.txt
<br>
<br>
regards
<br>
Klaus
<br>
<br>
On 29.10.2012 16:33, MÉSZÁROS Mihály wrote:
<br>
<blockquote type="cite">Hi All,
<br>
<br>
I am experiencing an issue when i try to contact <a class="moz-txt-link-abbreviated" href="mailto:xy@cisco.com">xy@cisco.com</a>.
<br>
I found that kamailio/sip-router can't resolve by default
resolving way
<br>
a TCP + SRV records from domain cisco.com.
<br>
<br>
e.g. cisco.com
<br>
<br>
misi@alma:~$ host -t NAPTR cisco.com
<br>
cisco.com has no NAPTR record
<br>
misi@alma:~$ host -t SRV _sip._udp.cisco.com
<br>
Host _sip._udp.cisco.com not found: 3(NXDOMAIN)
<br>
misi@alma:~$ host -t SRV _sip._tcp.cisco.com
<br>
_sip._tcp.cisco.com has SRV record 1 0 5060 vcsgw.cisco.com.
<br>
misi@alma:~$ host -t SRV _sips._tcp.cisco.com
<br>
_sips._tcp.cisco.com has SRV record 1 0 5061
vcsgw.cisco.com.
<br>
<br>
<br>
I can't call <a class="moz-txt-link-abbreviated" href="mailto:xy@cisco.com">xy@cisco.com</a> because it does not exists an NAPTR
record in
<br>
domain cisco.com,
<br>
and furthermore no SRV with udp.
<br>
<br>
But it exists sip+tcp record
<br>
and also exists an secure sip SRV, so sips+tcp record!
<br>
<br>
I read rfc3263
<br>
I find kamailio dns resolver is not working as it should
according RFC3263.
<br>
<br>
<a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/rfc3263">http://tools.ietf.org/html/rfc3263</a>
<br>
<br>
_If no NAPTR records are found, the client constructs SRV
queries
<br>
for those transport protocols it supports, and does a query
for each._
<br>
<br>
<br>
So kamailio should query all (udp, tcp, tls, sctp whatever)
protocols.
<br>
<br>
Can anyone help/guide me to create a fix to this issue?
<br>
My plan is to create a patch to kamailio resolver, to correct
and behave
<br>
according RFC3263.
<br>
<br>
Any help or guidance appreciated!
<br>
<br>
Thanks,
<br>
Misi
<br>
<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________
<br>
sr-dev mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:sr-dev@lists.sip-router.org">sr-dev@lists.sip-router.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev</a>
<br>
<br>
</blockquote>
</blockquote>
<br>
</body>
</html>