Version 5.6
157
November 2008
SIP User's Manual
3. Web-Based Management
Parameter
Description
it sends a 183 Session Progress message with SDP in response to
only the first received ISDN Proceeding or Progress message after a
call is placed to PBX/PSTN over the trunk.
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:
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.
Note:
The Busy Out behavior varies between different protocol types.
Default Release Cause
[DefaultReleaseCause]
Defines the default Release Cause (sent to IP) for IP-to-Tel calls when
the device initiates a call release and an explicit matching cause for this
release isn't found.
The default release cause is NO_ROUTE_TO_DESTINATION (3).
Other common values include NO_CIRCUIT_AVAILABLE (34),
DESTINATION_OUT_OF_ORDER (27), etc.
Notes:
The default release cause is described in the Q.931 notation and is
translated to corresponding SIP 40x or 50x values (e.g., 3 to SIP 404
and 34 to SIP 503).
When the Trunk is disconnected or is not synchronized, the internal
cause is 27. This cause is mapped, by default, to SIP 502.
For mapping SIP-to-Q.931 and Q.931-to-SIP release causes, refer to
Содержание Mediant 2000
Страница 1: ...Document LTRT 68808 November 2008 User s Manual Version 5 6 ...
Страница 2: ......
Страница 18: ...SIP User s Manual 18 Document LTRT 68808 Mediant 2000 Reader s Notes ...
Страница 83: ...Version 5 6 83 November 2008 SIP User s Manual 3 Web Based Management Figure 3 47 Trunk Settings Page ...
Страница 254: ...SIP User s Manual 254 Document LTRT 68808 Mediant 2000 Reader s Notes ...
Страница 334: ...SIP User s Manual 334 Document LTRT 68808 Mediant 2000 Reader s Notes ...
Страница 342: ...SIP User s Manual 342 Document LTRT 68808 Mediant 2000 Reader s Notes ...
Страница 408: ...SIP User s Manual 408 Document LTRT 68808 Mediant 2000 Reader s Notes ...
Страница 414: ...SIP User s Manual 414 Document LTRT 68808 Mediant 2000 Reader s Notes ...
Страница 418: ...User s Manual Version 5 6 www audiocodes com ...