Avaya G3SI V6 error encountered while duplicating a station

[spirulinia]

HI Guys,

I am trying to dup a station but when I do, I get " error encounted can't complete request. Then when I go look at the error log I see ( EECCR - 10009 ) not sure what I need to do in order to add or dup a new DID station for a new user. Could it be some type of curruption ?

 

[4merAvaya]

Sounds like software corruption. Open a case with Avaya.

Kevin

 

[koglass]

Instead of duplicating a station can you add it new? What type of phone is it? Can you cut and paste the error you are getting here?

 

[spirulinia]

I wrote in the error on my thread, I tried to add a phone as a new station too but still got the error, I tried to add a 7406d and also 8410d as well

 

[spirulinia]

when I add the station, it seems like it is taking it but then on the bottom of the screen i get the

" error encounted can't complete request.

then I looked in the error log and saw

( EECCR - 10009 )
as an error

 

[koglass]

When I look for the error 10009 in the Avaya manual I can not seem to locate that error. So I feel something might be missing from your explanation of the error code. If you can cut and paste the error there may be more info to help locate the error code. Is it under CM Object Dig-Line? The more info you supply the better it is for people to try to help.

 

[phoneguy55]

'run stat log' is anyone else making a change command? I would try and boot everyone out 'reset log X' and try your change again.

 

[PBXadmin]

We had the same problem a couple of months ago. We could add single line phones but not digital. Kept getting the error message. It did take Avaya to correct this.

I would take 4merAvaya's advice and open a case with Avaya to get this resolved.

Tom

 

[spirulinia]

Thank you all so much and I will open a case up with avaya. thanks again

 

[mdefedele]

I work for a business partner of Avaya and Have seen this on a lot of switches. It is definitly software corruption as it usually is when you receive "error encountered" Your specific issue is fixed in two ways without Avaya. I am assuming you are running a 3.x load prior to 3.1.4....Update your system to 3.1.4 using PCN1523BU and your issue will be solved. They have a combo patch out for 3.1.2 systems but you usually have to call a business partner or avaya to get it since it is not a public patch. For 3.1.2 the patch is 14358 i think (don't quote me on the patch number).

In short update to 3.1.4

 

[mikeydidit]

Avaya G3SI V6

Make the call to the software corruption group to get this one fixed.

Hell, there are no rules here - we're trying to accomplish something.
Thomas A. Edison

For the best response to a question, read faq690-6594