Re: Section 8.2.4, stray messages received at the container
- From: Wei Chen <
- To: <
- Subject: Re: Section 8.2.4, stray messages received at the container
- Date: Fri, 28 Feb 2014 11:21:04 -0800
From: Tom Strickland
Date: Friday, February 28, 2014 at 1:13 AM
Subject: Re: Section 8.2.4, stray messages received at the container
I agree with Binod.
On 27 February 2014 04:49, binod pg
> I would prefer option 1. Also, responses will be discarded silently.
> - Binod.
> On 2/26/2014 10:17 PM, Nitzan Nissim wrote:
>> One of our customers pointed to the following section as being problematic:
>> Section 8.2.4 (6.2.4 in JSR 289)
>> "When a SipSession terminates, either because the parent application
>> session timed out or because the SipSession was explicitly invalidated, the
>> container MUST purge all state of that SipSession from its memory. In such
>> a case, if a subsequent request or response belonging to the corresponding
>> dialog is received, the container is free to handle it in either of the
>> following ways:
>> 1.Reject the request by sending a 481 error response or
>> 2.Route the request or response without application involvement"
>> Letting this be decided by the container implementation presents a
>> portability issue (as our customer ran into...)
>> To maintain portability, the spec needs to decide on one way or another, or
>> it should provide a way to an app to select a preferred one (which might be
>> difficult when there are multiple apps installed).
>> Choosing one way and making it mandatory is the easier option to resolve
>> this issue, so we support that at this point. (The way to go #1 or #2 will
>> need to be voted on by the EG)
>> We would like to hear what the rest of the group thinks.
Note: The information contained in this message may be privileged and
confidential and protected from disclosure. If the reader of this message is
not the intended recipient, or an employee or agent responsible for
delivering this message to the intended recipient, you are hereby notified
that any dissemination, distribution or copying of this communication is
strictly prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and deleting it from
your computer. Thank you. CafeX Communications.