Strange errors in Incident Logs

Ben S · Post by **Ben S** » 28 Jun 2006 20:15

Hi Guys,

This has been an ongoing issue for a number of months and our current provider doesn't really have an answer for it.

We receive these entries in our Incident logs every few seconds, whilst it doesn't seem to have any sort of negative impact on the system it does fill the logs up making it hard to actually look at any other information as well as that, I don't really like the system erroring like this.

Has anybody seen this before? We've flashed the PAC/MMK but unfortunately this hasn't done anything.

Thanks, Ben

29/06/06 10:05:27 000001M|00/00/0/000|=3:4106x009=Error of protocol (code 80, op_code 0 command 0) (FBC/PAC/MAC)
29/06/06 10:05:27 000001M|00/00/0/000|=3:4106=Error of protocol (code 80, op_code 0 command 0) (FBC/PAC/MAC)
29/06/06 10:05:27 000001M|00/00/0/000|=3:4106=Error of protocol (code 80, op_code 0 command 0) (FBC/PAC/MAC)
29/06/06 10:05:27 000001M|00/00/0/000|=3:4106=Error of protocol (code 80, op_code 0 command 0) (FBC/PAC/MAC)
29/06/06 10:05:27 000001M|00/00/0/000|=3:4106=Error of protocol (code 80, op_code 0 command 0) (FBC/PAC/MAC)
29/06/06 10:05:40 000001M|00/00/0/000|=3:4106x007=Error of protocol (code 80, op_code 0 command 0) (FBC/PAC/MAC)
29/06/06 10:05:40 000001M|00/00/0/000|=3:4106=Error of protocol (code 80, op_code 0 command 0) (FBC/PAC/MAC)
29/06/06 10:05:58 000001M|00/00/0/000|=3:4106=Error of protocol (code 80, op_code 0 command 0) (FBC/PAC/MAC)
29/06/06 10:06:16 000001M|00/00/0/000|=3:4106=Error of protocol (code 80, op_code 0 command 0) (FBC/PAC/MAC)
29/06/06 10:06:34 000001M|00/00/0/000|=3:4106=Error of protocol (code 80, op_code 0 command 0) (FBC/PAC/MAC)
29/06/06 10:06:37 000001M|00/00/0/000|=3:4106=Error of protocol (code 80, op_code 0 command 0) (FBC/PAC/MAC)
29/06/06 10:06:37 000001M|00/00/0/000|=3:4106=Error of protocol (code 80, op_code 0 command 0) (FBC/PAC/MAC)
29/06/06 10:06:52 000001M|00/00/0/000|=3:4106x002=Error of protocol (code 80, op_code 0 command 0) (FBC/PAC/MAC)
29/06/06 10:06:52 000001M|00/00/0/000|=3:4106=Error of protocol (code 80, op_code 0 command 0) (FBC/PAC/MAC)
29/06/06 10:07:10 000001M|00/00/0/000|=3:4106=Error of protocol (code 80, op_code 0 command 0) (FBC/PAC/MAC)
29/06/06 10:08:04 000001M|00/00/0/000|=3:4106x002=Error of protocol (code 80, op_code 0 command 0) (FBC/PAC/MAC)
29/06/06 10:08:04 000001M|00/00/0/000|=3:4106=Error of protocol (code 80, op_code 0 command 0) (FBC/PAC/MAC)
29/06/06 10:08:22 000001M|00/00/0/000|=3:4106=Error of protocol (code 80, op_code 0 command 0) (FBC/PAC/MAC)
29/06/06 10:08:40 000001M|00/00/0/000|=3:4106=Error of protocol (code 80, op_code 0 command 0) (FBC/PAC/MAC)
29/06/06 10:08:58 000001M|00/00/0/000|=3:4106=Error of protocol (code 80, op_code 0 command 0) (FBC/PAC/MAC)

Post by **frank** » 28 Jun 2006 22:28

Does it do it when the operator is in night mode too?

Ben S · Post by **Ben S** » 29 Jun 2006 00:12

frank wrote:Does it do it when the operator is in night mode too?

Hi Frank, Thanks for the reply. I've just put the operator into Night Mode and can confirm that the error does still occur.

Cheers, Ben

Post by **frank** » 29 Jun 2006 09:08

Ok.. Next step.. DIsconnect the cable from the MAP/PAC that goes to the PBX and see if you still have the error

sadim · Post by **sadim** » 29 Jun 2006 13:52

Hi,
If the version of bnvua is 4.1, the you need to upgrade to 4.2 minimum. This binary can be found since patch F1.603.1h

axel_h · Post by **axel_h** » 30 Jun 2006 03:46

What are you using: 4049 or 4059?
Once I had to flash some, Alcatel support strongly recommended to flash it to FRENCE standard and afterwards to the desired country standard by he_dow_tuner.
As for the h patch in R6.0.1: All installation we have on R6 have this software without problems...

sadim · Post by **sadim** » 30 Jun 2006 05:16

Hi,
My answer was based on Alcatel Troubleshooting Guide NÂº 8 Edition 2 page 13:
"4106=Error of protocol (code 80, op_code 0 command 0) (FBC/PAC/MAC)
This incident happens when a 4059 attendant is connected on a UA32 board with a C1Nv
chipset on board (latest UA32, eUA32) and this board is loaded with bnvua 4.1 binary.
To fix this issue, install one of the latest version of bnvua binary with version 4.2 minimum. This binary can be found since patch F1.603.1.h."
Also i already had twice this problem and was solved following this procedure!!!!

Post by **frank** » 30 Jun 2006 08:26

Hi Sadim,

What kind of troubleshoting guides are you talking about ?
Is it something I can find on the Business Partner Web Site ?

Thank you

sadim · Post by **sadim** » 30 Jun 2006 09:17

This doc is a official Alcatel doc. They can be downloaded trought BPWS under Support/Techical Support, if you have rights for it.

Ben S · Post by **Ben S** » 02 Jul 2006 21:10

Thanks for replies. It's a 4059 console. It looks as though we're going to upgrade to release 7 in the very near future so I'll wait and see if that solves the problem (hopefully it does)

Cheers.. Ben