Adding a New User

Use the following instructions to add a new user. After you have added users, ensure you click the Commit Changes button to activate your changes.

To add a new radio user

1.	Click the Users tab. The Users page opens displaying the Users list.

2.	Click the Add New User button. The Add New User page opens.

3.	Select Radio system user. The required fields change based on your selection.

4.	In the Alias field, enter the alias for this user. The Alias name appears on all broadband endpoints, and is used to identify users during transmission. WAVE users also use the alias to specify a connection when making Private Calls.

Note:

Linked Capacity Plus radio users will not see this alias. It applies only to the WAVE clients. For instructions on creating an Alias for radio units, consult the documentation provided with your radio units and associate the WAVE Subscriber ID with an alias.

5.	In the Radio Interface: Linked Capacity Plus section, make the following modification:

A.	In Subscriber ID, enter the unique ID used in the Linked Capacity Plus radio system to identify this radio user. This ID can be found in the code plug of individual radio units.

B.	In Privacy, optionally select a privacy mode for this user. If Privacy is enabled for this user in the radio system, then match the type. If no Privacy is used, then select None.

C.	In Basic Privacy Key, enter the privacy key for this radio ID. The Privacy Key value can be found in the code plug for the radio.

6.	Click the Save button when you are done.

Important:

Clicking Save stores the user locally, but does not commit the new user to the system. You must click the commit changes to validate and activate the new configuration.

To add a new broadband user

1.	Click the Users tab. The Users page opens displaying the Users list.

2.	Click the Add New User button. The Add New User page opens.

3.	Select Broadband user. The required fields change based on your selection.

4.

In the Alias field, enter the alias for this user. The Alias appears on all broadband endpoints, and is used to identify users during transmission. WAVE clients display the Alias in the Directory tab for Private Calling. Radio users only see this alias if their individual radio unit is programmed with a matching name for the WAVE user’s Subscriber ID.

5.	In the Username field, specify a Username. The Username is used as a sign-in name on mobile clients, and does not appear to other users.

Note:

Usernames cannot contain spaces or non-alphanumeric characters, (numbers and letters only).

6.	In the Password field, specify a password. The password is used in conjunction with the sign-in name on WAVE clients.

Note:

Passwords cannot contain spaces or non-alphanumeric characters, (numbers and letters only).

7.	In Private Calls to Radios, enable or disable Private Calls to Radios. Disabling Private Calls does not affect Talk Group communication between broadband and radio users. Enabling Private Calls to radios does not block broadband to broadband Private Calls.

8.	In the Number of Simultaneous Sign-ins Allowed list (for WAVE users only) select the number of times a broadband user may sign-in simultaneously using more than one device. Note that multiple sign-ins each consume a license (CAL) on the WAVE 3000 Server when they are signed-in.

9.	Ensure the Active checkbox is selected if you want this WAVE user to be active in the system. Inactive users are disabled and cannot sign in, but can still be saved and activated later.

Note:

Linked Capacity Plus users are active by default and cannot be deactivated.

10.	In the Comments field, optionally enter comments. Comments do not appear outside the WAVE 3000 Server and for administrative purposes only.

11.	In the Radio Interface : Linked Capacity Plus field, optionally enter the ID used to identify this user in the system. IDs must be unique across all Talk Groups and Users.

Important:

Broadband users only require a Subscriber ID if they are Private Call enabled.

12.	Click the Save button when you are done.

Important:

Clicking Save stores the user locally, but does not commit the new user to the system. You must click the commit changes to validate and activate the new configuration. Until activated, the new user cannot sign in.