Search results for query: *

Had VMail connection issue after 11.1.1+ upgrade (VMPro, App server). Only fix was to reboot the IPO (500v2). 11.1.1 started it and we downgraded back to 11.1.0.2.14 to stabilize the system. We upgraded to 11.1.2.1.3 when it came out and Vmail would without warning just randomly loose...

Not surprising. The 11.1.2.0.237 software has been pulled from the site. https://downloads.avaya.com/css/P8/documents/101078908 -J series software upgrade issue? Do we not test software anymore before release?

Hm. I show 4.0.7 is in this new release for the J series which is not updated per the doc. In our tests 4.0.8 and 4.0.9 fixed the issue. 4.0.9 being the latest on the site. It's all good. Just information

Sounds like an issue we are familiar with. If you go to avaya.com/ support/ downloads. search J100 series. SIP 4.0. Download and load 4.0.9 to the SD card. This update fixed it for us after the J phones were updated. Hope that helps

Well, it does not include the J series software update that fixes the hold/transfer/conf issue. I'll give it a week or two for them to put up the new version of this release.

Yep, this is a known issue. We have about 15 sites experiencing it, almost all after upgrades. We have just received a patch for this issue and will implement over the next few days. Due to the nature, we may not know if it fixes it for a week or so. Avaya has just released a sp1 for 11.0.4...

We have had the same issue as well. Ticket open. Multiple traces have been sent. Still waiting. I just do not understand why we are made to feel from Avaya that we might be the only ones experiencing it. Yeah, haven't heard of that before....

Hmm, since its only one step (9-9.1), w/ VMail Pro and nothing more. I cant imagine it taking more than 2 hours or maybe 2.5 with a slow connect. Not sure what they were discovering for that long. Might want to ask how long the tech has been certified (He could be very new or had someone...

9.0.3. I've had it on the last 3-4 embedded systems. It is random and does not appear in the same place. Mostly while working with greetings though. I've re-sent the files as well as re-load the SD card and it still pops up every now and then. Almost appears to be a resource issue.

agreed, but the carrier is digging their head in the sand. They are using a Cisco 3945 router and nobody seems to know how to figure it or have any answers. Typical, they are just telling the customer it is the phone system and brush it away.

unique issue. IP500v2 9.0.0.829. We have a working PRI in slot 1 (network)from another carrier. We added a second PRI (fallback but tried unsuitable)in slot 2 above a Dig 8. The 1st PRI works fine without issue. We just turned up an ATT 10 channel PRI (NI2, esf,b8zs,cpe) and it works great...

Thanks, that pans out. The licensed field is the winner.

That would only tell what the last release on the box for the previous location if the config still exists, not what it was burned in at correct? Burned at 8.0, upgraded to 8.1. Still would need the 8.1 upgrade to work. Usually when a box comes back in we test at wipe it, sounds like a bad...

Is there a way to tell what release a 500v2 was originally burned at? The box knows. ex.. a IP500v2 is in stock (we are told by Avaya to swap boxes to rule hardware out all the time)and is tested good. Customer at 8.1 goes down, how do we determine if the replacement box was burned in at 8.0...

r45 does appear to fix (not mask) the issue. it is available currently from Avaya for 8.1.63, 8.0.51 but not included in yet. Not really sure why. We have it in about 8-10 sites without re-occurances.

You would think they would have come up with a person who actually had a pleasant voice rather than a possessed one. I cringe every time I hear it. It sounds so bad.

What about on embedded?

There is indeed a patch from Avaya for the 9508's and it has been successful in the sites implemented over the past few weeks. Assumimg that is why the delays.

This is a known issue. Avaya has several cases open on it. JIRA 32228.

I'm being told by Avaya that the upcoming release (being tested) will address the issue. They thought they had it with the earlier but still had some events.