< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

[reSIProcate] Corrupted 200 OK for Re-Invite


Hi,
        Somebody had suggested here that if one receives a 200 OK with bad SDP 
for
an INVITE, then the UAC should send a BYE immediately after sending an ACK
for the 200 OK.   Will the same behavior hold good for a corrupted SDP of
200 OK for a Re-INVITE ?   Can we BYE the original session in progress?
        This seems to be the only thing to do since we already ACK the 200 OK.

        Comments ?

-Regards
Asheesh.

-----Original Message-----
From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx]On Behalf Of Francesco
Fondelli
Sent: Thursday, November 17, 2005 5:05 PM
To: Joe Boucher
Cc: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [reSIProcate] DUM state machine

On 11/16/05, Joe Boucher <jboucher@xxxxxxxxxxxxx> wrote:
[cut]
> I'd say the proper mode of callback behavior would be:
> - Calling onAccepted() when the 200 is sent
> - Calling onConnected when the ACK is received


I'd *really* like this behavior. Actually I have to use tricks using timers
to
proper mark a call as started (from a billing point of view) because there
is
no indication of "onAckReceived". To have onConnected() called when the ACK
is received would be great.

my 2 cent
Ciao
FF
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxx
https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel