Re: [Sip-implementors] Multiple Expire parameter in Contact header

2011-11-10 Thread Paul Kyzivat
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 parame

Re: [Sip-implementors] Multiple Expire parameter in Contact header

2011-11-10 Thread Worley, Dale R (Dale)
> From: Kutay OZDOGRU [kut...@netas.com.tr] > > m: > ;description="Login";expires=84703; > +sip.instance="";reg-id=1 > ,;expires=0 Formatting that so it is easier to read: > m: > > ;description="Login";expires=84703;+sip.instance="";reg-id=1, > ;expires=0 What we see is *two* contact URIs, e

[Sip-implementors] Multiple Expire parameter in Contact header

2011-11-10 Thread Kutay OZDOGRU
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: ;description="Login";expires=84703; +sip.instance="";reg-id=1 ,;expires=0 There is no expire head