Saurav We always try to complete call somehow as providing reliable service to user is utmost important and i have seen solutions voilating standards in actual deployments to provide services to end user. And luckily in our scenario standard is recommending the acceptance of diff payloads to make call possible.so if implementors dont follow that and send bye then its not about following standard but its actually implementation limitation according to me. On Nov 5, 2014 8:55 PM, "Paul Kyzivat" <pkyzi...@alum.mit.edu> wrote:
> On 11/5/14 7:05 AM, Brett Tate wrote: > >> But my newer question is even by sending BYE for this >>> flow A is not violating any RFC. Since from the booth >>> RFCs mentioned above the expected behavior mentioned >>> by Ankur is SHOULD way not in MUST. So A behavior >>> may not the be best one but also not a violation of RFC. >>> >>> Whether my above conclusion is correct? >>> >> >> Correct. RFC 3261 section 15 indicates that the caller can send BYE over >> a >> confirmed dialog. Thus if the caller (or their device) only wants to >> allow >> an answered call to remain for 1 millisecond, that is their prerogative. >> > > Yes, it certainly is. > > This is not a standardization issue. It is a quality of implementation > issue. The customers might not be happy with this behavior. > > Thanks, > Paul > > _______________________________________________ > Sip-implementors mailing list > Sip-implementors@lists.cs.columbia.edu > https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
