You guys didn't make 4.4 to 4.6 easy... good lord!

[Robert B]

This should not be this difficult.

Disclaimer: I'm going to sound snarky and really pissed. It's how I vent
frustration. I apologize in advance.

Issues:

1. My BIND backups that I restore get destroyed every time sipx
restarts. Real nice, gents, real nice...

2. Why does iptables keep turning back on every time sipx restarts?
a. If SipX wants to be DNS, why on earth is port 53 blocked in the
default iptables configuration? Hello, MyFly...

3. After restoring my configuration from 4.4 to 4.6, I was also bitten
by the incorrect Superadmin PIN. Fortunately, I knew to use the
reset-admin from other posts.

4. Once my configuration is restored, what services do I need to
re-enable? The entire "Telephony Services" list is unchecked. Which do I
need to have what I had with 4.4? Boy howdy, these backups I was told to
make sure are proving useful...

5. It restored my Polycom firmware, but marked it as inactive. What the
hell?

6. Where can I monitor my registrations? That feature seems gone.

Did I maybe download the wrong installation ISO? I downloaded
"sipxecs-4.6.0-932.g00cded-x86_64.iso"... Is this the real GA release???

-- Robert

[Josh Patten]

I'm going to throw this out there:

If you guys want documentation on all this, feel free to edit the wiki.
eZuce documentation is reserved for eZuce customers, but anyone is free to
contribute to the sipfoundry wiki at http://wiki.sipfoundry.org. If you
need an account just ask.

Post by Robert B
This should not be this difficult.
Disclaimer: I'm going to sound snarky and really pissed. It's how I vent
frustration. I apologize in advance.
1. My BIND backups that I restore get destroyed every time sipx restarts.
Real nice, gents, real nice..

Charming....

System >> DNS >> Advanced settings >> Unmanaged stuff
Set your stuff as unmanaged and we shouldnt touch it. Bear in mind there
are a lot more DNS values in 4.6 than in 4.4
2. Why does iptables keep turning back on every time sipx restarts?

Post by Robert B
a. If SipX wants to be DNS, why on earth is port 53 blocked in the
default iptables configuration? Hello, MyFly...
Charming again...

Same as DNS. set it to unmanaged if you want to tinker.

3. After restoring my configuration from 4.4 to 4.6, I was also bitten by

Post by Robert B
the incorrect Superadmin PIN. Fortunately, I knew to use the reset-admin
from other posts.

By design. As we no longer use the old PIN format, everything needs to be
reset. If you set a default PIN/password during import, it should be set to
one of these

Post by Robert B
4. Once my configuration is restored, what services do I need to
re-enable? The entire "Telephony Services" list is unchecked. Which do I
need to have what I had with 4.4? Boy howdy, these backups I was told to
make sure are proving useful...

Enable what you want to use. When in doubt enable everything. By default
almost everything is turned off when the system is installed.

Post by Robert B
5. It restored my Polycom firmware, but marked it as inactive. What the
hell?

So activate it. When you restore the config, it copies it in for you.
You've just got to manually activate it to trigger the copy.

Post by Robert B
6. Where can I monitor my registrations? That feature seems gone.

Enable proxy/registrar telephony services, it will reappear

Post by Robert B
Did I maybe download the wrong installation ISO? I downloaded
"sipxecs-4.6.0-932.g00cded-x86_64.iso"... Is this the real GA release???

Yes, GA is g00cded

Post by Robert B
-- Robert
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

[Todd Hodgen]

This is kind of a useless email to send out to the mailing list. Vent, but
personally, I'd prefer my email box not get filled with it. This release
has been out there for the most part for about 6 months. Everyone has had
the same opportunity to load it on a test system, and test their own method
of migration. I've seen many do it, and leave comments. I've successfully
migrated systems without significant issues. As an open source product -
the Community is vital to assist in testing, validation, and cooperation to
make it a successful product.



To the developers, thanks for your work on the project, it's appreciated by
most.



BTW, I hear Shoretel is offering an end of year discount on
licensing.........



From: sipx-users-***@list.sipfoundry.org
[mailto:sipx-users-***@list.sipfoundry.org] On Behalf Of Robert B
Sent: Thursday, December 13, 2012 2:37 PM
To: sipx-***@list.sipfoundry.org
Subject: [sipx-users] You guys didn't make 4.4 to 4.6 easy... good lord!



This should not be this difficult.

Disclaimer: I'm going to sound snarky and really pissed. It's how I vent
frustration. I apologize in advance.

Issues:

1. My BIND backups that I restore get destroyed every time sipx restarts.
Real nice, gents, real nice...

2. Why does iptables keep turning back on every time sipx restarts?
a. If SipX wants to be DNS, why on earth is port 53 blocked in the
default iptables configuration? Hello, MyFly...

3. After restoring my configuration from 4.4 to 4.6, I was also bitten by
the incorrect Superadmin PIN. Fortunately, I knew to use the reset-admin
from other posts.

4. Once my configuration is restored, what services do I need to re-enable?
The entire "Telephony Services" list is unchecked. Which do I need to have
what I had with 4.4? Boy howdy, these backups I was told to make sure are
proving useful...

5. It restored my Polycom firmware, but marked it as inactive. What the
hell?

6. Where can I monitor my registrations? That feature seems gone.

Did I maybe download the wrong installation ISO? I downloaded
"sipxecs-4.6.0-932.g00cded-x86_64.iso"... Is this the real GA release???

-- Robert

[Kyle Haefner]

"2. Why does iptables keep turning back on every time sipx restarts?
a. If SipX wants to be DNS, why on earth is port 53 blocked in the
default iptables configuration? Hello, MyFly..."

The DNS being blocked issue was fixed, one should always run a yum update
after a fresh install to get the latest code.

Posting things that do not work or are confusing is a good thing for the
community, editing the wiki on how to fix them is even better. Posting
"snarky" comments does no one any good and is counterproductive especially
when you post to a list for help.

Post by Robert B
This should not be this difficult.
Disclaimer: I'm going to sound snarky and really pissed. It's how I vent
frustration. I apologize in advance.
1. My BIND backups that I restore get destroyed every time sipx restarts.
Real nice, gents, real nice...
2. Why does iptables keep turning back on every time sipx restarts?
a. If SipX wants to be DNS, why on earth is port 53 blocked in the
default iptables configuration? Hello, MyFly...
3. After restoring my configuration from 4.4 to 4.6, I was also bitten by
the incorrect Superadmin PIN. Fortunately, I knew to use the reset-admin
from other posts.
4. Once my configuration is restored, what services do I need to
re-enable? The entire "Telephony Services" list is unchecked. Which do I
need to have what I had with 4.4? Boy howdy, these backups I was told to
make sure are proving useful...
5. It restored my Polycom firmware, but marked it as inactive. What the
hell?
6. Where can I monitor my registrations? That feature seems gone.
Did I maybe download the wrong installation ISO? I downloaded
"sipxecs-4.6.0-932.g00cded-x86_64.iso"... Is this the real GA release???
-- Robert

--
Kyle Haefner, M.S.
Communication Systems Programmer
Colorado State University
Fort Collins, CO
Phone: [phone]
Email: ***@colostate.edu

01010010 01100101 01100001 01101100 00100000 01101101 01100101 01101110
00100000 01110000 01110010 01101111 01100111 01110010 01100001 01101101
00100000 01101001 01101110 00100000 01100010 01101001 01101110 01100001
01110010 01111001 00101110