Recent content by gntsfan8690

Update on this -- Control unit came up. We stepped it to 9.1.12 first, then went to 11.0.2, no issue. Everything was brand new. PCS value was 30, but the serial number indicates it was made in 2021. I thought that might be the answer as to why this happened with three prior control units with...

After the 9.0 step, we formatted and recreated the SD at 11.0.2, and the problem persisted. 500 just keeps rebooting and rebooting. At this point we've done a full system re-order. All new parts. We're going to see if the PCS number is 30. If so, we'll do initial boot up with 9.0.12 out of the...

We did try the reset button, I left that out. That said, we tried doing a boot up with the 500 at 9.0.12, low and behold, it has come all the way up. We are now trying a boot up with the 11.0.2 software on the SD card after a format and re-create. Update to follow...

We tried different PC's, and the version of Manager we used for 11.0.2, which we have used many times with no issue like this. That is why went back to it. At this point, I guess we can try the 9.0 step upgrade and see what happens, can't hurt right? The PCS version is 30 on all 3 control units...

We're running into a very unusual situation with the initial power up of a system we're going to install for a customer. When we power up the system (control unit, 2 Combo cards, and a Ds8) it appears to go through all the normal automatic upgrade processes you see (flashing LED's, clicking on a...

J129's are paperweights, and they've been riddled with bugs since they came out about 2 years ago. The user guide states contacts is a support feature on IPO, and there are instructions on how to create new from the phone. My bet is a bug in 11.0 FW for the phone.

Why would you not inform your BP's well in advanced of doing this?

What did you upgrade from? Starting at some point in 9.1, you needed to set a common password on the unsecured interface for voicemail in the 500's security settings, and in the password field of general preferences in VM Pro. Sometimes on an upgrade, you have to default security settings on the...

I'm running into this same issue with the UC module on my lab. Was fine at 10.1, but in 11.0 I am not able to get in anymore with WinSCP or Putty, even though I'm entering the correct Administrator and root logins. Where do I find the setting to enable SSH login, if that's the cause? Not seeing...

It's definitely the vmware environment. I just went through a new install with a customer who had the same thing constantly. Took them over a month to resolve, just two days before our scheduled cutover date.

jayjr1105 -- users can still hot desk onto the ports, even if the port is not blank. When they logoff the port it will just show the base extension that is on the port, and No User, unless they temporarily took a phone over that is on a port matching the extension of another user. My issue is in...

Been going through my first experiences with R11 these last 2 weeks, and am coming across the annoyance of Manager listing what IP/H323 extensions don't have a password on them, and now discovered if I want to blank-out a digital or analog port, it can't be done. Seem to need to have an...

I got the CP a couple of weeks ago and confirmed a 2420 I had worked fine on my lab. I asked the Avaya engineer if the 5400's had been labbed after the CP was applied, and was told yes and they worked as normal as well. You need to open an SR with Avaya to get the patch.

Just a wild guess, but I had a customer who had something like this happen while we only had a few demo users programmed on their Primary server in a Server Edition solution. It was virtual in a VMWare environment. It turned out they got hacked. The One X services would be at 100% CPU, and after...

@hilbroth -- let me totally clear out my Avaya folder of Manager and re-install 11.0 . The funny thing is 2400 are still supposed to be supported on 11.0 from what I saw in release notes I downloaded the other day. UPDATE: I stand corrected. Nothing in my Manager folder for 2400 or 5400 bins...