Thanks Paul and Brett. I have treated as a valid offer because the port is zero. Also, if all of the m lines presents do not have PT list. then I rejected with 488.
Thanking you again!! On Wed, Oct 23, 2013 at 8:03 PM, Paul Kyzivat <pkyzi...@alum.mit.edu> wrote: > On 10/23/13 6:23 AM, Brett Tate wrote: > >> Also I want to know what should be the answer in this case ? > > > > Because the offer SDP is malformed, the device can basically act how it > wants. Similarly, I assume that the behavior might vary based upon if > received within INVITE, UPDATE, PRACK, 18x, or 2xx. > > > > Some aspects are likely discussed within RFC 6337. > > > > A strict device would likely reject the INVITE or UPDATE (or PRACK > depending upon RFC 3262 interpretation) with a 400, 488, or 606. > > Or you could be lenient. Because the port is zero, the PTs don't matter. > So you can treat it as a valid offer with a zero port. > > Then, as I mentioned earlier, you still need to decide what you want to > do. You can accept the call and see what happens, or you can reject it, > probably with a 488 or 606. > > Thanks, > Paul > > _______________________________________________ > Sip-implementors mailing list > Sip-implementors@lists.cs.columbia.edu > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
