Thanks for the help. After working through some DNS issues for 2 days I was able to update the yum repo correctly, and perform the fix you mentioned. After all of that I still had the same trouble.
Since then I've loaded the stable release of 4.0.0 (virtualized), and I realize what the problem was.... DNS again... I was trying to access the system via IP since I wasn't on the lab DNS network.. Once I successfully logged into the web interface from the lab, I was able to add the IP address for a DNS alias. from then on I could access the web interface from anywhere. Thanks again, James On Mon, Apr 27, 2009 at 1:25 PM, Grant Lang <[email protected]>wrote: > Hi, > > > > There seems to be a java component missing out of the ISO images (I havent > been able to get to the site to see if this is still an issue with the > latest builds). > > > > *** for a fresh install this worked for me (and some others that I know > have the same problem)*** > > > > The fix that I implemented that worked for me: > > Start the installation and go through to the end of the first section which > sets up the network etc and DNS.. before you start the SipX section of the > setup jump into Putty and connect as you would normally. > > Assuming you are using the Centos single CD installation run this: > > wget -P /etc/yum.repos.d > http://sipxecs.sipfoundry.org/temp/sipXecs/sipxecs-unstable-centos.repo > > then edit the sipxecs-unstable-centos.repo file and change the $release > variable to 5 (I don't know why this doesn't work, it never has for me) and > change the gpgcheck from 1 to 0 so that you have this: > > [sipxecs-unstable] > > name=SIPfoundry sipXecs pbx - latest mainline version baseurl= > http://sipxecs.sipfoundry.org/temp/sipXecs/main/CentOS/5/$basearch/RPM > > gpgcheck=0 > > gpgkey=https://secure2.pingtel.com/RPM-GPG-KEY-pingtel > > enabled=1 > > > > What you have done now is added the unstable sources and you can add the > missing library/rpm file by: > > yum install sipxcommons > > Once that has installed then go back to the other screen and complete the > setup. > > Hope that helps > > > > Cheers > > Grant > > > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *James R > *Sent:* Tuesday, 28 April 2009 5:09 a.m. > *To:* sipx users list > *Subject:* [sipx-users] Admin interface inaccessible with 4.1.x ISO build > > > > I have a successful 3.10.x system running and I want to get a feel for the > 4.x system. I tried installing two different versions of 4.1 from the > ISO's, and everything seemed to be a success according to the build, but > when I try to reach the admin interface via the IP address, it converts my > URL to https and adds the :8443/sipxconfig in my browser (as I would > expect), but then it fails saying it can't display the webpage. > > > > I've tried multiple PC's with multiple browsers, and all have the same > result. > > > > Am I missing something with the new 4.x system? > > > > thanks, > James >
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
