----- Original Message -----
From: "Fred Peyrard" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Friday, May 18, 2001 2:54 AM
Subject: Obj.: Re: Re: [Sip-implementors] Does BYE terminate a Call or a
Callleg?
> Thank you bob for your clarifications.
> The conclusion could be:
> A BYE request terminates a CallLeg.
> If there is no more CallLeg remaining in the Call, it also terminates the
Call.
>
That sounds about right. If the UA that sent the BYE has other call legs
associated with the call, those call legs would continue. If all the call
legs are gone, then the call is done.
> Fred,
>
> >
> > Fred,
> >
> > BYE will terminate the call leg identified by the tag in the To or From
> > header (depending on who is terminated the call). In your example, the
200
> > OKs from X and Y will have different tag values added to the To header.
When
> > C issues the BYE, it would include the tag for Y in the To header. Only
the
> > call leg to Y will be terminated.
> >
> > (-:bob
> >
> > Robert F. Penfield
> > Chief Software Architect
> > Acme Packet, Inc.
> > 130 New Boston Street
> > Woburn, MA 01801
> > [EMAIL PROTECTED]
> >
> > ----- Original Message -----
> > From: "Fred Peyrard" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Cc: <[EMAIL PROTECTED]>
> > Sent: Thursday, May 17, 2001 11:26 AM
> > Subject: Obj.: Re: [Sip-implementors] Does BYE terminate a Call or a
> > Callleg?
> >
> >
> > > Is it the still the case for a statefull proxy?
> > > Let's consider the example in section 16.5 Forking Proxy(from rfc
> > 2543bis):
> > > C issues an INVITE request to P (P forking the request to X and Y
and...).
> > > X and Y reply with 200 OK.
> > > C realizes that he only wants to discuss with X, thus it decides to
issues
> > a BYE request to Y.
> > > This is exactly what is described in the example of the RFC.
> > > But now, consider that P could have added a Record-Route in the
INVITE.
> > > Thus, the BYE request that C intends to Y will now go through P.
> > > In this case, must P consider that the BYE (intended only to Y) must
> > terminate the call with X and Y?
> > >
> > > Fred,
> > >
> > > >
> > > > BYE terminates the call.
> > > >
> > > > Regards
> > > > Ranjit
> > > > Mascon Communication Technologies
> > > > http://www.masconit.com
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > ----- Original Message -----
> > > > From: Fred Peyrard <[EMAIL PROTECTED]>
> > > > To: <[EMAIL PROTECTED]>
> > > > Sent: Thursday, May 17, 2001 8:27 AM
> > > > Subject: [Sip-implementors] Does BYE terminate a Call or a Callleg?
> > > >
> > > >
> > > > Hello,
> > > >
> > > > I have a very basic question:
> > > > What does a BYE request terminate?
> > > > Section 4.2.4 from rfc2543bis states that: "The user agent client
uses
> > BYE
> > > > to indicate to the server that it wishes to release the call."
> > > > However, according to forking proxy example (section 16.4), it seems
> > that
> > > > the BYE rather terminates a call leg.
> > > >
> > > > Fred,
> > > >
> > > > Internet et mail gratuit AltaVista http://www.altavista.fr
> > > > _______________________________________________
> > > > Sip-implementors mailing list
> > > > [EMAIL PROTECTED]
> > > > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
> > >
> > >
> > > Internet et mail gratuit AltaVista http://www.altavista.fr
> > > _______________________________________________
> > > Sip-implementors mailing list
> > > [EMAIL PROTECTED]
> > > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
> > >
>
>
> Internet et mail gratuit AltaVista http://www.altavista.fr
> _______________________________________________
> Sip-implementors mailing list
> [EMAIL PROTECTED]
> http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
>
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
