# Multi-device User Groups

## Purpose

Use this form to manage personal ring groups (PRGs) that contain members who are:

- programmed as Multi-Device
  This Service Level indicates that the directory number (DN) is assigned to a user that has only basic telephony functionality (e.g., emergency or attendant calls) until programmed as a member of a Multi-Device user group or suite. The DN does not use an IP User License. However, the group or suite has a Multi-device Users or Multi-device Suites license which one person can use at a time in order to receive full telephony service. users

- licensed as a Standard group (collectively with a single Multi-device Users license)

- licensed as an External Twin group. A Multi-device Users license is not required for External Twinning but an IP User license must be available and is consumed on the primary node. If the user is an External Hot Desk User (EHDU), an EHDU license must be available and is consumed on the primary node.

NOTE: As of MiVoice Business Release 7.2, if an IPU license is not available, an MDU license is automatically consumed instead. See Multi-device User License Consumption for IP Users for more information.

Alternatively, use the Personal Ring Groups form to manage PRGs containing members who are programmed as Full Service
This Service Level indicates that the directory number (DN) is assigned to a standard user and device with full telephony functionality. or Trusted Service
This Service Level indicates that the directory number (DN) is assigned to a trusted Mitel application that has full telephony service once it registers with the system. Although the DN can be programmed on the same forms as a Full Service user/device, it does not use an IP User License. users.

## Conditions

See Multi-device User Group

IMPORTANT: Because Multi-device DNs in Multi-device user groups and suites cannot be called directly, emergency services personnel will be unable to place emergency callbacks to them. Follow the configuration and operational guidelines below to minimize the possibility of a mishandled emergency call:

- Do not configure Multi-device DNs as CESID
  Customer Emergency Service Identification. The CESID is a number that uniquely identifies the device that dialed 911. The CESID is fed into the automatic location identification (ALI) database at the Public Safety Answering Point (PSAP) so that emergency services can be dispatched to the correct location. callback numbers. Use the Prime or Pilot number for the group or suite instead.

- If the customer’s local state or provincial regulations require a unique CLI
  Calling Line Identification or Command Line Interface for each telephone, avoid Multi-device user groups or suites. Instead, provision conventional PRGs or suites and use Full Service DNs.

- If the customer is using CESIDs to locate the physical location of the specific device within the Multi-device User Groups, care must be taken as the CESID will not necessarily equate to a dialable number in a Multi-device User Groups scenario.

- Emergency Service calls from Cell/Mobile or any other off-system device should not be made through the MiVoice Business system, unless unavoidable. Calls from off-system devices should be made directly to the Emergency services so that the Emergency services personnel can locate the caller.

## Field Descriptions

Parameter | Description | Default Value
Multi-device User Groups
Multi-device User Group | Enter a valid prime DN up to seven digits in length to be used as the pilot number for the Multi-device User Group. The pilot number is the number dialed to access the Multi-device User Group. Multiline IP sets (including SIP endpoints) and Hot Desk users can be programmed as the prime DN. See Personal Ring Group Conditions for a list of valid numbers. | Blank
Group Type | Select Standard to apply standard group membership rules. Select External Twinning to apply external twinning membership rules (in addition to the Standard rules). See Multi-device User Group for rules on membership and license consumption. | Standard
Prime Member Name | System-generated, protected field. Indicates the name under which the Multi-device User Group's pilot (prime member) is listed in the telephone directory. If no name exists in the Telephone Directory form for the pilot number, this field is blank. |
Home Element | System-generated, protected field. Indicates the name of the primary element for the Multi-device User Group, which is the NE name of the local MiVoice Business system. |
Secondary Element | System-generated, protected field. The data in this field is the prime member's secondary element. "Not Assigned" is displayed if resiliency is not enabled on the prime member device. If the primary element fails, the Multi-device User Group fails over to the secondary element that is displayed in this field. If the secondary element field is blank, the group is resilient but the secondary element name is blank. |
Local-only DN | If "True" the pilot number of the Multi-device User Group is a local-only directory number. If "False" it is a cluster dialable number. This field only appears in the form if your system has been migrated to support Remote Directory Number Synchronization. | False
Multi-device User Groups Members
Member Index | System-generated, protected field. Indicates the number of the member within the group. |
Number | Enter the directory numbers programmed with a Multi-Device Service Level belonging to the Multi-device User Group. See Personal Ring Group Conditions for valid numbers and the maximum members allowed per group. | Blank
Presence | Allows you to set a group member's presence status to Present or Absent. | Present
Name | System-generated, protected field. Indicates the name corresponding to the directory number, as entered in the Telephone Directory form. If no name exists for the associated directory number the field is blank. |
Home Element | System-generated, protected field. Indicates the name of the primary element for the Multi-device User Group, which is the NE name of the local MiVoice Business system. |
Secondary Element | System-generated, protected field. The data in this field is the prime member's secondary element. "Not Assigned" is displayed if resiliency is not enabled on the prime member device. If the primary element fails, the Multi-device User Group fails over to the secondary element that is displayed in this field. If the secondary element field is blank, the group is resilient but the secondary element name is blank. | Not Assigned