The system date and time for the MCU can be set manually or using the Network Time Protocol (NTP).
To configure Time settings, go to | . |
Note that changing the time or NTP settings will have an effect on the recorded times in the Call Detail Records log. For more information, refer to Working with Call Detail Records.
The current system date and time is displayed.
If you do not have NTP enabled and need to update the system date and/or time manually, type the new values and
click | . |
The MCU supports the NTP protocol. If you are using it, configure the settings as required, and then click 
.
The MCU
If there is a firewall between the MCU and the NTP server, configure the firewall to allow NTP traffic to UDP port 123.
If the NTP server is local to Port A or Port B then the MCU will automatically use the appropriate port to communicate with the NTP server. If the NTP server is not local, the MCU will use the port that is configured as the default gateway to communicate with the NTP server, unless a specific IP route to the NTP server's network/IP
| address is specified. To configure the default gateway or an IP route, go to | . |
| ||
|
|
|
|
|
|
|
|
|
|
|
|
|
| If selected, use of the NTP protocol is Enabled on |
|
|
|
|
| the MCU. |
|
|
|
|
|
|
|
| |
|
| The offset of the time zone that you are in from | You must update the offset manually when the |
| |
|
| Greenwich Mean Time. | clocks go backwards or forwards: the MCU does |
| |
|
|
| not adjust for daylight saving automatically. |
| |
The IP address or hostname of the server that is acting as the time keeper for the network.
If NAT is used between the MCU and the NTP server, with the MCU on the NAT's local network (and not the NTP server), no extra configuration is required.
If NAT is used between the MCU and the NTP server, with the NTP server on the NAT's local network, then configure the NAT forwarding table to forward all data to UDP port 123 to the NTP server.
150
