RFC 5086 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
