I'm starting to work with an application that examines the Referred-By header that is ultimately generated by a REFER request generated by a UA. The RFC that defines it (3892) does not seem to say much about what value should be put in the header. In principle, it seems that it should be a URI that can be used to reach the UA, or the user operating it. In dialog event package terms, either the "identity" or "target" of the UA in the dialog -- either the Contact address, or the AOR of the "line" that sent/received the dialog.
Instead, in a recent version of a popular phone, it seems to be using the To header that was present in the incoming INVITE that established the dialog. This strikes me as a Bad Idea, because with complex call redirection, there is no close relationship between the To URI and the UA that accepted the call, and no reason to believe that another request to that URI would arrive at the same UA. What have others discovered about the Referred-By header? Dale _______________________________________________ Sip-implementors mailing list Sip-implementors@cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
