29 Oct
2008
29 Oct
'08
12:30 a.m.
Alex Balashov wrote:
Does Kamailio match 'uri == myself' if the
domain is the same as the
canonical hostnames/aliases but the port is different than the one
Kamailio knows itself to be listening on?
Not sure, but I think: yes
Also interesting would be if domain == domain:5060
I have added more log messages to Kamailio trunk - thus if you set
loglevel to 4 you can follow the matching logic.
klaus
-------- Original Message --------
Subject: Re: [Sip-implementors] REGISTER R-URI with port parameter
Date: Tue, 28 Oct 2008 16:46:04 -0500
From: Dale.Worley(a)comcast.net
To: sip-implementors(a)lists.cs.columbia.edu
References:
<00D42150952F70458C66072322F7FE2502EDA940(a)saturn2.aculab.com>
<200810241652.m9OGqx6s027493(a)dragon.ariadne.com>
<200810241902.43581.ibc(a)aliax.net>
From: =?iso-8859-1?q?I=F1aki_Baz_Castillo?= <ibc(a)aliax.net>
El Viernes, 24 de Octubre de 2008, Dale.Worley(a)comcast.net escribió:
sip:xxx@host:5060
sip:xxx@host:15060
sip:xxx@host:25060
sip:xxx@host:35060
In that case, the request-URI of the REGISTER needs to contain the
proper port number.
Well, not totally needed. A UA could construct a REGISTER like this:
REGISTER sip:xxx@host SIP/2.0
and sent it to host:15060.
You can't depend on that working -- It's never been settled what must
happen if a SIP message arrives at a UAS which isn't the UAS that the
RFC 3263 rules would send it to. It's possible that the UAS will
forward it based on the request-URI.
It's safer to include the port, if the destination port is not 5060.
For example Twinkle does it if you set the registrar in a port
different than 5060.
I wouldn't depend on that working.
Dale
_______________________________________________
Sip-implementors mailing list
Sip-implementors(a)lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors