Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

1400 series upgrade issues with Combi cards 5

Status
Not open for further replies.

amriddle01

Programmer
May 2, 2007
23,938
GB
Running any version of Release 9 and using the new V2 combo cards (possibly others), if you see the below on the handsets about half way through the upgrade it is the combi card failing to upgrade the handsets, it isn't the handset or system or SD card, using a DS8 or another combi you know is fine will result in a successful upgrade. This has been noted/confirmed by a few BP's on a number of systems.

I had seen this in the past with the original combo cards but assumed Avaya had resolved such things by now..... apparently not :)

photo.JPG


 
Combi, Combo...same thing :)

 
back to the roots of evil, aka Avaya brings back old problems.
Sound familiar?

Quality Control problem as usual.

Thanks for letting us know, do you want a star so you can catch tlpeter?

Joe W.

TeleTechs.ca
FHandw, ACSS (SME), ACIS (SME)


“This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter
 
BTW, the new upload greeting option with R9 in the LVM greeting utility doesn't work either, just ignores any greeting uploaded and uses the system default... yes I put it in the correct place, even though Manager Help files don't actiually mention the setting at all or where to put it :)

 
Not the menu options, that works, I mean user VM greetings...just clarifying :)

 
The Options:

options.png


The Help file:

Help.PNG


.....Informative :)

 
The LVM Greeting option works as a charm to me.
I run Manager as Administrator and the default output path is c:\Program Files (x86)\Avaya\IP Office\Manager
In Windows version 7, 8 or 8.1 ( my OS ) you don't have writ permissions to that path unless you run the software as Administrator, not even if you run Windows as a Administrator.
Further more first I select the type of file to generate, e.g. Autoattendant, Greeting etc and then I select a .wav file recorded with VM Pro, I enter the output file name full like Welcome.c11 and a recording name. Then click OK and the c11 file is there were I setup before.

About the Combo Cards, I have had this on some occassions with 9.0, the IPO was only fitted with the new combo cards, I took a DS8 out of my car, put it in and all phones got the firmware without a issue. One customer had seen it and was a bit upset, the poor guy called Avaya.... I think he is still on the phone waiting for a answer...
In the past I would report it to Avaya but since the IPOSS sh*t I refuse to report anything at all. We should post this in the general forum which is under NSA like surveillance by Avaya....
 
It generates the c11 files just fine, but the system doesn't recognise it as a Greeting for the specified user or group. When looking at the file for the "Main" group it's labelled "Main GREETING" when you record it normally, when uploading the LVM generated file its labelled "Main Greeting" (lower case) as such the system ignores it and plays the default greeting as though non had been recorded. As I say for Attendant menu options it's fine, user/group mailbox greetings not :)

 
I had the same problem on a 8.1.69
I eventually upgraded the cards on another system and they worked ok
I had 2 combi cards in the system and 1 ds8 card
I never thought of trying the ds8 card .

Something to look out for now
Thanks for the info

By the way how do you put an image photo on the page[ponder]
 
OK misunderstood, My fault.
 
This kind op problems are unacceptable.
It is getting to a point where this will cost us customers.
Avaya used to be good but the last couple of years it is going downhill fast.
We cannot trust the software anymore.
I found a bug in 9.0 SP1 where any user can hotdesk, even without a login code!
9.0GA does not have this bug.
So Avaya did not fix any issues (just some internal testing stuff) but broke something essential.I wonder if they do it on purpose to push BP's to sell IPOSS which we still don't do as the customers refuse to buy it.


BAZINGA!

I'm not insane, my mother had me tested!

 
The root of all evil is the IPOSS. If not bought that it is nearly impossible to get support and have some bugs reported.
I have a customers wer 90% of the calls longer then 15 minutes are disconected, it only happens with 1408 phones on R9SP1.
The traces show clearly that the phone disconnects and the users swear they did not do it, I believe them on this.
No IPOSS so no help. Really bad for doing business wit Avaya.
 
Intrigrant, are you sure about those 1416 only?
I have a new customer on 9.0 SP1 and if that happens then i will take a long holiday to avoid this kind of shit :)


BAZINGA!

I'm not insane, my mother had me tested!

 
Well, the only ones experience this are the 1416 users, the IP phone and 1408 phone users do not complain.
I did not replace any phone but I am planning to swap a few with 9508 phones and see what happens.
 
We have a lot of customers on 9.1SP1 and the lot of them use 1408 or 16xx phones and no one complained.... yet?
 
Hmmm, hopefully it is a 1416 problem then.
But no SSO so no fix at all?
How can Avaya ignore this as it is functionality that you can expect from a phone so i guess this should be fixed for free.
A phone that cannot make long calls is absurd.

BAZINGA!

I'm not insane, my mother had me tested!

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top