> i'm not sure what you mean by this: > "Concerning RFC 4028, the session expiration stuff > is negotiated again with every re-INVITE and UPDATE"
It means that the session expiration activation, deactivation, et cetera can basically change with every successful re-INVITE or UPDATE. > 4028 is clear that the supported header in the initial > INVITE indicates whether or not refreshers are supported > by the UAC. In this case, there is no Supported header > in the initial INVITE, so it can be assumed that the > A-side does not support refreshers. That being the case, > is the B-side allowed to sending the > Session-Expires: 3700;refresher=uac and Min-SE: 600 in > the re-invite? Yes. If confused by meaning of UAC and UAS, see RFC 3261 section 6 definitions for User Agent Client and User Agent Server. It is irrelevant if A supports RFC 4028. B sent the re-INVITE; thus B is the "uac" within the re-INVITE's Session-Expires. _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
