Hi Dean, >>> The edge proxy is only supposed to add the ob parameter to >>> the Path if the edge proxy included a flow token in the path >>> URI. This should only happen when the UA included a reg-id >>> and instance-id parameter in its Contact header. >> >> Correct. But, the point is that the UA would then still be "allowed" >> to use STUN keep-alive between itself and the outbound proxy, even if the >> registrar doesn't support outbound. > >So I think you're saying that we've gotten the decision as to whether >to use keepalive between the UA and the edge proxy tangled up with >whether or not we use the outbound-style persistent binding at the >registrar?
Yes. >Perhaps if the keepalive negotiation were independent of outbound, it >would work better for you. Well, that is what I initially said in this thread, and what I believe we already did have before Outbound-12: the outbound proxy was able to insert the "keep" parameter in the Path header to indicate support of keep-alive... I think that the UA relying on configuration whether the outbound proxy supports keep-alive or not is never going to work - especially not in mobile environments... Regards, Christer _______________________________________________ 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
