Avaya

Modular Messaging Help

 Getting Started 
 Installation 
 Administration 
 Maintenance 
 Reference 
 
Home > Administration > Administering subscribers > Managing local subscribers > Administering time zone classes-of-service

Administering time zone classes-of-service

The time zone assigned to a subscriber is used by the Telephone User Interfaces (TUIs) and by the Avaya Web Client to adjust times for input by and presentation to subscribers. For more information about multiple time zones, see the Concepts and Planning Guide (pdf).

For some Modular Messaging configurations, some subscribers may reside in a time zone that is different from the time zone in which the Avaya Web Client server that they use to access messages is located. To accommodate subscribers in different time zones, a time zone can be assigned to a subscriber on a class-of-service (COS) basis, or subscribers can change their time zone using Subscriber Options or Web Subscriber Options. For more information about multiple time zones and setting the time zone using Subscriber Options or Web Subscriber Options, see Feature matrix.

For most subscribers, Use System Time zone, which is the default value for every class-of-service, is the appropriate time zone. However, if your Modular Messaging configuration has an Avaya Web Client server that subscribers use to access messages on more than one Message Storage Server (MSS) and the MSSs are not all located in the same time zone, a COS should be set up for each time zone that is different from the system time zone. Then, a COS with the appropriate time zone should be assigned to each subscriber. If a COS is not set up for each time zone that is different from the system time zone, some subscribers who use the Avaya Web Client to access messages will see message times that have not been adjusted correctly for their time zone. For information about editing a class-of-service, see Editing a class-of-service. For information about adding a new subscriber or changing subscriber information, including the class-of-service assigned to a subscriber, see Adding local subscribers and Editing local subscribers.

For example, a Modular Messaging system has an MSS in Denver, CO (MSS-D), an MSS in Chicago, IL (MSS-C), and an Avaya Web Client server in Denver (WC-D) that is used to access messages on both MSS-D and MSS-C. Subscribers in Denver can be assigned COSs that have the default time zone value, because both the MSS and the web client are located in Denver. If subscribers in Chicago were assigned COSs that have the default time zone value, messages accessed using a TUI would be presented in Central time (MSS-C is located in Chicago) and messages accessed using the web client would be presented in Mountain time (WC-D is located in Denver). However, if subscribers in Chicago are assigned COSs that have been set up for the Central time zone, all message times are adjusted to show Central time.

If the number of subscribers who use the Avaya Web Client to access an MSS in a different time zone is small, you could ask those subscribers to change their time zone using Subscriber Options or Web Subscriber Options instead of setting up and assigning COSs with time zones other than the default time zone (Use System Time zone). The time zone specified using Subscriber Options or Web Subscriber Options overrides the time zone specified in a subscriber's COS.

Top of page