User`s manual

H.323 User's Manual 5. Web Management
Version 5.0 83 December 2006
Table 5-7: Advanced Parameters, General Parameters (continues on pages 80 to 84)
Parameter Description
Debug Level
[GwDebugLevel]
Syslog logging level. One of the following debug levels can be selected:
0 [0] = Debug is disabled (default)
1 [1] = Flow debugging is enabled
2 [2] = Flow and device interface debugging are enabled
3 [3] = Flow, device interface and stack interface debugging are enabled
4 [4] = Flow, device interface, stack interface and session manager debugging
are enabled
5 [5] = Flow, device interface, stack interface, session manager and device
interface expanded debugging are enabled.
6 [6] = Flow, device interface, stack interface, session manager and device
interface expanded debugging are enabled. In addition, all H.323 messages
are printed according to their ASN.1 format.
Note: Usually set to 6 if debug traces are needed.
Misc. Parameters
Progress Indicator to IP
[ProgressIndicator2IP]
No PI [0] = Progress Indicator (PI) isn’t set in the H.225 Alert messages.
PI = 1 [1] = Progress Indicator is set to 1 (PI = 1) in the sent H.225 Alert
messages.
PI = 8 [8] = Progress Indicator is set to 8 (PI = 8) in the sent H.225 Alert
messages.
Not Configured [-1] = Default values are used.
The default for FXO modules is 1; The default for FXS modules is 0.
Enable X-Channel Header N/A
Enable Busy Out
[EnableBusyOut]
No [0] = ‘Busy out’ feature is not used (default).
Yes [1] = ‘Busy out’ feature is enabled.
When Busy out is enabled and certain scenarios exist, the gateway performs a
specific behavior depending whether it's an analog or digital gateway:
 Analog gateways: a reorder tone (determined by FXSOOSBehavior) is
played when the phone is offhooked.
 Digital gateways: 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)
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 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.
Notes for Analog gateways:
 The FXSOOSBehavior parameter is used to control the behavior of the
FXS endpoints of the gateway when a Busy out or Graceful Lock occurs.
 FXO endpoints during Busy out and Lock are inactive.
 Refer to LifeLineType parameter for complementary optional behavior.
Note for Digtal gateways: The Busy out behavior varies between different
protocol types.
Default Release Cause
[DefaultReleaseCause]
Default Release Cause (to IP) for IPÆTel calls, used when the gateway
initiates a call release, and if an explicit matching cause for this release isn’t
found, a default release cause can be configured:
The default release cause is: NO_ROUTE_TO_DESTINATION (3).
Other common values are: NO_CIRCUIT_AVAILABLE (34) or
NETWORK_OUT_OF_ORDER (38), etc.
Note: The default release cause is described in the Q.931 notation, and is
translated to corresponding to H.323 NetCause equivalent value.