TzUtil - PABX.INI

TzUtil - PABX.INI file settings

The are the settings that can also be found in the PABX.INI 2.12 reference manual.

The setting outside the time zone section can be ignored.

[Time Zone Section]

The MonTel 32 bit Client needs to have both the same local time, and the same Time zone settings at the Server, since the Server stores call record start and end times in GMT (or UTC).

To make sure that the Time Zone settings are the same for both the server and the local machine, MonTel by default checks the local machines time zone against the PABX.INI settings and prompts the user to adjust it if it is not exactly the same.

For more information see: How can I stop the new 32bit client from changing the Time Zone settings on my computer.

To test the settings use TZUtil.

See Also How TZUtil (MonTel Time Zone Adjust) works

In this section TimeZoneDisplay TZStandardName TZDaylightName TZStandardGMTModifyMins TZDaylightStartDateTime TZDaylightEndDateTime TZDaylightSTDModifyMins ConfirmTimeZoneMatchesOS SetUserFeedbackLevel ShowWindowsTimeZoneInfo

TimeZoneDisplay

Used by: Client, Server.

Version 2.12.1 onwards

Max length: 128 characters

Example:

TimeZoneDisplay = "MonTel Adjusted Perth"

This is the display name of the time zone, as shown in "Date/Time Properties" control panel applet or when double clicking on the clock in the system notification area. The "(GMT +1:hours)" part of the name is not included in this setting an if MonTel needs to write the name to the registry is calculated from the time zone information.

This setting is a concatenation of the old CapitalCity and TimeZoneName settings from version 2.11.x into the much more sensible TimeZoneDisplay, which matches name in the time zone settings of the Windows Registry.

TZStandardName

Used by: Client, Server.

Max length: 33 characters

Example:

TZStandardName = ""

The Standard Time Zone name, truncated to 31 characters, e.g. "(AUS) Eastern Standard Time"

TZDaylightName

Used by: Client, Server.

Max length: 33 characters

Example:

TZDaylightName = ""

The Daylight Time Zone name, truncated to 31 characters, e.g. "(AUS) Eastern Daylight Time"

TZStandardGMTModifyMins

Used by: Client, Server.

Max length: 33 characters

Example:

TZStandardGMTModifyMins = 600

Number of Minutes added or subtracted from local time to equal GMT. (ie -480 for Western, -570 for Central, -600 for Eastern)

TZDaylightStartDateTime

Used by: Client, Server.

Max length: 33 characters

Version 2.12.1 format change

Example:

TZDaylightStartDateTime = "Second Sun in Mar at 02:00:00"

This is the date and time of the start of the next or current daylight savings period. See also TZDaylightName, TZDaylightEndDateTime, TZDaylightSTDModifyMins.

From Version 2.12.1 there are two formats (and an old one removed): 'Absolute format' with date and time string, in a modified ISO8601 format, and 'Day-in-month' format, with the old Australian date format no longer allowed (see below).

'Day-in-month format'

The 'Day-in-month format' is the most typical format for a daylight saving start or end date. It follows the following formula: {Ordinal-Adjective} {day-of-week} in {month} at HH:MM:SS. Where {Ordinal-Adjective} is one of First, Second, Third, Fourth or Last; {day-of-week} is a three letter abbreviation for the day of the week; and {month} is a three letter abbreviation for the month.

Specifically the months 1 through 12 are: "Jan", "Feb", "Mar", "Apr", "May", "Jun", "Jul", "Aug", "Sep", "Oct", "Nov", "Dec"; and the day-of-week 0 through 6 are: "Sun", "Mon", "Tue", "Wed", "Thu", "Fri", "Sat".

Some examples would be "Second Sun in Mar at 02:00:00", "Last Sun in Oct at 02:00:00", or "First Sun in Oct at 02:00:00".

'Absolute format'

TZDaylightStartDateTime = "2008-03-09 02:00:00"

The alternative 'Absolute format' is the 'space' version of the ISO8601 ("YYYY-MM-DDThh:mm:ss"), replacing the 'T' with a space. However, the 'T" can still be included for this setting instead of a space. The example above, "2008-03-31 02:00:00", corresponds to March 31, 2008 at 2:00 AM.

This is rarely used but might be required when an exact date is specified or such as when time zone days are changed from year to year and it is not correct to refer to a day in a month.

Version 2.12.0 and earlier including all version 2.11.x

Prior to version 2.12.1 the format was an Australian date formatted to match: "hh:mm:ss DD/MM/YY".

TZDaylightStartDateTime = "02:00:00 27/08/00"

Date and time of start of the next or current daylight savings period.

The time and Date must be in this format or not present. The one exception is that leaving off the year, montel will assume the current year. e.g..

TZDaylightStartDateTime = "02:00:00 31/10"

The date for both TZDaylightStartDateTime and TZDaylightEndDateTime must be in the same year. MonTel will automatically adjust this to the equivalent day (not date) in the current year.

If no date and time is specified it will default to the first Sunday in October at 2:00 AM.

