2009/3/11 BONNAERENS Ben <[email protected]>: > Hi, > > Can we elaborate on the (re)REGISTER case ? > >> They should repeat the resolution and selection when they >> refresh the registration returned by sip2 (which is what most >> clients we've worked with do). > > Isn't this in contrast to what is stated in the standards (see below) ? > I assume these statements are there in order to > avoid that a user is registered via different registration paths. > > RFC 3261 10.2.4 > " Registration refreshes SHOULD be sent to the same > network address as the original registration, unless redirected."
I think this should be: "Registration refreshes SHOULD be sent to the same destination as the original registration, unless redirected." If that destination is a SIP URI with hostname/domain instead of an IP then DNS failover (RFC 3263) takes place. I hope I'm right. -- Iñaki Baz Castillo <[email protected]> _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
