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!
broken queue
- Thread starter weaksauce
- Start date
a long stick used for billiards
Pat Guido
NEXTIRAONE
Pat.guido@nextiraone.com
Formerly Nextira, formerly Williams Communications, formerly Wiltel, formerly Nortel networks, formerly Northern Telecom, formerly, Nynex meridian systems formerly Northern Telecom.
Pat Guido
NEXTIRAONE
Pat.guido@nextiraone.com
Formerly Nextira, formerly Williams Communications, formerly Wiltel, formerly Nortel networks, formerly Northern Telecom, formerly, Nynex meridian systems formerly Northern Telecom.
sorry had to do it life is a 3 stage deal your born you live you die i am still living and i need to have some fun...what is the broken q in reference to any error msg what switch yada yada yada ...
Pat Guido
NEXTIRAONE
Pat.guido@nextiraone.com
Formerly Nextira, formerly Williams Communications, formerly Wiltel, formerly Nortel networks, formerly Northern Telecom, formerly, Nynex meridian systems formerly Northern Telecom.
Pat Guido
NEXTIRAONE
Pat.guido@nextiraone.com
Formerly Nextira, formerly Williams Communications, formerly Wiltel, formerly Nortel networks, formerly Northern Telecom, formerly, Nynex meridian systems formerly Northern Telecom.
- Thread starter
- #4
Yeah it is an error. I have an 81c that has decided lately to INI everyday at 17:15 or so. I do not get any errors, except the hexadecimal ones. When I have the code decifered, it says "broken-queue". I am not sure what that is. Another weird thing is when the switch INI's it usually displays which core it is on, but these INI's gives me a question mark. I am at a lost with this one.
what release on switch and does this look like it
INI000 000C
INI000 0000C Broken Queue Initialize
INI000 0000000C 16 17 49 00000000 00000000 00000000 00000000 0 ? 1 00000084
BUG681
BUG681 Set_acd_ptrs failed,DN. Procedure ACD
BUG681 : 55 E4F1E663 00479D8D 00001001 00008018 00005084 00000000 0 00000000 000 00000 00000000 0 6242 00000084 00002426 00000000 00000000 00000000 00000000 000
BUG111
BUG111 Call Register is not in range. Procedure IDLECR
BUG330
BUG330 Traffic times start mismatch.
BUG440
Bug440 TNTRANS failed on TERTN. Procedure CDR.
BUG105 Double timeslot problem prevented
RCV002
RCV002 Broken Queue problem detected. Auto recovery has taken corrective action.
RCV002 + 046C5EE4 04507A96 04504528 044F87E2 04701CBA 04446CCE
RCV002 : 00000000 005C0C3F 00000000 005E8905
Pat Guido
NEXTIRAONE
Pat.guido@nextiraone.com
Formerly Nextira, formerly Williams Communications, formerly Wiltel, formerly Nortel networks, formerly Northern Telecom, formerly, Nynex meridian systems formerly Northern Telecom.
INI000 000C
INI000 0000C Broken Queue Initialize
INI000 0000000C 16 17 49 00000000 00000000 00000000 00000000 0 ? 1 00000084
BUG681
BUG681 Set_acd_ptrs failed,DN. Procedure ACD
BUG681 : 55 E4F1E663 00479D8D 00001001 00008018 00005084 00000000 0 00000000 000 00000 00000000 0 6242 00000084 00002426 00000000 00000000 00000000 00000000 000
BUG111
BUG111 Call Register is not in range. Procedure IDLECR
BUG330
BUG330 Traffic times start mismatch.
BUG440
Bug440 TNTRANS failed on TERTN. Procedure CDR.
BUG105 Double timeslot problem prevented
RCV002
RCV002 Broken Queue problem detected. Auto recovery has taken corrective action.
RCV002 + 046C5EE4 04507A96 04504528 044F87E2 04701CBA 04446CCE
RCV002 : 00000000 005C0C3F 00000000 005E8905
Pat Guido
NEXTIRAONE
Pat.guido@nextiraone.com
Formerly Nextira, formerly Williams Communications, formerly Wiltel, formerly Nortel networks, formerly Northern Telecom, formerly, Nynex meridian systems formerly Northern Telecom.
It's vital to check that the patches on the system are right and the latest updates.
Callregisters has to be right in size depending on the switch type, size and equipment.
Some solutions can make the switch run out of callregister space. I have seen when attendant call over VNS for example makes the switch go nuts. So it can be difficult to find.
But first of all, check patches and callregister parameters.
Callregisters has to be right in size depending on the switch type, size and equipment.
Some solutions can make the switch run out of callregister space. I have seen when attendant call over VNS for example makes the switch go nuts. So it can be difficult to find.
But first of all, check patches and callregister parameters.
- Status
Similar threads
- Locked
- Question