IP phones Protocol error incident

[abhishekawasthi_12]

Hi ,
I am getting the protocol error incident as follows:-

22/05/12 14:54:37 000001M|---/--/-/---|=0:1612=Protocol error on Alcatel 8&9 ser
ies, type 18 (neqt 5159)
22/05/12 14:54:37 000001M|---/--/-/---|=3:1613=15.04.12.00.06.06.82.12.10.ff.00.
00.00.00.00
22/05/12 14:54:37 000001M|---/--/-/---|=0:1612=Protocol error on Alcatel 8&9 ser
ies, type 18 (neqt 5159)
22/05/12 14:54:37 000001M|---/--/-/---|=3:1613=15.04.12.00.06.06.82.12.10.ff.00.
00.00.00.00
22/05/12 14:54:37 000001M|---/--/-/---|=0:1612=Protocol error on Alcatel 8&9 ser
ies, type 11 (neqt 5159)

(1)bnp_bank> incinfo GEA 1612

INCIDENT NUMBER: 1612
Network indicator: Alcatel 4400
OBJECT CLASS: Dhs3x_node
EVENT TYPE: ProcessingErrorAlarm (10)
PROBABLE CAUSE: Unknown (0)
SEVERITY: Indeterminate

"Protocol error on Alcatel 8&9 series, type P1 (neqt P2)"
"P1 : error type"
" -11: Error on create operation"
" -12: Error on delete operation"
" -13: Error on set property operation"
" -14: Error on get property operation "
" -18: Error on insert item operation"
" -19: Error on delete item operation"
" -29: Warning on create operation"
" -30: Warning on set property operation"
"P2 : equipment number of extension"
" -11: Error on create operation"
" -12: Error on delete operation"
" -13: Error on set property operation"
" -14: Error on get property operation "
" -18: Error on insert item operation"
" -19: Error on delete item operation"
" -29: Warning on create operation"
" -30: Warning on set property operation"
"Incorrect phone message received by 40x8 or 40x9 sets"
"The message is ignored and is displayed on the console, if this one is active"
"(mtracer)."
"no operator action required";

Please suggest what should be done or clarify on the same ..
Thanks ...

[Eliott]

The incident has many different causes.
Some of them are:
-Wrong set type (management doesn't match real phone)
-Wrong firmware (set not flashed with OXE FW version)
-Special scenario not handled correctly by OXE SW (e.g. Agent Logon/-off)

In most cases you can ignore the incident.
It's very complex to analyze is and wastes too much time.
The only way to get a clue is to make trace and analyze them step by step...
Try zdpost d <DN> |grep -i noe
Which OXE Version do you use?