Just to be sure is not the same issue I've noticed some time ago - could you check the permissions of sipXecs files? I've seen something similar after an update when files permission was changed to root:root...
On Sunday, May 15, 2011, Josh M. Patten <[email protected]> wrote: > > > > > > > It wasn't but I installed it shortly after upgrading. I was one of the > installs that had the RPM dependency problem relating to the g729 passthrough > RPM that required removing that > RPM (happened to other people on this list) which in turn removed the > sipxecs pseudopackage. Once I reinstalled the pseudopackage sipxacccode was > installed. > > > > From: [email protected] > [[email protected]] on behalf of Tony Graziano > [[email protected]] > Sent: Saturday, May 14, 2011 9:23 PM > To: Discussion list for users of sipXecs software > Subject: Re: [sipx-users] 4.4 sipXrls dead > > > > is sipxacccode rpm installed? > > On Sat, May 14, 2011 at 9:47 PM, Josh M. Patten > <[email protected]> wrote: > > > > I've attached the last 500 lines of my sipxsupervisor.log (looks nothing like > that) > > Basically it's telling me what I already know, that SSL is borked. I just > don't really know how to fix it. I've tried the normal methods and they didnt > work. > > > > From: > [email protected] > [[email protected]] on behalf of Tony Graziano > [[email protected]] > > Sent: Saturday, May 14, 2011 8:41 PM > > To: Discussion list for users of sipXecs software > Subject: Re: [sipx-users] 4.4 sipXrls dead > > > > > > > does your issue resemble these messages? > http://track.sipfoundry.org/secure/attachment/19154/sipxsupervisor.log > On May 14, 2011 9:32 PM, "Josh M. Patten" <[email protected]> wrote: >> All packages are 4.4.0-192 or 4.4.0-202 >> >> Verified with both yum and rpm -qa >> ________________________________ >> From: [email protected] >> [[email protected]] on behalf of Tony > Graziano [[email protected]] >> Sent: Saturday, May 14, 2011 8:21 PM >> To: Discussion list for users of sipXecs software >> Subject: Re: [sipx-users] 4.4 sipXrls dead >> >> >> sipxconfig gui is functional so port 8443 is reachable. did you check ans >> make sure all your packages updated and that you don't have two versions of >> one package either? >> >> On May 14, 2011 9:12 PM, "Josh M. Patten" >> <[email protected]<mailto:[email protected]>> wrote: > > > > > > > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: > http://list.sipfoundry.org/archive/sipx-users/ > > > > > > -- > ====================== > Tony Graziano, Manager > Telephone: 434.984.8430 > sip: [email protected] > Fax: 434.326.5325 > > Email: [email protected] > > LAN/Telephony/Security and Control Systems Helpdesk: > Telephone: 434.984.8426 > sip: [email protected] > > Helpdesk Contract Customers: > http://support.myitdepartment.net > > > <http://support.myitdepartment.net>Blog: > http://blog.myitdepartment.net > > > Linked-In > Profile: http://www.l <http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4> > > > > _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
