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 Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
J139 on R10.1?
- Thread starter IPrick11
- Start date
intrigrant
Systems Engineer
The J139 is supported from R10.1SP3.
BUT, it s*cks. We have 35 of them on stock used only a few weeks as they does not work very well and we had to replace them with 1608 phones.
BUT, it s*cks. We have 35 of them on stock used only a few weeks as they does not work very well and we had to replace them with 1608 phones.
- Thread starter
- #4
- Thread starter
- #5
sizbut? why reply at all? what is the value of your comment? Of course I asked Avaya. I'm asking this forum as well.
Below is Avaya's response in case you'd like to see it.
Atac:
"I reported this to the A1S programmers and this was the response I got back:
J169 and J179 are already restricted to R11. I’ll make the update for J139 on MR37943 IPO - Add J100 Expansion Module for Feb.
This will be corrected on the A1S configurator probably in Feb but they are definitely not supported on R10."
Below is Avaya's response in case you'd like to see it.
Atac:
"I reported this to the A1S programmers and this was the response I got back:
J169 and J179 are already restricted to R11. I’ll make the update for J139 on MR37943 IPO - Add J100 Expansion Module for Feb.
This will be corrected on the A1S configurator probably in Feb but they are definitely not supported on R10."
10.1 SP3 added support for J169/179, but they don't mention J139.
However they are running in H323 mode with some special firmware so you might consider running R11 if you want those phones.
"Trying is the first step to failure..." - Homer
However they are running in H323 mode with some special firmware so you might consider running R11 if you want those phones.
"Trying is the first step to failure..." - Homer
@IPrick11 - Because AS1 is Avaya's tool rather than an IP Office component, so we have absolutely no clever ways to programming around it. Also we have no psychic powers to know whether you have told Avaya or not and there's no "of course" since too many people like to rant in forums without actually doing the anything themselves (so thank you for doing so and saying you have). [though I understand as engaging with super-tanker enterprises like Avaya to get changes can be painfully slow at times)
Just like product issues, we can only work with the information given and the forum is flooded at the moment with people who think two line explanations of an issue are enough and they have to be prodded with questions in order to get the information from which we can get enough clues to finally start helping them. And... (calm down, about to fly off on a rant myself).
Stuck in a never ending cycle of file copying.
Just like product issues, we can only work with the information given and the forum is flooded at the moment with people who think two line explanations of an issue are enough and they have to be prodded with questions in order to get the information from which we can get enough clues to finally start helping them. And... (calm down, about to fly off on a rant myself).
Stuck in a never ending cycle of file copying.
- Status
Similar threads
