2N NetStar Admin manual - Manual (Page 104)

104
6.1 Global Parameters
Disable all new calls
Tick off the parameter to switch the PBX into a mode in which no new calls can be
made but active calls are not forcibly terminated. Trying to set up a call, the user fails
being played a defined message. This function is useful for servicing purposes.
Switch on regime ME
Use this option to switch your PBX into the Mobility Extension mode, which is
specifically used whenever the PBX is connected as a gateway between another PBX
and various types of private or public networks. When this mode is active, all the Flash
patterns and DTMF characters are sent directly to the opposite port of the PBX, which
does not respond to them. This function has nothing to do with the Mobility
Extension used for authorised external extensions!
Unselected as missed
This option sets the way of displaying missed calls. It refers to cases when an incoming
call is routed to a group of extensions or to one user with multiple extensions and is
answered by one of these extensions. If this option is not checked, missed calls are not
displayed. If it is checked, missed calls are displayed at all extensions except for the
one that has answered it.
Generate phone directories from users
Use this option to define the way of automatic generation of phone directories using
the list of users or extensions in the
Users – Phone directories – Group generated
menu. If this option is checked off, the phone directory is filled with user names and
respective internal numbers. If not, the phone directory is filled with extension names
and respective numbers.
Repeat destinations
With firmware v. 2.7.0 and higher, you can repeatedly route a call to one and the same
object. This is used, for example, for new routing in a bundle if the
Repeat cyclically
parameter is enabled.
Timeout – define the time interval after which the same call can be routed to
the selected object. If routed before the timeout end, the call is ignored by the
PBX.
Count – define the count of routing repetitions via one object for the given call.
When this count is completed, call routing is terminated in the next routing
attempt to this object.
An unduly low timeout value may result in a considerable PBX
overload due to call deadlock.