The codec will only receive time from NTP, otherwise it will use it's local internal clock which will eventually be incorrect.
If the codec is setup to use DHCP to obtain an IP address, it will ask the DHCP server what NTP serer to use, typically a domain controller on your network can provide the time.
If the codec is setup to use a static IP address, then the codec will use the manually entered NTP server in the codec's configuration, by default it is setup to resolve to an old TANBDERG NTP. It's recommended that this be changed to an NTP server of your choice, you can use a domain controller if your environment has any, or any known reachable NTP server.
We are facing jitter issue in our video call, jitter is normally relates to a timing/clock source, in this instance if a call is happening between A and B we can conclude that Master clock will be source and slave clock will be destination.
We want to track down what timing/clock source is followed by video codec (mostly C20, SX 20 codecs) when call is running.
For NTP we have changed all NTP settings in device and those are pointed to our NTP server, this works fine.
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...
If you have 2 ISR routers, one acting as Failover, do we need to have both the same number of SRST licenses on the 2 routers?
No. You will only need the SRST licenses on the primary router. Because this feature...