6 Oct
2005
6 Oct
'05
3:43 p.m.
Hello,
How can we use ser and rtpproxy for load-balancing and
failover ?
if ser is able to handle n calls per second how can we
calculate the load for rtpproxy ( memory, cpu, ...)
in order to send all traffic to one rtpproxy?
If this one is down nathelper module is able to send
traffic to an other rtpproxy .
SER-----------------------------
| | |
rtpproxy1 rtpproxy2 rtpproxy3
via unix socket
What's the best way for SER failover ?
___________________________________________________________________________
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger
Téléchargez cette version sur http://fr.messenger.yahoo.com
3:55 p.m.
My question is "if ser is able to handle n calls per
second how can we calculate the load for rtpproxy (
memory, cpu, ...)" not mediaproxy !
Harry
from nathelper.c:
* Introduce failover mechanism, so that if SER
detects that one
* of many proxies is no longer available it
temporarily decreases
* its weight to 0, so that no traffic will be
assigned to it.
* Such "disabled" proxies are periodically checked
to see if they
* are back to normal in which case respective weight
is restored
* resulting in traffic being sent to that proxy
again.
*
* Those features can be enabled by specifying more
than one "URI"
* in the rtpproxy_sock parameter, optionally
followed by the weight,
* which if absent is assumed to be 1, for example:
*
* rtpproxy_sock="unix:/foo/bar=4 udp:1.2.3.4:3456=3
udp:5.6.7.8:5432=1"
--- Andreas Granig <andreas.granig(a)inode.info> a écrit
:
harry gaillac wrote:
___________________________________________________________________________
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger
Téléchargez cette version sur http://fr.messenger.yahoo.com
How can we use ser and rtpproxy for
load-balancing
and
failover ?
Mediaproxy supports this using DNS SRV.
Andy
4:30 p.m.
harry gaillac wrote:
My question is "if ser is able to handle n calls
per
second how can we calculate the load for rtpproxy (
memory, cpu, ...)" not mediaproxy !
Two of three of your questions were how to do do load-balancing and
failover with rtpproxy, which is not possible with the current stable
release of ser, but it's possible with mediaproxy (and with nathelper of
cvs head, as you have already figured out).
Andy
4:39 p.m.
rtpproxy is able to perform failover not
load-balancing !!!
Harry
from nathelper.c:
* Introduce failover mechanism, so that if SER
detects that one
* of many proxies is no longer available it
temporarily decreases
* its weight to 0, so that no traffic will be
assigned to it.
* Such "disabled" proxies are periodically checked
to see if they
* are back to normal in which case respective weight
is restored
* resulting in traffic being sent to that proxy
again.
*
* Those features can be enabled by specifying more
than one "URI"
* in the rtpproxy_sock parameter, optionally
followed by the weight,
* which if absent is assumed to be 1, for example:
*
* rtpproxy_sock="unix:/foo/bar=4 udp:1.2.3.4:3456=3
udp:5.6.7.8:5432=1"
--- Andreas Granig <andreas.granig(a)inode.info> a écrit
:
harry gaillac wrote:
___________________________________________________________________________
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger
Téléchargez cette version sur http://fr.messenger.yahoo.com
My question is "if ser is able to handle n
calls
per
second how can we calculate the load for rtpproxy
(
memory, cpu, ...)" not mediaproxy !
Two of three of your questions were how to do do
load-balancing and
failover with rtpproxy, which is not possible with
the current stable
release of ser, but it's possible with mediaproxy
(and with nathelper of
cvs head, as you have already figured out).
Andy
4:50 p.m.
harry gaillac wrote:
rtpproxy is able to perform failover not
load-balancing !!!
And how to you interprete the paragraph above, where it says:
"Added support for using more than one rtp proxy, in which
case traffic will be distributed evenly among them."
You really should read more carefully.
Andy
6987
days inactive
6987
days old
5 comments
2 participants
participants (2)
-
Andreas Granig -
harry gaillac