<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7653.38">
<TITLE>More about URI port and URI parameters when comparing SIP URI's</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>what about "myself"?<BR>
if(from_uri==myself)<BR>
do authentication<BR>
<BR>
A wrong From=sip:username@domain\IPaddress:5070; matches<BR>
A correct From=sip:username@domain\IPaddress; doesn't match.<BR>
<BR>
---<BR>
Daniele<BR>
<BR>
Message: 1<BR>
Date: Wed, 25 Feb 2009 20:13:51 +0100<BR>
From: I?aki Baz Castillo <ibc@aliax.net><BR>
Subject: Re: [Kamailio-Devel] More about URI port and URI parameters<BR>
when comparing SIP URI's<BR>
To: devel@lists.kamailio.org<BR>
Message-ID: <200902252013.51579.ibc@aliax.net><BR>
Content-Type: text/plain; charset="iso-8859-1"<BR>
<BR>
El Mi?rcoles, 25 de Febrero de 2009, Juha Heinanen escribi?:<BR>
> I?aki Baz Castillo writes:<BR>
> > Yes, table 1 says that "port" is not allowed in From URI. But I think<BR>
> > is better to ignore it when comparing isntead of giving error when<BR>
> > parsing (there are too much SIP devices adding the port to the From<BR>
> > header).<BR>
><BR>
> i don't know which application requires comparing from uris,<BR>
<BR>
Well, easy answer...<BR>
if ( $fu == "sip:kamailio@kamailio.org" )<BR>
:)<BR>
<BR>
> but why<BR>
> don't you just compare if their userparts and domain parts are the same?<BR>
<BR>
This would be great, but according to RFC 3261 comparing two SIP URI's is more<BR>
complex than comparing the userpart and domain. :(<BR>
<BR>
> i thought that from uri is an aor anyway.<BR>
<BR>
I agree.<BR>
<BR>
<BR>
--<BR>
I?aki Baz Castillo<BR>
<BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML><pre>**********************************************************************
The information in this message is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this message
by anyone else is unauthorized. If you are not the intended recipient, any
disclosure, copying, or distribution of the message, or any action or
omission taken by you in reliance on it, is prohibited and may be unlawful.
Please immediately contact the sender if you have received this message inerror.
**********************************************************************</pre>