Hi Roman, sorry for the late response:
2012/6/18 Roman Shpount <[email protected]>: > You can work around the issue you mention by putting the public GRUU in the > route header instead of flow token. For all the subsequent requests proxy > will look up if the flow exists for this GRUU and send the request over this > flow. This is not safe. The outbound id token must be safely generated by the Outbound proxy (and not by the UA), in fact, the proxy should be able to check whether a outbound id token in a Route header has been created by the proxy itself. > Overall I do agree with you that SIP Outbound is fairly raw, almost > unimplementable spec which needs to be either updated or replaced (maybe > with sip over websockets :). I have an idea in mind (which would be an extension to Outbound mechanism) so after a disconnection the UAC could re-register by asking the proxy to set the previous Outbound id token to the new connection (in this way incoming in-dialog requests would reach the UAC without the need of using GRUU). Regards. -- Iñaki Baz Castillo <[email protected]> _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
