Search results for query: *

We were able to get a replacement and it was plug and chug - we are back up. It would of course be prudent to have a spare but in theory the equipment is on the list to be phased out/integrated with corporate Cisco VOIP, so meanwhile we slog along and put out any fires. Thanks everyone for the...

thank you, we did swap so we at least had the main controls up and it definitely seems to be the power supply.

ok our guy was calling that the "switch." Thanks for your help. I am thinking the power supply is toast.

what does the breaker reset look like?

I will ask. The bad part is I am remote and have never seen the system in person. I have actually not "seen" a real Avaya in 10 years.

card cabinet has no lights but power is on

Building power had to be cut and now PBX will turn on but just a white cursor on screen and nothing going on- any advice? It was gracefully shut down.

Well now I feel silly.

Thank you - not sure why when first entering the ld it gives the error but I got the time set so all is well.

We only have one set - it seems like after an incredible lag it came back with the ttad I just did an stad and I *think* it took it, but still throwing errors I did the ld 22 password check thing I saw on another thread and it is PWD2 if that helps >ld 02 TFC000 . TIM000 10:00 26/3/2014 CPU 0...

I apologize for the lag here thanking everyone - my end users are slow to get back to me- but apparently the setup still is not working. I will gather some details.

I saw a similar thread that was closed - last week I got in fine and could STAD, TTAD on a Meridian but some genius tripped over the power supply and now the system is back up, but when I try to ut in LD02 I get TFC000 So I am not sure how to wake up LD 02 so that I can set the time.

What I am trying to do is have both extensions ring the same set and for them both to have voicemail. they are on the floor and don't really sit at the desk much but wanted to keep calls distinct. (One on each shift)

I have been able to point both DID to this phone and they both ring it. But internal callers to the extension and external callers that dial an ext from the main number just go straight to VM on one of the lines. I did this by having two target line assignments on one set. DN 201 line access...

The Change DN and the wizard seem to do the same thing - thanks for the tip though, it is neat to see how the configuration is available on certain of the "nodes" as you climb through the trees. Thee wiring guy is there now and tells me "it is easier to switch the wires" which seems dumb. It...

it is actually a 3.7 for what it is worth Trying a different login to see if the ports field will not be grayed out - if I could just change the port number I think that would cut it. The patch down panel pics they sent are not user friendly or well-labelled.

well, the DN does swap the names but the numbers still ring the wrong physical location. I do have a 2nd set of hands out there tomorrow to help me

Thanks for the tip curlycord! I only have a gui interface, which oddly is less easy than hyper term I don't see a "change DN" in here the main part but I do see it in the wizards Once upon a time I thought I saw a hyper-term to this thing. I just gave it s shot and will let you know how it goes.

I tried swapping the target lines. At first this seemed to work and then it is like it reverts back. Do I need to have someone go just physically swap at the ports? (I am at a remote location)

Thanks for your reply. Sounds like a boat load of fun if the hard drive is out - I have a backup but it does show some errors but hopefully can help.