Remote Administration - Problem Initiating Session

[pvision]

I recently replaced an ACS R3.0 with a R6.0 processor. I downloaded the translations from the R3.0, and created a new R6.0 translation file with the same settings. I dialed into Ext. 76 of the R6.0 processor, connected at 14400, but was not able to start the session with the processor in order to upload the translations. I created a remote password, so that wasn't the problem. I deleted the modem drivers, shut down my PC, and rebooted adding back the modem, as suggested in a previous post, but got the same results. I even tried a different Remote PC Card, to no avail.

I'm sure I'm missing a simple step - HELP!

 

[pvision]

I was finally able to connect on a different PC. There seems to be some sort of incompatibility with my new R6.0 processor and the modem in the PC that I have ALWAYS used to program my R3.0 processor (as recently as 3 days ago!)

I also had to do each step of the retrieval process (Remote Backup, Retrieve Translations, etc) separately, as the software hung after performing the backup when I tried to it all in one step. Perhaps the newest version of the software will clear up this issue (I'm running V6.0.0.9)

Is there someone who would email me a copy of the latest software, or tell me where I can download it. I have a ACS processors to program over then next two weeks, and I want to make it as troublefree as possible.

Thanks!

 

[MrSharpFL]

Im installing a new Partner ACS with a R6.0 processor and a Remote Access PC Card and having the same issues.

Im using my laptop and set the extention to "intercom" mode created a "remote password" and even set my modem to connect below 9600 per the document library.

I can sometimes complete the handshake sometimes not? Even when I do complete the handshake I never get a login box. The connection seems to be just timing out, I cant even retrieve the translation.

Your second post you indicated that you connected via a different PC. Has anyone identified what the incompatibility with the processer and the modem was. When completed this system will be managed by a Win2K advanced server setting in the same room as the ACS. I will be purchasing a modem to connect the server to the ACS and after reading your posts think a hardware modem may be the answer but would definately appriecate any recomendations.

Also did any one know how to get a copy of the latest software, or tell me where I can download it.

 

[pvision]

MrSharpFL,

Here is the link for the lastest version I could find (6.0.0.9):

ftp://ftp.avaya.com/incoming/Up1cku9/tsoweb/partner_acs/remoteddminr6v6.0.0.9postga.zip

As for the modem, the modem I was having problems with was a rock-solid USR internal 56K/v.90 hardware modem (which, by the was, worked fine with my ACS 3.0). Believe it or not, the modem that finally worked was a cheap HCF 56K winmodem! I'm guessing that either the ACS is generating some interference that the 1st modem didn't like, or the 1st PC I used was generating "noise" that the ACS didn't like (i.e. it may have been moving to the 2nd PC itself that solved the problem, not the different modem). If you have an external modem, I would try that.

Good luck!

 

[Midstream]

The documentation "Requirements" section of the Remote Administration Getting Started states that you need a V.34 BIS modem, whatever that is.

The internal modem on my HP Laptop [Conexant 56K] and an external USR 33.6 do not work. I'm going to try to lookup V.34 BIS on Google and see what I get.

 

[hdingman]

Yes, Older is better for modems to connect phone systems. Computer-geeks (yes, I'm one) haven't used 300 baud or even 1200 baud for 20 years or more, but most of the systems I work on connect at 9600 or less. The cheapo modems, especially the no-name jobs that use the Audio Modem Riser (AMR) have troubles negotiating down that slow. Their objective is speed, usually 56K, and the manufacturers are starting to discontinue support for Bell 103 300-baud and other low-speed standards. If they do connect, they may not stay connected; they just drop for no reason.

So.... what to do? Go to the flea markets, used computer stores, or something like that, and see if you can find a Hayes Smartmodem 9600 or Smartmodem 1200. A US Robotics Courier 9600 is good too, but the big thing is to try to find a name-brand 9600 or 14400 modem. Second choice is a 28,800.

The real rub is this - if the modem attempts to negotiate a speed faster that 28800, like 56K, it will not negotiate to anything below 28800. That's too fast for the remote admin. The easiest fix is to get an old clunker that won't go any faster, and use it for dial-in. You can usually find them for 5-10 bucks or less.

hd

 

[Furball8675309]

6.0.0.11 is the newest, make sure you have ther newest.

 

[ttech]

The newest is actually 7.0.0.4

and it is campatible with all of the releases partner R3-R7

ftp://ftp.avaya.com/incoming/Up1cku9/tsoweb/partner_acs/R7_PC_Admin_and_Diag_V7.0.0.8.zip

Don