Getting started with the 8378 DECT IP-xBS solution
on OXO
8AL90357ENAAed01
36
/
37
AIR SYNCHRONIZATION:
See more details in doc[2]
Why the sync master change from one base to another one?
With automatic air synchronization, it is the 8378 DECT IP-xBS sub-system which
selects the best 8378 DECT IP-xBS acting as the Sync Master. So, it is normal that
the Sync Master can change.
How to stabilize an unstable air synchronization tree? How can I detect unstable air sync
tree?
Unstable air synchronization is due to unstable radio environment and due to a bad
deployment. The position of the 8378 DECT IP-xBS must be set to always have a
stable radio environment (i.e. a door which when close break the synchronization
link). Unstable air synchronization can be detected looking the number of Sync
Master, looking the synchronization tree and associated RSSI level and looking the
statistics. See doc[2] for more details.
How often a stable air sync changes its sync tree?
It is not abnormal that a synchronization tree changes ten times a day.
How much time the air synchronization will take to stabilize during initial startup?
It takes about 10min to build the first tree
How much time needs a tree to be reconfigured in case of modification of the environment?
The tree is reevaluated every 15 min.
Are the key synchronization components redundant?
Yes, natively as the synchronization is automatic.
FIRMWARE UDATE:
Can I upgrade the handset firmware by air on a xBS infrastructure?
No
Where do I find the xBS firmware? On the Business Portal?
No, it is embedded in the CS releases inside their TFTP server directory.
GEO-LOCATION:
I want to make geo-location using DECT, are the RPN of the xBS always allocated identically?
RPN remains identical between first allocation and any subsequent CS restarts.
