On Sat, Jun 7, 2008 at 9:19 AM, Damian Krzeminski <[EMAIL PROTECTED]> wrote: > M. Ranganathan wrote: > > [...] > >> Sipxbridge is really two independent services - media relay and >> signaling. Currently, sipxbridge waits for sipxbridge.xml to appear in >> /etc/sipxpbx before it actually starts running. So in a fresh install, >> it will wait and do nothing until you have configured a >> sipxbridge.xml. This necessitates you to actually configure it before >> it starts running. We should change that. A dummy sipxbridge.xml >> should be installed. This need contain nothing other than a port >> range. >> > > If sipXbridge is really 2 different services maybe it would be better if it > actually was split into 2 independent and independently configured services. > Tricks with installing "default" version of sipxbridge.xml are going to > backfire sooner or later (upgrade problems come to mind).
Actually that is not quite correct ( my error for bad explanation ) . Sipxbridge is dependent upon media relay but not vice versa. Does it really matter to you if they run as two independent processes? I dont mind if the configuration has to be read from two different files but when we had this discussion at the start of the project you wanted to combine them into a single file. On the other hand it makes life easier for me if sipxbridge and the media relay run as an independent process. > >> I do think that the port range information in sipxbridge.xml should be >> displayed somewhere independent of the sbc configuration. > > Much easier to achieve if media relay was independent from SBC > functionality... Why? As you are in the business of writing xml files, please write two independent xml files and let the implementation of the relay and bridge do what it needs to do. Do you care if I run the relay in a thread or a process or as two independent processes? That is an implementation choice that does not affect anything else. > > [...] > > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev > -- M. Ranganathan _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
