Even if you can get the addresses bound correctly I guess that the real
problem will be how to create the databases and configuration files per
instance.
However, perhaps that could be sorted by creating different chroot
environments for each instance?
Also, for what it's worth, I'm running a reasonably well loaded sipxecs
test system under VMWare. The only real issues I've had are clock
running too slow - now fixed - and an uncomfortably high CPU load on the
host system while not much at all is happening.
I've also tried to run it as a live image but I find all sorts of audio
problems when previously unplayed (and hence uncompressed) audio files
break up
John Buswell wrote:
Thanks, going back to my original question though :
sipxacd which is bound to 0.0.0.0:8110 <http://0.0.0.0:8110/>
sipxpresence which is bound to 0.0.0.0:8111 <http://0.0.0.0:8111/>
watchdog which is bound to 0.0.0.0:8092 <http://0.0.0.0:8092/>
Is there any reason why these cannot be bound to a specific IP ? Is
there any command to force them to bind, or would I need to modify the
source to make that happen? Or are there other issues that would mess
up multiple sipxecs deployments on the same box like that?
On Sun, Aug 17, 2008 at 11:18 PM, Raymund Nones
<[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:
hi john,
that maybe true but i guess it's worth a try :) another option is to
use opensipstack (http://www.opensourcesip.org). this app would allow
you to support multiple domains with your sipxecs.
raymund
On 8/18/08, John Buswell <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
> Raymund,
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
