Solaris

Looking for ideas on why I can't dial into our new Avaya CMS server (Sun Netra 210 - Sol 9) - remotely thru our ASA - site admin software.

Running R3-V13 Avaya CMS software - just did a fresh install of the CMS software - install went perfect.

The Sun supplied DB9 connector is installed correctly on the Netra and the DB25 connector on the Sportster 33.6 and the factory CAT5 cable is connected to the DB9 & DB25.

ASA software settings are exactly what I use to dial remote to all our switches & VMs - 8-N-1 Hardware - Emulation 4425 (from my IBM Notebook) and I have tried the analog modem setting ... generic 1200/2400/9600 - generic 9600 etc and while the modem answers and handshakes every time - and the ASA terminal Emulation screen opens up when connected - I cannot get a Login.

This is driving me crazy. Should be simple. I have tried (4) different Sportster 33.6 modems - same result.

I put an RS-232 tester on the DB25 connector from the CMS - no connecttion to the Sportser yet - got green LED on TD & Red on RTS & DTR. When I connected the tester w/ the DB25 to the Sportser and turned it on - Green was TD-CD-RD & Red was RTS-DSR-CTS-DTR. When I dialed into the CMS - and got a successful handshake - the TD & RD were green and other LEDs were red .... but no data shows on the ASA terminal screen?

Very strange. I'm guessing it is something simple so any help or tips would be helpful.

May I suggest you try using the tip command to talk out of the appropriate serial port and send:

ATI3

which the modem should respond with its version number?

The tip command uses the file /etc/remote to configure a connection for you, copy the hardwire line(s) and change "hardwire" in your copied line to "modem" (e.g.) the port and baud rate to what your modem expects, then do run:
# tip modem
then once you have the connected message send the ATI3 command.

this will test the wiring of the serial port and the modem without too many layers of software in the way.