Customers typically build additional profiles to create specific configurations from Site to Site, Department to Department, and Extension to Extension. When the Zebra Voice Client retrieves an authorized extension, the configuration for that extension is built using this hierarchical process.
The Root profile is retrieved first.
If a configuration profile is defined for that Site, the Site configuration overlays the Root.
If a configuration profile is defined for the Department of that Site, the Department configuration overlays the Site.
If an Extension has specific configuration parameters, these parameters are added to the configuration.
The final configuration is delivered to the Zebra Voice Client.
Configuration parameters overwrite prior values in the following order: Root, Site, Department, Ext.
The definition of a configuration profile can be quite specific, detailing specific functionality for an extension, such as Button Icons, Night Call Forward services, or many other possibilities. The customer administrator should carefully consider a profile naming convention when multiple Sites, Departments, and Extensions are involved.
Figure 15, Figure 16, and Figure 17 illustrate the logical hierarchical relationships and the sign-in flow where the var_location is:
