Thanks a lot Bob but if i had to deduce something from what you said about 
INFO not getting forked being an in-dialog request,can i  say that any 
in-dialog request will not get forked as dialog is already established 
????


Achint




"Bob Penfield" <[EMAIL PROTECTED]> 
10/05/2006 01:50 AM


To
<[email protected]>, Achint Aggarwal/[EMAIL PROTECTED]
cc

Subject
Re: [Sip-implementors] A query as to know whether an INFO message canget 
forked






Since INFO is defined as an in-dialog request (RFC 2976 still called it a 
call leg, but its a dialog), the request should not be forked.

In a dialog there are only two UAs at either end. Any forked in-dialog 
request would receive a 481 response from the UAS's that are not part of 
that dialog.

cheers,
(-:bob

Robert F. Penfield
Chief Software Architect
Acme Packet, Inc.
71 Third Avenue
Burlington, MA 01803
[EMAIL PROTECTED]


----- Original Message ----- 
From: "Achint Aggarwal" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, October 04, 2006 1:11 AM
Subject: [Sip-implementors] A query as to know whether an INFO message 
canget forked


> Hi
>
> I have just subscribed to sip-implementors and thought of posting one
> query that is itself contradicting with the basic we all know about INFO
> as a method in SIP.
>
> Actuall as per rfc 2976 "there is always a potential for INFO messge to
> get forked eventually"
> but as per the same rfc"In terms of SIP forking,INFO will behave as
> another BYE message in SIP"
>
> I feel these 2 statements are contradictory to each other but i need
> further suggestions to clarify this dilema.Can somebody help me 
please???
>
> regards
> Achint
>
> ***********************  FSS- Confidential   ***********************
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
> 




***********************  FSS- Confidential   ***********************
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to