Cisco Cisco IP Contact Center Release 4.6.1 Technical References
Dynamic Configuration Settings
41
than are actually available on the switch, errors will occur. This may include
the dropping of calls from the system or Avaya Gateway shutdowns and
restarts.
the dropping of calls from the system or Avaya Gateway shutdowns and
restarts.
The entry “1-n” in the Valid Values column indicates that you should enter
as many Cluster IDs as are available to the Avaya Gateway. If there are no
other applications using Cluster IDs, then these values can be set to the
maximum for the version of the Avaya G3 switch.
as many Cluster IDs as are available to the Avaya Gateway. If there are no
other applications using Cluster IDs, then these values can be set to the
maximum for the version of the Avaya G3 switch.
4.2. Dynamic Configuration Settings
Dynamic configuration settings are those settings that take effect
immediately without restarting the Avaya Gateway.
immediately without restarting the Avaya Gateway.
Table 17 shows the Config Registry entries.
Table 17: Config Registry Entries
Registry
Key String
Key String
Valid
Values
Values
Default
Value
Value
Description
GatewayPB
XHeartbeat
Interval
XHeartbeat
Interval
1-150
15
This is how often (in seconds) that the
Gateway will send a heartbeat request
to the PBX.
Gateway will send a heartbeat request
to the PBX.
GatewayPB
XHeartbeat
Timeout
XHeartbeat
Timeout
1-150
10
Time to wait (in seconds) for heartbeat
response from the PBX before
considering the connection “down”.
response from the PBX before
considering the connection “down”.
StateMachi
neHangInte
rval
neHangInte
rval
1-600
6
This is how often (in seconds) that the
running State Machines will be checked
to see if any are hung.
running State Machines will be checked
to see if any are hung.
StateMachi
neHangTim
eout
neHangTim
eout
1-600
7
Timeout value for State Machines (in
seconds). If a State Machine has not
received a message for processing in
this amount of time, the Watchdog
Thread will assume the State Machine
is “hung” and will send a “Hung”
message to the State Machine to allow
it to clean up before being destroyed.
seconds). If a State Machine has not
received a message for processing in
this amount of time, the Watchdog
Thread will assume the State Machine
is “hung” and will send a “Hung”
message to the State Machine to allow
it to clean up before being destroyed.
PIMMsgTi
meoutInter
val
meoutInter
val
1-600
30
This is how often (in seconds) that the
Gateway will check the time that the
last message came in from the PIM in
order to determine if the interface to the
PIM is “down” or not. If the last PIM
message was received more than the
timeout value (in seconds) in the past,
the Gateway will shut down in order to
reestablish the connections. If there are
no calls occurring, the PIM should still
be sending heartbeats to the Gateway to
verify connectivity.
Gateway will check the time that the
last message came in from the PIM in
order to determine if the interface to the
PIM is “down” or not. If the last PIM
message was received more than the
timeout value (in seconds) in the past,
the Gateway will shut down in order to
reestablish the connections. If there are
no calls occurring, the PIM should still
be sending heartbeats to the Gateway to
verify connectivity.