Search results for query: *

She is not nulling the key beforehand, as she never needed to do that with TM (yeah- ha ha!). However, I do believe this too may be the issue. I think EM is too slow to catch up that quickly- needs "refreshed" in sorts. The error does not occur via CLI... just EM. I will have her try nul...

The instructions to change the passwords are in the Linux Platform Base and Applications Installation and Commissioning (NN43001-315) NTP starting on page 191. If you do not have access to the NTPs, you can ask your vendor to provide the document or you can download the document from the Avaya...

I have a customer new to Rls 7.5. From Phones in EM, she is trying to change a key from SCR to SCN (same extension). She receives a SCH0600 error (Illegal input character) when saving the change. She has to make the change a few times before it will actually save. There is no illegal...

Resolution!!! First : Further investigation found that dep list patch 20911 was causing the INI. The patch library shows that patch is obsolete (but still in the active DSN dep list!!) and replaced with 21935. Removed patch 20911 and replaced with 21935 Second: Found out the patch 20911 was...

@mastang13 - we already had the grounding and rectifiers tested and checked. @trvlr1 - the circuits are running fine and clean :) @johnpoole- remember this is DSN, so the patch needs to end in .atv or I cant load it! @everyone- Nortel still has the ticket- not much fun working these days.

So after trying everything under the sun- I opened a ETAS ticket this morning. So far- they dont have a clue either! I will let everyone know what the outcome is :) Thanks for all the input- and references!

@GHTROUT- LOL- that does not help! Again, only INIs during the day!

No- You would need a MC3100 or some find me/follow me functionality. You cannot "pull back" a call with a regular call forward external. Thanks!

I have a Opt81 DSN system that will INI 3 times per day during normal office hours (does not happen after hours or on weekends). I have captured history data and there is no warning before the system goes down. Can someone please take a look at the INI messages and tell me if they see anything...

I am interested in hearing the results. I have the same problem in a new 1000E/T 4.5 that was just installed. I have tried building "0" as ACD, ATT, 500, 3904, blah, blah... I have not been able to get the name to pass in any of these instances. And yes, I checked DNDA, CNDA, etc.. Anyone...