[OpenSIPS-Users] mediaproxy relay on none default route interface failed

[Iñaki Baz Castillo]

El Jueves, 10 de Septiembre de 2009, Dan Pascu escribió:
> > That's not true, you could run as many Realys as you want on the  
> > same server,
> > only have to patch mediaproxy-relay to be able to call it with a
> > diferent .cfg as the default one, have diferent listen ports and no  
> > more.
> 
> You don't need to patch anything. Just unpack mediaproxy in as many  
> different directories as you need, run ./build_inplace and modify each  
> config.ini in those directories as needed. Then run mediaproxy from  
> those directories and each of them will use the local config.ini from  
> its own directory.

Is this really preferable to a single and so common "-c CONFIG_FILE" 
commandline option?

A "-c" option would break nothing since the absence of it means "default 
config file". Also a "-c" option allows deb usual installation and upgrade 
(the only requeriment would be create N init scripts having each one a 
different "-c" config file and PID file).

Perhaps you suggest the above solution as a feasible workaround without 
patching the code. I expect it because I cannot imagine how managing N full 
installations of N mediaproxies can be better than a simple "-c" option 
involving a single installation of the software.

Of course this is just my opinion. Take is as a suggestion and not as a 
demand.

Regards.

-- 
Iñaki Baz Castillo <ibc at aliax.net>