Alcatel Unleashed

Hello guys...

Well long story: short some couple of weeks ago calls between the HQ and a branch started to hang at random, and sometimes you only hear them talking but not the other way around. So I called the vendor and the guy came sat here 4 hours and only told me that the problem was because of broadcast... yep charge and did nothing and the problem still persist.

Im the resident netamin and I dont know whack about the OmniPCX, but by reading around here I found about the incvisu command... so heres a piece of the output:


25/10/12 07:59:48 000001M|002/06/0/000|=3:1307=MCDU in distri tab entity 1, col Night , line 4 incorrect or missing
25/10/12 07:59:48 000001M|002/06/0/000|=3:1307=MCDU in distri tab entity 0, col Night , line 4 incorrect or missing
25/10/12 08:04:23 000001M|002/06/0/000|=3:1307=MCDU in distri tab entity 1, col Night , line 4 incorrect or missing
25/10/12 08:04:23 000001M|002/06/0/000|=3:1307=MCDU in distri tab entity 0, col Night , line 4 incorrect or missing
25/10/12 08:05:38 000001M|002/06/0/000|=3:1307=MCDU in distri tab entity 1, col Night , line 4 incorrect or missing
25/10/12 08:05:38 000001M|002/06/0/000|=3:1307=MCDU in distri tab entity 0, col Night , line 4 incorrect or missing
25/10/12 08:05:50 000001M|002/06/0/000|=3:1307=MCDU in distri tab entity 1, col Night , line 4 incorrect or missing
25/10/12 08:05:50 000001M|002/06/0/000|=3:1307=MCDU in distri tab entity 0, col Night , line 4 incorrect or missing
25/10/12 08:06:26 000001M|002/06/0/000|=3:1307=MCDU in distri tab entity 1, col Night , line 4 incorrect or missing
25/10/12 08:06:26 000001M|002/06/0/000|=3:1307=MCDU in distri tab entity 0, col Night , line 4 incorrect or missing
25/10/12 08:06:50 000001M|002/06/0/000|=3:1307=MCDU in distri tab entity 1, col Night , line 4 incorrect or missing
25/10/12 08:06:50 000001M|002/06/0/000|=3:1307=MCDU in distri tab entity 0, col Night , line 4 incorrect or missing
25/10/12 08:07:08 000001M|002/02/0/000|=5:2053=Terminal 0 in service
25/10/12 08:21:33 000001M|000/00/0/000|=4:0426=IPTOUCH terminal reset 33,00:80:9f:b2:e8:78,3753
25/10/12 08:21:34 000001M|001/00/0/035|=5:2053=Terminal 35 in service
25/10/12 08:33:16 000001M|001/00/0/022|=4:0386=Sig. on IP set: No response from de set 00:80:9f:b2:e3:61,8778
25/10/12 08:33:24 000001M|001/00/0/015|=4:0386=Sig. on IP set: No response from de set 00:80:9f:b2:e3:64,8767
25/10/12 08:33:24 000001M|001/00/0/014|=4:0386=Sig. on IP set: No response from de set 00:80:9f:b2:e3:50,8776
25/10/12 08:33:24 000001M|001/00/0/017|=4:0386=Sig. on IP set: No response from de set 00:80:9f:b2:e8:66,8779
25/10/12 08:33:24 000001M|001/00/0/036|=4:0386=Sig. on IP set: No response from de set 00:80:9f:b2:e6:4a,3754
25/10/12 08:33:38 000001M|---/--/-/---|=0:0412=Lost set on IP domain : Domain number 0 pourcent of the set lost 66
25/10/12 08:34:02 000001M|000/00/0/000|=4:0426=IPTOUCH terminal reset 13,00:80:9f:b2:e3:64,8767
25/10/12 08:34:02 000001M|000/00/0/000|=4:0426=IPTOUCH terminal reset 13,00:80:9f:b2:e3:50,8776
25/10/12 08:34:02 000001M|000/00/0/000|=4:0426=IPTOUCH terminal reset 13,00:80:9f:b2:e8:66,8779
25/10/12 08:34:02 000001M|000/00/0/000|=4:0426=IPTOUCH terminal reset 13,00:80:9f:b2:e6:4a,3754
25/10/12 08:34:03 000001M|001/00/0/015|=5:2053=Terminal 15 in service
25/10/12 08:34:03 000001M|001/00/0/014|=5:2053=Terminal 14 in service
25/10/12 08:34:03 000001M|001/00/0/017|=5:2053=Terminal 17 in service
25/10/12 08:34:03 000001M|001/00/0/036|=5:2053=Terminal 36 in service
25/10/12 08:34:04 000001M|000/00/0/000|=4:0426=IPTOUCH terminal reset 13,00:80:9f:b2:e3:61,8778
25/10/12 08:34:05 000001M|001/00/0/022|=5:2053=Terminal 22 in service
25/10/12 08:48:10 000001M|002/02/0/002|=5:2053=Terminal 2 in service
25/10/12 09:01:24 000001M|001/00/0/019|=4:2013=Connection request on unknown link: 20003
25/10/12 09:04:03 000001M|002/02/0/004|=5:2053=Terminal 4 in service
25/10/12 09:05:02 000001M|001/00/0/019|=4:2013=Connection request on unknown link: 20003
25/10/12 09:06:45 000001M|001/00/0/019|=4:2013=Connection request on unknown link: 20003
25/10/12 09:15:31 000001M|001/00/0/019|=4:2013=Connection request on unknown link: 20003
25/10/12 09:35:53 000001M|002/06/0/000|=3:1307=MCDU in distri tab entity 1, col Night , line 4 incorrect or missing
25/10/12 09:36:23 000001M|002/06/0/000|=3:1307x002=MCDU in distri tab entity 1, col Night , line 4 incorrect or missing
25/10/12 09:52:59 000001M|002/06/0/000|=3:1307=MCDU in distri tab entity 1, col Night , line 4 incorrect or missing
25/10/12 09:52:59 000001M|002/06/0/000|=3:1307=MCDU in distri tab entity 0, col Night , line 4 incorrect or missing
25/10/12 10:00:08 000001M|001/00/0/017|=4:0386=Sig. on IP set: No response from de set 00:80:9f:b2:e8:66,8779
25/10/12 10:00:24 000001M|001/00/0/015|=4:0386=Sig. on IP set: No response from de set 00:80:9f:b2:e3:64,8767
25/10/12 10:00:24 000001M|001/00/0/038|=4:0386=Sig. on IP set: No response from de set 00:80:9f:b2:e3:7e,3756
25/10/12 10:00:27 000001M|001/00/0/035|=4:0386=Sig. on IP set: No response from de set 00:80:9f:b2:e8:78,3753
25/10/12 10:01:00 000001M|002/00/-/---|=3:4401=Ethernet broadcast reception disabled due to excessive traffic
25/10/12 10:01:06 000001M|000/00/0/000|=4:0426=IPTOUCH terminal reset 13,00:80:9f:b2:e8:78,3753
25/10/12 10:01:08 000001M|001/00/0/035|=5:2053=Terminal 35 in service
25/10/12 10:01:08 000001M|000/00/0/000|=4:0426=IPTOUCH terminal reset 13,00:80:9f:b2:e8:66,8779
25/10/12 10:01:09 000001M|002/00/-/---|=3:4401=Ethernet broadcast reception disabled due to excessive traffic
25/10/12 10:01:09 000001M|001/00/0/017|=5:2053=Terminal 17 in service
25/10/12 10:01:11 000001M|000/00/0/000|=4:0426=IPTOUCH terminal reset 13,00:80:9f:b2:e3:7e,3756
25/10/12 10:01:13 000001M|001/00/0/038|=5:2053=Terminal 38 in service
25/10/12 10:01:14 000001M|001/00/0/015|=4:0382=Init of IP set: No response from de set 00:80:9f:b2:e3:64,8767
25/10/12 10:02:37 000001M|000/00/0/000|=4:0426=IPTOUCH terminal reset 13,00:80:9f:b2:e3:64,8767
25/10/12 10:02:38 000001M|001/00/0/015|=5:2053=Terminal 15 in service
25/10/12 10:09:03 000001M|002/00/-/---|=3:4401=Ethernet broadcast reception disabled due to excessive traffic
25/10/12 10:10:20 000001M|---/--/-/---|=3:1125=external alarm : "mtcl login"
25/10/12 10:13:16 000001M|001/00/0/037|=2:0435=Security alert: ARP spoofing detected by 00:80:9f:b2:e8:79
25/10/12 10:17:39 000001M|---/--/-/---|=0:1612=Protocol error on Alcatel 8&9 series, type 13 (neqt 322)
25/10/12 10:17:39 000001M|---/--/-/---|=3:1613=15.04.0d.00.02.02.85.12.60.ff.00.00.00.00.00
25/10/12 10:17:45 000001M|002/00/-/---|=3:4401=Ethernet broadcast reception disabled due to excessive traffic
25/10/12 10:19:01 000001M|001/00/0/031|=4:0386=Sig. on IP set: No response from de set 00:80:9f:b2:e3:5f,3749
25/10/12 10:19:39 000001M|000/00/0/000|=4:0426=IPTOUCH terminal reset 13,00:80:9f:b2:e3:5f,3749
25/10/12 10:19:40 000001M|001/00/0/031|=5:2053=Terminal 31 in service
25/10/12 10:19:41 000001M|002/06/0/000|=3:1307=MCDU in distri tab entity 1, col Night , line 4 incorrect or missing
25/10/12 10:20:11 000001M|002/06/0/000|=3:1307x002=MCDU in distri tab entity 1, col Night , line 4 incorrect or missing
25/10/12 10:20:43 000001M|---/--/-/---|=0:1612=Protocol error on Alcatel 8&9 series, type 13 (neqt 322)
25/10/12 10:20:43 000001M|---/--/-/---|=3:1613=15.04.0d.00.02.02.85.12.60.ff.00.00.00.00.00
25/10/12 10:21:03 000001M|002/06/0/000|=3:1307=MCDU in distri tab entity 1, col Night , line 4 incorrect or missing
25/10/12 10:21:33 000001M|002/06/0/000|=3:1307x002=MCDU in distri tab entity 1, col Night , line 4 incorrect or missing
25/10/12 10:25:57 000001M|---/--/-/---|=0:1612=Protocol error on Alcatel 8&9 series, type 13 (neqt 322)
25/10/12 10:25:57 000001M|---/--/-/---|=3:1613=15.04.0d.00.02.02.85.12.60.ff.00.00.00.00.00
25/10/12 10:27:02 000001M|---/--/-/---|=0:1612=Protocol error on Alcatel 8&9 series, type 13 (neqt 322)
25/10/12 10:27:02 000001M|---/--/-/---|=3:1613=15.04.0d.00.02.02.85.12.60.ff.00.00.00.00.00
25/10/12 10:28:52 000001M|---/--/-/---|=0:1612=Protocol error on Alcatel 8&9 series, type 13 (neqt 322)
25/10/12 10:28:52 000001M|---/--/-/---|=3:1613=15.04.0d.00.02.02.85.12.60.ff.00.00.00.00.00
25/10/12 10:30:10 000001M|---/--/-/---|=0:1612=Protocol error on Alcatel 8&9 series, type 13 (neqt 322)
25/10/12 10:30:10 000001M|---/--/-/---|=3:1613=15.04.0d.00.02.02.85.12.60.ff.00.00.00.00.00
25/10/12 10:34:36 000001M|---/--/-/---|=0:1612=Protocol error on Alcatel 8&9 series, type 13 (neqt 322)
25/10/12 10:34:36 000001M|---/--/-/---|=3:1613=15.04.0d.00.02.02.85.12.60.ff.00.00.00.00.00
25/10/12 10:35:37 000001M|001/00/0/019|=4:2013=Connection request on unknown link: 20003

