Kutay,
Yes, you need to handle this.
Each contact can have its own expiration time setting, which is what you
see here. The way to treat this is to consider the value in the Expires
header (if any) as a default value for every Contact, which is then
overridden by an expires header field parameter (if any) on each Contact
header field.
An algorithm for doing this might be:
- set default expiration time to an implementation-specific default
(your choice)
- if there is an Expires header in the REGISTER message,
set the default expiration time to the value in that header
- process each Contact header field in turn
- set the expiration time for this header to the default set above
- if there is an expires header field parameter, set the expiration
time for this header to that value
Note that the example you show below is a good one to illustrate why you
might want this. It is adding one contact uri and simultaneously
removing another.
Thanks,
Paul
On 11/10/11 10:14 AM, Kutay OZDOGRU wrote:
> Hi all,
>
> I have a sipserver that registers multiple clients to IMS side however,
> when my sipserver gets 200 OK message for
> De-register as below, it faces confusion because of 2 expire parameters.
>
> m:
> <sip:[email protected]:5061>;description="Login";expires=84703;
> +sip.instance="<urn:uuid:c19497bf-9ba3-404a-b77f-0d6014021eed>";reg-id=1
> ,<sip:[email protected]:5060>;expires=0
>
>
> There is no expire header in 200 OK message so expire parameter is in
> contact header but why remote sip server sends me
> 2 different expires....
>
> How can I be sure about which expire should I use? :S
>
> I have a confusion on this point. I cannot find any information about
> this in RFC3261... is it applicable?
> Do I have to handle this?
>
> Could you please give me your comments?
>
> Thanks,
> Kutay
>
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
