On Fri, Jun 13, 2008 at 12:26 AM, M. Ranganathan <[EMAIL PROTECTED]> wrote: > In accordance with the decisions made a few days ago, I have > introduced a stand alone symmitron process. You should see a new > process called sipxrelay when you fire up sipx. > > Its role in life is to run the symmitron interface. It is controlled > as before using XML rpc and the API is essentially unchanged. It is > independent of sipxbridge ( although it uses the same classes to > manage ports and relay data as does sipxbridge, it shares no state > with sipxbridge). It manages a port set independently of sipxbridge. > From an external perspective, since the xml rpc interface is unchanged > Robert should see no impact. However, I should like to change the URL > that is used to access it to http://host/sipxrelay in keeping with its > new name, if thats ok with Robert. > > Please ask if you have questions. > > Thanks > > Ranga > > -- > M. Ranganathan >
Configuration support for this process in sipxconfig is forthcoming ( should be integrated with the NAT traversal configuration ). However, in the meanwhile, you can hand edit a configuration file "sipxrelay.xml" and drop it in the etc/sipxpbx directory -- 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
