Incident 1612 & 1613 (NOE protocol error)

[knightr1der]

The same incidents happen here.
This customers has blade server for CS so all hardware is on IP.
In this case the error only occur on common hardware (MG).
Sets behind crystal hardware don't have the problem.

29/06/07 11:31:39 000001M|--/--/-/---|=0:1612=Protocol error on Alcatel 8&9 series, type 13 (neqt 4531)
29/06/07 11:31:39 000001M|--/--/-/---|=3:1613=15.04.0d.00.02.02.95.15.00.ff.00.00.00.00.00
29/06/07 11:32:03 000001M|--/--/-/---|=0:1612=Protocol error on Alcatel 8&9 series, type 13 (neqt 3977)
29/06/07 11:32:03 000001M|--/--/-/---|=3:1613=15.04.0d.00.02.02.95.15.00.ff.00.00.00.00.00
29/06/07 11:32:16 000001M|--/--/-/---|=0:1612=Protocol error on Alcatel 8&9 series, type 13 (neqt 3977)
29/06/07 11:32:16 000001M|--/--/-/---|=3:1613=15.04.0d.00.02.02.95.15.00.ff.00.00.00.00.00
29/06/07 11:32:22 000001M|--/--/-/---|=0:1612=Protocol error on Alcatel 8&9 series, type 13 (neqt 3977)
29/06/07 11:32:22 000001M|--/--/-/---|=3:1613=15.04.0d.00.02.02.95.15.00.ff.00.00.00.00.00
29/06/07 11:32:25 000001M|--/--/-/---|=0:1612=Protocol error on Alcatel 8&9 series, type 13 (neqt 3977)
29/06/07 11:32:25 000001M|--/--/-/---|=3:1613=15.04.0d.00.02.02.95.15.00.ff.00.00.00.00.00
29/06/07 11:33:10 000001M|--/--/-/---|=0:1612=Protocol error on Alcatel 8&9 series, type 13 (neqt 4533)
29/06/07 11:33:10 000001M|--/--/-/---|=3:1613=15.04.0d.00.02.02.94.15.00.ff.00.00.00.00.00
29/06/07 11:33:19 000001M|--/--/-/---|=0:1612=Protocol error on Alcatel 8&9 series, type 13 (neqt 4533)
29/06/07 11:33:19 000001M|--/--/-/---|=3:1613=15.04.0d.00.02.02.94.15.00.ff.00.00.00.00.00

No one else have any idea ?
I think I will have to go for an SR.

I forgot : It's an OXE release f5401.17c

luckyme2, your error log identifies specifically 3 sets with the neqt's shown. Are they the right type plugged in compared to management? do they appear in the 'downstat t' menu as sets waiting to be dowloaded?

[Eliott_DUP]

luckyme2, your error log identifies specifically 3 sets

and
tradeq 4531
tradeq 3977
tradeq 4533
tells you, which sets.

[knightr1der]

luckyme2, your error log identifies specifically 3 sets

and
tradeq 4531
tradeq 3977
tradeq 4533
tells you, which sets.

Anything Eliott types is like sweet music

[luckyme2]

Your error log identifies specifically 3 sets with the neqt's shown. Is that part of a list or only those ones ?
It is a part of a list ...
Are they the right type plugged in compared to management?
Yes and confirmed - Type 4029

Do they appear in the 'downstat t' menu as sets waiting to be dowloaded?
IPTOUCH TDM phone downloaded informations :
-------------------------------------
1 Display up to date IPTOUCH TDM phones
2 Display IPTOUCH TDM phones not yet updated
3 Display download in progress
4 Display out of order IPTOUCH TDM phones
5 Display all IPTOUCH TDM phones
0 Quit

Your choice ? 1

| IPTOUCH TDM with up to date version
+------+----------+-------+-------+-----------------+--------+--------------+--------
-----------+------------+
| Index| QMCDU | Neqt | Nulog | Name | Type | Dw Policy | Custo
| Local |
+------+----------+-------+-------+-----------------+--------+--------------+--------
-----------+------------+
| 0001 | 16912 | 05326 | 00059 | FABERT Coralie | IPTOUCH| DELAYED |
...................
all other the same....

Your choice ? 2

No IPTOUCH TDM to be updated with download policy ON DEMAND
No IPTOUCH TDM to be updated with download policy ASAP


Thanks !!

[Eliott_DUP]

Anything Eliott types is like sweet music

The reverese command to tradeq <neqt> is tradna <Directory number>

PS: Virtual neqts are listed with the neqt_log command.
And auxillaries with tab__aux and timers with tabtemp and played vg's with vgemis and so on

[ToniMati]

Hi,

I have the same incidents, it happens when I try to do any operation with a serie 9 terminal. The incident doesn’t worries me to much. But the problem is that when you perform a search by name on a 4035 it find’s for example 15 users. Then if you made the same search on a 4039 it only finds 12 (less instances than on the 4035).

The PBX is on Cristal HW, version g1.302 6h, the users are on a UA32.
I checked the downstat and it’s OK. Some body can tell me if it is problem of the version? Or how can I solve it.

06/05/09 16:22:24 000001M|---/--/-/---|=3:1613=15.04.0d.00.02.02.84.10.21.ff.00.
00.00.00.00
06/05/09 16:22:24 000001M|---/--/-/---|=0:1612=Erreur protocolaire poste Alcatel
sÚries 8&9 , type 13 (neqt 1779)
06/05/09 16:22:24 000001M|---/--/-/---|=3:1613=15.04.0d.00.02.02.84.10.24.ff.00.
00.00.00.00
06/05/09 16:22:24 000001M|---/--/-/---|=0:1612=Erreur protocolaire poste Alcatel
sÚries 8&9 , type 13 (neqt 1779)
06/05/09 16:22:24 000001M|---/--/-/---|=3:1613=15.04.0d.00.02.02.84.10.25.ff.00.
00.00.00.00
06/05/09 16:22:24 000001M|---/--/-/---|=0:1612=Erreur protocolaire poste Alcatel
sÚries 8&9 , type 13 (neqt 1779)
06/05/09 16:22:24 000001M|---/--/-/---|=3:1613=15.04.0d.00.02.02.8f.10.41.ff.00.
00.00.00.00
06/05/09 16:22:24 000001M|---/--/-/---|=0:1612=Erreur protocolaire poste Alcatel
sÚries 8&9 , type 13 (neqt 1779)
06/05/09 16:22:24 000001M|---/--/-/---|=3:1613=15.04.0d.00.02.02.88.10.30.ff.00.
00.00.00.00
06/05/09 16:22:24 000001M|---/--/-/---|=0:1612=Erreur protocolaire poste Alcatel
sÚries 8&9 , type 11 (neqt 1779)
06/05/09 16:22:24 000001M|---/--/-/---|=3:1613=15.04.0b.00.00.00.82.20.80.ff.00.
00.00.00.00