User`s manual

Version 5.4 173 May 2008
SIP User's Manual 3. Web-Based Management
Parameter Description
Enable X-Channel Header
[XChannelHeader]
Determines whether the x-channel header is added to SIP messages for
trunk / B-channel information.
 [0] Disable = x-channel header is not used (default).
 [1] Enable = x-channel header is generated with trunk/B-channel and
IP address information.
The header provides information on the E1/T1 physical trunk/B-channel
on which the call is received or placed. For example, 'x-channel:
DS/DS1-5/22;IP=192.168.13.1', where 'DS/DS-1' is a constant string, '5'
is the trunk number, '22' is the B-channel, and in addition, the device's IP
address is added to the header. This header is generated by the device
and is sent in INVITE messages and 183/180/200OK responses.
Enable Busy Out
[EnableBusyOut]
Determines whether the Busy Out feature is enabled.
 [0] Disable = 'Busy out' feature is not used (default).
 [1] Enable = 'Busy out' feature is enabled.
When Busy Out is enabled and certain scenarios exist, the device
performs the following:
Mediant 1000 Analog interface: A reorder tone (determined by
FXSOOSBehavior) is played when the phone is off-hooked.
Digital interface: All E1/T1 trunks are automatically taken out of service
by taking down the D-Channel or by sending a Service Out message for
T1 PRI trunks supporting these messages (NI-2, 4/5-ESS, DMS-100,
and Meridian).
These behaviors are performed due to one of the following scenarios:
 Physically disconnected from the network (i.e., Ethernet cable is
disconnected).
 The Ethernet cable is connected, but the device can't communicate
with any host. Note that LAN Watch-Dog must be activated
(EnableLANWatchDog = 1).
 The device can't communicate with the proxy (according to the Proxy
keep-alive mechanism) and no other alternative exists to send the
call.
 The IP Connectivity mechanism is enabled (using
AltRoutingTel2IPEnable) and there is no connectivity to any
destination IP address.
Notes for Mediant 1000 Analog interfaces:
 The FXSOOSBehavior parameter controls the behavior of the FXS
endpoints when a Busy Out or Graceful Lock occurs.
 FXO endpoints during Busy Out and Lock are inactive.
 Refer to the LifeLineType parameter for complementary optional
behavior.
Note: The Busy Out behavior varies between different protocol types (for
Digtal interfaces).