Re: [sipx-users] 4.6.0 superadmin password lost

On Wed, Sep 26, 2012 at 11:53 AM, 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 nice way o

Re: [sipx-users] 4.6.0 superadmin password lost

>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

Re: [sipx-users] 4.6.0 superadmin password lost

>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 ___

Re: [sipx-users] 4.6.0 Restored 4.4.0 - password bug?

Well, there was no 'password' in 4.4. There was PIN, SIP Password and IM Password. In 4.6 there is user Password (replaces IM Password and now used for user portal access as well), PIN and SIP Password. Mike On Tue, Sep 25, 2012 at 9:47 PM, wrote: > >Password or pin? > > No bug, just mixed

Re: [sipx-users] 4.6.0 superadmin password lost

On Wed, Sep 26, 2012 at 11:20 AM, George Niculae wrote: > On Wed, Sep 26, 2012 at 2:38 AM, 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 en

Re: [sipx-users] 4.6.0 superadmin password lost

On Wed, Sep 26, 2012 at 2:38 AM, 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 > > I can

Re: [sipx-users] 4.6.0 Restored 4.4.0 - password bug?

>Password or pin? No bug, just mixed up my passwords due to the new Voicemail PIN option. Thanks for the input on the other two items. -- ~~ Tony Graziano, Manager Telephone: 434.984.8430 sip: tgrazi...@voice.myitdepartment.net Fax: 434.465.6833 ~~ Linked-In

Re: [sipx-users] 4.6.0 Restored 4.4.0 - password bug?

Password or pin? -- ~~ 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 services! ~~ Using

Re: [sipx-users] 4.6.0 Fax and Custom email question

1. I assume so. 2. Pdf is the default in 4.6. -- ~~ 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 servi

[sipx-users] 4.6.0 Restored 4.4.0 - password bug?

I restored a newly installed 4.6.0 using a 4.4.0 backup. The only options I picked when restoring was to keep the same host/domain name, nothing else. In testing, I was trying to log in as a user but could not. I looked at that users account and it’s password looked to be the same as on the 4.4

[sipx-users] 4.6.0 Fax and Custom email question

Couple of quick questions... 1: Is the ' EmailFormats.properties' file still needed in the /etc/sipxpbx/sipxivr directory for custom email text? 2: How does one set incoming faxes to PDF? ___ sipx-users mailing list sipx-users@list.sipfoundry.org List

Re: [sipx-users] 4.6.0 superadmin password lost

>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 se

Re: [sipx-users] 4.6.0 Statistics Page

Ok, thanks for the help. It is very much appreciated. Robert Schroeder IT Manager Information Systems Member First Mortgage: NMLS ID# 149532 616 44th St SE Grand Rapids, MI 49548 ( Direct Dial: (616) 301-3354 ( Local: (616) 538-1818 ext. 3354 ( Toll Free: (866) 898-1818 ext. 3354 7 Fax: (6

Re: [sipx-users] 4.6.0 Statistics Page

On Wed, Sep 26, 2012 at 12:45 AM, Robert Schroeder < robert.schroe...@memberfirstmortgage.com> wrote: > I found where to add custom groups however how do you add the custom > service? > > ** > That part is only for configuring firewall to accept remote connections from a 3rd party tool, e.g.

Re: [sipx-users] 4.6.0 Statistics Page

I found where to add custom groups however how do you add the custom service? Robert Schroeder IT Manager Information Systems Member First Mortgage: NMLS ID# 149532 616 44th St SE Grand Rapids, MI 49548 ( Direct Dial: (616) 301-3354 ( Local: (616) 538-1818 ext. 3354 ( Toll Free: (866) 898-18

Re: [sipx-users] 4.6.0 Statistics Page

George, Thank you for the information. I will try that out. Robert Schroeder IT Manager Information Systems Member First Mortgage: NMLS ID# 149532 616 44th St SE Grand Rapids, MI 49548 ( Direct Dial: (616) 301-3354 ( Local: (616) 538-1818 ext. 3354 ( Toll Free: (866) 898-1818 ext. 3354 7 F

