6 Dec
2012
6 Dec
'12
9:06 a.m.
my bogus register request was without +sip.instance, but with
reg-id. in such a case, reg-id should be ignored:
A Contact header field value with an instance-id media feature tag
but no "reg-id" header field parameter is valid (this combination
will result in the creation of a GRUU, as described in the GRUU
specification [RFC5627]), but one with a reg-id but no instance-id is
not valid. If the registrar processes a Contact header field value
with a reg-id but no instance-id, it simply ignores the reg-id
parameter.
that didn't happen. the result was that location record had NULL in
instance field and 1 in reg-id field.
it would simplify contact handling if in the above case both fields
would be null.
what is the rational that if there is no reg-id field, then location
table has reg-id value 0 instead of null?
-- juha