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 SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
V9.1 Manager Backwards compatibility 2
- Thread starter IPGuru
- Start date
-
1
- #2
intrigrant
Systems Engineer
Haven't noticed yet, did you look at the help in R9.1? It really s*cks.
Until now I only use the 9.0.5 manager unless I really need the 9.1 version.
Until now I only use the 9.0.5 manager unless I really need the 9.1 version.
From the R9.1 docs:
"Manager application can be used to manage configurations from systems running earlier software releases.
Manager is able (to?) display systems with software levels it does not support in the Select IP Office discovery menu, however those systems are indicated as not supported."
It looks like it should support any release. (But that's probably just badly explained, the new help files are pretty much like Intrigrant put it, and I don't like the new layout either)
Kind regards
Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam
"Manager application can be used to manage configurations from systems running earlier software releases.
Manager is able (to?) display systems with software levels it does not support in the Select IP Office discovery menu, however those systems are indicated as not supported."
It looks like it should support any release. (But that's probably just badly explained, the new help files are pretty much like Intrigrant put it, and I don't like the new layout either)
Kind regards
Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam
![[smile]](/data/assets/smilies/smile.gif "[smile] [smile]")
- Thread starter
- #6
The manager didn't even show the system I was trying to connect to (perhaps somthing is wonky with TFTP discovery)
We have may customers who are still using V2.1/V3.0DT quite happily.
The 2030 handsets were some of the nicest ever supported by the IPO (No bloody appearance keys needed! + context sensitive menus so DSS buttons did not have to be sacrificed for standard functions such as DND, Divert & hunt group enable)
If it ain't broke don't fix it!
A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear
We have may customers who are still using V2.1/V3.0DT quite happily.
The 2030 handsets were some of the nicest ever supported by the IPO (No bloody appearance keys needed! + context sensitive menus so DSS buttons did not have to be sacrificed for standard functions such as DND, Divert & hunt group enable)
If it ain't broke don't fix it!
A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear
-
1
- Thread starter
- #8
I Hadn't
just tired it & it still don't work
looking at a wireshark trace I think Avaya havefucked up broken the TFTP 'whois' request they are sending nasystemw/who_is instead of nasystem/who_is
it beats me why they would even need to be editing this portion of the code.
still its about the only thing they haven't broken previously ;-)
A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear
just tired it & it still don't work
looking at a wireshark trace I think Avaya have
it beats me why they would even need to be editing this portion of the code.
still its about the only thing they haven't broken previously ;-)
A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear
- Status
