It is not clear that we need the extra rule that you suggest. Route
headers would normally be used to propagate a flow token up to the point
where the last app is reached. This app then calls setFlow. There should
not be any applications between the one that is flow aware and the flow
This would mean that the behaviour we need at a B2B app is that it
propagates the route headers from its incoming leg to the outgoing one.
If the flow aware app is a SipServlet the added consideration is the
fact that it is the app router that pops the Route header and not the
application itself. The header containing the flow token will be
available either as the poppedRoute or the initialPoppedRoute. As long
as the intervening apps use a CONTINUE or REVERSE directive the
poppedRoute will be preserved.
We could continue to impose the current rules in 14.2.1 to flows but it
is not clear that they are important in practice.
Re: On SIP Outbound and app composition (Re: Meeting Notes.)