Thanks, I'm starting installation now

Thanks,
Vic 


-----Original Message-----
From: sipx-users-boun...@list.sipfoundry.org
[mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Josh Patten
Sent: Wednesday, July 28, 2010 11:43 AM
To: sipx-users@list.sipfoundry.org
Subject: Re: [sipx-users] Warning about updating your sipXecs
systemstarting now

OK, I think the best suggestion at this point is to start over since you

haven't configured any users.

Take note of whether or not the installation ever asks you for a 
password of any kind. If it does not and you still can't login with 
username root password setup then you probably either have a caps-lock 
key on, a messed up keyboard, a faulty installation disk or a bug

Josh Patten
Assistant Network Administrator
Brazos County IT Dept.
(979) 361-4676


On 7/28/2010 11:39 AM, Vic Hindocha wrote:
> I was paying attention. At no point did it display any credentials. I
> have set  my own useranem and password but that don't work either. i'm
> VERY new at this, thus I'm asking for help
> Thanks,
> Vic
>
>
> -----Original Message-----
> From: Tony Graziano [mailto:tgrazi...@myitdepartment.net]
> Sent: Wednesday, July 28, 2010 11:35 AM
> To: Vic Hindocha; dhub...@ezuce.com; sipx-users@list.sipfoundry.org
> Subject: Re: [sipx-users] Warning about updating your sipXecs
> systemstarting now
>
> Then you need to pay more attention to what you did.
>
> The username is not set here. The root password is set. That's all.
>
> What are you trying to do? Access shell? If so it is usrrname "root"
and
> whatever you set your password during the install script. If you are
not
> aware of the password you set, reinstall and pay more attention to it.
>
> If you are trying to access the web interface, you will be prompted on
> first
> access to set the superadmin password.
>
> Your post here has absolutely nothing to do with the subject.
> ============================
> Tony Graziano, Manager
> Telephone: 434.984.8430
> Fax: 434.984.8431
>
> Email: tgrazi...@myitdepartment.net
>
> LAN/Telephony/Security and Control Systems Helpdesk:
> Telephone: 434.984.8426
> Fax: 434.984.8427
>
> Helpdesk Contract Customers:
> http://www.myitdepartment.net/gethelp/
>
> ----- Original Message -----
> From: Vic Hindocha<hindo...@selex-si-us.com>
> To: Tony Graziano<tgrazi...@myitdepartment.net>; dhub...@ezuce.com
> <dhub...@ezuce.com>; sipx-users@list.sipfoundry.org
> <sipx-users@list.sipfoundry.org>
> Sent: Wed Jul 28 12:29:55 2010
> Subject: RE: [sipx-users] Warning about updating your sipXecs
> systemstarting
> now
>
> I have tried that but no joy
> Also typed in the username and password I set before but no joy
>
> Thanks,
> Vic
>
>
> -----Original Message-----
> From: Tony Graziano [mailto:tgrazi...@myitdepartment.net]
> Sent: Wednesday, July 28, 2010 11:29 AM
> To: Vic Hindocha; dhub...@ezuce.com; sipx-users@list.sipfoundry.org
> Subject: Re: [sipx-users] Warning about updating your sipXecs
> systemstarting now
>
> If you installed from ISO it is displayed on the terminal for you.
>
> It is displayed so you never have to ask it.
>
> root/setup
>
> Why are you asking instead of looking at your screen? Are you
installing
> without access to a terminal?
> ============================
> Tony Graziano, Manager
> Telephone: 434.984.8430
> Fax: 434.984.8431
>
> Email: tgrazi...@myitdepartment.net
>
> LAN/Telephony/Security and Control Systems Helpdesk:
> Telephone: 434.984.8426
> Fax: 434.984.8427
>
> Helpdesk Contract Customers:
> http://www.myitdepartment.net/gethelp/
>
> ----- Original Message -----
> From: sipx-users-boun...@list.sipfoundry.org
> <sipx-users-boun...@list.sipfoundry.org>
> To: Douglas Hubler<dhub...@ezuce.com>; sipx-users
> <sipx-users@list.sipfoundry.org>
> Sent: Wed Jul 28 12:24:54 2010
> Subject: Re: [sipx-users] Warning about updating your sipXecs
> systemstartingnowI'm stuck on this screen, is there a default username
> and password?
>
> Thanks,
> Vic
>
>
> -----Original Message-----
> From: sipx-users-boun...@list.sipfoundry.org
> [mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Douglas
> Hubler
> Sent: Wednesday, July 28, 2010 11:15 AM
> To: Michael Scheidell
> Cc: sipx-users
> Subject: Re: [sipx-users] Warning about updating your sipXecs
> systemstarting
> now
>
> On Wed, Jul 28, 2010 at 11:21 AM, Michael Scheidell
> <scheid...@secnap.net>  wrote:
>    
>> On 7/28/10 10:52 AM, Douglas Hubler wrote:
>>
>> I'm going to restore a URL that would update your sipXecs
installation
>> to the community build when you perform your next yum update. This
>>      
> done, folks can now update if they want.
>
>    
>> is this different than the one thats been bugging us since yesterday?
>>      
> I'm not sure what you mean here
>
>    
>> is there a readme file listing the  old bugs that were fixed?
>>      
> All I have is this for list of fixes
>   http://github.com/dhubler/sipxecs/commits/release-4.2
>
> but now that track.sipfoundry.org is tracking this build, we can start
> to generate release notes from jira for upcoming releases.
>
>
>    
>> New software updates available
>>
>> The package information was last updated Jul 27, 2010 5:59 PM.
>> The system is currently running 4.2.0-018575
>> Update details:
>>    sipxecs 4.2.1-18591.8.1
>>      
> If you update, you'd be going to.
>
>    4.2.1-018932 2010-06-22T03:26:29 build10
>
> I tested going from the last non-community build to this build and
> update went fine.
> _______________________________________________
> sipx-users mailing list
> sipx-users@list.sipfoundry.org
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
> _______________________________________________
> sipx-users mailing list
> sipx-users@list.sipfoundry.org
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>    
_______________________________________________
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to