radhaKrishna,
Merged requests: yes, you're right
loop detection: no, because that signals spiralling requests (i.e. requests
that arrive a second time but with changed routing headers) as looping
You need to calculate the via-branch as 2 parts for *every* request, and
then when you receive a request you have seen before (i.e. Via header
host:port:transport recognised as being part of your element) you calculate
the hash again and compare with the first time. Not changed means you have a
loop
Regards,
jeroen
----- Original Message -----
From: "RadhaKrishna" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
<sip-implementors@cs.columbia.edu>
Sent: Thursday, November 10, 2005 2:48 PM
Subject: RE: [Sip-implementors] RE: Loop detection in SIP
Looping and merged request are different concepts.
The scenario for merged request is as follows
When a UA sends a request and a downstream proxy forks the request and
both
the requests come to the same destination then this will be a merged
request.
Simple way to detect loop is
if the request comes to the same proxy again with the same request URI and
the VIA list contains a branch parameter inserted by this proxy.
Pls correct me if my understanding is wrong.
Regards,
radhaKrishna. Manikonda
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Thursday, November 10, 2005 5:59 PM
To: [EMAIL PROTECTED]; sip-implementors@cs.columbia.edu
Subject: RE: [Sip-implementors] RE: Loop detection in SIP
Thanks a lot!!
What is Merge request...Is it to do with Looping again??
________________________________
From: Ajit Kumar [mailto:[EMAIL PROTECTED]
Sent: Thu 11/10/2005 4:51 PM
To: Naveen Kak (WT01 - Voice & Next Generation Networks);
sip-implementors@cs.columbia.edu
Subject: RE: [Sip-implementors] RE: Loop detection in SIP
Branch parameter placed in the via has two parts in which the second
part is used for loop detection, this part is calculated by hashing
various headers of the request, now if the request is getting looped
than this part of the branch parameter calculated by the proxy will
match the corresponding part of the branch parameter already placed in
the one of the via field but if it is spiraling than the one calculated
and the one already in the via header will be different.
The basic thing is that in looping the routing information ( i.e. the
headers used to calculate the second part of branch parameter) don't
change, while in spiraling one or more of these header fields changes
changing the hash value.
Regards
Ajit
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Thursday, November 10, 2005 3:40 PM
To: sip-implementors@cs.columbia.edu
Subject: [Sip-implementors] RE: Loop detection in SIP
Hi Guys,
Request a response ASAP.
Thanks in Advance
Naveen
________________________________
From: Naveen Kak (WT01 - Voice & Next Generation Networks)
Sent: Thu 11/10/2005 3:33 PM
To: sip-implementors@cs.columbia.edu
Subject: Loop detection in SIP
________________________________
Hi,
Can anybody expain me how looping is detected by the Proxy.
I know that if the proxy finds its address in the Via header, it means
it has forwarded the request before.
But then how branch ID is used to detremine that its a loop or
spiral(The RFC says it does a hashing of the Branch Id and also that of
the Request URI and compares both).
Could somebody simplify this for me( how excatly is branch ID is used in
this context).
Thanks
Naveen
Confidentiality Notice
The information contained in this electronic message and any attachments
to this message are intended
for the exclusive use of the addressee(s) and may contain confidential
or privileged information. If
you are not the intended recipient, please notify the sender at Wipro or
[EMAIL PROTECTED] immediately
and destroy all copies of this message and any attachments.
_______________________________________________
Sip-implementors mailing list
Sip-implementors@cs.columbia.edu
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
Confidentiality Notice
The information contained in this electronic message and any attachments
to
this message are intended
for the exclusive use of the addressee(s) and may contain confidential or
privileged information. If
you are not the intended recipient, please notify the sender at Wipro or
[EMAIL PROTECTED] immediately
and destroy all copies of this message and any attachments.
_______________________________________________
Sip-implementors mailing list
Sip-implementors@cs.columbia.edu
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
Sip-implementors@cs.columbia.edu
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
Sip-implementors@cs.columbia.edu
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
