How to handle version is defined in the SDP spec:
> <version> is a version number for this announcement. It is needed
> for proxy announcements to detect which of several announcements for
> the same session is the most recent. Again its usage is up to the
> creating tool, so long as <version> is increased when a modification
> is made to the session data. Again, it is recommended (but not
> mandatory) that an NTP timestamp is used.
So, basically, increment how you like. ++ seems easiest, though.
Because there is also ordering within SIP, the only case you need worry
about is where the CSeq is higher, but the version is unchanged. I don't
think you need to handle the case where the CSeq increments but the
version is lower. This should not happen; if it does, its within your
rights to reject this request.
-Jonathan R.
> "Lau, Henry" wrote:
>
> At the SIP Bake-off event last week, there was an announcement for a
> clarification of the SDP portion of the re-INVITE message. What I put
> down in my notes are:
>
> 1. Have to keep the same session ID.
> 2. The t-line is mandatory.
> 3. Increment the version.
>
> I did not put down how the version is supposed to be incremented. Can
> someone refresh my memory on that please?
> Thank you
>
> -----
> Henry Lau, System Software Manager
> Nuera Communications, Inc.
> 10445 Pacific Center Court, San Diego, CA 92121
> Direct: 858-824-6383, Main: 800-966-8372 ext 6383, Fax: 858-625-2422
>
>
--
Jonathan D. Rosenberg 72 Eagle Rock Ave.
Chief Scientist First Floor
dynamicsoft East Hanover, NJ 07936
[EMAIL PROTECTED] FAX: (732) 741-4778
http://www.cs.columbia.edu/~jdrosen PHONE: (732) 741-7244
http://www.dynamicsoft.com
