@TomMills
No, you cannot light the Message Waiting Light on multiple user phones for Group Mailboxes (nor other user's mailboxes) like you can on IP Office.
There are several more limitations and feature differences between IP Office and ACO.
ACO lacks many features that IP Office users love and use extensively.
Some of these differences are really surprising, in that they are not available in ACO, and can be a Show-Stopper!
Before migrating a client to ACO, it is wise to review the client's specific use cases, and the specific features they use in IP Office, to determine how that will change once in ACO platform.
Due to this, we are in the process of compiling a comprehensive list of differences that we have discovered thus far.
(thinking of starting at POST to invite others on this forum to contribute their findings related to IP Office and ACO feature and capability differences)
ACO is Powerful, and really excels in the area of Remote User Deployment.
However, as @critchey mentioned, it is not the end all be all answer for everyone.
Just a few disparities we have found: (small sample)
Only 3 calls possible on an Ad-Hoc conference call when using the J-Series Desk Phones
No Direct to Voicemail Button
Contacts in the ACO platform do not pull down to desk phones (if you want contacts in the phone, you have to add them manually via TUI or phone's Web GUI)
Only 10 users allowed in a Call Queue (max time in queue is 15 minutes)
No buttons to Monitor Call Groups, or Join/Leave a Call Group (must use the HUD and/or Web Admin to do so)
Cannot light the Message Waiting Light on multiple users phones for Group Mailboxes or other Users Mailboxes
No User Variables to affect call flows using the a TUI (must always use the Admin Portal to change call flows)
No live status dashboard, (think System Status) to aid in trouble shooting call flow issues.
Again, there are many limitations at this time, most of which are not apparent until you get into the nuts and bolts of a deployment, and then the differences start to add up
(Disclaimer: It is possible that some of the items listed above are possible, but we have not figured out how to do it yet, so if any of the above are incorrect/false, please advise, and for the benefit of all let us know how you solved for the issue)
Also to note, for the ACO platform to exhibit features/capability native in most PBX environments, your client will need to purchase the Premium License Level, which can be cost prohibitive for smaller IP Office clients. (things like, Incoming Caller ID with Name, or allowing a call in Queue to exit out to an Auto Attendant, or Extension, or the ability to push out different Outbound Caller ID for different business units on the system, and many others) At this time, you can not purchase features Ad-Hoc, so it is all or noting, meaning that you can choose Standard or Premium, but cannot cherry pick Premium Feature for an otherwise Standard License Level.
I think it would be beneficial to compile a comprehensive list of Differences and Limitations between the platforms, for the benefit of all on this Forum.
As I mentioned before, we are working on such a list, however, it would be great to get contributions from this knowledgeable Tek-Tips community, as everyone will surely encounter different scenarios.
Possibly starting an AVAYA ACO specific Forum here on Tek-Tips, would be beneficial as well?
Cheers All!