3Com V7122 User Manual page 195

ini File Field Name
Web Parameter Name
EnableSemiAttendedTransf
er
[Enable Semi-Attended
Transfer]
3xxBehavior
[3xx Behavior]
MaxActiveCalls
[Max Number Of Active Calls]
MaxCallDuration
[Max Call Duration]
EnableBusyOut
[Enable Busy Out]
V7122 Gateway User Guide
Valid Range and Description
Determines the gateway behavior when a Transfer is initiated while still in
Alerting state.
Valid options include:
0 = Send REFER with Replaces (default).
1 = Send CANCEL, and after a 487 response is received, send REFER
without Replaces.
Determines the gateway's behavior when a 3xx response is received for an
outgoing INVITE request. The gateway can either use the same call
identifiers (CallID, branch, to and from tags) or change them in the new
initiated INVITE.
0 (forward) = Use different call identifiers for a redirected INVITE message
(default).
1 (redirect) = Use the same call identifiers.
Defines the maximum number of calls that the gateway can have active at
the same time. If the maximum number of calls is reached, new calls are
not established.
The default value is max available channels (no restriction on the maximum
number of calls). The valid range is 1 to 240.
Defines the maximum call duration in minutes. If this time expires, both
sides of the call are released (IP and Tel).
The valid range is 0 to 120. The default is 0 (no limitation).
0 = Not used (default)
1 = Enable busy out
If Busy out is enabled, all E1/T1 trunks are automatically put out of service
by sending a remote alarm (AIS) or Service Out message for T1 PRI trunks
that support these messages (NI-2, 4/5-ESS, DMS-100 and Meridian), due
to one of the following scenarios:
Physically disconnected from the network (that is, Ethernet cable is
disconnected).
The Ethernet cable is connected, but the gateway can't communicate
with any host. Note that LAN Watch-Dog must be activated
(EnableLANWatchDog = 1).
The gateway can't communicate with the gatekeeper/proxy (according
to the Proxy keep-alive mechanism) and no other alternative exists to
send the call.
The Busy out behavior varies between different protocol types.
195