> > I'm not going to discourage you. But I will warn that you > are faced > > with a learning curve. > > I can't tell you how many things are working hard at pushing > me away from using sipx. I keep trying to stick to it but my god.
You can do this. > Here is the URL of what I've followed so far. I'm guessing > that as is often the case, this is old, wrong information? > > http://sipx-wiki.calivia.com/index.php/Setting_up_a_developmen t_environment Well, I won't call them either wrong or old. Some people can work through those instructions without any frustration. I'm not one of them. That's why I created EDE. > I'll follow what you just told me. Then I'll have to ask a > dozen other questions on compiling since I'm really after the > cgi only it sounds like. I looked a little more at the mailboxmgr.cgi... There's lots of stuff in there that's dependant on the install path, so I do think you do an RPM build. Your Step #4 should be this: ./ede_build_devuser.sh -r -c 4.0 BTW, it's actually the sipxpbx RPM that contains mailboxmgr.cgi (not sipxvxml, as I previously suggested.) I'm not sure whether to advise that you upgrade this RPM, or just drop in the modified executable. RPM install seems cleaner, but I think you'll need to either a) tweak versions in the sipxvxml RPM spec file, or b) update all the RPMs. But, after the Step #4 command above you will have mailboxmgr.cgi somewhere under your WORKING dir. (Run: find . -name mailboxmgr.cgi.) Sorry for the uncertainty, but I've never tried this myself. Also, there is risk here. So make sure you patch and test on a non-production system, before you attempt to update your actual phone system. :) -Paul [email protected] _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
