Yeah - this is an implementation specific issue. The client can request a value BUT it might not get what it wants.
Chris. >-----Original Message----- >From: Scott Lawrence [mailto:[EMAIL PROTECTED] >Sent: 30 October 2003 14:32 >To: George Petrov Georgiev-Rusiichev >Cc: [EMAIL PROTECTED] >Subject: Re: [Sip-implementors] REGISTER Expires: question > >George Petrov Georgiev-Rusiichev <[EMAIL PROTECTED]> writes: > >> If if have configurable value for Expires: header in REGISTER >> and UAS returns Expires: header or ;expires in Contact: which is >> different with UAC Expires: value - UAC shoud take this value for >> setting it timer for next re-registration. But there is nothing >> mentioned about what should be Expires: value in next REGISTER >> (re-registration). Does to have to be UAC's configurable value or the >> value taken form UAS? > >The UAC is free to request any value it wants, using whatever criteria >it chooses. > >-- >Scott Lawrence > Pingtel Corp. > >_______________________________________________ >Sip-implementors mailing list >[EMAIL PROTECTED] >http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
