Disconnect Issues after CM3.1.1 upgrade 1

[manfmmd]

We are having a problem staying connected to our S8700 via ASA after we upgraded to CM3.1.1 from CM2.1. The system will disconnect us after we have been idle for "usually" more that 2 hours. Has anyone had this issue or know how to resolved it?

Thanks in advance.

manfmmd

 

[98Converter]

When you create a site in ASA, there is a spot in the wizard that has time-out settings... Try to adjust it there.

Thanks,
CJH

We are what we repeatedly do. Excellence, then, is not an act but a habit. ARISTOTLE 384-322 B.C.

 

[manfmmd]

Tried that.. We didn't make any changes except for the CM upgrade. Idle Timeout is set to "0".

 

[manfmmd]

Additional Information:

If I do a list history is shows a "logf" with the qualifier of "TIME-OUT". It is logging us off after 60 minutes according the the list history.

 

[Tolson]

we have run into the same issue after upgrading to version 3.0.1. Looks like Avaya is trying to protect us from ourselves again.

 

[manfmmd]

From:

http://support.avaya.com/elmodocs2/comm_mgr/r3_1/pdfs/03_300682_1.pdf

Administrable time-out for inactive SAT sessions
You can now administer the idle time that the system permits before the system shuts down a
SAT session. Set the Command Time-Out field on the Maintenance-Related System
Parameters screen to any value from 10 to 360 minutes.
The default value is 120 minutes.

It can also be set to blank.