Thank Brett.
When forking the SUBSCRIBE request, how does the call leg look like? Should the rule of forking of an INVITE be applied, meaning the (forking) SUBSCRIBEs will have the same FROM (+ tag), TO (+ tag), CALLID, Cseq, but with different BRANCH?
Thanks.
-- Dai
-----Original Message-----
From: Brett Tate [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 03, 2001 11:46 AM
To: Ngo, Dai (c); [EMAIL PROTECTED]
Subject: RE: [Sip-implementors] Question Regarding to "To" Tags in
Response to SUBSCRIBE and NOTI FY
> In section 5.1.1 "Correlation to logs, calls
> and terminals" of the draft-ietf-sip-events-00.txt
> the "TO" tag is required in the responses to
> SUBSCRIBE requests. In section 5.2.1 it says
> "the From field of a NOTIFY request MUST
> contain a tag". The question is "Does the
> tag in the responses (to SUBSCRIBE) and the
> tag in the From field of a NOTIFY need to be
> the same?
Yes.
> What's the implication/significant of it?"
The sender of the SUBSCRIBE would assume that
forking of the request had occurred. It would
either send a 481 or 200 based upon its support
of forking for SUBSCRIBE.
