Re: [Sip-implementors] INFO message routing.

[sunayak]

Hi Jung,
     You are right about that. INFO should be treated just
like BYE since its a mid-dialog request. Hence it will not
be forked.

     RFC 2976 which you are referring to has been obsoleted
by draft-ietf-sip-info-method-05.txt where this is clearly
specified.

Ref:
http://www.cs.columbia.edu/sip/drafts/draft-ietf-sip-info-method.txt
http://www.ietf.org/proceedings/00jul/I-D/sip-info-method-05.txt

Regards,
Subhash Nayak.
Hughes Software Systems
http://www.hssworld.com








������ <[EMAIL PROTECTED]> on 06/22/2002 11:17:31 AM

To:   "SIP Implementors" <[EMAIL PROTECTED]>
cc:    (bcc: Subhash Ullal Nayak/HSSBLR)

Subject:  [Sip-implementors] INFO message routing.




Hi.

I have some doubt about INFO method routing.
Is the following paragraph in RFC 2976 right?

4. Guidelines for extensions making use of INFO
        :
        :
   - There is potential that INFO messages could be forked by a SIP
     Proxy Server.  The implications of this forking of the information
     in the INFO message need to be taken into account.

As far as I know, INFO message should be treated like BYE message.
And the RFC 2976 also says that "The signaling path for the INFO method is
the signaling path established as a result of the call setup".

why do I worry about forking?

j.m.jung

Hi.

 

I have some doubt about INFO method routing.

Is the following paragraph in RFC 2976 right?

 

4. Guidelines for extensions making use of INFO

        :

        :

   - There is potential that INFO messages could be forked by a SIP
     Proxy Server.  The implications of this forking of the information
     in the INFO message need to be taken into account.

 

As far as I know, INFO message should be treated like BYE message.

And the RFC 2976 also says that "The signaling path for the INFO method is the signaling path established as a result of the call setup".

 

why do I worry about forking?

 

j.m.jung