Changing remote PC - admin now fails

[jlshelton]

I need to give up my laptop, with which I've been doing Remote Partner ACS Administration. The laptop has Avaya Remote version 6, and a built-in modem of some kind. It works just fine. From a local extension, I can dial "76" into a Rel 6 ACS, connect, and administer.

Before letting go of the laptop, I thought I should try remote admin from a desktop PC. Sitting in the same room, connected to the same station line, the desktop PC fails to connect. Obviously, the ACS processor is not at fault. I installed Avaya Remote version 7, because it was there. The desktop has some generic modem in it (Creative Modem Blaster), which I configured to cruise at no faster than 2400 bps. The speaker is on, and I can hear the PC and ACS modems chattering with each other; they agree to talk, and the speaker goes silent. But 15 seconds later, the software reports it could not connect.

I tried my old trick of routing the call externally. (Ask the modem to dial 9 - then an inbound number into my ACS) That helps sometimes by reducing the signal level. But no luck.

Any other suggestions? Tempting to get a new Rel 7 processor, but that's kind of an expensive fix.

 

[itpphoneguy]

Hi jlshelton,
That won't help. My PC used to work fine until the CPU went CROAK. New cpu and I can't connect to any ACS system. I put an external USR 33.6 fax/modem on the computer (after trying a Lucent internal modem - no joy) and I can connect sometimes. This computer was reliable. I have reinstalled PC Admin. Then I removed all the keys in the registry and reinstalled it again. No change. This is the first computer that didn't work for me (out of 6). Avaya has no clue what the problem is.
Try a USR ecternal and I wish you luck!

-Chris