The SDP is invalid per RFC 4566. You can either allow it (for interoperability reasons since mostly irrelevant) or reject it.
If you reject it, you can send a 488 response with Warning header code 399 or send a 400 response. The 400 tends to get more attention; however some prefer not to send it when the body is malformed. <sess-version> is a version number for this session description. Its usage is up to the creating tool, so long as <sess-version> is increased when a modification is made to the session data. Again, it is RECOMMENDED that an NTP format timestamp is used. sess-version = 1*DIGIT > -----Original Message----- > From: [email protected] [mailto:sip- > [email protected]] On Behalf Of > [email protected] > Sent: Friday, April 12, 2013 6:39 AM > To: [email protected] > Subject: [Sip-implementors] IN SDP Session version value received > negative > > Hello All, > > What is the rang of origin Session ID and Session version in SDP > message ? > > Owner/Creator, Session Id (o): - 112 -123 IN IP4 192.168.1.32 > > The Problem is that some UAS Send the first INVITE with negative ("- > 123") > session version value, so what to do in this case received the INVITE > or reject the INVITE. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
