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 gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
IP Office 3.0 issues
- Thread starter tjcom
- Start date
What IPGuru said. Mine works fine, but I had to restart the licence server service to get the licenses to take.
Dispensing quality rants and mishaps since 1999:
Dispensing quality rants and mishaps since 1999:
daveinwearside
Programmer
I Have had a few problems with this release !
1. TAPI does not work.
2. I get duplicate mail boxes (one for NAME and one for FULL NAME) on phone manager.
3. If using 54xx handsets with appearence keys call waiting does not work.
4. If you replace the call appearence keys with other keys the call log on the 54xx phones does not work.
5. I've also heard that the wizard does not work, although i have'nt tried this for my self.
I may be wrong if I am please correct me, I just think AVAYA may have been under too much pressure to release this as quick as possible (even though it's late)
1. TAPI does not work.
2. I get duplicate mail boxes (one for NAME and one for FULL NAME) on phone manager.
3. If using 54xx handsets with appearence keys call waiting does not work.
4. If you replace the call appearence keys with other keys the call log on the 54xx phones does not work.
5. I've also heard that the wizard does not work, although i have'nt tried this for my self.
I may be wrong if I am please correct me, I just think AVAYA may have been under too much pressure to release this as quick as possible (even though it's late)
Individual Call waiting no longer works on v3.0.
It is only used for hunt groups.
To achieve call waiting you must assign more than one call apperance key,this works fine for external calls but internal calls will also camp on which i don't like.
It is only used for hunt groups.
To achieve call waiting you must assign more than one call apperance key,this works fine for external calls but internal calls will also camp on which i don't like.
daveinwearside,
Point 3 is almost the whole design intent of 3.0, if you have multiple call appearance buttons on any phone in 3.0, there usage to indicate current and waiting calls overrides (replaces) the use of call waiting.
Point 4 has been that way since the arrival of 4620 way back on (I think 2.0).
Point 5, you use the wizard ....
Point 3 is almost the whole design intent of 3.0, if you have multiple call appearance buttons on any phone in 3.0, there usage to indicate current and waiting calls overrides (replaces) the use of call waiting.
Point 4 has been that way since the arrival of 4620 way back on (I think 2.0).
Point 5, you use the wizard ....
Point 3: this is clearly stated in the release notes
If call aperance keys are used then call waiting does not work (& trying to use a 54XX handset without apperances is not a good idea)
Point 4: Apperance keys MUST be programed sequentialy & Must be the 1st keys on the phone. Again this is stated in the documentation.
Point 1: I had tapi working without a problem during the 3.0 trials, What version of windows are you using, are you shure this is not a firewall issue?
Point 2: Do you have any more details on this, it is not something I have seen.
If call aperance keys are used then call waiting does not work (& trying to use a 54XX handset without apperances is not a good idea)
Point 4: Apperance keys MUST be programed sequentialy & Must be the 1st keys on the phone. Again this is stated in the documentation.
Point 1: I had tapi working without a problem during the 3.0 trials, What version of windows are you using, are you shure this is not a firewall issue?
Point 2: Do you have any more details on this, it is not something I have seen.
Here's a fun one... trying to use call monitor still crashes a 412 in R3 (did with 2.1.27 also). It loses contact with the expansion modules, all phones go belly up, and a reboot of the 412 is required to bring it back up.
Does anyone know if you still have to dial your monitor shortcode twice on a 403/406 under R3?
Peter
PS By call monitor I mean listening in on phone calls, not the monitor application.
Does anyone know if you still have to dial your monitor shortcode twice on a 403/406 under R3?
Peter
PS By call monitor I mean listening in on phone calls, not the monitor application.
Do you guys have the release note document from avaya that lists all the bugs located during field trial & there stats?
a few are still listed as open, to be fixed in the 1st maintanence release, although they do not look too serious.
if not check the V3.0 section of my FTP serer I will place it there.
a few are still listed as open, to be fixed in the 1st maintanence release, although they do not look too serious.
if not check the V3.0 section of my FTP serer I will place it there.
daveinwearside
Programmer
FAO IP Guru
Point 1.
I tried Tapi with release 3 but when i looked for the conection to phone from (in outlook) it wasn't there. so i tried it again with 2.1 and it worked straight away so I don't think the firewall is an issue. I tried it on various PC's. I'm sure it's a release 3 problem.
Point 2.
When you add users to the system you give then 2 names The "Full Name" and "Name".
The mail tab on phone manager lite displayed a mailbox for each of these names even though they were for the same user. I tried going into the voicemail accounts on the mail server to delete one of them but there was only one mailbox per user in the folder.
I have since spoken to someone at AVAYA and he said he had the same problem !
Any Solutions or ideas would be great!
Point 1.
I tried Tapi with release 3 but when i looked for the conection to phone from (in outlook) it wasn't there. so i tried it again with 2.1 and it worked straight away so I don't think the firewall is an issue. I tried it on various PC's. I'm sure it's a release 3 problem.
Point 2.
When you add users to the system you give then 2 names The "Full Name" and "Name".
The mail tab on phone manager lite displayed a mailbox for each of these names even though they were for the same user. I tried going into the voicemail accounts on the mail server to delete one of them but there was only one mailbox per user in the folder.
I have since spoken to someone at AVAYA and he said he had the same problem !
Any Solutions or ideas would be great!
Perhaps one day.....one day....
Avaya will let go a release of IP Office software that will
JUST WORK!
perhaps I will start a sweepstake!
I will go for release 46.2(29)
UK Based IP Office Discussion
Avaya will let go a release of IP Office software that will
JUST WORK!
perhaps I will start a sweepstake!
I will go for release 46.2(29)
UK Based IP Office Discussion
milestoned
Vendor
perhaps I will start a sweepstake!
I will go for release 46.2(29)"
46.2(29) It's gonna work as designed it will simply be a box with lights no phones no technology simply a rack mountable box with pretty lights. People will go in your server room hey what's that Avaya box do. Nothing It works great flawless.
I will go for release 46.2(29)"
46.2(29) It's gonna work as designed it will simply be a box with lights no phones no technology simply a rack mountable box with pretty lights. People will go in your server room hey what's that Avaya box do. Nothing It works great flawless.
crashtest1000
Vendor
Melmac
Yes Phone manager has some sort of problem on some PCs where it has a Memory violation I have 6 ghosted machines and 1 out of 6 has the problem go figure I am logging a case with Avaya you should do the same.
It also has a bad habit of showing two user mail box's on the Message tab one for the full name and one for the Account Name also logging a case
PS In saying all this phone manager V3 is very popular and I think one of the high lite's of version 3.0.
![[cheers]](/data/assets/smilies/cheers.gif "[cheers] [cheers]")
Yes Phone manager has some sort of problem on some PCs where it has a Memory violation I have 6 ghosted machines and 1 out of 6 has the problem go figure I am logging a case with Avaya you should do the same.
It also has a bad habit of showing two user mail box's on the Message tab one for the full name and one for the Account Name also logging a case
PS In saying all this phone manager V3 is very popular and I think one of the high lite's of version 3.0.
IPOUK
IS-IT--Management
- Jun 9, 2004
- 388
I did a 403 DT upgrade (with DS expansion modules), from 2.1(27) to V3 the day V3 came out and didn't read the release notes. The upgrade went absolutely fine - so I didn't do the upgrade to 2.1(99) or whatever it is - the notes say without going here first an upgrade will fail - why didn't it then!!! The notes are very shoddy - they certainly haven't been proof read - a whole load of inconsistencies!
The 2.99 step is to do with memory allocation for bin files, upgrade bin files, configuration, working emory etc.
Whilst it seems you can go from 2.1 to 3.0 without going via 2.99, I suspect you may be sitting on a time bomb for some future upgrade from 3.0(40) to 3.0(xx).
Whilst it seems you can go from 2.1 to 3.0 without going via 2.99, I suspect you may be sitting on a time bomb for some future upgrade from 3.0(40) to 3.0(xx).
IPOUK
IS-IT--Management
- Jun 9, 2004
- 388
cool thanks guys - that makes perfect sense. It was the way the docs were written that made me a bit suspicious. I'll test the downgrade to 2.99 on our test 403 first!
Just the upgrade from 1.x to 2.x needed the 1.99 interim build first WHATEVER the situation - Avaya should make it a little clearer!
Just the upgrade from 1.x to 2.x needed the 1.99 interim build first WHATEVER the situation - Avaya should make it a little clearer!
- Status
