Mike: In case of re-INVITE (primary means to modify an established session), the request should have *at least* the negotiated SDP. Having said that, one is free to modify characteristics of the streams (add/delete, etc.) on top of the negotiated SDP. For instance, if there were 'n' m= lines in the negotiated SDP, the re-INVITE should have *at least* 'n' (no restriction on adding more lines) m= lines in it's SDP. Hence, the scenario you are referring to will not happen (illegal) in SIP.
Hope this helps you. Regards, --victor Victor Paulsamy E-mail: [EMAIL PROTECTED] Senior Software Engineer Phone : 650.930.1339 (Direct) Zapex Technologies, Inc. Phone : 650.930.1300 (Main) Mountain View, CA 94043 Fax : 650.930.1399 > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Feldman, > Michael > Sent: Wednesday, May 22, 2002 10:38 AM > To: [EMAIL PROTECTED] > Subject: [Sip-implementors] reinvite question > > > when you have a re-invite, how does the far end reject the changes in the > following case... > (mind you I am not sure when this would happen) > > > Call in progress... > user1 > user2 > Invite (no SDP information) --> > <-- 200 OK (with SDP information) > ACK (with SDP information) --> > > user 2 does not like the information given in the ACK by user1, > a bye does not make sense since we do not want to terminate the call. > > > > thanks, > mike > > _______________________________________________ > 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
