ACS R4 Remote Access

[MWM]

The new 4.0 Remote Access software is very helpful & productive -- you can set up the system on a PC prior to the actual install.

But getting connected to the module is a problem so far ...

Setup: a stand-alone (no carrier) new ACS 4.0 module w/ Remote Access card installed, 18D phone and laptop running Remote Access.

Plugged directly into a station port, the laptop modem quickly negotiates at 14400 but fails every time to establish a session. Error Message: Failed to establish a session.

BTW, this direct hookup requires an intercom call to ext 76, which in turn requires the chosen port to be configured with Intercom as Auto Line Selection.

I defaulted the system prior to starting: any other setup I'm missing?

Thanks a lot

Mike

 

[TouchToneTommy]

Well, I had the unfortunate experience of replacing a dead R3 with a new R4 this evening. A new R4 CANNOT be made into an R3 with an R3 upgrade card, and it will not read an R3's backed up program from the old card.

So we're basically screwed! Moral of the story, keep complete, up to date system planners!!

 

[MWM]

TT Tommy;

Well, the brief success I mentioned a couple of weeks ago has become an uncertain success. That is to say, connecting to the new R4 works but achieved a session lockup is not at all certain. And, having achieved a session, it fails to upload or download. Sometimes unchecking the "Maintenance Files" portion of the file transfer allows it to succeed, at least to that point.

I am focusing on the "Directly Connected" method, directly through a port and not the dial-in approach.

The Nortel RAD solution works. Why not Partner?

Are there DEALERS out there who have the secret to success with Partner Remote Access?

Mike

 

[x28800]

I've had *no* problems at all using 4.0.0.8, either directly connecting to extn 76 (I have a laptop plugged into the Aux port of a system phone), or dialling in and connecting via Auto Attendant/ Hunt Group 6 (*8 then 776). Are you sure that the problems aren't related to the PC you are using? (The laptop I use has Windows XP) Have you tried installing the software on another PC? And obviously it could be the modem in your PC which is causing the problems (I have an LT Win Modem, with the latest drivers installed). Check online for modem driver updates, or spend a few dollars on a new modem, and your problems may be solved!

 

[MWM]

Thanks, 28800.

Yes, I would gladly spend money to solve the problem, and I am glad to know that you are succeeding. That means there is hope.

And, yes, I am also running XP. I have tried Remote Access on three PCs, 2 laptops and a desktop, both internal and external modems. One laptop is new with latest everything.

You are also encouraging with respect to getting everything to work.

At some point, I might ask you to state the obvious, perhaps, and give your specific step by step instructions, though of course the hookup should be like connecting to other machines. I'm still trying!

Yours,
Mike, RCDD, CCNA

 

[TouchToneTommy]

Well, the long saga continues! Partner ACS R5 has been announced, and with it is R5 Remote Admin. Software. A 3meg donload from the Business Partner website, just got it, but haven't had time to install and try it out yet.

 

[MWM]

Thanks, TTTommy;

I plan to get one of the 5.0 processors and card soon, but, as I am not a dealer will have to get the software the hard way ($$$).

Yours,
Mike
RCDD, CCNA

 

[drewmich]

Yes - the new ACS R5.0 processor and PC flash upgrade software is now available. It should be a good release for some Partner system users or new ones also as there it supports additional modules which expands the Partner ACS system's capacities. Avaya has programmed into this release of the ACS R5.0 software, the ability/compatibility to use an Endeavor 362 line mod ... plus the new Partner 012E line mod which has 12 station ports.

I have attempted to download the new ACS R5.0 Remote Admin software but the link I got from Avaya via email doesn't work.

Can anyone help get this straightened out for us? Here is what they sent me ....

https://www.avaya.com/doc/pv/productsandsolutions/ProductInformation-R5Installer500.zip.

Any help would be appreciated.

Andrew Roach
President
Drew Communications
Drew Telecom Group, Inc.
Lucent Voice Mail and Component Repair Specialists
Lucent Telecom Brokers/Resellers
drew@triton.net
616-498-9213

 

[systemkeeper]

I am glad to see that I am not the only one having problems with the Partner remote access. I have noticed the dial tone from the Intercom has affected the modem in my laptop. I listened in with a butin and noticed that it took several seconds for my laptop to recognize the odd dialtone.

I am having a problem with the RS232 port on a messaging card. It is set up for 2400 Baud instead of the 19200 the book says and most other Parnters I have work on. If power is cycled it spits out chkdsk 0 and I think chksum 0000 to Hyperterminal.

Could this be an older card than release 4?

 

[x28800]

You can set the dialtone type to regular dialtone .. I can't remember the setting name, but it is supported for exactly the reason you mentioned (allowing modems / fax machine to recognize dialtone more easily)

 

[x28800]

#309 ... To quote the manual:
"This System Programming procedure determines the type of dial tone that the system provides at an extension. It may be necessary to change this setting to Machine (outside line) dial tone for an autodialing device, such as a fax or modem, that has trouble making calls. For example, if you have a modem that checks for outside line dial tone before dialing, use this procedure to change from Regular to Machine dial tone."

 

[MWM]

Avaya tech support (White, Michelle D (Michelle) [mailto:michellewhite@avaya.com], Senior Engineer, Avaya, Inc. 720-444-5815) provided one bit of information regarding ACS 5.0 Remote Access which has allowed it to work for me: set the modem for 1200 (you read it correctly--1200!) It now performs the required tricks to step through the modem connect, session establish, download, revise, upload and restore proceedure.

I had previously tried (many hours!) to get a direct connect working: tried two PCs, with internal and three external modems, many variations of modem setup for compression, error correction, handshaking, init strings, etc. Nothing worked reliably. I had tried forcing connect speeds down to 4800 but not to 1200!

Also, she said that attempting an upload without first downloading would cause the Partner to reset its password ("reset" means NO password).

Yours,
Mike

 

[franke]

Just got around to reading some past links here and thought I'd add my two cents.

There seems to be alot of hair pulling with the remote access card, and I too went thru the same agony. For what it's worth, I found (with the help of AVAYA tech support, when they were still BP friendly & free) that the problem was with certain 308 modules plugged into slot 1. When I replaced the 308 module with a 206 or different PEC code 308, the remote access came right up. I should point out that this presents itself in being able to connect 'internally' but not remotely. Unfortunately, I don't have the PEC code of the affected 308 modules any longer.

Perhaps someone that still has a 'relationship' with tech support can find out and post it.