RTPEngine horizontal scaling with fixed IPs

[vijay kumar]

Hello All,

How can we scale RTPEngine dynamically by exposing a fixed set of IPs.?

For example,

1. can we put RTPProxy as frontend, and add multiple RTPEngine as RTPProxy backend?

2. Is there any ratio that behind 1 RTPPRoxy how many RTPEngine we could scale.?

3. Can RTPengine itself be configured as frontend, and behind it, can we scale multiple RTPEngine as backend RTPengines.?

CONFIDENTIALITY NOTE: This e-mail is intended only for the person or entity to which it is addressed and contains information that is privileged, confidential, or otherwise protected from disclosure. Dissemination, distribution, or copying of this e-mail or the information contained herein by anyone other than the intended recipient, or an employee or agent responsible for delivering the message to the intended recipient, is prohibited. If you have received this e-mail in error, please delete this message and immediately notify the sender by e-mail. 

NOTE: This e-mail does not constitute an electronic signature and the sender does not intend to enter into any agreement by way of this e-mail, unless otherwise expressly provided by the sender within this e-mail.

[Richard Fuchs]

On 07/03/2024 09.01, vijay kumar wrote:
> Hello All,
> How can we scale RTPEngine dynamically by exposing a fixed set of IPs.?
>
> For example,
> 1. can we put RTPProxy as frontend, and add multiple RTPEngine as
> RTPProxy backend?
> 2. Is there any ratio that behind 1 RTPPRoxy how many RTPEngine we
> could scale.?
> 3. Can RTPengine itself be configured as frontend, and behind it, can
> we scale multiple RTPEngine as backend RTPengines.?

I'm not sure what you mean with frontend and backend? You wouldn't
combine rtpengine with rtpproxy. Scaling is achieved in the controlling
agent, i.e. from within the Kamailio control module. Maybe you need to
give a more concrete example of what you're talking about?

Cheers

[vijay kumar]

Hi Richard, 

for example, we give set of ips to to client to whitelist media gateway ips.  and there are multiple clients.

so lets say tomorrow if we add more rtengine in the set in that case, we will again have to ask to existing client to whitelist the new media engine.

And it will become dependency on the clients for scaling new rtpengine. because if we add new media engine in the set, and client would not have whitelisted the new media engine IP, in that case media will not flow and client will face, voice blank issue when new media engine got engaged for a call.

Hence, i was checking if there is any way to put some kind of Application location balancer for media engine for which it could co-ordinate with media engines , so that client would have to whitelist the Application load balancer, and scaling perspective we could scale more rtpengines without worrying about the IP whitelisting.

So basically, just want to check if is there any way to solve scaling problem in terms of IP whitelisting.

--
You received this message because you are subscribed to the Google Groups "Sipwise rtpengine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rtpengine+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rtpengine/29f04b38-6691-42a5-9983-2617bc539e86%40sipwise.com.

[Richard Fuchs]

On 09/03/2024 14.16, vijay kumar wrote:
> Hence, i was checking if there is any way to put some kind of
> Application location balancer for media engine for which it could
> co-ordinate with media engines , so that client would have to
> whitelist the Application load balancer, and scaling perspective we
> could scale more rtpengines without worrying about the IP whitelisting.
> So basically, just want to check if is there any way to solve scaling
> problem in terms of IP whitelisting.

I'm sure there is a way but I don't have any experience with such a
setup myself. I don't think it would require any cooperation from
rtpengine itself though, as I would assume it could be solved purely on
a network level. Maybe someone else here has some ideas.

Cheers

[vijay kumar]

Sure. Thanks Richard.

--
You received this message because you are subscribed to the Google Groups "Sipwise rtpengine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rtpengine+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/rtpengine/f8aa277a-1e39-419f-9457-4e5c4c651299%40sipwise.com.

[sumit kumar]

I had a similar use case and we have deployed rtpengine on EC2 machines, we thought of putting rtpengine behind NLB (not ALB) but the limitation here is that you can't open a range of ports on NLB. 
So what we have done, is written a small utility that checks the health of rtpengine through ping and registers it in redis. Now, the application that communicates with RTPengine gets the list of all machines from Redis and it can do round robin on that.
Let me know if you find a better solution.

[sumit kumar]

Hi Vijay,
Did you find any solution to this?