I have been reading and reading Avaya's documentation for information on where the Admin port is located on the ACS 509, but there is no definitive location given.

We have three clinics with the Partner ACS 509 systems and none of them have a port on them that actually states 'Admin Port'.

My goal is to put PCs into the data closets where the ACS 509s are located, remote into the PC and connect to the ACS 509 for administration.

I have made a 355AF knock-off adapter as per the topics listed here, but have not a clue which port to plug the cable into. TouchToneTommy - Gotta love your major flow chart, but the jack next to the SMDR jack on our units is the 'Contact Closure Jack'. I have speculated that the Admin jack could be #10 or #11, but do not want to risk damaging the units.

After reading other posts here, the question of using a cross over cable also arises.

I see that there are many years of knowledge here, so I am not trying to waste the talents of those years.

Thankz in advance,

There isn't an admin jack on the 509 like there is on a Legend or Magix. The 355AF is used on the SMDR port. Extensions 10 and 11 are just that, extensions but they are the two that you use to program the system. You do the programming from the telephone sets at either of those extensions. You will need a backup/restore/remote access card installed into the Partner to be able to do remote programming. Part number 700317035.

An ACS "509 as you call it" WILL have an admin port for administering the system.

509's are either Partner ACS R.7 or R.8

The PARTNER ACS 509 processor module provides the software intelligence that controls the
system’s features. It has jacks for five outside lines, nine enhanced tip/ring extensions, a Music-On-Hold audio source, a grounding screw, a jack that supports an adjunct for two Contact
Closures, and a jack for a call reporting (SMDR) device, such as a printer. You can connect a
loudspeaker paging system to any line jack on the PARTNER system.
This is straight out of the Avaya documentation, so no, it is not "as I call it".

Again, a 509 Avaya Partner ACS HAS an admin port.
If you don't see an admin port on the processor, it's not a 509 ACS R.7 or R.8.

If you have a 509, the admin port is between the SMDR and line 1.

Sounds like you may need to do some foot work and less reading.

Sounds like you have an attitude.

I'm no Avaya Guru like Michael is, but that is exactly where the Admin port is on my repair bench's 509!

Not at all pal.
Just stating facts.

We have three clinics with the Partner ACS 509 systems and none of them have a port on them that actually states 'Admin Port'.

I have looked at the devices many times and not one specifically is marked as an "Admin Port", that is why I have asked for help.

Your approach is somewhat condescending.

I joined this forum for help, not sarcasm.

How might I tell what models we have? ie: R.7 / R.8?

Didn't mean to come across condescending by no means.
I'll say this one more time: If your processors do not have a admin port on them, they are not 509's (ACS R.7 or R.8).

You can press feature 59 from any display phone on an ACS and it will show you the release version on the display of the phone.

As you look at the "front" of an R7 or R8 processor, you'll see the 2 slots for PCMCIA cards.

Below them is the processor status LED.

Below that is the SMDR port.

Below that is the Admin port.

If none of them have that arrangement, you're looking at some other type of Partner processor.

As Mike mentioned, pressing "FEATURE 59" on any system telephone with a display will tell you exactly what revision a processor is.

pg 20 of the ACS manual

Geeze, I can't stand it! The admin port on the ACS R7&8 never was used. It goes nowhere and does nothing! That's why you will find nothing in the documentation (notice that there is no call-out for it in the above illustration). Only way to remote administer is through a modem and PC admin software.

-Hal

Sure it is,........it is used to admin the system with the GUI interface.
I think you may be talking about the Ethernet port. The one above the CC port.

Yeah, I think you are right Mike. Documentation only alludes to "PC programming" though, no specifics are given. I never used it, only the remote. Doesn't matter anyway because if the OP doesn't have an ADMIN port then he doesn't have an R7 or 8. He will have to connect (call into it) via a modem, PC admin software and a RAC card.

-Hal

Mike (Mdaniel) is correct in what he is telling you.
If you would like a call from Avaya, to clarify the same, I am sure that could be arranged.

PS. Great post Skip

I would like to thank all of you who have posted here to help me with my issues.

After another close inspection, and "FEATURE 59", it turns out we have R6 systems, which explains my confusion.

Thankz again,

I only saw one attitude.

Mike thanks for your patience and knowledge and the willingness to share that knowledge even when insulted.

Thanks to everyone for trying to assist the OP.

Feature 59 can be your friend!

so is physically observing and counting no need for ftr 59 to see that this wasn't a "509 " processor

Skip, :thumb:

Hey guys, why not keep things simple? Why in the world would this guy complicate things up like this? The Partner is a "set it and forget it" type system.
First, why isn'the contacting the Avaya Authorized Dealer who installed it for support... wait, he probably got it on the cheap from some gray market internet site. Second, why would he even think about hooking up a PC to any of it? Having sold almost 1500 Partner systems personally or in the company I own, I can count on 1 hand the number of systems that might remotely benefit from a PC admin hook up for programming changes. Why? because in the rare event alot of programming changes are needed it is so easy to hit feature zero zero and get it done before you can even unzip a laptop or log in via a remote program like logmein or pcanywhere. Since the partner programs while off hook, even remote changes can be directed to an onsite person in second.
Third, if a person has a hard time locating the different ports on the system, without sounding rude here, it might be better to hire an expert or someone with Avaya training or experience. A person can spend way too much time and effort on something that could be done in a jiffy by someone with lots of experience.
In short, keep things simple and dont dink around with some sort of PC remote admin if you dont know what you are doing. My humble opinion.

I know this is off subject, but welcome back Hal!

We remotely administer alot of Partners. Most of the time it is as simple as walking the customer through the programming changes. Or if you have a T1 card, and need to make DID changes then you have to do it through the GUI, I mostly use the Admin port to save a backup of a system on my laptop if I may need to replace it. Or you can just carry a backup card. The new partner even has the modem built in, tell the customer to transfer you to 76 and your in.