2011/6/10 Roman Shpount <[email protected]>: > 1. Client registers and creates two TCP flows to two different edge proxies > 2. Client sends an INVITE message to edge proxy 1 which responds with 100 > Trying and forwards it through the authoritative proxy to the final > destination > 3. Edge proxy 1 restarts and client flow to it is closed
Hi Roman, I don't know very well RFC 5626, but I expect it does not cover the case you describe. In fact, your SIP UA does not need an extra specification for the case you describe: After point 3 above, your UAC should realize that the TCP connection has been closed so should terminate the transaction and, maybe, generate a new one. This is, AFAIK RFC 5626 exists for helping SIP TCP clients behind NAT rather than helping servers replying such clients after the TCP connection has been broken (since as you say, there is no real solution for that). -- Iñaki Baz Castillo <[email protected]> _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
