We are currently running Avaya CM R.017x.01.0.532.0. We have created and alias 9611ABM with a set type of 9611. The phone setting for Audio Path is available to users with the 9611 set type but not the 9611ABM set type. The actual connected set type for both is a 9611. Both use the same settings file. Has anyone run across this issue? Our management system requires the 9611ABM set type to differentiate between the phones with expansion modules and those without.
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 IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Alias of Avaya 9611 set type not showing same phone menu options as actual 9611 set type
- Thread starter dmcbride
- Start date
Similar threads
- Locked
- Question
- Question
- Locked
- Question