DECT Subscription Problem

[megglesfield]

Hi,
Having a problem subscribing DECT handset onto the system (MX-ONE TSW SP7). I have many DECT handsets working,but I cannot add anymore. As a test I deleted a working handsets subscription, then a CXAKE, CXAKI:AUTKEY=,IPEI=, but when I try to resubscribe the handset it always fails. I have no alarms or HIMDP. Also recently rebuilt the system from INL and PCREGEN, but still have the problem. Any ideas.

 

[doktor]

Do you have enough licenses?
Entered the correct IPEI code ? *#06#?


///doktor

http://www.kandu.dk/spg153996.aspx

 

[megglesfield]

Yes Have enough licences


CORDLESS-EXTENSION FAL104454 65535 148
Checked the IPEI many times.

 

[doktor]

Sometimes you need to end both the CXAKE and the GEDIE.
-> and the DECT phone needs a Master Reset.
Try that and let us know your status.

///doktor

http://www.kandu.dk/spg153996.aspx

 

[Satellite1900]

what kind of model is the DECT?

\Satellite1900

 

[megglesfield]

I have tried using CXAKE and GIDIE, not sure how to do a master reset on a DT690. The problem still exists. This is more than one phone, I cannot subscribe any new phones or if I delete the subscription on an existing working phone I cannot resubscribe. This occurs on both the DT690 and DT412.

 

[doktor]

You cannot master reset a DT690.
Did you restart CTLP? or other restarts ?
S/w level of the bases and ELU31?

///doktor

http://www.kandu.dk/spg153996.aspx

 

[Satellite1900]

what operations you perform on the DECT for recording?

\Satellite1900

 

[megglesfield]

Tried an RFPUI on both CTLP and CTLMP, no change, also tried an SFCEI and also even RFEXI, no change. Here are the board and BS revs.

<CNBIP:BPOS=1-1-20;

DEVICE BOARD REVISION INFORMATION
DATE: 16SEP11 TIME: 21:38:08

BPOS BOARD/BRDID PRODUCT NUMBER REVISION STATUS ADD
/IND

001-1-20 ELU31 ROF1375412/3 R1C
CAA 158 0047 R4A EXE
CAA 112 2940 R1F FB
00 BS330-9001/4E1
WORF4 BOOT R4H 6 EXE
WORF4 GAP R4H 3/40 EXE
01 BS330-9001/4E1
WORF4 BOOT R4H 6 EXE
WORF4 GAP R4H 3/40 EXE
02 BS330-9001/4E1
WORF4 BOOT R4H 6 EXE
WORF4 GAP R4H 3/40 EXE
03 BS330-9001/4E1
WORF4 BOOT R4H 6 EXE
WORF4 GAP R4H 3/40 EXE
04 BS340-9001/4E1
WORF4 BOOT R4H 6 EXE
WORF4 GAP R4H 3/40 EXE
05 BS340-9001/4E1
WORF4 BOOT R4H 6 EXE
WORF4 GAP R4H 3/40 EXE
06 BS340-9001/4E1
WORF4 BOOT R4H 6 EXE
WORF4 GAP R4H 3/40 EXE
07 BS330-9001/4H1
WORF5 BOOT R5B 6 EXE
WORF5 GAP R5B 3/40 EXE

END
<

I have recently started logging on all mobility events. I cannot see anything re subscription. Also tried a signal trace, but I could not seen anything obvious.

 

[singhbrindisi]

Dear Martin,

Is the Autkey in system & the one you are entering is similar?
Board revisions seems to be outdated as well.

CAA 158 0047 R4A EXE CAA 112 2940 R1F FB --- Why in FB ??
Did you try to upgrade the board revision without completing the process?

Tomorrow, I will check parameters in my system & put additional thoughts.

Cheers,

""The truth about action must be known and the truth of inaction also must be known; even so the truth about prohibited action must be known. For mysterious are the ways of action""

 

[megglesfield]

Already double checked for silly mistakes like you mention. I am using the latest boards ELU31/3 and they have the latest firmware as per the Aastra Knowledge Base.

Could it be another DECT system and I need to enter the PARK? I have tried in another LIM approx 20Km away and the same problem, so it would be a coincidence if it was. I thought the PARK was the same as the SARI but in decimal or oct instead of Hex, but either comes up with an wrong PARK error.

 

[doktor]

Could it be another DECT system and I need to enter the PARK? ->

Yes. If you have more (and different) DECT systems in the same area, you need to enter the PARK key.
PARK is not the same as SARI.
There exist a EXCEL spreadsheet from Aastra that converts from PARI to PARK, and this is needed if you want to enter the correct PARK code.
Post your PARI and SARI codes, if you want them converted.


///doktor

http://www.kandu.dk/spg153996.aspx

 

[megglesfield]

Doktor,

Thanks for Excel file. However I think it has a problem, at least when related to our SARI. However I work it out manually and when I include my calculated PARK I can register.

I worked out the PARK in the following manner:

SARI = 100403BD

2. Mulitplied the SARI (Hex) by 4
-- 4 x 100403BD = 40100EF4 (Hex)

3. Covert to octal
-- 40100EF4 (Hex) = 10004007364 (Octal, 11digits)

4. Add 31 in front of Octal Value to form
-- 3110004007364

Now Calculate the Checksum

1. Multiply the 1st digit by 1, 2nd digits by 2 and so on. Add the products:
3 x 1 = 3
1 x 2 = 2
1 x 3 = 3
0 x 4 = 0
0 x 5 = 0
0 x 6 = 0
4 x 7 = 28
0 x 8 = 0
0 x 9 = 0
7 x 10 = 70
3 x 11 = 33
6 x 12 = 72
4 x 13 = 52

==================
Total=263 (Dec)
==================

2. Divide by 11
-- 263 / 11 = 23.909090909090909090909090909091

3. Remove the interger
-- 0.909090909090909090909090909091

4. Multiply by 11
-- 0.909090909090909090909090909091 x 11 = 10.

5. This is the checksum = *
(1=1, 2=2, ..... , 9=9, 10=*)

Now the PARK is the result of step 4 + * so PARK = 3110004007364*

In your Excel spreadsheet it wrongly works out the PARK to 311000400736410, The 10 at the end should be interpreted as *.

Now however it is fixed and I can register.

 

[megglesfield]

Doktor,

Worked out a fix to the fault in your spreadsheet as per my previous post. On the DecOct sheet Replace the existing formula in H4 with =IF(MOD(H3,11)=10,K1,MOD(H3,11)) and put an * in K1. You then get the correct PARK output when the checksum=10 from the formula above.

 

[doktor]

Thanks for the update:

When I enter: 100403BD as SARI I get : 311000400736410 as you.
I did forget to tell you about the 10 is a star, since a PARK code has max. 14 digits.


///doktor

http://www.kandu.dk/spg153996.aspx