Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - VeeDubb65

Pages: 1 ... 5 6 [7]
91
Well, after 4 days of banging my head against the wall, I found the solution.

The installer is written in Java (horrifying) and instead of using the updated/proper/secure java that is installed on your system, it uses it's own outdated java (also horrifying).

I got it to run by going into the install directory from the command line and executing the same commands as the program shortcut, but using my properly installed java instead of theirs. Seems to work like a charm, and all 3 pbx's are doing an online upgrade as I type this.

92
Are you getting downtime because these "three different 3300s" are on completely different networks and not clustered, ie belong to different customers or something?

Adding a second controller to a network so you have resiliency is actually very cheap: the hardware costs very little as most of the costs are in the per-user licensing, which you already have.

It's a casino/hotel. We have two 3300's that are clustered to support everything but the hotel. Until recently we were using resiliency at all, mostly because my predecessor didn't care much about his job. We now have MANY extensions that haven't been configured with a secondary element yet, purely because of the man-hours involved. 

The third 3300 is for the Hotel, and is not part of the cluster because our telecom vendor advised that this was the best way to keep the various hospitality settings from messing things up on the casino side.

So, it means knocking the entire hotel down for however long it would take to install and restore, and I would assume the multiple reboots on the clustered controllers would result in multiple fail-overs for sets, which still require 2+ minutes of downtime on every failover. Additionally, we have something like 9 analog service units, and all of those analog lines would be down for the duration.

Compared to a single reboot, it's a whole lot of downtime.

If I can't find any solution that allows me to upgrade, then I'll wait until I've had time to configure resilience for everything, but that's still a very long way from 'plan-A.'



On a totally separate but related note, this is supposed to work. If it's not working, I'm either doing something wrong, or have something configured wrong on the system I manage.

Either way, I want to fix the real problem rather than just work around it.

93
I'm starting to think I'm completely crazy.

After much poking around, I discovered that you can theoretically perform an upgrade without the software installer by using the scheduled tasks, in which you can schedule events to download the software from your FTP server, install the upgrade, and then activate the upgrade.

However, when I tried to schedule the task (which I've done many times for other kinds of tasks) I found that I was unable to submit the task. The submit button is there, but just doesn't do anything.

94
Have you tried blocking internet access to see if it brings up the offline licensing option?

I went ahead and blocked internet from the PC that was running the upgrade, and it had no effect. Then I blocked internet access from the PBX, and there was no effect on the installer, although I did get an error (as expected) when I logged into the web management page for the PBX and tried to retrieve licenses from there.



TBH, at this point I would just do a backup, maybe 2, and then do a manual software install, re-license on the controller and restore the DB.

I have had lots of issues in the past with the software installer tool, although in the last 3-4 years it is tremendously better, but I still use the manual method every once in a while, especially with AX controllers... for some reason when I do upgrades they tend to be troublesome sometimes.

I'm seriously considering it, but this is at a 24 hour a day, 365 day a year operation that has enough phones and phone traffic to run three 3300's. To create that much downtime for a non-emergency means sending out notices for a full week, and coming in at 2 or 3 in the morning for three days in a row to pull them down for the update one at a time. I'm willing to spend a pretty good chunk of time and effort to avoid that.

95
Have you tried blocking internet access to see if it brings up the offline licensing option?

I haven't, but that's a very interesting suggestion. I'll have to try it as soon as I get back to the office in the morning.

96
Even if it's a firewall issue I wouldn't expect it to crash. Do you have another laptop or PC you can test the installer on?

I've actually tried it on 4 different PC's, running 4 different operating systems. XP, 7, 10, 2016. I also tried XP compatibility mode on the 7, 10, and 2016; as well as 7 compatibility mode on the 10 and 2016. I also tried most of those as a domain user with admin rights AND right-click runs as administrator.

Also tried at least a couple of those pointing to each PBX.

Same results across the board.

97
I do. The entire system (all three 3300's) is fully licensed and authorized, and from the PBX I can refresh license information without issue.

98
We've got three different 3300's all running MCD 7.2, and our vendor was kind enough (and knows I'm generally capable enough) so he gave use the MiVoice Business Software Installer 14.0.0.10 and and MiVoice Business 3300 Installation 14.0.1.29 (MCD 8.1) so that I could install them without having to hire them to come out for a simple software upgrade.

The problem is that every time I get to the part where you have to click "Retrieve Licenses" to proceed, it momentarily pops up a box that says Retrieving license information and then the whole thing closes out.

It's not leaving any meaningful error in the windows Event Viewer, 3300 Maintenance Log, or anywhere else that I can find. I'm stumped, and so is our phone vendor. Has anyone encountered anything like this before?

The only similar problems I could find online turned out to be firewall issues, but the PC firewall is completely disabled on the machine running the upgrade, and we've thoroughly tested our external firewall and filters, finding no indication that anything is blocked. Everybody involved can ping sync.mitel-amc.com, and the workstation can actually open an ssh session (although I can log in for obvious reasons).

99
Thanks for the sanity check. You've basically confirmed exactly what I was thinking. We may still keep the copper, just because we're in a rural-ish area and we've seen PRI problems in the local CO a few times. On the flip side, $300/month is $300/month.

We actually have two other trunks I haven't mentioned, which are also copper LS trunks. They're connected to controller A, and all 3 controllers use those as the 1st-choice route for outbound 911, so we've always got a clean line waiting for 911 calls.

As for the Enterprise vs standalone, I just double checked: All 3 are Enterprise.


100
I'm working on cleaning up a mitel system that I inheritted from a guy who didn't seem to care much about his job.

We've got 3 3300's, call them A, B, and C.

The call center consoles are attached to A.

A and B are clustered.

C has hospitality enabled, and is not clustered. Technically there's a console attached, but it's only for setting wake-up calls.

Right now we have 4 PRI trunks, and 6 LS. 

For the PRI's, A has 2. B and C each have one, and there are no routes in place to share between A, B and C. A does run out of lines once in a while, B less often, and C almost never. The circumstances that would make one or another run out of lines are all very different, so all three running out at once is unlikely to ever happen.

All 6 of the LS trunks are connected to C, but they're not actually configured. The inbound numbers for those lines are unpublished, and there are no routes that use them. Looking through the ARS, you can see that they may have been configured as 2nd-choice routes in the past, but no calls have touched them for years.

What I'd like to know is what the best method would be to make proper use of all of our trunks, and provide the best total service quality and redundancy. Ideally, I'm thinking that the best option would be to move those 6 LS trunks around so that each PBX has 2. Then use route lists like the following:


A
1st choice PRI group on A
2nd choice route to B
3rd choice route to C
4th choice LS on A, COS restrictricted so only A can use it.

B
1s choicet PRI group on B
2nd choice route to C
3rd choice route to A
4th choice LS on B, COS restrictricted so only B can use it.

C
1st choice PRI group on C
2nd choice route to A
3rd choice route to B
4th choice LS on C, COS restrictricted so only C can use it.

If I build that out right, it should put all the PRI's into a single pool of 92 lines, while still keeping lines to the outside world, even if 2 PBXs go offline. If the PRIs all went down but left the LS trunks up, each PBX would keep 2 lines open for outbound calling.


That brings the questions:

1. Is this even a sane idea, or is there a clear reason why this wouldn't be a good idea?
2. How to I do this without creating a loop? Alternatively, do I care if this creates a loop?
3. Is there a better way to accomplish this?

Pages: 1 ... 5 6 [7]