Avaya Communication Manager IP DECT, Installation, Administration And Maintenance Manual

Page: 67 / 128

Issue 1 August 2006 67
Chapter 4: Avaya Communication Manager
Usage and Important Notes
S8300, S8500 and S87x0 systems are supported where Avaya Communication Manager
(ACM) should be CM3.1.2 load 632.1 or later with appropriate update file.
One or more fixed IP trunk connection is required between ADMM and ACM. The IP DECT
base stations are controlled by the ADMM, they do not register to ACM system. In case the IP
network is down between the ADMM and the IP DECT base station the DECT operation is not
controlled for the base station.
The ADMM does not support survivability as ACM does with LSP and ESS capabilities for
Media Gateways. Several ADMM can be connected to the same ACM system where DECT
users can do roaming between these systems with subscribing to the proper IP DECT system.
Separate ADMM could be configured for such site which has survivability for the ACM system
and has CLAN for the IP trunk connection at that site and the DECT operation is required when
ACM system is in survivable mode. DECT operation is not available for such ACM site where
LSP takes over the control (no CLAN available for the IP trunk connectivity for such site).
For IP DECT users the same features are available as for DECT R2 users. The available
features and feature operation is the same as for analog station users, but interactions with
Multiple Locations feature set is limited and depending on the configuration of the ACM and IP
DECT system.
The Avaya 3711 user should use the ADMM’s AVAYA Menu for activating/deactivating ACM
features if the station’s COS has the Console Permission turned off (set to `n`).
ACM system administration
●
SA8567 needs to be enabled in the license file:
display system-parameters special-applications Page 4 of 6
SPECIAL APPLICATIONS
(SA8481) - Replace Calling Party Number with ASAI ANI? n
(SA8500) - Expanded UUI Display Information? n
(SA8506) - Altura Interoperability (FIPN)? n
(SA8507) - H245 Support With Other Vendors? n
(SA8508) - Multiple Emergency Access Codes? n
(SA8510) - NTT Mapping of ISDN Called-Party Subaddress IE? n
(SA8517) - Authorization Code By COR? n
(SA8518) - Automatic Callback with Called Party Queuing? n
(SA8520) - Hoteling Application for IP Terminals? n