if the yum update doesn't work as suggested, try sipxecs-setup --reset-all thanks, mike
On Tue, Jul 24, 2012 at 3:13 AM, Todd Hodgen <[email protected]> wrote: > Okay, I made a big mistake. I did not do a stop of sipXecs services prior > to doing a yum update on Sunday Night. Net result, I can’t get into > sipxconfig, nor is it processing calls. Not sure if this is entirely > from this lack of following protocol, or if there were any other issues > introduced by the RPM.**** > > ** ** > > I’d like to just wipe the system, and re-install sipXecs, without > re-installing the operating system. Are there any convenient ways of > doing this.**** > > ** ** > > Secondly, I’d like to make any pertinent information available for > developers in case there is something else that might have caused this. > If there is any interest, please let me know what you would like to see and > I will pull it prior to making any changes to the system. It’s pretty much > dead-in-the-water right now. But if there are logs that would serve a > purpose to someone, please let me know.**** > > ** ** > > Todd**** > > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > -- Michael Picher, Director of Technical Services eZuce, Inc. 300 Brickstone Square**** Suite 201**** Andover, MA. 01810 O.978-296-1005 X2015 M.207-956-0262 @mpicher <http://twitter.com/mpicher> linkedin <http://www.linkedin.com/profile/view?id=35504760&trk=tab_pro> www.ezuce.com ------------------------------------------------------------------------------------------------------------ There are 10 kinds of people in the world, those who understand binary and those who don't.
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
