1. Workcloud Communication Extension Manager Customer Administrator Guide
  2. Client and Server Configuration
  3. Deployment Checklist
  • Workcloud Communication Extension Manager Customer Administrator Guide
Deployment Checklist

Deployment Checklist

Table 1 highlights topics to consider when creating an Extension Manager configuration.
Extension Manager Checklist
Component
Consideration
PBX
PBX location and services provided to the Zebra Voice clients.
Are the PBXs that provide services to the Zebra Voice clients local to the site or centralized?
  • Helps determine how many PBXs need to be defined in the Extension Manager.
Are all PBXs from the same vendor?
  • Different PBXs have different configuration parameters.
Are you deploying a nurse call system?
  • Might require multiple PBXs for each extension and user.
Are excellent codecs used?
  • Might require specific configuration parameters for the PBX.
What TCP transport protocol is used?
  • Specific configuration parameters required for PBX?
  • Do firewall settings need to be reviewed?
Identify all the codes for call park, conference call, and other features.
  • Develop use case requirements.
  • Incorporate settings into each PBX definition.
Sites
Site locations that support the Zebra Voice clients.
Is the IP address used at each site consistent and predictable?
  • The device's IP address can be used to automatically assign a site.
How many sites are deployed?
  • All sites need to be accounted for and added to the Extension Manager.
Does a predictable number scheme identify sites?
  • A site numbering scheme is helpful in understanding the scale of the deployment’.
  • Site numbering schemes help identify organizational operating units and help organize the configuration.
Can users or devices select a site location?
  • Some customer locations resolve each building into a site.
  • Helps identify the movement of assets and the use case requirements.
Are there unique PBX differences per site?
  • Telephony systems evolve over time, and hybrid systems with multiple PBXs serving the same site for different purposes can result.
Departments
Each site may have more than one department. A department can be considered a logical container or a collection of extensions.
What are the departments for a given site?
  • Needed to establish department configuration.
  • Meaningful department names.
  • Easily recognizable by the users.
  • Not all departments may have an associated extension.
Are the departments consistent from site to site?
  • Identifies consistent configurations for profile re-use.
Are there departments that support multiple extensions?
  • Identifies the use of departmental extension pooling.
Are all Departments available to all users?
  • Identifies the requirements for roles.
  • May identify the use of hidden departments.
  • Establishes the hierarchy of departments for management and associates.
Are there unique configuration elements for any department?
  • Some departments may require different ringtones or other operational attributes.
Extensions
Extensions are defined and associated with a specific department. Each extension defines a specific extension in the PBX. The extensions can be bound one-to-one to the PBX or pooled for a department.
Do the extensions have identifiable and meaningful names?
  • Users may identify an extension name more easily than a number.
Which extensions belong to which defined department?
  • Ranges of extensions may be assigned to specific departments to improve the user experience.
  • Some departments may have only one extension, and there is no reason to prompt the user for the extension.
How does the extension identify itself to the PBX?
  • Pseudo or physical MAC address?
    • Information needed to complete the extension definition.
    • Standard Cisco implementation.
  • SIP ID and password
    • Information needed to complete the extension definition.
    • Non-Cisco implementation.
Are any extensions used for one specific purpose or user?
  • Identifies the use of a reserved extension or hidden department.
Do all extensions connect to the same PBX?
  • Determines the PBX definition for the specific extension.
  • Reveals a hybrid solution requiring different services.
Do any extensions connect to multiple PBXs?
  • Needed if there are multiple paths to route the call.
Are there unique configuration elements for any Extension?
  • Useful for identifying the role of users.
  • Some users may have a Night Forward button or other functionality not found in other extensions.