Top

Time Format

The time format (also known as 'TZ' format) is based on the format described by the IEEE 1003.1 standard (i.e. POSIX specification).

The Time Format contains two parts separated by a semicolon:
  • The first part, mandatory, is the system timezone expressed in the IEEE 1003.1 POSIX format (also known as 'TZ' format).
  • The second part, available since 46.0 is optional. It is the timezone used for the time displayed in some of the SBC Web pages (Live Calls, Events, and Registration). This part is only useful for units with the Sbc service. This string must be expressed in the IANA format. If this part is not present, the UTC time zone is used on the SBC Web pages.
The first part of the time format has this POSIX syntax:
STDOFFSET[DST[OFFSET],[START[/TIME],END[/TIME]]]
where:
  • STD / DST: Three or more characters for the standard (STD) or alternative daylight saving time (DST) time zone. Only STD is mandatory. If DST is not supplied, the daylight saving time does not apply. Lower and upper case letters are allowed. All characters are allowed except:
    • digits
    • leading colon (:)
    • comma (,)
    • minus (-)
    • plus (+), and
    • ASCII NUL.
  • OFFSET: Difference between the GMT time and the local time. The offset has the format h[h][:m[m][:s[s]]]. If no offset is supplied for DST, the alternative time is assumed to be one hour ahead of standard time. One or more digits can be used; the value is always interpreted as a decimal number.
    • The hour value must be between 0 and 24.
      IMPORTANT: If preceded by a minus sign (-), the time zone is east of the prime meridian, otherwise it is west, which can be indicated by the preceding plus sign (+). For example, New York time is GMT 5.
    • The minute and second values, if present, must be between 0 and 59.
  • START / END Indicates when to change to and return from the daylight saving time. The START argument is the date when the change from the standard to the daylight save time occurs; END is the date for changing back. If START and END are not specified, the default is the US Daylight saving time start and end dates. The format for start and end must be one of the following:
    • n where n is the number of days since the start of the year from 0 to 365. It must contain the leap year day if the current year is a leap year. With this format, you are responsible to determine all the leap year details.
    • Jn where n is the Julian day number of the year from 1 to 365. Leap days are not counted. That is, in all years – including leap years – February 28 is day 59 and March 1 is day 60. It is impossible to refer to the occasional February 29 explicitly. The TIME parameter has the same format as OFFSET but there can be no leading minus (-) or plus (+) sign. If TIME is not specified, the default is 02:00:00.
    • Mx[x].y.z where x is the month, y is a week count (in which the z day exists) and z is the day of the week starting at 0 (Sunday). For instance: M10.4.0 is the fourth Sunday of October. It does not matter if the Sunday is in the 4th or 5th week. M10.5.0 is the last Sunday of October (5 indicates the last z day). It does not matter if the Sunday is in the 4th or 5th week. M10.1.6 is the first week with a Saturday (thus the first Saturday). It does not matter if the Saturday is in the first or second week. The TIME parameter has the same format as OFFSET but there can be no leading minus (-) or plus (+) sign. If TIME is not specified, the default is 02:00:00.
More information on time zones are available at:
Top

Time Format Examples



Time Zone String IANA format (Optional, 46.0+)
Atlantic Time (Canada) AST4ADT,M3.2.0,M11.1.0 America/Halifax
Australia Eastern Standard Time AEST-10AEDT,M10.1.0,M4.1.0/3 Australia/Sydney
Central European Time CET-1CEST,M3.5.0,M10.5.0/3 Europe/Brussels
Central Time (Canada & US) CST6CDT,M3.2.0,M11.1.0 America/Chicago
China Standard Time CST-8 Asia/Shanghai
Eastern Time Canada & US) EST5EDT,M3.2.0,M11.1.0 America/Toronto
Greenwich Mean Time GMT0BST,M3.5.0/1,M10.5.0 Europe/London
Mountain Time (Canada & US) MST7MDT,M3.2.0,M11.1.0 America/Denver
Pacific Time (Canada & US) PST8PDT,M3.2.0,M11.1.0 America/Los_Angeles
Japan Standard Time JST-9 Asia/Tokyo
UTC (Coordinated Universal Time) UTC0 Etc/UTC
Western Europe Time WET0WEST,M3.5.0/1,M10.5.0 Europe/Lisbon
Top

Examples of Allowed Time Format Combinations

Time Format Example
Timezones with both the TZ and IANA strings (46.0+) EST5EDT,M3.2.0,M11.1.0;America/Toronto
UTC5;America/Lima
Only first part present (all DGW versions) CST6CDT,M4.1.0,M10.5.0
Top

Selecting the Unit's Time Zone

Context
Time Servers should be configured under Network/Host/SNTP Configuration. For more details refer to the DGW Configuration Guide - VLan Configuration published on the Media5 Documentation Portal.
Steps
  1. Go to Network/Host.
  2. In the Time Configuration table, in the Static Time Zone field, specify the time zone in which the Mediatrix unit is located.
    Note: If preceded by a minus sign (-), the time zone is east of the prime meridian, otherwise it is west, which can be indicated by the preceding plus sign (+). For example, New York time is GMT 5.
  3. Click Apply.
Result

Any DGW parameter referring to a time value will use the local time described by this time zone reference. The Hoc.SystemTime will return the unit local time in accordance with the configured time zone.

Top

Online Help

If you are not familiar with the meaning of the fields and buttons, click Show Help, located at the upper right corner of the Web page. When activated, the fields and buttons that offer online help will change to green and if you hover over them, the description will bedisplayed.

Top

DGW Documentation

Mediatrix devices are supplied with an exhaustive set of documentation.

Mediatrix user documentation is available on the Media5 Documentation Portal.

Several types of documents were created to clearly present the information you are looking for. Our documentation includes:
  • Release notes: Generated at each GA release, this document includes the known and solved issues of the software. It also outlines the changes and the new features the release includes.
  • Configuration notes: These documents are created to facilitate the configuration of a specific use case. They address a configuration aspect we consider that most users will need to perform. However, in some cases, a configuration note is created after receiving a question from a customer. They provide standard step-by-step procedures detailing the values of the parameters to use. They provide a means of validation and present some conceptual information. The configuration notes are specifically created to guide the user through an aspect of the configuration.
  • Technical bulletins: These documents are created to facilitate the configuration of a specific technical action, such as performing a firmware upgrade.
  • Hardware installation guide: They provide the detailed procedure on how to safely and adequately install the unit. It provides information on card installation, cable connections, and how to access for the first time the Management interface.
  • User guide: The user guide explains how to customise to your needs the configuration of the unit. Although this document is task oriented, it provides conceptual information to help the user understand the purpose and impact of each task. The User Guide will provide information such as where and how TR-069 can be configured in the Management Interface, how to set firewalls, or how to use the CLI to configure parameters that are not available in the Management Interface.
  • Reference guide: This exhaustive document has been created for advanced users. It includes a description of all the parameters used by all the services of the Mediatrix units. You will find, for example, scripts to configure a specific parameter, notification messages sent by a service, or an action description used to create Rulesets. This document includes reference information such as a dictionary, and it does not include any step-by-step procedures.
Top

Copyright Notice

Copyright © 2023 Media5 Corporation.

This document contains information that is proprietary to Media5 Corporation.

Media5 Corporation reserves all rights to this document as well as to the Intellectual Property of the document and the technology and know-how that it includes and represents.

This publication cannot be reproduced, neither in whole nor in part, in any form whatsoever, without written prior approval by Media5 Corporation.

Media5 Corporation reserves the right to revise this publication and make changes at any time and without the obligation to notify any person and/or entity of such revisions and/or changes.