Michael Scheidell
2012-07-29 15:44:31 UTC
I updated from 4.2.0 -> 4.2.1, -> 4.4.0 and set a fax did.
works great.
I was surprised that it came in as a pdf, I thought it was tiff by
default (I prefer pdf)
I watched the packet traffic, and it was T.38
all good work.
backups and restores seem to work fine if you do it right (remember if
you had dns yes/no, and if you had dhcp/yes/no).
Even works if you mount a usb thumb drive and do the restore from that.
I don't have all that much time to work on our live system, especially
when there is so much to regress test.
Note: I think sipx 4.4.0 totally broke the cisco 7960 phones.
You put any external call on hold (G.711, moh active), external caller
hears moh, but when you pick him back up, the call drops
(and of course, call transfers from a cisco to a polycom don't work, I
don't think they ever did. we trained people to use blind transfer)
packet trace shows nothing all that much interesting, but if someone has
a 'gotcha' on the upgrade, that can be fixed, let me know.
Also, I can only test this, weekends, every other week, since we are a
24/7 shop, international calls come in at all hours of the day and night.
some noted on upgrade:
backed up a 4.2.0 system, booted the 4.2.0 iso, restored, yum upgrade to
4.2.1
backed up the upgraded 4.2.1, booted 4.2.1 iso, restored, yum upgrade to
4.4.0
backed up the upgraded 4.4.0, booted 4.4.0 iso, restored backup.
(I also tried the 'port 5060 for sipx trunks and calls', and if I
remember, that doesn't work yet, so I keep my PAT on my firewall)
I would really like to keep 4.4.0, for a couple of reasons, one being
the faxes, second being that if we need to purchase commercial support,
we can get it on the current version.
I have been VERY busy lately, (http://www.secnap.tv), and haven't any
time to work on regression testing, and need everything to work 'normal'
before I leave.
So, if I have to revert to 4.2.1, today, than I have to. If I have time
in two weeks, I will try again.
Any words of wisdom?
(ITSP is Level3, sending on udp port 5060, I PAT to 5080 via firewall,
ip address authentication, no registration), and ps, they support T.38
trunking!
--
Michael Scheidell, CTO
o: 561-999-5000
d: 561-948-2259
* Best Intrusion Prevention Product
* Hot Company Finalist 2011
* Best Email Security Product
* Certified SNORT Integrator
______________________________________________________________________
This email has been scanned and certified safe by SpammerTrap(r).
For Information please see http://www.spammertrap.com/
______________________________________________________________________
works great.
I was surprised that it came in as a pdf, I thought it was tiff by
default (I prefer pdf)
I watched the packet traffic, and it was T.38
all good work.
backups and restores seem to work fine if you do it right (remember if
you had dns yes/no, and if you had dhcp/yes/no).
Even works if you mount a usb thumb drive and do the restore from that.
I don't have all that much time to work on our live system, especially
when there is so much to regress test.
Note: I think sipx 4.4.0 totally broke the cisco 7960 phones.
You put any external call on hold (G.711, moh active), external caller
hears moh, but when you pick him back up, the call drops
(and of course, call transfers from a cisco to a polycom don't work, I
don't think they ever did. we trained people to use blind transfer)
packet trace shows nothing all that much interesting, but if someone has
a 'gotcha' on the upgrade, that can be fixed, let me know.
Also, I can only test this, weekends, every other week, since we are a
24/7 shop, international calls come in at all hours of the day and night.
some noted on upgrade:
backed up a 4.2.0 system, booted the 4.2.0 iso, restored, yum upgrade to
4.2.1
backed up the upgraded 4.2.1, booted 4.2.1 iso, restored, yum upgrade to
4.4.0
backed up the upgraded 4.4.0, booted 4.4.0 iso, restored backup.
(I also tried the 'port 5060 for sipx trunks and calls', and if I
remember, that doesn't work yet, so I keep my PAT on my firewall)
I would really like to keep 4.4.0, for a couple of reasons, one being
the faxes, second being that if we need to purchase commercial support,
we can get it on the current version.
I have been VERY busy lately, (http://www.secnap.tv), and haven't any
time to work on regression testing, and need everything to work 'normal'
before I leave.
So, if I have to revert to 4.2.1, today, than I have to. If I have time
in two weeks, I will try again.
Any words of wisdom?
(ITSP is Level3, sending on udp port 5060, I PAT to 5080 via firewall,
ip address authentication, no registration), and ps, they support T.38
trunking!
--
Michael Scheidell, CTO
o: 561-999-5000
d: 561-948-2259
*| *SECNAP Network Security Corporation
* Best Mobile Solutions Product of 2011* Best Intrusion Prevention Product
* Hot Company Finalist 2011
* Best Email Security Product
* Certified SNORT Integrator
______________________________________________________________________
This email has been scanned and certified safe by SpammerTrap(r).
For Information please see http://www.spammertrap.com/
______________________________________________________________________