Re: [sipx-users] 4.6.0 Statistics Page

On Wed, Sep 26, 2012 at 12:20 AM, Robert Schroeder < robert.schroe...@memberfirstmortgage.com> wrote: > In the end I would like to be able to monitor the system. I do admit that > in 4.4.0 the MRTG is not that useful with exception for alarms and high CPU > threshold alerts. > > ** ** > > With

Re: [sipx-users] 4.6.0 Statistics Page

In the end I would like to be able to monitor the system. I do admit that in 4.4.0 the MRTG is not that useful with exception for alarms and high CPU threshold alerts. With the current firewall rules in 4.6 and not having the option to have custom options within the 4.6.0 interface it seems mo

Re: [sipx-users] 4.6.0 superadmin password lost

On Tue, Sep 25, 2012 at 6:47 PM, 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 thought

Re: [sipx-users] 4.6.0 superadmin password lost

>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

Re: [sipx-users] 4.6.0 superadmin password lost

>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 mea

Re: [sipx-users] 4.6.0 superadmin password lost

On Tue, Sep 25, 2012 at 4:08 PM, 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 order

Re: [sipx-users] 4.6.0 superadmin password lost

>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 th

Re: [sipx-users] 4.6.0 superadmin password lost

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, 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

Re: [sipx-users] 4.6.0 superadmin password lost

On Tue, Sep 25, 2012 at 3:58 PM, 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 Centos 6.3 i

Re: [sipx-users] 4.6.0 superadmin password lost

>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

Re: [sipx-users] 4.6.0 Statistics Page

>>> Michael Picher 09/24/12 11:01 AM >>> >This is the direction we're headed... being able to get system (sipxecs / >openuc) related stats for better monitoring.> >We're doing this so that users with any monitoring solution can monitor >sipxecs/openuc in the same manner as all their other equi

Re: [sipx-users] 4.6.0 Statistics Page

On Mon, Sep 24, 2012 at 10:50 AM, Tony Graziano < tgrazi...@myitdepartment.net> wrote: > Though it would be nice to see some way to collect proxy and registrar > stats either from snmp for inclusion at some point or as a separate > mechanism, since as a proxy and registrar THOSE stats are actually

Re: [sipx-users] 4.6.0 Statistics Page

This is the direction we're headed... being able to get system (sipxecs / openuc) related stats for better monitoring. We're doing this so that users with any monitoring solution can monitor sipxecs/openuc in the same manner as all their other equipment. As part of the openUC commercial solution

Re: [sipx-users] 4.6.0 Statistics Page

My last two cents on MRTG. It's nice, easy to look at, but the historical data is IMO pretty worthless. There are a lot of monitoring systems out there which allow you to put an agent on a linux or windows (etc.) system and collect the stats leaving the prequisites and load on sipx lighter than try

Re: [sipx-users] 4.6.0 Statistics Page

Tony is correct MRTG integration is gone. MRTG was driven from SNMP data and all that data is still available on the systems so you could integrate the MRTG stats back again. Going forward it's - BYOMS - Bring Your Own Monitoring System. I accept responsibility for this regression in functiona

Re: [sipx-users] 4.6.0 Statistics Page

I think MRTG is a casualty. I'm not sure if it is being put back in or not. With the "network queue" there are perhaps better and more consistent methods to pull out statistics if I recall properly, but it has not been discussed yet.. The current MRTG does not really provide enough useful informat

[sipx-users] 4.6.0 Statistics Page

I noticed in the 4.6.0 release that there seems to no longer be a statistics page. Is that by new design or is the feature just not available in the current beta builds? Testing of 4.6.0 is going well for me. Thanks everyone for your hard work on this release. It is appreciated very much. Th

Re: [sipx-users] 4.6.0 superadmin password lost

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

Re: [sipx-users] 4.6.0 superadmin password lost

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, 201

Re: [sipx-users] 4.6.0 superadmin password lost

I rebuilt it so it’s a new server but sure, I’ll give it a try and post what happens. From: George Niculae 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

Re: [sipx-users] 4.6.0 superadmin password lost

