On 10/19/12 9:40 PM, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
But in this case the call is completed, because negative response codes are absorbed by tm, 200ok being sent back, so no need to destroy any rtp session. iirc, for all branches of a parallel fork there is one rtp session in rtpproxy (cannot tell about other media relays).
sorry that i was not clear enough: the branch replying with 200 ok is not using rtpproxy (e.g. is not behing nat), whereas one or more of the other ones that replied negatively would have used it.
You can set a transaction flag when you force rtpproxy for a branch, then in onreply route, if you get a 200ok from a branch not involving rtp relay and that flag is set, then destroy the rtp relaying session.
Cheers, Daniel