Yeah, that was exactly my concern. It should ADD the entries to the existing History-Info if present.
> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Hadriel Kaplan > Sent: Monday, July 28, 2008 03:28 > To: Jonathan Rosenberg; IETF SIP List > Subject: Re: [Sip] Proposed solution for UA > loose/target/History-Info problem > > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of > > Jonathan Rosenberg > > > > For a proxy: > > If the proxy is rewriting the r-uri as a consequence of > looking it > > up in a registration database, it looks at the incoming request. It > > removes any existing H-I values. It then adds two H-I > values that look like this: > > > > History-Info: <sip:incoming-ruri>;target;index=1 > > <sip:outgoing-ruri>;target;index=1.1 > > > > and thats it. So really easy for a proxy. > > I'm confused. Why is it removing any existing HI values? > Doesn't that break its compatibility with legacy HI usage? > > -hadriel > _______________________________________________ > Sip mailing list https://www.ietf.org/mailman/listinfo/sip > This list is for NEW development of the core SIP Protocol Use > [EMAIL PROTECTED] for questions on current sip > Use [EMAIL PROTECTED] for new developments on the application of sip > _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
