Juha Heinanen wrote: > Christer Holmberg writes: > > > The UA *CAN* send double CRLF, but the problem is that the edge proxy > > doesn't know whether the UA is going to do it, so it may provide > > short registration refreshes also for TCP connections. > > christer, > > this directly contradicts what you supported earlier today, i.e., that > the responsibility to handle nat is in the ua. proxy NEVER needs to > "provide" anything for tcp ua's nat problem. as i wrote already, if tcp > ua is behind nat it simply sends CRLFs or (if it is not able to send > CRLFs) uses short enough registration interval.
Absolutely -- that's the most elegant way of doing things which takes no support in server, no negotiation protocol, and is placed where it belongs, in the client. I think specific action items that can be taken are: - TCP-keep-alive as described above - UDP-keep-alive taking some answer Both IMO best placed in BEHAVE for reuse by other apps. -jiri > > -- juha > _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
