One other thing you might want to do is set a couple symbolic links with different names to opensips binary and call them for each instance. It makes it easier to kill one instance without disturbing the others.
And then copy opensipsctl to individual names so you can set opensipsctlrc to the pid file and fifo or socket for each. Makes things like "dispatcher reload" work nicer. Richard On May 27, 2010, at 5:00 PM, Saúl Ibarra Corretgé wrote: > Hi, > > On 27/05/10 22:57, David Cunningham wrote: >> Hello, >> >> I've seen mentioned that you can run multiple instances of OpenSIPS as >> follows. Is it definitely possible (with 1.4?), and each OpenSIPS will >> be completely independent of the others? >> >> opensips -l 192.168.1.109:5030 -f /var/app/config/opensips_1.cfg -P >> /var/run/opensips_1.pid >> opensips -l 192.168.1.109:5040 -f /var/app/config/opensips_2.cfg -P >> /var/run/opensips_2.pid >> opensips -l 192.168.1.109:5050 -f /var/app/config/opensips_3.cfg -P >> /var/run/opensips_3.pid >> >> Thanks in advance! >> > > Yes, they will be independent as long as you supply a different > configuration file and specify a different PID, just like those examples > in your email show. > > > Regards, > > -- > Saúl Ibarra Corretgé > AG Projects > > _______________________________________________ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users _______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
