> > > > For example, consider this header inserted in a response > > by a monitor: > > > > Call-Info: > > <sip:atlanta.example.com?Call-Info=%3cx:y%3e;purpose%3dcall-co > > mpletion%3bcookie%3d123456> > > ;purpose=call-completion > > ;m=NR > > > > The contained monitor's contact URI is thus: > > > > > > sip:atlanta.example.com?Call-Info=%3cx:y%3e;purpose%3dcall-com > > pletion%3bcookie%3d123456 > > > > When that URI is used to generate a SUBSCRIBE, the > > resulting request > > looks like this: > > > > SUBSCRIBE sip:atlanta.example.com SIP/2.0 > > Call-Info: <x:y>;purpose=call-completion;cookie=123456 > > Call-Info: <...>;purpose=call-completion;m=NR > [JRE] I don't understand how you get two Call-Info header fields. > > John > Hi John,
if I renember correctly the explanation was the following: The first Call-Info has been inserted by the processing of the "?Call-Info" header-parameter in the monitor's contact URI. The second Call-Info has been inserted by ordinary CC SUBSCRIBE generation by the caller's agent. But since the monitor created this situation, it knows how to interpret two Call-Info values. BR, Martin _______________________________________________ BLISS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bliss