TZDaylightEndDateTime

Used by: Client, Server.

Max length: 13 characters

Version 2.12.1 format change

Example:

TZDaylightEndDateTime = "First Sun in Nov at 02:00:00"

This is the date and time of the end of the next or current daylight savings period.. See also TZDaylightName, TZDaylightStartDateTime, TZDaylightSTDModifyMins.

From Version 2.12.1 there are two formats (and an old one removed): 'Absolute format' with date and time string, in a modified ISO8601 format, and 'Day-in-month' format, with the old Australian date format no longer allowed (see below).

'Day-in-month format'

The 'Day-in-month format' is the most typical format for a daylight saving start or end date. It follows the following formula: {Ordinal-Adjective} {day-of-week} in {month} at HH:MM:SS. Where {Ordinal-Adjective} is one of First, Second, Third, Fourth or Last; {day-of-week} is a three letter abbreviation for the day of the week; and {month} is a three letter abbreviation for the month.

Specifically the months 1 through 12 are: "Jan", "Feb", "Mar", "Apr", "May", "Jun", "Jul", "Aug", "Sep", "Oct", "Nov", "Dec"; and the day-of-week 0 through 6 are: "Sun", "Mon", "Tue", "Wed", "Thu", "Fri", "Sat".

Some examples would be First Sun in Nov at 02:00:00", "Last Sun in March at 03:00:00", or "First Sun in April at 03:00:00".

'Absolute format'

TZDaylightEndDateTime = "2008-11-02 02:00:00"

The alternative 'Absolute format' is the 'space' version of the ISO8601 ("YYYY-MM-DDThh:mm:ss"), replacing the 'T' with a space. However, the 'T" can still be included for this setting instead of a space. The example above, "2008-11-02 02:00:00", corresponds to November 2, 2008 at 2:00 AM.

This is rarely used but might be required when an exact date is specified or such as when time zone days are changed from year to year and it is not correct to refer to a day in a month.

Version 2.12.0 and earlier including all version 2.11.x

Prior to version 2.12.1 the format was an Australian date formatted to match: "hh:mm:ss DD/MM/YY".

TZDaylightEndDateTime = "02:00:00 27/08/00"

Date and time of start of the next or current daylight savings period.

The time and Date must be in this format or not present. The one exception is that leaving off the year, montel will assume the current year. e.g..

TZDaylightStartDateTime = "02:00:00 31/10"

The date for both TZDaylightStartDateTime and TZDaylightEndDateTime must be in the same year. MonTel will automatically adjust this to the equivalent day (not date) in the current year.

If no date and time is specified it will default to the first Sunday in October at 2:00 AM.

TZDaylightSTDModifyMins

Used by: Client, Server.

Example:

TZDaylightSTDModifyMins = -60

Number of minutes added or subtracted from the new Daylight Savings to equal normal local time. (0 for none, -60 for others). (At 2am time will be turned forward one hour to read 3am).

ConfirmTimeZoneMatchesOS

Used by: Client, Server.

Version 2.12.1 onwards

Example:

ConfirmTimeZoneMatchesOS = 0;

This setting confirms (by prompting the user with a message) that the time zone settings here match those in the operating system when a MonTel program starts, and may offer the user the opportunity to have their Windows time zone information automatically updated. (TzUtil also needs this setting as well as ShowWindowsTimeZoneInfo to check the time zone information).

If SetUserFeedbackLevel = 0 then the application will AUTOMATICALLY and silently update the local operating system to the time zone settings here. This may actually be a good thing! But using this setting and SetUserFeedbackLevel need to be considered carefully.

It is important that all computers using MonTel, client or server, have the correct time zone settings. Call records have the start time stored as GMT (or UTC) but displayed in local time. (This is among other things to allow for call records to be compared and processed at a head office). If the time zone setting were different then users will see different call record starting times.

The default setting is 0, so if you see call records seem to have the wrong start time, and the local (client) PC's time zone is correct, check both the INI file time zone and the time zone settings on the Server PC. Naturally you should also check that the time is correct and they daylight savings has been taken into account on both systems.

This setting replaces CheckWIN32TimeZone in 2.11.x

SetUserFeedbackLevel

Used by: Client, Server.

Example:

SetUserFeedbackLevel = 3

Used in MonTel32bit client only. The amount of messages or prompts ranges from 4 down to 0. Use 0 if you want no messages, in which case if the time zone (if different) will be changed automatically on the local computer without any user interaction. A setting of 3 is the default (SetUserFeedbackLevel = 3).

ShowWindowsTimeZoneInfo

Used by: TZUtil (only).

Example:

ShowWindowsTimeZoneInfo = 0

When ShowWindowsTimeZoneInfo is set to Zero (it defaults to 1), it prevents the Windows Time Zone Information Dialog box being displayed, so that TZUtil can be used to silently update the Windows time zone information.

While ShowWindowsTimeZoneInfo is a fueature of the freeware TZUtil, it has been added to EdUser32 and EdIni32 so that it can be used as part of MonTel.