.
Is there a way to disable connection preservation on SIP trunks in Communication Manager?
System: CM5.2, G650, TN799DP, TN2602, Meeting Exchange 5.2
When the far end of a SIP trunk looses connection (network or shutdown) CM sets the trunk group to pending-busyout on active TDM terminal calls after about 1 minute. It then takes from 3-10 minutes for the active calls to be forced to drop. The problem is, if this is a conference net that is left up to be monitored, there is no indication during the <10 minutes the far end is down and the call needs to be establed to a backup server. The network administration guide describes this as call or connection preservation. The behavior is the same wether the far end is meeting exchange, SIP enablement server, or another CM server (CLAN).
Trunk group setting "preferred minimum session refresh interval" is set to lowest value.
System: CM5.2, G650, TN799DP, TN2602, Meeting Exchange 5.2
When the far end of a SIP trunk looses connection (network or shutdown) CM sets the trunk group to pending-busyout on active TDM terminal calls after about 1 minute. It then takes from 3-10 minutes for the active calls to be forced to drop. The problem is, if this is a conference net that is left up to be monitored, there is no indication during the <10 minutes the far end is down and the call needs to be establed to a backup server. The network administration guide describes this as call or connection preservation. The behavior is the same wether the far end is meeting exchange, SIP enablement server, or another CM server (CLAN).
Trunk group setting "preferred minimum session refresh interval" is set to lowest value.
.
Comment