Recent content by AlexLD

I'll just move them over to the centralised server and see how that works over the WAN. 1.5Mbps isn't ideal but it could be worse I suppose.

They don't use One-X or any other apps at the distributed site and the distributed sites have only 4VM ports. So this UCM would not be doing the central part, it would be handling the distributed site.

The goal is to have zero physical servers in this one office, so that precludes VMPro on a local VM. It's either VMPro at another site over the 1.5Mbps WAN or the UCM.

The unified communications module.

Here's an update: It appears that this has solved our problem with random reboots that show in the log as <DSI Exception > CRIT RAISED addr=00000014 .

Just to clarify, I did mean IP500 V2 running R9.

I've always tried to stay away from the UCM for some reason but now I have a site that has a server failure and they have decided they don't want to have a physical server there anymore. My options are to run the VM on their central VMPro Server over the 1.5Mbps WAN link or to get a UCM for the...

Looks like the same issue we had. I'm installing the critical patch for 9.0.3 tonight. It was released yesterday by Avaya. Hopefully this will solve the problem.

What you need is a box, a Viking LDB-3 advanced loop detector and two ECE solid state relays part number ESR5102404000. I have used this setup to do exactly what you're asking for, in a call center they wanted a big sign to light up saying "calls in queue" when the queue was notifying an...

Thanks for sharing that. I'll be tacking the patch tonight and hopefully it will solve my R9 issue. If it doesn't I fully expect to be burned at the stake next week...

I'm having a reboot issue with two R9.0.3 systems as well. I haven't been able to isolate the cause yet however. It happens about once a week on a system with 60 users and the system with 210 users reboots every 2-3 days. It seems to be somewhat common with R9.

It seems too convenient that the config got corrupt on two different systems at the same time. (Oddly the other is an IP500 V1 not as V2 like this one) I did reflash the unit and that didn't seem to make a difference. I'm going to have to leave the monitor on to hopefully get a better idea of...

Anyone know if there have been any fixes for this from Avaya yet? My main Avaya guru at the VAR I use is on some serious sick leave apparently so I'm going to have to wade through the VAR employees that know less than I do to open a trouble ticket.

Crap. It's both vexing and reliving to know I'm not alone...

After upgrading to R9.0.3 from R8.1 on June 22 I've had a DSI Exception three times in somewhat short order. Anyone seen this issue with 9.0.8 build 941? I have a second IP500V1 system that has crashed once since this update with the same address reference addr=00000014 which leads me to wonder...