<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi,<br>
<br>
Quote from the RFC ( 19.1.4 section ) :<br>
<pre style="color: rgb(0, 0, 0); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: break-word; white-space: pre-wrap; "> A URI omitting any component with a default value will not
match a URI explicitly containing that component with its
default value. For instance, a URI omitting the optional port
component will not match a URI explicitly declaring port 5060.
The same is true for the transport-parameter, ttl-parameter,
user-parameter, and method components.
Defining <a class="moz-txt-link-freetext" href="sip:user@host">sip:user@host</a> to not be equivalent to
<a class="moz-txt-link-freetext" href="sip:user@host:5060">sip:user@host:5060</a> is a change from RFC 2543. When deriving
addresses from URIs, equivalent addresses are expected from
equivalent URIs. The URI <a class="moz-txt-link-freetext" href="sip:user@host:5060">sip:user@host:5060</a> will always
resolve to port 5060. The URI <a class="moz-txt-link-freetext" href="sip:user@host">sip:user@host</a> may resolve to
other ports through the DNS SRV mechanisms detailed in [4].
</pre>
That's why I was saying this restriction makes sense for FQDNs,
where SRV might come into place and select a different port, but
doesn't make alot of sense for cases where the host part of the URI
is an actual IP.<br>
<br>
Regards,<br>
Vlad<br>
<br>
Pe 3/15/2012 11:15 PM, Bogdan-Andrei Iancu a scris:
<blockquote cite="mid:4F625BE5.10607@opensips.org" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
Sorry, a typo in my prev email - I wanted to say "a missing port <b>
should</b> match the default port "....<br>
<br>
Bogdan<br>
<br>
On 03/15/2012 11:09 PM, Vlad Paiu wrote:
<blockquote cite="mid:4F625AA1.30702@opensips.org" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
Hi Bogdan,<br>
<br>
Yes, that what the RFC says. Although I don't really see the
reason for this when the URI domains are IPs, and not FQDNs<br>
<br>
Regards,<br>
Vlad<br>
<br>
Pe 3/15/2012 11:02 PM, Bogdan-Andrei Iancu a scris:
<blockquote cite="mid:4F6258F1.8090306@opensips.org" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
Hi Vlad,<br>
<br>
AFAIR, according to SIP-wise URI matching, a missing port
shouldn't match the default port for that proto ? Correct me
I'm wrong :D<br>
<br>
Regards,<br>
Bogdan<br>
<br>
On 03/15/2012 09:44 PM, Vlad Paiu wrote:
<blockquote cite="mid:4F624683.2000307@opensips.org"
type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
Hello Flavio,<br>
<br>
Yes, indeed, the only thing different seems to be that the
sequential request contains the 5060 port, while the dialog
information does not have it.<br>
According to the 3261 RFC, these URIs do not match.<br>
<br>
Regards,<br>
Vlad<br>
<br>
Pe 3/15/2012 9:37 PM, Flavio Goncalves a scris:
<blockquote
cite="mid:CAJkFROxNu6bUsQ8GSu=mX-WrcV+cvkRExaaovAASYg8=sDoUzw@mail.gmail.com"
type="cite">
<div>Hello all, </div>
<div><br>
</div>
I'm noticing some issues with validate dialogs in one of
our servers.
<div><br>
</div>
<div>ERROR:dialog:dlg_validate_dialog: failed to validate
remote contact: dlg=[<a moz-do-not-send="true"
href="mailto:sip%3A140012556185441445@216.59.16.137">sip:140012556185441445@216.59.16.137</a>]
, req=[<a moz-do-not-send="true"
href="http://sip:140012556185441445@216.59.16.137:5060">sip:140012556185441445@216.59.16.137:5060</a>].
</div>
<div><br>
</div>
<div>What I see different on dlg and req is the port
number. Is this correct?</div>
<div>
<div><br clear="all">
Flavio E. Goncalves<br>
<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Users mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
<pre wrap=""><fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Users mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
</blockquote>
<br>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
</blockquote>
<br>
</body>
</html>