<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Hello,<br>
<br>
Trunk has just been enhanced with URI matching according to RFC 3261,
so you shouldn't have any more problems with parameter reordering, etc.<br>
Please give it a try, if you have the time.<br>
<br>
<br>
Regards,<br>
<span id="OLK_SRC_BODY_SECTION"></span>
<pre class="moz-signature" cols="72">--
Vlad Paiu
OpenSIPS Developer</pre>
<br>
<br>
On 04/13/2011 06:23 PM, Jeff Pyle wrote:
<blockquote cite="mid:C9CB3663.1E069%25jpyle@fidelityvoice.com"
type="cite">
<meta http-equiv="Content-Type"
content="text/html; charset=windows-1252">
<div>Bogdan,</div>
<div><br>
</div>
<div>Don't hold back…let's hear how you really feel. :)</div>
<div><br>
</div>
<div>I understand your position. Unfortunately since there are UAs
that do this, and they RFC compliant in their behavior, the
validate_dialog() function is less useful in the real world. I've had
to remove it from my configs.</div>
<div><br>
</div>
<div>I'm fighting a similar situation regarding the behavior of the
uac_replace_from function. It seems that Acme SBCs replace the value
of the From header (old To header) on new requests within a dialog, and
this breaks the uac_replace_from function. I've cited the second
paragraph of section 12.2.1.1 of RFC 3261. The carrier I'm fighting
with now reads this "mandatory reflection" behavior as part of the old
RFC 2543, not 3261. They aren't willing to put any more time into
configuring their Acme to maintain the headers. I work with another
carrier partner who also uses Acme who was able to make the change.
I'm trying to get the details from the second carrier so I can share
them with the first.</div>
<div><br>
</div>
<div><br>
</div>
<div>- Jeff</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div
style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in; font-family: Calibri; font-size: 11pt; text-align: left; color: black;"><span
style="font-weight: bold;">From: </span> Bogdan-Andrei Iancu <<a
moz-do-not-send="true" href="mailto:bogdan@opensips.org">bogdan@opensips.org</a>><br>
<span style="font-weight: bold;">Reply-To: </span> OpenSIPS users
mailling list <<a moz-do-not-send="true"
href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>><br>
<span style="font-weight: bold;">Date: </span> Wed, 13 Apr 2011
10:54:00 -0400<br>
<span style="font-weight: bold;">To: </span> "<a
moz-do-not-send="true" href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>"
<<a moz-do-not-send="true" href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>><br>
<span style="font-weight: bold;">Subject: </span> Re:
[OpenSIPS-Users] dlg_validate_dialog errors in loose_route<br>
</div>
<div><br>
</div>
<div>
<div bgcolor="#ffffff" text="#000000"> Hi Jeff,<br>
<br>
Well, life sucks.....You see, the UA you use is re-ordering the URI
params...This is perfectly allowed from RFC point of view, but is
bullshit in real life. So your UA is compliant, but not fairplay :)....<br>
<br>
The only solution to this is to extend the "SIP URI matching" from
simple string comparison, to RFC-wise comp - parsing the URI, checking
username, domain, params, etc.....I tried to avoid this as much as
possible as it BS to me....<br>
<br>
Regards,<br>
Bogdan</div>
</div>
</span></blockquote>
<br>
</body>
</html>