Denial event 1010, unable to access line

[tweege]

have an extension that appears on 4 phones, 3 lines on each. line one is having issues...will give either wave off when accessed (which shows denial event 1010 when a list trace is ran), or gets dialtone but will not break it. event 1010 is listed as 'Terminating Extension Group was denied an origination.' not sure how that comes into play in this situation. the exts are not associated with a term ext group. i have tried busy/release on all sets, unplugged all sets, reset the card they are attached to, with no changes in the problem. was going to go as far as removing all the exts and the main number having the problem, but i cant do that as the switch thinks line 1 in use! any ideas would be great.

thanks!

 

[dialtonebone]

If you do a "list history" do you see any EECCR errors?
How about "save translation" any errors?
"list usage ext XXXX" where XXXX is the problem line

I suspect corruption based upon what you've said so far but it could definitely be something else still.

 

[joe2938]

Try removing the lines and then adding them back and retest.

 

[tweege]

like I said, was going to remove all stations involved, but cannot as the system see's line 1 as in use.

don't see any of the errors mentioned in first post either. currently waiting on support to get back with me

 

[joe2938]

Then busy out that line 1st

 

[tweege]

if only it were that easy, lol. even when that station is busied out i cannot remove/change any bridge appearances.

 

[AvayaTier3]

Command: reset system 2

This will drop calls and recover in a minute or so. Schedule a maintenance window. That will fix your issue.

Another option would be a software corruption engineer connecting to your system and writing software tables to drop calls using Command: go tcm

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

45 years Bell, AT&T, Lucent, Avaya
Tier 3 for 35 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[tweege]

tried interchanging servers before running the reset system 2 command. problem fixed.

thanks for the input all!