HiPath Cordless IP - IEEE 1588

The Wiki of Unify contains information on clients and devices, communications systems and unified communications. - Unify GmbH & Co. KG is a Trademark Licensee of Siemens AG.

Revision as of 11:47, 1 March 2011 by Haidar (talk | contribs)
Jump to: navigation, search

HiPath Cordless IP: Synchronisation per Ethernet (regarding IEEE1588)

In difference to the HiPath Cordless IP synchronization over air, the Ethernet based synchronization mechanism (according IEEE1588, PTP Precious Time Protocol) requires fewer configurations.
On the other hand, great demands are made on the Ethernet characteristics like loss, delay, jitter etc. Therefore special requirements regarding the Ethernet components (especially to the Ethernet switches) have to be considered. If these values (especially jitter) are bad Sync loses are likely. Please remember, if a HiPath Cordless IP base station loses the Sync it will not accept any calls and will try to resync.

Basic requirement to the LAN to use Sync over LAN

The HiPath Cordless IP base station which provides the Sync signal is called Sync Master, the HiPath Cordless IP base stations(s) which gets the Sync signal is called Sync Slave in the following. One Sync Master can provide the Sync signal to many (or even all) Sync Slaves.

A maximum number of three cascaded Ethernet switches are supported between the Sync Master and a Sync Slave. This means max. 3 switches (hops) between Sync Master and each Sync Slave (for instance: DECT IP base station with Sync Master -> (1) floor switch -> (2) building switch -> (3) floor switch -> DECT IP base station with Sync Slave)
Only enterprise grade switches are able to support these requirements (tested switches please see below).

The DECT functionality of all DECT IP base station which is configured as Sync Slaves depends on the availability of the Sync Master. If the Sync Master is not functional (e.g. not online because of network problems) the DECT functionality of all Sync Slave BSIP goes down.