Brett Tate <br...@broadsoft.com> writes: > If it matters, solutions using things like Replaces and REFER raise the > typical concerns with authorization, security, billing, et cetera. For > instance, see security section of RFC 3891.
Security is "interesting" because there is no guarantee that the new dialog is handled (at the near end) by the same carrier as the old dialog. So whatever authentication technique is used, it has to be "global". It also means that the remote target address that the UA sees must be globally accessible. If we were willing to bill the two dialogs as separate calls, then billing would likely be very simple. But if we want to allow the possibility that the two dialogs would be billed as one call, the INVITE-Replaces needs to carry enough information that the carrier can make that determination. But perhaps the dialog identifiers in Replaces are enough, as they do uniquely connect the new dialog with the old one. Dale _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
