Page 1 of 1

dect shell not becoming empty anytime after dect set switched off

Posted: 06 Apr 2010 12:18
by knightrider
Hi gang,

Can anyone tell me if this is normal behaviour?

I have 2 nodes running h130125a and dect in network is working fine.

When a node A dect user visits node B and switches on his dect, all is good and he can use his dect set. But when he switches off his dect, the shell still seems occupied forever and can only be released by a 'dectclean mcdu' command at node A.

The reason this is a problem is because after the user swicthes off his set, the sysadmin wants to jump on to mgr and divert his set (in node A) to any number he wants. After the management, nothing changes and the call still routes to the shell at Node B.

Hope this makes some sense and thanks in advance for any assistance :)

Posted: 07 Apr 2010 00:28
by vad
User from node A visits node B, registered in shell. Shel will be released when user swith on his dect at home (node A).
For calls diversion - before set switch off - dial "forward + destination" 8-)
Or go to mgr and declare diversion on node B (for occupated shell)

Posted: 08 Apr 2010 09:01
by knightrider
hey thanks VAD.

Problem with this is that the customer said this never used to happen in R4. Back in those days, as soon as visitor to Node B switched off his dect, then shell would release straight away.

Apparently Alcatel have confirmed that this was true but since that release it operates differently now (like you say) and ALU say that to revert the code will cost tooooo much money!

And how is customer supposed to establish which occupied shell to divert?!?