[OpenSIPS-Users] OpenSIPS searches for wrong SRV record

[Jarrod Baumann]

Nabeel,

You may find this issue useful: https://github.com/OpenSIPS/opensips/issues/420 <https://github.com/OpenSIPS/opensips/issues/420>

Jarrod

> On Jul 6, 2015, at 7:49 AM, Nabeel <nabeelshikder at gmail.com> wrote:
> 
> The URI it seems to be resolving is "sip:mydomain.com <http://mydomain.com/>" (from the log):
> 
> Jul  6 10:27:20 server0 /usr/local/sbin/opensips[1731]: DBG:core:parse_msg:  uri:     <sip:mydomain.com <http://mydomain.com/>>              
> 
> Jul  6 10:27:20 server0 /usr/local/sbin/opensips[1731]: DBG:core:parse_to: display={}, ruri={sip:+447479189410 at mydomain.com <mailto:sip%3A%2B447479189410 at mydomain.com>}                                                                    Jul  6 10:27:20 server0 /usr/local/sbin/opensips[1731]: DBG:core:get_hdr_field: <To> [38]; uri=[sip:+447479189410 at mydomain.com <mailto:sip%3A%2B447479189410 at mydomain.com>]                         
> 
> I think the routing URI should be "sip:mydomain.com <http://mydomain.com/>;transport=tls".  Please let me know how I can specify the URI for TLS in OpenSIPS.
>            
> I have an SRV record at my domain for TLS, but not a NAPTR record.   In the log below,  OpenSIPS first looks for NAPTR record, doesn't find it, then looks for SRV record, but it is for UDP so it fails:
> 
> Jul  6 07:42:14 server0 /usr/local/sbin/opensips[1731]: DBG:core:mk_proxy: doing DNS lookup...
> Jul  6 07:42:14 server0 /usr/local/sbin/opensips[1731]: DBG:core:sip_resolvehost: no port, no proto -> do NAPTR lookup!
> Jul  6 07:42:14 server0 /usr/local/sbin/opensips[1731]: DBG:core:get_record: lookup(mydomain.com <http://mydomain.com/>, 35) failed
> Jul  6 07:42:14 server0 /usr/local/sbin/opensips[1731]: DBG:core:sip_resolvehost: no valid NAPTR record found for mydomain.com <http://mydomain.com/>, trying direct SRV lookup...
> Jul  6 07:42:14 server0 /usr/local/sbin/opensips[1731]: DBG:core:get_record: lookup(_sip._udp.mydomain.com <http://udp.mydomain.com/>, 33) failed                                                    Jul  6 07:42:14 server0 /usr/local/sbin/opensips[1731]: DBG:core:sip_resolvehost: no valid SRV record found for _sip._udp.mydomain.com <http://udp.mydomain.com/>, trying A record lookup...
> Jul  6 07:42:14 server0 /usr/local/sbin/opensips[1731]: ERROR:tm:update_uac_dst: failed to fwd to af 2, proto 1  (no corresponding listening socket)
> 
> On 6 Jul 2015 09:34, "Bogdan-Andrei Iancu" <bogdan at opensips.org <mailto:bogdan at opensips.org>> wrote:
> Hi,
> 
> What is the complete SIP URI that OpenSIPS tries to resolve ? What kind of query (NATPR , SRV, AAA) and the query string depends on the RURI you have.
> 
> Regards,
>  Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
> http://www.opensips-solutions.com <http://www.opensips-solutions.com/>
> On 05.07.2015 09:36, Nabeel wrote:
>> I'm running OpenSIPS with TLS support compiled and enabled.   The first SRV record OpenSIPS searches for when connecting is  _sip._udp. (as shown below).   
>> 
>> It should be _sips._tcp.  How can this be fixed?
>> 
>> 
>> DBG:core:get_record: lookup(_sip._udp.domain.com <http://udp.domain.com/>, 33) failed
>> 
>> 
>> 
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org <mailto:Users at lists.opensips.org>
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users <http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
> 
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20150706/6d40d33b/attachment.htm>