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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

ERROR: Conferencing DSP -> CPU I/F Queue has OVERFLOWED!

Status
Not open for further replies.

davidsonv

IS-IT--Management
Dec 25, 2014
3
UA
Avaya IP 406 DS 5.0(26). Just upgraded from 3.2. When I connect to system monitor it shows standard system information and then goes crazy. I can close the system monitor only if disconnect the LAN cable from my PC.
What these errors means?

PRN: Monitor Status IP 406 DS 5.0(26)
PRN: LAW=A PRI=1, BRI=0, ALOG=0, ADSL=0 VCOMP=4, MDM=0, WAN=0, MODU=0 LANM=0 CkSRC=0 VMAIL=0(VER=0 TYP=1) CALLS=0(TOT=1)
60142mS RES: Wed 24/12/2014 10:03:07 FreeMem=38604804(1) CMMsg=2 (2) Buff=100 594 500 1068 5 Links=10417
60143mS RES2: IP 406 DS 5.0(26) Tasks=24 RTEngine=0 CMRTEngine=0 Timer=45 Poll=0 Ready=0 CMReady=0 CMQueue=0 VPNNQueue=0 Monitor=1
60153mS PRN: Slot A, Falc 1: LOCK RAI crc=1 set=1 FMR1=4e FMR2=83
60154mS ISDNL1Evt: v=1 peb=1,F1 F3
60154mS ISDNL1Evt: v=1 peb=1,F2 F1
60155mS ISDNL1Evt: v=1 peb=1,F3 F2
60191mS ISDNL1Evt: v=1 peb=1,F1 F3
62150mS PRN: Confer DSP DTMF detect: invalid detector 0
62151mS PRN: Confer DSP DTMF detect: invalid detector 0
62151mS PRN: WARNING:
62151mS PRN: ERROR: Conferencing DSP -> CPU I/F Queue has OVERFLOWED!
62151mS PRN:
62152mS PRN: Confer DSP DTMF detect: invalid detector 0
62152mS PRN: Confer DSP DTMF detect: invalid detector 0
62153mS PRN: Confer DSP DTMF detect: invalid detector 0
62153mS PRN: Confer DSP DTMF detect: invalid detector 0
62154mS PRN: Confer DSP DTMF detect: invalid detector 0
62154mS PRN: Confer DSP DTMF detect: invalid detector 0
62155mS PRN: Confer DSP DTMF detect: invalid detector 0
62155mS PRN: Confer DSP DTMF detect: invalid detector 0
....
94058mS PRN: Confer DSP fax detect: invalid detector 63
94058mS PRN: Confer DSP DTMF detect: invalid detector 0
94059mS PRN: Confer DSP fax detect: invalid detector 63
94059mS PRN: Confer DSP DTMF detect: invalid detector 0
94059mS PRN: Confer DSP fax detect: invalid detector 63
94059mS PRN: Confer DSP DTMF detect: invalid detector 0
94059mS PRN: Confer DSP fax detect: invalid detector 63
94060mS PRN: Confer DSP DTMF detect: invalid detector 0
94060mS PRN: Confer DSP fax detect: invalid detector 63
94060mS PRN: Confer DSP DTMF detect: invalid detector 0
94060mS PRN: Confer DSP fax detect: invalid detector 63
94061mS PRN: Confer DSP DTMF detect: invalid detector 0
94061mS PRN: Confer DSP fax detect: invalid detector 63
94061mS PRN: Confer DSP DTMF detect: invalid detector 0
 
Monitor goes berserk? Never seen the error codes before.
I'm thinking system programming creating loops, motherboard shot, enabled all filter options in monitor or a major hacker attack.

You only got 4 VCM ch, but you have a PRI?
I assume all phones are Digital or Analog, not exhausting your VCM capacity.

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

2cnvimggcac8ua2fg.jpg
 
This seems like a broken conference chip to me.

BAZINGA!

I'm not insane, my mother had me tested!

 
I have to also maybe ask the same thing that smokinjoe2938 did
Did you upgrade the correct path and I go one further and ask if you did R4.2 as interim step as that is required before going to R5.0.
If you did then I have to agree with tlpeter and say it is pooched, get a new one, they are a dime a dozen on ebay (better a used communications hardware dealer close to you so you can go back and replace it should it not work) or get a new IP500V2 but then you need to get a bit higher in the release and maybe have to spend some money on licenses and maybe hardware.

Joe W.

FHandw, ACSS (SME), ACIS (SME)


ôThis is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter
 
I'm not sure if I did the upgrade properly. I upgraded from 3.2 to 5.0 without 4.2 as interim step.
VCM used for trunks only. I disconnected it as a step of troubleshooting
As for now I downgraded the system to 4.2 and reset to defaults - messages are still there.
Then I downgraded to 3.2 - messages gone.
I will test it for some time.


The main reasone to upgrade to 5.0 is sip trunks. Should I try to upgrade 3.2-4.2-5.0 to get it working? Or there some hardware incompatibility?
 
You need to step upgrade [smile]

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

2cnvimggcac8ua2fg.jpg
 
4.2 can do SIP trunks as well. 5.0 has SIP extensions as well.


Joe W.

FHandw, ACSS (SME), ACIS (SME)


"This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter
 
been a while but isn't there a 3.99 step before the 4.X step?
Mike
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top