t than anyone else would have so why would I have a different outcome. > > > From: Tony Graziano > Sent: Sunday, September 23, 2012 3:40 PM > To: m...@grounded.net ; Sipx-users list > Subject: Re: [sipx-users] 4.6.0 superadmin password lost > > > I don't think I've h

Re: [sipx-users] 4.6.0 superadmin password lost

So based on the steps I posted, I don’t see that I did anything different than anyone else would have so why would I have a different outcome. From: Tony Graziano Sent: Sunday, September 23, 2012 3:40 PM To: m...@grounded.net ; Sipx-users list Subject: Re: [sipx-users] 4.6.0 superadmin

Re: [sipx-users] 4.6.0 superadmin password lost

ore 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 superadmi

Re: [sipx-users] 4.6.0 superadmin password lost

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 wrote: > Do a /etc/init.d/sipxconfig db drop to drop all dbs before sipxecs-etup > &g

Re: [sipx-users] 4.6.0 superadmin password lost

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

Re: [sipx-users] 4.6.0 superadmin password lost

r 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 Se

Re: [sipx-users] 4.6.0 superadmin password lost

ew PIN. > However, no matter what I enter, it is responding with; The name "superadmin" is already being 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 softw

Re: [sipx-users] 4.6.0 superadmin password lost

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, wrote: > > >I'm am not sure restoring a 4.20 system t

Re: [sipx-users] 4.6.0 superadmin password lost

>> 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 lis

Re: [sipx-users] 4.6.0 superadmin password lost

to lead to notes of >> previous versions than 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 &g

Re: [sipx-users] 4.6.0 superadmin password lost

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-user

Re: [sipx-users] 4.6.0 superadmin password lost

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 Explain the steps you have taken to get here. -- ~~ Tony Graziano, Manager Telephone: 434.984.8430

Re: [sipx-users] 4.6.0 superadmin password lost

m. > > 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 > > > Explain the steps you have taken to get here. > > -- > ~

Re: [sipx-users] 4.6.0 superadmin password lost

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/tony-graziano/14/4a6/7a4 Ask about our Internet Fax servic

Re: [sipx-users] 4.6.0 superadmin password lost

>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 se

Re: [sipx-users] 4.6.0 superadmin password lost

My point about superadmun ONLY had to do importing, not restoring. Superadmin should be the one you had restored. They logging in to the server at port 12000. -- ~~ Tony Graziano, Manager Telephone: 434.984.8430 sip: tgrazi...@voice.myitdepartment.net Fax: 434.465.6833 ~

[sipx-users] 4.6.0 superadmin password lost

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 super

Re: [sipx-users] 4.6.0

Worked like a charm. As always. -Bryan Anderson On Fri, Jul 27, 2012 at 10:31 AM, Bryan Anderson wrote: > Not a problem. I'll run it after the move here is done. > > Thanks, > -Bryan Anderson > > > > > On Fri, Jul 27, 2012 at 10:22 AM, Douglas Hubler wrote: > >> On Fri, Jul 27, 2012 at 11:55

Re: [sipx-users] 4.6.0

Not a problem. I'll run it after the move here is done. Thanks, -Bryan Anderson On Fri, Jul 27, 2012 at 10:22 AM, Douglas Hubler wrote: > On Fri, Jul 27, 2012 at 11:55 AM, Bryan Anderson > wrote: > > Ok, I had noticed that with the GUI but hoped the setup script would fix > > that. Thanks.

Re: [sipx-users] 4.6.0

On Fri, Jul 27, 2012 at 11:55 AM, Bryan Anderson wrote: > Ok, I had noticed that with the GUI but hoped the setup script would fix > that. Thanks. I got caught-up w/something but you can fix the system with psql -U postgres SIPXCONFIG -c 'delete from timezone where timezone_id > 1' __

Re: [sipx-users] 4.6.0

Ok, I had noticed that with the GUI but hoped the setup script would fix that. Thanks. Any update with the polycom? The phone works without the restore. Haven't tried the restore again yet. (Right now I am moving an office between floors.) -Bryan Anderson On Fri, Jul 27, 2012 at 8:30 AM, D

