Alcatel Unleashed

Hi Alcatel-DECT-Experts!

what we have:
+ several OmniPCX in crystal-technique
+ about 1100 DECT-BTS (4070) as RBS
+ the DECT-network is structured in multiple PARIs and 4 areas per PARI

what we don't have
+ working handover for GAP-handsets

tested:
. 1. walking with Alcatel mobile 200 registered as GAP+ handset
. a.) within a building with very dense BTSe (one every 20 m)
. b.) within a building with normal coverage (one BTS every ~ 50 m)
. result for both: handover no Problem

. 2. walking with a Siemens SL1 (or Ascom or Philips) registered as GAP handset
. a.) as before
. b.) as before
. result for both: handover does not work. calls get interrupted when
. leaving the zone of coverage of one BTS. Abour 1 sec later the
. phone rings and the call comes back.
. Same game for almost every BTS.

what we would like to have:
+ working handover for all GAP-handsets

what we need:
+ an advise, what when wrong in configuration
- or does seamless handover not work at alle for GAP handsets in Alcatel OmniPCX crystal-environments?

ciao, Markus


Moved by tot3nkopf

As I uderstand - we say about handover (not about roaming).
If you have different PARI - you must use PLI depends of your PARI - 27, 24 (not 31).
When you make registration - check what PLI value will be suggested by PBX. You can have next problem:
you manage different PARI;
you manage PLI f.e. 27.
During registration you can see - PBX show that this set will be registered with PLI 31 (and work only with one PARI).
What you can do - if you have OPS lock roaming - manage in DECT set parameters Network mobility rights=true before registration (and remove after);
or use "dectinston" command with options -pli [your PLI value].

Hi vad!

We need a PLI of 26 here. And "network mobility right" is on.
After registration PLI of the GAP handsets is 26. => ok

in meantime we made some more tests and found out:

handover for Siemens XX GAP handsets work when
performing handover von BTS to BTS on DIFFERENT DECT-boards.

handover doesn't work when both BTS are on the same board.

weird, isn't it?

But we found out another thing: with a Plantronics DECT-headset
in GAP-mode handover worked in any cases without problems.

So it is possible, that this is not a config problem on our OmniPCX
but a Firmware-Problem of Siemens-handsets.

To verify this we would appreciate, if someone with RBS-DECT-environment
a Siemens-handset could tell, if on his network handover shows the
same behaviour as in our!

I know similar problems but can't explain it.

I assume External handover flag and DTM syncro in RBS system is set,
infocs and dectinfo 3 looks okay and the INTOF ICS versions (see TC0274) are compatible.

What does dectobs + <directorynumber> tells you? (dectobs - <directorynumber> to stop)
What does trcterm d <directorynumber> shows you? (trcterm stop to stop)