128 Avaya 374x DECT Telephones - User Guide 02/2016
Impact for the Users
During speech
If the radio stops to handle traffic as described in Sync Lost Counter on page 127, it does not
necessarily mean a disconnected call. In a system with good overlapping coverage it might be
possible to make a handover to another IPBS without disconnecting the call. If the handset does
not quickly find any other IPBS the call will be disconnected and the handset will indicate “No
System”. As soon as the IPBS is synchronized it is available again for handset communication.
The handset will then connect to the system in the same way as for a normal power on.
In idle mode
In idle mode the user will most likely not discover any problem. Since the handsets have a short
delay before showing “No System” the handset has time to roam to another IPBS. This requires
a good overlap between radio cells to make it possible for the handset to roam to another IPBS.
If no other IPBS is available the handset(s) will indicate “No System”. As soon as the IPBS is
synchronized it is available again for handset communication. The handset will then connect to
the system in the same way as for a normal power on.
DECT Sync
Air Sync Overview
This section only applies to the Master.
To see a graphic presentation of the air synchronization in a system, select DECT Sync > Air
Sync Overview.
The internal synchronization for each region is shown separately by an expandable tree view,
see figure 30
. The green, yellow and red dots in the sync tree show the following sync status for
the Radios:
l Green: Synchronized
l Yellow: Synchronized but poor received signal strength (RSSI < -83 dBm)
l Red: Unsynchronized
The grey dot at top in the sync tree shows that it is a reference sync RFPI.
To Next Page
Loading...