If someone could help this noob and share some light on the subject It will be greatly appreciated.!

One-way audio problems are usually related to the GD/GD3/INTIP/INTIP3 boards. Can you please tell me which OXE Release & Patch(command "siteid") has been installed on the site? The problem you are having should probably be a simple issue that can be resolved by installing a patch for your release where there binary corrections for the compressors have been included.

Klink,

Thanks for the reply appreciated... ran the command and this is what I got:

Cpu: c80s1

ACD VERSION
release : 8
bug_fixing : 1
protocol_id : 90
version_dy_hr_stat : 11

(1)empagua> siteid

Customer's name : ;
Customer's address : ;
Customer's town : ;
Customer's country : ;
Customer's install number : ;

CPU type : cpu80
Linux version : 62.3

Delivery software version : h1.301 ;
Patch version : 28 ;
Dynamic patch version : b ;

MAO software version : H1.301.28 ;
Software Version Name : R9.0 ;
System Country : LATIN_AMERICA (92);
System for Large Config : no;

Node number : 1 ;
Network number : 0 ;

Alarm relay state : ACTIVE

I'm so sorry 4 the extremely late reply fher. I totally missed the email for your post.

I hope you have already upgraded to the latest h1.301.50a patch and that it solve the issue. You should also run an infocollect in interactive mode and check what you get in the boardinfo command regarding the binary version of your compression board. The compressor board binaries will surely be outdated and have the audio bug issue. 95% chance that upgrading solves the issue.

Mani23, not the same problem for you buddy. Check your trunk entity, overflow directory number, entity routing hours, entity trunk overflow and stuff. It's some basic config error that's causing this. To investigate, try creating a new incoming trunk, physically plug your line into that trunk and test with an incoming call. If the issue is not reproduced, switch to the new trunk or compare the configs of both trunks.

Please do not hesitate to mail me personally or PM me for troubleshooting/solutions on OXE.

Cheers!