Iñaki, 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.
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 :). _____________ Roman Shpount On Mon, Jun 18, 2012 at 4:26 AM, Iñaki Baz Castillo <[email protected]> wrote: > 2012/6/15 Roman Shpount <[email protected]>: > > SIP Outbound is all about SIP clients operating from behind NAT, but it > > fails to address sending responses to SIP messages received over TCP. > > Hi Roman, as I told in my initial(s) mails in this thread, that's not > the only problem. The worst problem, IMHO, is the fact that a single > TCP disconnection using Outbound + Path + GRUU means that the SIP > dialog gets useless (in at least one direction). > > -- > Iñaki Baz Castillo > <[email protected]> > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
