Re: [Sofia-sip-devel] No BYE sent after error in re-INVITE

[Fabio M. <fab...@gm...>]

Hi there.
I believe there has been no progress in this issue I reported a few
months back. I would just like to know if it is still in your radar to
be fixed in the not so distant future.
Would you like me to open a bug for it to help you keep track of everything?
Thanks a lot.

On Thu, Feb 26, 2009 at 09:14, Fabio Margarido<fab...@gm...> wrote:
> On Mon, Feb 23, 2009 at 12:30, Pekka Pessi <pp...@gm...> wrote:
>>
>> When you return 480 to re-INVITE, nua considers the dialog terminated and
>> clears its state.
>
> I wonder why re-INVITEs are treated different (if indeed they are). I
> believe this could cause other problems, as section 12.2.2 of the RFC
> states: "Requests sent within a dialog, as any other requests, are atomic.
> If a particular request is accepted by the UAS, all the state changes
> associated with it are performed. If the request is rejected, none of the
> state changes are performed."
> In my case, my application is a B2BUA. I've noticed this problem in a
> scenario in which the call is established and the receiving end generates a
> re-INVITE. The originating end answers with the 480, which is ACKed, and
> then nothing happens. The end that generated the re-INVITE chooses not to
> disconnect the call and the conversation should still be going on. What
> happens next is that after some time, the original caller chooses to hang
> up, and sends a BYE. nua correctly answers the BYE, but when my application
> tries to hang up the second leg (the one that received the re-INVITE),
> nothing happens and the receiving end wastes resources until the person
> decides to hang up too because of the lack of audio.
>
>>
>> In that sense, the behaviour is as expected. Nua
>> should probably allow sending BYE after the session has otherwise been
>> cleared, however.
>
> I'd appreciate that very much as I believe this is a fairly serious problem
> in our scenario.
> Thanks a lot.
>
> Fabio
>