11.6 |
Planning Notes for Networked HiPath 3000 Systems Featuring Network-Wide Roaming |
| The demand for additional B channels for fixed connection paths (CorNet-NQ) must be taken into account for the system-wide extension connections described in Section 11.5 "Multi-SLC and System-Wide Networking". |
| The demand for additional B channels for fixed connection paths (CorNet NQ) must be taken into account for the system-wide extension connections described in Section 11.5 "Multi-SLC and System-Wide Networking". |
| If the "Network-wide roaming" feature is used, please ensure that there is no overlapping in the radio areas of individual systems with identical DECT IDs. Handsets treat networked systems with identical DECT IDs as a single system. |
| If the radio areas of systems with identical DECT IDs overlap, mobile telephones inadvertently try to perform network wide handover, which results in communication breakdown. |
| If networking is required for systems in which the individual radio fields overlap (for example, to increase capacity limits or through decentralized installation), different DECT IDs must be configured in the individual systems. Network-wide roaming does not apply in this case. |
| The following describes three different scenarios for networked HiPath 3000 systems. |
Scenario 1: Incorrect DECT Configuration of Networked HiPath 3000 Systems |
| Identical DECT IDs and overlapping radio areas result in incorrect handover causing a breakdown in communication. |
Scenario 2: Correct DECT Configuration when Networking HiPath 3000 Systems |
| No incorrect handover due to identical DECT IDs despite overlapping radio areas. Disadvantage: network-wide roaming not possible. |
Scenario 3: Correct DECT Configuration when Networking HiPath 3000 Systems |
| No incorrect handover despite identical DECT IDs as the radio areas do not overlap. Network-wide roaming possible. |
| HiPath 3000/5000 V8, Service Documentation, Issue 10 | up  |
|
 |
||
| Disclaimer & Copyright | ID: P31003H3580S100017620 | 2011-01-24 |
