[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sip-implementors
Subject:    Re: [Sip-implementors] Subscribe transaction
From:       Tarun2 Gupta <tarun2.gupta () aricent ! com>
Date:       2011-09-08 7:16:51
Message-ID: 80A9B9A571A97C4993A1772F1773524214DA1B4731 () GUREXMB01 ! ASIAN ! AD ! ARICENT ! COM
[Download RAW message or body]

Hi isshed

Early NOTIFY's are a common phenomenon (due to potential of out-of-order messages and \
forking). Retransmissions are a property of the transaction layer. Even on receipt of \
a NOTIFY, the UAC should not cease retransmissions of Subscribe.

Regards,
Tarun Gupta
Aricent

-----Original Message-----
From: sip-implementors-bounces@lists.cs.columbia.edu \
                [mailto:sip-implementors-bounces@lists.cs.columbia.edu] On Behalf Of \
                isshed
Sent: Thursday, September 08, 2011 12:25 PM
To: sip-implementors
Subject: [Sip-implementors] Subscribe transaction

Hi All,

Can any one tell me the behavior of the scenario as below?

UAC===================================================UAS
1. =======================SUBSCRIBE======================
2. <====================200-SUBSCRIBE=====================
3. <========================NOTIFY========================
4. =======================200-NOTIFY=======================>

If the UAS does not send 200-SUBSCRIBE or it does not reach to UAC,
subscription dialog still gets created by NOTIFY as per RFC 3265.
I am having doubt about the behavior of the SUBSCRIBE transaction.
If the transport is UDP, the UAC retransmits SUBSCRIBE. is it correct ? Or
UAC should cease to retransmit SUBSCRIBE.

Thanks,
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors




===============================================================================
Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.
===============================================================================


[prev in list] [next in list] [prev in thread] [next in thread]