Planning And Preparation Activities; Developing A List Of Roles; Developing A List Of Groups; Planning Walkie-Talkie Channels And Addresses - Motorola CA50 Developer & User Manual

Planning and Preparation Activities

Developing a List of Roles

To develop a list of company-wide roles, use associate titles. The most important aspect of a role is selecting a
profile template that allows each role to a range of privileges. For example, some associates might have access to
business applications where other associates may not.

Developing a List of Groups

To develop a list of company-wide groups, or departments, use phone extension pools and additional phone book
entries. The groups drive how a phone extension gets assigned when an associate logs in. It is then used to
organize the phone book to facilitate looking up various associates.

Planning Walkie-Talkie Channels and Addresses

Plan walkie-talkie channel allocations and multicast addresses/ports for the walkie-talkie channels. Walkie-talkie
channels use multicast packets and this requires a plan when using multicast addresses to route the multicast
packets. Normally, channels are allocated on the same multicast address with incrementing port numbers.
NOTE The UCA server and the UCA client application reserve the first port for asynchronous communications
from the server to the UCA clients. This means that Channel 1 on a device is not the first port in the range.
It is recommended to start the port ranges on a '0'. For example, the multicast channels start on address
239.192.2.2 port 5000. This means that the reserved server communications channel is on port 5000.
This means that walkie-talkie channel 1 is on port 5001, channel 2 is on 5002, and so forth.

Planning User Authentication (Device Users and Console Users)

The UCA server defaults to using the built in Device User Authentication and Console User Authentication via Web
Services that access the UCA database. These authentication services can be redirected to alternate user
authentication Web Services. If the built in user authentication is used, the user can be maintained via the Console
or the User Management Web Service. If it is desired to use an external authentication database for either device
users or console users, custom authentication Web Services can be developed based on the UCA Sample
Authentication and UCA Console Sample Authentication reference implementations supplied in the UCA server
Install. Because they are separate authentication Web Services, the Device Users and Console Users can be
independently redirected.
For detailed information about the these optional APIs, see the following sections:
•
CA50 Device User Authentication Process on page 11-5
•
Device User Authentication Web Service on page 11-8
•
User Management Web Service on page 11-29
•
Console User Authentication Web Service on page
Device Users UCA\Client\Authentication\Authentication.asmx
Console Users UCA\Server Management\Authentication\ ManagementAuthentication.asmx
Built In Authentication Web Service
Site Installation Guidelines 13 - 9
11-40.
Built In Management Web Service
UCA\Server Management\UserManagement.asmx
UCA\Server Management\UserManagement.asmx