Re: [sipx-users] 4.6.0

On Fri, Jul 27, 2012 at 10:38 AM, Bryan Anderson wrote: > @All - yes I like the idea of removing those from the UI (I am embarrassed > to admit that I had never thought of rerunning the setup script in the past. > That may help with something else I am working on in 4.4) re: 4.4 - be warned chan

Re: [sipx-users] 4.6.0

@Michael - The file name doesn't matter but it updated the config file and so the file named looked for didn't exist. @Tony - Digging didn't work. That's when I discovered named didn't load the file and why. @All - yes I like the idea of removing those from the UI (I am embarrassed to admit that

Re: [sipx-users] 4.6.0

On Fri, Jul 27, 2012 at 7:58 AM, Michael Picher wrote: > i would probably be good to make it not quite so easy to just change the > domain name. y, another good reason. here's the issue http://track.sipfoundry.org/browse/XX-10327 ___ sipx-users maili

Re: [sipx-users] 4.6.0

i would probably be good to make it not quite so easy to just change the domain name. Kind of like why upgrade is not in the gui anymore... On Fri, Jul 27, 2012 at 7:21 AM, Tony Graziano wrote: > I think that makes it all fixed! > On Jul 27, 2012 7:00 AM, "Douglas Hubler" wrote: > >> On Thu, J

Re: [sipx-users] 4.6.0

I think that makes it all fixed! On Jul 27, 2012 7:00 AM, "Douglas Hubler" wrote: > On Thu, Jul 26, 2012 at 8:35 PM, Bryan Anderson > wrote: > > Ok, Thanks for the update on the Polycom, now I have something regarding > > updating DNS records/configuration. > > > > I had changed the "Domain Name

Re: [sipx-users] 4.6.0

On Thu, Jul 26, 2012 at 8:35 PM, Bryan Anderson wrote: > Ok, Thanks for the update on the Polycom, now I have something regarding > updating DNS records/configuration. > > I had changed the "Domain Name" under system > domain. It updated > /etc/named.conf with the new name including the name of t

Re: [sipx-users] 4.6.0

Since I am confused, let's ask this: Since one would assume the zone file name should equal the domain name and it does not, the truer test would be if dig commands (or nslookup) from another device on the network using the sipx server as the dns server return the proper records for the "new" doma

Re: [sipx-users] 4.6.0

The file name itself doesn't matter... The config statements inside the zone file and the named.conf file matter. It may of course confuse some. On Jul 26, 2012 8:35 PM, "Bryan Anderson" wrote: > Ok, Thanks for the update on the Polycom, now I have something regarding > updating DNS records/conf

Re: [sipx-users] 4.6.0

Ok, Thanks for the update on the Polycom, now I have something regarding updating DNS records/configuration. I had changed the "Domain Name" under system > domain. It updated /etc/named.conf with the new name including the name of the zone file (I went from domain.net, to sipx.domain.net), but di

Re: [sipx-users] 4.6.0

Let's keep an eye on it. It is harmless to run multiple times. Btw I have a fix for the import and polycom issue, just testing it.I'll respond later On Jul 26, 2012 5:17 PM, "Bryan Anderson" wrote: > I guess third time's the charm??? I setup a new vm and setup from the > same image. This time

Re: [sipx-users] 4.6.0

I guess third time's the charm??? I setup a new vm and setup from the same image. This time it only asked once. -Bryan Anderson On Thu, Jul 26, 2012 at 12:56 PM, Douglas Hubler wrote: > On Thu, Jul 26, 2012 at 2:52 PM, Bryan Anderson wrote: > >> Is the /usr/bin/sipxecs-setup supposed to run

Re: [sipx-users] 4.6.0

On Thu, Jul 26, 2012 at 2:52 PM, Bryan Anderson wrote: > Is the /usr/bin/sipxecs-setup supposed to run the first *two* times you > log into the system? If sipxecs-setup is successful, it removes itself from /root/.bashrc which is called upon login. The code to remove itself is also in ~/.bashr

