Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

LEDTICK:Slip error on all (4) DS30 expansion modules

Status
Not open for further replies.

Erik Olson

Programmer
Oct 9, 2017
5
US
Hello,

I have an Avaya IPO500 (9.1.200.91) with about 70 extensions on 2 DS30 expansion modules which have been operating quite nicely for 4 years.

All of my DS30's simply boot up with a flashing green LED, and the serial port is outputing in the dreaded LEDTICK:Slip Error.

I've tried everything imaginable including (I think) bricking one of the DS30's with the serial port commands.

I had a certified phone guy come out for a day but ultimately he couldn't help and tried to sell me a different brand phone system.

The things I've tried:

+ All the expansion ports
+ Making sure I have the magic cable
+ Other cables
+ Boot IPO first, then modules
+ Boot modules first, then IPO (repeat repeat repeat)
+ Reset security & upgrade to same version (took about 90 minutes)
+ AT-X on one of the DS30's and after outputting lots of errors requesting the bin file for a while, now it's completely dead (red light for 5 seconds then no light)
+ 3rd party TFTP on VM server
+ 3rd party TFTP on workstation (all variations showed the IPO downloading the hold music wav file but nothing else)
+ Verify the DS30 bin file is in the TFPT folder
+ Rebooting over and over
+ Asking God to bless the phone system
+ Unplugging all extensions
+ trying just one module at a time
+ Bought a refurb online from PhoneLady ... also same problem
+ Borrowed a loaner from aforementioned phone guy, it worked for a day then same problem
+ The phone guy also took my 2 original DS30's to his "Supplier" who tested them, the one I bricked was declared dead, the other one was "fine"

At first the issue was intermittent, I was able to get one chassis up for a few days, and the loaner I mentioned for a day but after a reboot nothing has ever worked again.

I think these are the lines from the Monitor which repeat the system status, showing MODU=0 (it used to say MODU=2)

[pre]********** SysMonitor v9.1.2.0 build 91 [connected to 172.16.16.2 (Chargebacks911)] **********
09:18:45 279635mS PRN: Monitor Status IP 500 V2 9.1.2.0 build 91
09:18:45 279636mS PRN: LAW=A PRI=0, BRI=0, ALOG=0, VCOMP=64, MDM=0, WAN=0, MODU=0 LANM=0 CkSRC=0 VMAIL=1(VER=3 TYP=1) 1-X=0 CALLS=0(TOT=1)
09:18:47 280644mS RES: Tue 4/6/2019 09:18:47 FreeMem=55235080 (Heap=54987000(3) + Cache=248080) MemObjs=11670(Max 12488) CMMsg=3(3) Buff=5200 1357 1000 7406 5 Links=57050(58000) BTree=13751 CPU=03.11% CPUStats=02.72%/1/3/17784/24239/24428/00.06%/0/02
.10% MCR=0 MCW=0
09:18:47 280644mS RES2: IP 500 V2 9.1.2.0 build 91 Tasks=48 RTEngine=0 CMRTEngine=0 ExRTEngine=0 Timer=71 Poll=0 Ready=0 CMReady=0 CMQueue=0 VPNNQueue=0 Monitor=1 SSA=1 TCP=38(TLS=8) TAPI=0 ASC=1 SYS=MNTD OPT=UMNT SDSPD=2034
09:18:47 280645mS RES4: XML MemObjs=63 PoolMem=4876404(2) FreeMem=4861100(0)
09:18:47 280645mS RES5: CLog MemObjs=1678 FreePoolMem(Objs)=1144(22) TotalMem=288250
[/pre]

Here's the TFTP log (also shows me testing GET test.txt from a local linux box)
[pre]Tuesday, June 4, 2019 9:14:20 AM : Received TFTP request for C:\Program Files (x86)\Avaya\IP Office\Manager\test.txt from 172.16.16.4:43782
Tuesday, June 4, 2019 9:14:20 AM : Sent 100% of C:\Program Files (x86)\Avaya\IP Office\Manager\test.txt to 172.16.16.4:43782
Tuesday, June 4, 2019 9:14:25 AM : Received BOOTP request for 00e0078c1c8a, 0.0.0.0:68
Tuesday, June 4, 2019 9:14:25 AM : Sending BOOTP response to 00e0078c1c8a, 0.0.0.0:68
Tuesday, June 4, 2019 9:14:25 AM : Received BOOTP request for 00e0078c1c8a, 0.0.0.0:68
Tuesday, June 4, 2019 9:14:25 AM : Sending BOOTP response to 00e0078c1c8a, 0.0.0.0:68
Tuesday, June 4, 2019 9:15:13 AM : Received BOOTP request for 5c777674e9c3, 0.0.0.0:68, unable to process
Tuesday, June 4, 2019 9:15:14 AM : Received TFTP request for C:\Program Files (x86)\Avaya\IP Office\Manager\HoldMusic.wav from 172.16.16.2:4100
Tuesday, June 4, 2019 9:15:15 AM : Sent 5% of C:\Program Files (x86)\Avaya\IP Office\Manager\HoldMusic.wav to 172.16.16.2:4100
...
etc
...
Tuesday, June 4, 2019 9:15:19 AM : Sent 100% of C:\Program Files (x86)\Avaya\IP Office\Manager\HoldMusic.wav to 172.16.16.2:4100
Tuesday, June 4, 2019 9:15:48 AM : Received BOOTP request for 6451063d14c0, 0.0.0.0:68, unable to process
Tuesday, June 4, 2019 9:16:11 AM : Received BOOTP request for 5c777674e9c3, 0.0.0.0:68, unable to process
Tuesday, June 4, 2019 9:20:18 AM : Received BOOTP request for b418d165d52d, 0.0.0.0:68, unable to process
[/pre]

I'm currently operating with 8 Digital, 2 analog extensions on the CU and 9 IP extensions

(I also have the system seamlessly integrated with Twilio and 2 Asterisk servers, and several trunks & extensions on those as well. My fall back plan is to start handing out SIP phones attached to the Asterisk hosts)

The only thing I can think of is that ALL of the expansion ports on the CU have gone bad. Does anyone have anything else to suggest or can you recommend someone in the Tampa Bay Area? Avaya's directory on their website has about 20 vendors listed and none of them are in business or answer the phone.
 
 https://files.engineering.com/getfile.aspx?folder=9ca12cce-e115-438a-9dbf-c186ba1f28e1&file=LEDTICK.png
Try this. This guy actually uses the LEDTICK:Slip error in his examples. I would also try formatting and recreating the SD Card if you're using a V2 control unit. Try replacing power supplies on the units without lights, or just outright. Failure to deliver enough power may throw errors if the internals aren't getting the proper dose of zaps.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top