[Kamailio-Users] [Fwd: Re: [Sip-implementors] REGISTER R-URI with port parameter]

Alex Balashov abalashov at evaristesys.com
Tue Oct 28 22:48:11 CET 2008


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?

-------- Original Message --------
Subject: Re: [Sip-implementors] REGISTER R-URI with port parameter
Date: Tue, 28 Oct 2008 16:46:04 -0500
From: Dale.Worley at comcast.net
To: sip-implementors at lists.cs.columbia.edu
References: 
<00D42150952F70458C66072322F7FE2502EDA940 at saturn2.aculab.com> 
<200810241652.m9OGqx6s027493 at dragon.ariadne.com> 
<200810241902.43581.ibc at aliax.net>

    From: =?iso-8859-1?q?I=F1aki_Baz_Castillo?= <ibc at aliax.net>

    El Viernes, 24 de Octubre de 2008, Dale.Worley at comcast.net escribió:
    >         sip:xxx at host:5060
    >         sip:xxx at host:15060
    >         sip:xxx at host:25060
    >         sip:xxx at 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 at 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 at lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

-- 
Alex Balashov
Evariste Systems
Web    : http://www.evaristesys.com/
Tel    : (+1) (678) 954-0670
Direct : (+1) (678) 954-0671
Mobile : (+1) (706) 338-8599




More information about the sr-users mailing list