unplug writes:
mediaproxy spends much of the CPU to handle the call
compared with
rtpproxy. From the result that I made in the load test, the number of
concurrent call is much much less than we expected.
maximum concurrent call using mediaproxy (openser & mediaproxy in the
same server): 30
maximum concurrent call using rtpproxy (openser & rtpproxy in the same
server): 60
you can distribute mediaproxy to as many host you want. or are you
saying that mediaproxy module functions use_mediaproxy/end_mediaproxy
are the bottleneck?
-- juha