atcomsystems.ca/forum Forums TDM Business Telephone Systems Avaya - Lucent Telephones & Systems Partner messaging R1

I received a usb-serial adapter cable today. Made an adapter with a db25 breakout box, and got into the system. I was able to reset the IP to an address that works on my network, and now I can access the web GUI. I have not yet been able to get the administration program to run on either of my PC's but this is a HUGE step in the right direction. Thank you all for your help, especially TTT.

Here is a picture of the monstrosity it took to make a pig fly:

I looked into the specifics of the 355A adapter when I got my Merlin Legend. Surprisingly it's not some weird proprietary pin-out: it's a standard EIA-561 to DB25 adapter, with some clamping diodes (likely) to handle surges/noise. EIA is the group that published the RS232/RS422/RS485 standards, and EIA-561 is a standard for RS232 on an 8P8C connector.

A little detour, but still about ACS serial ports... I just picked up a cheap PC running XP pro, so I can manage the partner messaging module. In addition, I would like to leave it connected to the SMDR port on the processor to keep a running call log. Is there any harm in leaving a pc connected to that port running all the time? It was really neat to connect it to my laptop and see it spit out a call log in hyperterminal, and I think it would be kind of handy to have a record, just not sure if it's kosher to leave that cable connected all the time.

Won't hurt anything, that's what a call accounting system does.

Cool. Thanks, TTT.