Dale R. Worley wrote:
The reason that the Call-Id's on successive registrations are the same
is so that the registrar can update the previous registration's record
rather than creating a new one. I have seen some instances where UAs
generated new Call-Id's for each registration, and the registrar's
database did get cluttered with old registrations (which it kept around
for an hour or so after they expired).
I guess people can implement as they wish, but that sounds like a bad
implementation to me. There is nothing illegal, according to 3261, if
two UAs (using different callids of course) keep doing registrations
that overwrite the same contact address. In that case there is no reason
to retain a record of the older registration.
I too know of implementations that don't work as well if a UA changes
its callid. And I know they have then been harmed by UAs that violated
this assumption. But in that case they have nobody but themselves to blame.
Paul
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
