From what I understand, any calls that traversed at some point the Obi or the Obi AA,
will have their corresponding RTP streams hairpinned on the Obi.
So as an example, assuming that user A gets a callback from the Obi and dials out to a user B,
and assuming that all calls are SIP based, the RTP call path will be:
A <----> Obi <----> B
This naturally results in non-optimal data routing paths.
In some cases, the delays introduced because of this may be the dominant delays on a call.
Consider the scenario where the Obi is in the US, user A in Germany and user B in France:
in the case the voice traffic will be Germany ---> USA ---> France.
SIP supports options for path minimization. So in the above example case,
once the call is established, the two users will be connected with a direct A <----> B RTP streams,
as opposed to going through the Obi on the other side of the Atlantic.
Anyone knows if there is any way to enable path minimization within Obi?
Or any specific reasons (including business ones) of why this makes or doesn't make sense for Obi ?
Any plans or thoughts on this from the Obi folks?
Or may be my above assumptions and understanding are wrong ?
thanks
L.
PS: I do realize that the RTP streams do not always extend all the way to the end callers but
to some GW that eventually reaches the end users. But to keep things simply I show
the users as the RTP end points.
