Discussion:
[asterisknow] AsteriskNOW 1.5 - beta
Jason Parker
2008-10-14 15:04:14 UTC
Permalink
For the last few months, we've been working on an updated version of
AsteriskNOW. What's changed in AsteriskNOW 1.5? Everything!

We switched the core Linux distribution to CentOS from rPath (which uses yum
rather than conary).
We switched the default GUI to FreePBX from AsteriskGUI (though it is still
available if you'd like to continue using it).
We also switched to DAHDI from Zaptel.

When will it be available for public beta? Immediately!

For more information, please see
http://blogs.digium.com/2008/10/13/asterisknow-15-beta-available-more-coming-soon/
- if you want to jump right to the download page, go to
http://www.asterisknow.org/downloads/



For existing users of AsteriskNOW, as I expect most of you are, we'll be posting
shortly about how this would affect you and what steps (if any) you need to take.
Rick Green
2008-10-14 22:05:20 UTC
Permalink
So I've got it downloaded and installed. My web browser is asking for a
username and password for the freepbx gui.

Where so I go from here?
--
Rick Green

"Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety."
-Benjamin Franklin
Jason Parker
2008-10-14 22:17:41 UTC
Permalink
Post by Rick Green
So I've got it downloaded and installed. My web browser is asking for a
username and password for the freepbx gui.
Where so I go from here?
Apparently I copied the wrong article.. The other one had a note at the bottom.

Default username/password is freepbx/fpbx
Rick Green
2008-10-14 23:04:46 UTC
Permalink
Post by Jason Parker
Post by Rick Green
So I've got it downloaded and installed. My web browser is asking for a
username and password for the freepbx gui.
Where so I go from here?
Apparently I copied the wrong article.. The other one had a note at the bottom.
Default username/password is freepbx/fpbx
Thanks. Got one step further!

I defined one of my extensions, using the same extension # and secret as
before. Then I went into the sipura ATA config, and changed only the IP
address of the line1 'proxy' config, but it failed to register.
I don't see any message on the alt-f9 console telling me it even saw a
registration attempt, much less a reject reason. Where should I look?
--
Rick Green

"Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety."
-Benjamin Franklin
Sebastian
2008-10-15 18:08:29 UTC
Permalink
Post by Rick Green
I defined one of my extensions, using the same extension #
and secret as
before. Then I went into the sipura ATA config, and changed
only the IP
address of the line1 'proxy' config, but it failed to register.
I don't see any message on the alt-f9 console telling me
it even saw a
registration attempt, much less a reject reason. Where should I look?
This may be stating the obvious but did you reboot the ATA? I presume it
registered with the old asterisk server OK? When you say 'it failed to
register', I presume you mean that it remains unregistered, rather than
receiving an error in ATA telling you that registration failed?
Rick Green
2008-10-15 19:55:00 UTC
Permalink
Post by Sebastian
Post by Rick Green
I defined one of my extensions, using the same extension #
and secret as
before. Then I went into the sipura ATA config, and changed
only the IP
address of the line1 'proxy' config, but it failed to register.
I don't see any message on the alt-f9 console telling me
it even saw a
registration attempt, much less a reject reason. Where should I look?
This may be stating the obvious but did you reboot the ATA? I presume it
registered with the old asterisk server OK? When you say 'it failed to
register', I presume you mean that it remains unregistered, rather than
receiving an error in ATA telling you that registration failed?
I didn't power cycle the ATA afterupdating the line1 config. The web gui
told me it was restarting the ATA.
The info page on the ATA (Sipura SPA-2002) told me 'not registered'
immediately after the config change, but when I refresh the page a minute
later, it says 'failed', and next attempt in 13s.

I've tried deleting the extension definition and re-creating it several
times. I'm sure I haven't fat-fingered the secret, or left the caps-lock
on.

Now I'm encountering an even more serious problem. I can't contact the
*NOW box at all. From the console, `ifconfig` returns nothing! Executing
`/etc/init.d/network start` brings it back online, but WTF! Looking back
at /var/log/messages, I see a few at 10:24 this morning from avahi-daemon,
beginning with one that says 'Withdrawing address record 192.168.156.101
from eth0'. A googling I will go....
--
Rick Green

"Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety."
-Benjamin Franklin
Rick Green
2008-10-15 20:38:39 UTC
Permalink
Post by Rick Green
Post by Sebastian
Post by Rick Green
I defined one of my extensions, using the same extension #
and secret as
before. Then I went into the sipura ATA config, and changed
only the IP
address of the line1 'proxy' config, but it failed to register.
I don't see any message on the alt-f9 console telling me
it even saw a
registration attempt, much less a reject reason. Where should I look?
This may be stating the obvious but did you reboot the ATA? I presume it
registered with the old asterisk server OK? When you say 'it failed to
register', I presume you mean that it remains unregistered, rather than
receiving an error in ATA telling you that registration failed?
I didn't power cycle the ATA afterupdating the line1 config. The web gui
told me it was restarting the ATA.
The info page on the ATA (Sipura SPA-2002) told me 'not registered'
immediately after the config change, but when I refresh the page a minute
later, it says 'failed', and next attempt in 13s.
I've tried deleting the extension definition and re-creating it several
times. I'm sure I haven't fat-fingered the secret, or left the caps-lock
on.
Now I'm encountering an even more serious problem. I can't contact the
*NOW box at all. From the console, `ifconfig` returns nothing! Executing
`/etc/init.d/network start` brings it back online, but WTF! Looking back
at /var/log/messages, I see a few at 10:24 this morning from avahi-daemon,
beginning with one that says 'Withdrawing address record 192.168.156.101
from eth0'. A googling I will go....
More info:
avahi-daemon is a user-mode program that implements service discovery on
a network, supposedly to enable 'automagic' configuration of printers,
NAS, etc. I didn't find anything to indicate why it would have the
authority to bring down all intervfaces, both eth0 and lo!

tcpdump on eth0 reveals that an icmp message is being sent to the ata,
saying 'udp port sip unreachable'. A quick check with `netstat -l` tells
me that ports 5060 and 5061, both tcp and udp, are not in LISTENing state.
So it looks like this installation is totally non-functional. Just a
pretty GUI, with absolutely no functional engine under the hood!
--
Rick Green

"Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety."
-Benjamin Franklin
Eric Moniz
2008-10-27 02:26:06 UTC
Permalink
Hello,

Let me first say I am very happy with my AsteriskNow 1.5 w/ FreePBX install
and configuration. I am up and running in full production.
I "upgraded" to ASN 1.5 from Trixbox CE and I am quite happy and found the
transition to ASN (thanks to FreePBX) very comfortable.

Now for my question...I would like to secure my install by changing the
default passwords. Here is what I know from my pass experience.(which maybe
the root cause to my problems)

I was able to change the AMPMGRPASS with no difficulty, but when I bring up
the FreePBX GUI after the change it still requires me to use the default
user name and password to access the GUI. So then I changed the AMPDBPASS
to something other than fpbx and I get a db fault on the GUI start up. My
guess is I am not changing the password in all of the locations needed to
update this password.

I have search the web, but they all reference the asterisk GUI and what I
really want to secure is the FreePBX login (freepbx/fpbx)

Any help you may offer and/or any other default password I should change to
secure my install would be greatly appreciated.

Thanks in advance.

eric84
Post by Jason Parker
For the last few months, we've been working on an updated version of
AsteriskNOW. What's changed in AsteriskNOW 1.5? Everything!
We switched the core Linux distribution to CentOS from rPath (which uses yum
rather than conary).
We switched the default GUI to FreePBX from AsteriskGUI (though it is still
available if you'd like to continue using it).
We also switched to DAHDI from Zaptel.
When will it be available for public beta? Immediately!
For more information, please see
http://blogs.digium.com/2008/10/13/asterisknow-15-beta-available-more-coming-soon/
- if you want to jump right to the download page, go to
http://www.asterisknow.org/downloads/
For existing users of AsteriskNOW, as I expect most of you are, we'll be posting
shortly about how this would affect you and what steps (if any) you need to take.
_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--
asterisknow mailing list
http://lists.digium.com/mailman/listinfo/asterisknow
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisknow/attachments/20081026/8d1c9af4/attachment.htm
Jason Parker
2008-10-27 15:14:36 UTC
Permalink
Post by Eric Moniz
Hello,
Let me first say I am very happy with my AsteriskNow 1.5 w/ FreePBX
install and configuration. I am up and running in full production.
I "upgraded" to ASN 1.5 from Trixbox CE and I am quite happy and found
the transition to ASN (thanks to FreePBX) very comfortable.
Now for my question...I would like to secure my install by changing the
default passwords. Here is what I know from my pass experience.(which
maybe the root cause to my problems)
I was able to change the AMPMGRPASS with no difficulty, but when I bring
up the FreePBX GUI after the change it still requires me to use the
default user name and password to access the GUI. So then I changed the
AMPDBPASS to something other than fpbx and I get a db fault on the GUI
start up. My guess is I am not changing the password in all of the
locations needed to update this password.
I have search the web, but they all reference the asterisk GUI and what
I really want to secure is the FreePBX login (freepbx/fpbx)
Any help you may offer and/or any other default password I should change
to secure my install would be greatly appreciated.
Thanks in advance.
eric84
You'll also need to change the password for the FreePBX user in MySQL.
Loading...