On Wed, Sep 26, 2012 at 2:38 AM, m...@grounded.net wrote:
I'd say it's safe enough to do it and you'll find all the support
needed on the list.
Though following best practice deployments I advise you to run it for
couple of days in test env before going live and check the
functionality you need
On Wed, Sep 26, 2012 at 11:20 AM, George Niculae geo...@ezuce.com wrote:
On Wed, Sep 26, 2012 at 2:38 AM, m...@grounded.net wrote:
I'd say it's safe enough to do it and you'll find all the support
needed on the list.
Though following best practice deployments I advise you to run it for
You should enable 'SIP Registrar' service in order to have this page
Got it, thanks.
I’m not sure it’s going to be a good idea to go to 4.6.0 on a remote system
because of it’s many changes. Might be safer to rebuild a 4.4.0 then get on
4.6.0 again in a few weeks.
Mike
Yep, as Laurentiu mentioned you need to enable registrar and proxy on
that machine. Go to Servers Telephony tab and choose services you
want to run on the box (registrar, proxy, voicemail)
I like that services are modularized. It's a nice way of managing servers,
turning things on and off to
On Wed, Sep 26, 2012 at 11:53 AM, m...@grounded.net wrote:
Yep, as Laurentiu mentioned you need to enable registrar and proxy on
that machine. Go to Servers Telephony tab and choose services you
want to run on the box (registrar, proxy, voicemail)
I like that services are modularized. It's a
Or use sipxecs-setup --reset-all that should automatically drop all dbs
The restore seemed to work the second time around so was able to spend a little
time with 4.6.0. However, I need to convert this server to a 4.4.0.
This was a fresh Centos 6.3 install with sipx installed via repo. Other than
On Tue, Sep 25, 2012 at 3:58 PM, m...@grounded.net wrote:
Or use sipxecs-setup --reset-all that should automatically drop all dbs
The restore seemed to work the second time around so was able to spend a
little time with 4.6.0. However, I need to convert this server to a 4.4.0.
This was a fresh
You can not run sipXecs 4.4.0 on CentOS 6.x...
mentioned over and over on the list...
On Tue, Sep 25, 2012 at 8:58 AM, m...@grounded.net wrote:
Or use sipxecs-setup --reset-all that should automatically drop all dbs
The restore seemed to work the second time around so was able to spend a
4.4 does not run on CentOS 6.x so pretty sure you have to rebuild
server.
Oops, forgot about that. Thanks.
Wondering why you need to revert from 4.6 to 4.4, mind to
provide some feedback?
I need to build a replacement 4.4.0 server in order to move a server from
one location to another. I
On Tue, Sep 25, 2012 at 4:08 PM, m...@grounded.net wrote:
4.4 does not run on CentOS 6.x so pretty sure you have to rebuild
server.
Oops, forgot about that. Thanks.
Wondering why you need to revert from 4.6 to 4.4, mind to
provide some feedback?
I need to build a replacement 4.4.0 server in
Well we're running 4.6 on eZuce for 2 months now and it works just
fine. Of course there are updates / bug fixes but nothing to affect
core functionality. Hope you'll get back to 4.6.0 really soon
I could use 4.6.0, just a little nervous that since the server will be
remote to us, it could mean
Well we're running 4.6 on eZuce for 2 months now and it works just
fine. Of course there are updates / bug fixes but nothing to affect
core functionality. Hope you'll get back to 4.6.0 really soon
I'm in the middle of a move which is why I thought building a 4.4.0 system
would be the safest.
I
On Tue, Sep 25, 2012 at 6:47 PM, m...@grounded.net wrote:
Well we're running 4.6 on eZuce for 2 months now and it works just
fine. Of course there are updates / bug fixes but nothing to affect
core functionality. Hope you'll get back to 4.6.0 really soon
I'm in the middle of a move which is why
I'd say it's safe enough to do it and you'll find all the support
needed on the list.
Though following best practice deployments I advise you to run it for
couple of days in test env before going live and check the
functionality you need
I can do that, I have a few days of space.
I've been
I built a centos 6.3 server, added the sipxecs repo, installed from repo and
everything went fine.
Searched for info on backing up a 4.2.0 server and restoring it on a new 4.6.0
server and found plenty of problems and pretty much only one solution mentioned
by Tony about not including the
Superadmin should be the one you had restored.
They logging in to the server at port 12000.
I’m assuming you said try logging into the server on port 12000 but that
doesn’t seem to make any difference. Still getting
‘User ID and PIN combination is not valid’.
I’ve also tried the backed up
Explain the steps you have taken to get here.
--
~~
Tony Graziano, Manager
Telephone: 434.984.8430
sip: tgrazi...@voice.myitdepartment.net
Fax: 434.465.6833
~~
Linked-In Profile:
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax
4.6.0 along with commands that don’t seem to work on 4.6.0. I have not yet
found information on how to restore the superadmin password on a 4.6.0 system.
Mike
From: Tony Graziano
Sent: Sunday, September 23, 2012 10:36 AM
To: m...@grounded.net ; Sipx-users list
Subject: Re: [sipx-users] 4.6.0
: Re: [sipx-users] 4.6.0 superadmin password lost
Explain the steps you have taken to get here.
--
~~
Tony Graziano, Manager
Telephone: 434.984.8430
sip: tgrazi...@voice.myitdepartment.net
Fax: 434.465.6833
~~
Linked-In Profile:
http://www.linkedin.com/pub
, September 23, 2012 10:36 AM
*To:* m...@grounded.net ; Sipx-users listsipx-users@list.sipfoundry.org
*Subject:* Re: [sipx-users] 4.6.0 superadmin password lost
Explain the steps you have taken to get here.
--
~~
Tony Graziano, Manager
Telephone: 434.984.8430
sip: tgrazi
to work on 4.6.0. I have not
yet found information on how to restore the superadmin password on a 4.6.0
system.
Mike
From: Tony Graziano
Sent: Sunday, September 23, 2012 10:36 AM
To: m...@grounded.net ; Sipx-users list
Subject: Re: [sipx-users] 4.6.0 superadmin password lost
...@grounded.net ; Sipx-users list
Subject: Re: [sipx-users] 4.6.0 superadmin password lost
Explain the steps you have taken to get here.
--
~~
Tony Graziano, Manager
Telephone: 434.984.8430
sip: tgrazi...@voice.myitdepartment.net
Fax: 434.465.6833
~~
Linked
: George Niculae
Sent: Sunday, September 23, 2012 12:18 PM
To: m...@grounded.net ; Discussion list for users of sipXecs software
Subject: Re: [sipx-users] 4.6.0 superadmin password lost
On Sep 23, 2012 8:08 PM, m...@grounded.net wrote:
I'm am not sure restoring a 4.20 system to 4.6 would
Thank you for the good tips. I’ll keep these for future reference and give
4.6.0 another try soon.
Mike
From: George Niculae
Sent: Sunday, September 23, 2012 1:13 PM
To: m...@grounded.net ; Discussion list for users of sipXecs software
Subject: Re: [sipx-users] 4.6.0 superadmin password lost
of sipXecs software
Subject: Re: [sipx-users] 4.6.0 superadmin password lost
Or use sipxecs-setup --reset-all that should automatically drop all dbs
George
On Sunday, September 23, 2012, George Niculae geo...@ezuce.com wrote:
Do a /etc/init.d/sipxconfig db drop to drop all dbs before sipxecs-etup
used by a user or service.
From: George Niculae
Sent: Sunday, September 23, 2012 12:18 PM
To: m...@grounded.net ; Discussion list for users of sipXecs software
Subject: Re: [sipx-users] 4.6.0 superadmin password lost
On Sep 23, 2012 8:08 PM, m...@grounded.net wrote:
I'm am
to restore this time if that’s not fully working
well from 4.4.0 to 4.6.0.
From: George Niculae
Sent: Sunday, September 23, 2012 1:13 PM
To: m...@grounded.net ; Discussion list for users of sipXecs software
Subject: Re: [sipx-users] 4.6.0 superadmin password lost
Or use sipxecs-setup
list for users of sipXecs software
Subject: Re: [sipx-users] 4.6.0 superadmin password lost
Maybe you hit a bug or something, mind to explain exactly the issues you're
seeing? We're running 4.6 restored from 4.4 in our office for almost 2 months
now
George
On Sunday, September 23, 2012, m
Sent: Sunday, September 23, 2012 4:11 PM
To: m...@grounded.net ; Discussion list for users of sipXecs software
Subject: Re: [sipx-users] 4.6.0 superadmin password lost
Maybe you hit a bug or something, mind to explain exactly the issues you're
seeing? We're running 4.6 restored from 4.4 in our
29 matches
Mail list logo