Re: [sipx-users] 4.6.0

Is the /usr/bin/sipxecs-setup supposed to run the first *two* times you log into the system? -Bryan Anderson On Wed, Jul 25, 2012 at 5:18 PM, Douglas Hubler wrote: > Restore from 4.4 *should be* foolproof. you can restore from (almost) any > previous version, any domain, any ip address, any

Re: [sipx-users] 4.6.0 install - homer dependencies

Yeah. There are still some issues related to SQL not saving the correct port information. On 07/26/2012 02:07 PM, Bryan Anderson wrote: I now see packets getting captured, just can't search. :) -Bryan Anderson On Wed, Jul 25, 2012 at 5:12 PM, Douglas Hubler > wrot

Re: [sipx-users] 4.6.0 install - homer dependencies

I now see packets getting captured, just can't search. :) -Bryan Anderson On Wed, Jul 25, 2012 at 5:12 PM, Douglas Hubler wrote: > should have fix in few minutes. > > On Wed, Jul 25, 2012 at 6:59 PM, Kurt Albershardt wrote: > > Ran a 'yum update' on my 4.6 test VM today and saw this, so I bu

Re: [sipx-users] 4.6.0

Restore from 4.4 *should be* foolproof. you can restore from (almost) any previous version, any domain, any ip address, any FQDN. PINs that are longer than 6 numbers or alphanumeric we cannot restore, but you can reset them upon restore. We do not preserve all data, for example, as you said, no

Re: [sipx-users] 4.6.0 install - homer dependencies

should have fix in few minutes. On Wed, Jul 25, 2012 at 6:59 PM, Kurt Albershardt wrote: > Ran a 'yum update' on my 4.6 test VM today and saw this, so I built a clean > VM and installed from scratch -- same errors at the end of the groupinstall: > > > --> Finished Dependency Resolution > Error:

[sipx-users] 4.6.0 install - homer dependencies

Ran a 'yum update' on my 4.6 test VM today and saw this, so I built a clean VM and installed from scratch -- same errors at the end of the groupinstall: --> Finished Dependency Resolution Error: Package: sipxhomer-4.6.0-18.gf9da.x86_64 (sipXecs) Requires: libresip.so()(64bit) Error: P

Re: [sipx-users] 4.6.0

I'll re-install and start from fresh, and compare. I did notice in the config file the sntp section reads: -sipx-sip.cfg nothing after no close out or anything. Thanks, -Bryan Anderson On Wed, Jul 25, 2012 at 2:53 PM, Tony Graziano wrote: > I also wonder if the poly com and NTP issues

Re: [sipx-users] 4.6.0

I also wonder if the poly com and NTP issues were a byproduct of the restore. I wouldn't put much effort into that if it does not happen on fresh non-restored system. On Jul 25, 2012 5:51 PM, "Tony Graziano" wrote: > The restore was not compatible. I am not sure how they plan to overcome > that b

Re: [sipx-users] 4.6.0

The restore was not compatible. I am not sure how they plan to overcome that but this has not been something I would think is implicitly supported get. You would be better off not doing that. Instead export the 4.4 system and remove superadmin and randomize the passwords (remove the password with t

Re: [sipx-users] 4.6.0

The backup was from 4.4. I have the SNTP sever set to the default under System > Date and Time. I just went to devices > phones and clicked on the phone then went to the "SNTP" Link. The url was: https://sipx.domain.net/sipxconfig/phone/EditPhone,$phone$PhoneNavigation.$setting$SettingsNavigat

Re: [sipx-users] 4.6.0

No real services are enabled by default. That's "normal". When you restored from backup did you restart the server? If the backup was from a prior version also it may not work due to the way passwords were stored and encrypted with the domain. You might check the jira for the poly com issue and o

[sipx-users] 4.6.0

I installed SipXecs 4.6.0 yesterday and have updated it using yum. Currently I am running 4.6.0. 2012-07-25EDT11:07:42 ip-10-72-43-110.ec2.internal. The wiki says to send the experiences so here are mine so far: When I first installed next to nothing was enabled for services. I guess that is to