[asterisk-dev] rtp in core

Matthew Rubenstein email at mattruby.com
Wed Apr 4 20:24:17 MST 2007

On Wed, 2007-04-04 at 19:54 -0700, asterisk-dev-request at lists.digium.com
> Date: Wed, 4 Apr 2007 15:47:21 -0400
> From: "Clod Patry" <cpatry at gmail.com>
> Subject: [asterisk-dev] rtp in core
> To: "Asterisk Developers Mailing List" <asterisk-dev at lists.digium.com>
> Message-ID:
>         <ba3a70d80704041247v4d6d4c61pe237a9ce980b8d58 at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
> hi,
> is there any reason why the rtp is in the core and not possibly a
> module?
> I mean, if your * just receive and throw zap channels, having this rtp
> in
> the core is really pointless.
> The problem is that for embeded system, the final bin is pretty huge,
> since
> it has so much stuff built-in (rtp is just one).
> Could we port rtp.c to a module (res_rtp.c, maybe), which would offer
> the
> possibility to unload it in some setups, where rtp isnt implicated.
> Thanks.

	I have another app with an RTP server that I've integrated with
Asterisk. But I have two redundant (not in a good way) RTP servers. If
Asterisk's RTP server were modular, I could use it for the other app, or
drop it to use the other app's server. And it would be easier to make
clusters of just the RTP servers for load balancing.

> Clod Patry 

(C) Matthew Rubenstein

More information about the asterisk-dev mailing list