I notice that our BroadSoft AS platform on a multiple diverted call sends the following to a Network element, where it appears two Diversion are concatenated into a single Diversion: header as follows.
Diversion:"NodePhone"<sip:[email protected];user=phone>;privacy=full;reason=unconditional;counter=1,"NodePhone"<sip:[email protected];user=phone>;privacy=full;reason=unconditional;counter=1 Most examples in for example draft-levy-sip-diversion/RFC5806 where multiple diversions exist show multiple Headers, one for each diversion. I did notice that in RFC3261 7.3 Headers Fields the following <quote> That applies to SIP as well, but the specific rule is different because of the different grammars. Specifically, any SIP header whose grammar is of the form header = "header-name" HCOLON header-value *(COMMA header-value) allows for combining header fields of the same name into a comma-separated list. </quote> I note whilst RFC4244 for History-Info has (4.1) History-Info = "History-Info" HCOLON hi-entry *(COMMA hi-entry) That RFC5806 for Diversion has (4) Diversion = "Diversion" ":" 1# (name-addr *( ";" diversion_params )) My question is does BroadSoft's use of combining multiple Diversions in a single Diversion Header appear to follow RFC5806? Thanks for your consideration. Cheers, Peter -- Peter Childs - Voice Engineer Internode/Agile _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
