Hi Vivek, inline On Fri, Jul 13, 2012 at 7:52 PM, Vivek Singla <[email protected]> wrote:
> Thanks Brett for the corrected number. So I was looking into this rfc, I > didn't see any error conditions mentioning a duplicate diversion header. > I am forgetting, but SIP has its own way of stopping the loops and looping > messages, isnt it? > I am trying to think of any header or a parameter which SIP client or > server look for in case of a loop. > I mean what if there are more than 2 duplicated entries in Diversion > headers. > Looking through the RFC5806 it doesn't mention that Diversion header can be used more than once neither. As I understand it implies redirection, and explicitly specifies the destination party (single/one), therefore duplication is not reasonable. > > Vivek. > > > From: Brett Tate <[email protected]> > To: Vivek Singla <[email protected]>; " > [email protected]" < > [email protected]> > Sent: Friday, July 13, 2012 11:31 AM > Subject: RE: [Sip-implementors] Duplicate diversion headers in Invite > > Sorry for the resend, fixed RFC number. > > > -----Original Message----- > > From: [email protected] [mailto:sip- > > [email protected]] On Behalf Of Brett Tate > > Sent: Friday, July 13, 2012 12:29 PM > > To: Vivek Singla; [email protected] > > Subject: Re: [Sip-implementors] Duplicate diversion headers in Invite > > > > RFC 5806 is the historic RFC for diversion. As far as I know, it does > > not forbid it. > > > > The typical reason that you might see it involves looping. A loop > > occurred and the device either handled it differently or has not yet > > detected the loop (or reached Max-Forwards 0). > > > > > -----Original Message----- > > > From: [email protected] [mailto:sip- > > > [email protected]] On Behalf Of Vivek Singla > > > Sent: Friday, July 13, 2012 11:58 AM > > > To: [email protected] > > > Subject: [Sip-implementors] Duplicate diversion headers in Invite > > > > > > > > > Hi, > > > > > > I am trying to figure out a scenario in which a SIP proxy will get 2 > > > very same Diversion headers. > > > > > > For example: > > > Diversion: <sip:[email protected];user=phone>; privacy=off; > > > reason=unconditional; counter=1 > > > Diversion: <sip:[email protected];user=phone>; privacy=off; > > > reason=unconditional; counter=1 > > > > > > These 2 headers come in the same INvite message. > > > > > > I am just trying to see if there is a RFC out there to justify this > > > duplication of these 2 headers? > > > > > > Vivek. > > > > > > _______________________________________________ > > Sip-implementors mailing list > > [email protected] > > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > > > > Something like TTL in IP headers. > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
