Remote Access Session Initiation Failure 1

[MattsDad]

I recently upgraded to Partner ACS R6.0, with remote access. I can dial, and apparently connect with modem internally, through direct connnect and 76, I get a message saying connected at 14400, and then a long pause and an error message advising that "Session Iniation has failed." Is there something I am missing, or does anyone have a suggestion for a solution? Thanks, jim

 

[392]

From a previous post, but still valid:

I maintain literally hundreds of Partners via remote, there are a couple of tips to follow. First, when using operator assisted connection (transfer 76), click the "OK" button when you hear it ring, but remain on the phone. Once the modems connect and begin to handshake, hang up GENTLY. Some phones will introduce a hookswitch or flash if not hung up gently. Taking the handset cord out of the receiver can leave the load of the extra 2500 set in the connection, possibly lowering quality of the connection. Using a splitter at the point the line enters the modem for your telephone rather than the telephone jack on the modem also helps. Be sure to set your port speed at no more than 38600, some say 9600 is better, others say 2400 or 1200. Just be sure port speed is not maxed out at 115000 (default), as you'll get carrier but no data flow. When you load the password under #730, immediately do a #124 and backup your system. All future backups and uploaded/restored translation files will not disturb your password if you do this. Be sure you use the latest remote software, as there were bugs in many editions. The current, functional level is 5.0.0.7 6.0.0.9. I have 3 systems that will not establish a session no matter the line called on, called from or technique used. They do connect locally from an extension port, however. This has been traced to line quality issues at the local CO or facilities in the "last mile". Can't win on those; Qwest and PacBell refuse to do anything beyond making them of "voice quality".

Also: for the absolute worst connections, set modem speed to 2400 and it will connect. Some say using W98 is the best platform; that I can't vouch for as it's the only platform I use. Also, be sure to power cycle the switch after an upgrade to "clean it up". All said, you should be able to connect well locally, even if you have to bump it down to 9600.

 

[itpphoneguy]

Hi MattsDad,
You definitely have a problem somewhere. Can you connect on a station port by dialing ext 76 directly? If you can't, then the system has a problem. Listen to intercom dial tone with the dial tone broken (say, dial "1&quot. If you hear noise on a good station port, search in the system. I had a Partner VS R4 that caused this problem on the only system I couldn't connect. A Messaging R1 solved that issue. (2400 didn't help there)
-Chris

 

[rkochis]

Hello all,

I am having the same problem at even 2400 baud on three seperate switches. Could the reason be that my modem travels through a PBX to get to remote sites? I am using a USR Sportster 33.6 faxmodem.

Thanks in advance, Bob

 

[itpphoneguy]

Hi Bob,
Can you connect okay to any of your sites? If you can, then your problem is either at or before those sites. Could even be your telco! I am guessing you can connect while on the system. (direct dial ext76 through your modem onto a station port).
I can dial into all my sites with multiple machines. They are ACS 3.0 through ACS 6.0. Many different sites (48).
I have used your type of modem, so the fault isn't there.
-Chris