hi,
now why has it been proposed that a UA shouldn't worry about the response
for a BYE?
--raj
Rajarshi Chakraborty
B-196, IIT Campus,
Kharagpur,
West Bengal, India
PIN-721302
----Original Message Follows----
From: Christer Holmberg <[EMAIL PROTECTED]>
To: Ajit Kalele <[EMAIL PROTECTED]>
CC: Reshmi Nair <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Subject: Re: [Sip-implementors] Re-Invite & Bye - on the wire
Date: Thu, 17 Oct 2002 15:14:52 +0300
Hi,
I think it's valid for a node, after it has sent a BYE (even if the
transaction is still pending), to send 481 Call/Transaction does not exist
if it receives any messages for that session, becuase from the node's point
of view the session is most
likely already terminated (even if the specific BYE transaction is still
pending). I would assume (of course I can't confirm this) most nodes really
don't care what response they get to a BYE anyway...
Regards,
Christer Holmberg
Ericsson Finland
Ajit Kalele wrote:
> Hi,
>
> User B should send a 491 Request Pending.
>
> Regards
> Ajit
>
> Reshmi Nair wrote:
>
> > Hi,
> >
> > Consider this scenario :
> > A & B are two user agents.
> >
> > A B
> > INV
> > -------------------------------->
> > 200
> > <--------------------------------
> > ACK
> > -------------------------------->
> >
> > ================= Dialog established.
> >
> > INV(hold) BYE
> > -----------> <--------
> >
> > ==============================================
> >
> > In this scenario, A sends an Invite(hold), just when B has sent
a BYE. How should user agent B respond to the INVITE ? It has already sent a
BYE when it receives an Invite. Is it supposed to send a 4XX - maybe a 487
Request Terminated ??
> >
> > Regards,
> > Reshmi
> >
> >
------------------------------------------------------------------------
> > Name: Wipro_Disclaimer.txt
> > Wipro_Disclaimer.txt Type: Plain Text (text/plain)
> > Encoding: 7bit
>
> *********************************************************
> Disclaimer
>
> This message (including any attachments) contains
> confidential information intended for a specific
> individual and purpose, and is protected by law.
> If you are not the intended recipient, you should
> delete this message and are hereby notified that
> any disclosure, copying, or distribution of this
> message, or the taking of any action based on it,
> is strictly prohibited.
>
> *********************************************************
> Visit us at http://www.mahindrabt.com
>
> _______________________________________________
> 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
_________________________________________________________________
Protect your PC - get McAfee.com VirusScan Online
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
- [Sip-implementors] Re-Invite & Bye - on the wire Reshmi Nair
- Re: [Sip-implementors] Re-Invite & Bye - on ... Ajit Kalele
- Re: [Sip-implementors] Re-Invite & Bye -... Christer Holmberg
- Rajarshi Chakraborty
