Hi All
We have upgraded some customer to MX-ONE, where the customer wanted to add several elder MD110 systems with ELU31 DECT (SARI/PARI) to their new MX-ONE.
The idea was to use the AUTPAR in CXAKI commands to the new MX-ONE system, but this was not possible, since the IPEI does not exist in the MD110.
Anyway it does exist in the MX-ONE, so the sites with MX-ONE did not give us extra work.
Conclusion is that AUTPAR can only be used with the same SARI/PARI license in the system.
The DIR used in CXAKI:AUTPAR must match the DIR in CXAKP:AUTDET.
The SARI used in CXSYI must match SARI used when CXAKI:IPEI was made.
So if you add MD110 systems with ELU-31 DECT, yu must read all IPEI codes from all handsets - and re-send all CXAKI commands.
MDSH> cxakp:dir=1136,autdet=yes;
CORDLESS EXTENSION AUTHENTICATION KEY DATA
DIR CUST AUTPAR
2236 8 EF7855348E91183EAC1E746B8C3429059558C44DAD45D789
END
///doktor
____________________________________
We have upgraded some customer to MX-ONE, where the customer wanted to add several elder MD110 systems with ELU31 DECT (SARI/PARI) to their new MX-ONE.
The idea was to use the AUTPAR in CXAKI commands to the new MX-ONE system, but this was not possible, since the IPEI does not exist in the MD110.
Anyway it does exist in the MX-ONE, so the sites with MX-ONE did not give us extra work.
Conclusion is that AUTPAR can only be used with the same SARI/PARI license in the system.
The DIR used in CXAKI:AUTPAR must match the DIR in CXAKP:AUTDET.
The SARI used in CXSYI must match SARI used when CXAKI:IPEI was made.
So if you add MD110 systems with ELU-31 DECT, yu must read all IPEI codes from all handsets - and re-send all CXAKI commands.
MDSH> cxakp:dir=1136,autdet=yes;
CORDLESS EXTENSION AUTHENTICATION KEY DATA
DIR CUST AUTPAR
2236 8 EF7855348E91183EAC1E746B8C3429059558C44DAD45D789
END
///doktor
____________________________________