The following is a list of requirements for the EMU feature:
QSIG must be the private networking protocol in the network of Communication Manager systems. This requirement also includes QSIG MWI.
EMU phase 1: Communication Manager Release 3.1 and later software must be running on the home server and all visited servers.
EMU phase 2: Communication Manager Release 4.0 and later software must be running on the home server and all visited servers. EMU phase 2 is not backward compatible with Communication Manager 3.1.
All servers must be on a Linux platform. EMU is not supported on DEFINITY servers.
The visited telephone must be the same model type as the primary telephone to enable an optimal transfer of the image of the primary telephone. If the visited telephone is not the same model type, only the call appearance (call-appr) buttons and the message waiting light are transferred.
All endpoints must be self-designating terminals.
Uniform Dial Plan (UDP).
Note:
All systems in a QSIG network must be upgraded to Communication Manager 4.0 or later in order for the Enterprise Mobility User feature to function properly. If only some systems are upgraded, and their extensions expanded, the EMU feature might not work with the systems that have not been upgraded. See your Avaya technical representative for more information.
For optimal performance and feature functionality EMU requires,
Private numbering administration supporting UDP dialing between enterprise sites.
The EMU visiting user is able to dial directly the EMU home user using UDP dialing.
The EMU home user is able to dial directly the EMU visiting user using UDP dialing.
All locations dialing. If per location dialing or partition group route administration is configured, Communication Manager does not support EMU. If an EMU user is assigned to a location or is reached through partition group routing, EMU registration is not supported.
