2N NetStar Admin manual - Manual (Page 165)

165
Bundle conduct
Cause object – use this option to select one of the cause objects as pre–defined
in the
menu. These objects represent a Global data – Causes – Cause objects
set of causes to be responded to by the bundle. When one of the cause objects
has been selected, the
and options are Respond to busy Respond to reject
disabled automatically.
Cause object for queue – select this option to route an incoming call with
queue to all the bundle destinations that have not returned the cause defined in
the selected cause object.
Respond to busy – use this option to route an incoming call to the next row in
case the object is busy. This increases the successful routing rate. Here cause 17
– User Busy – is relevant only.
Respond to reject – use this option to route an incoming call to the next row if
rejected by the called user. Here cause 21 – Call reject is relevant only.
Route to next row at no answer – use this command to proceed to the next
bundle row in case the call is not answered within the timeout defined in the No
parameter or under causes 18 – No user responding – and answer timeout [s]
19 – No answer from user.
Let ring the last call – if this option is checked and Route to next row no
is used, the incoming call is not routed to the Default destination after answer
routing to the last unused object, but it rings at the last destination. The last
unused object need not be the object from the last row of the bundle.
Repeat destinations – if this option is cheked off and proceeding to the next
row on busy is applied, the call is not routed to the default destination after the
last bundle record, but routing starts from the first bundle record again. First
means the
within this incoming call. A timeout for repeating First used
destinations and acceptable count of repetitions is defined in the Global
parameters for convenience and deadlock protection. If a call is routed to a
destination before the timeout expires, the destination pretends to be
unavailable.
Default alert tones
In this section select variable alert tones for specific situations.
Normal – sets the alert tone to be used in all situations except for the two cases
mentioned below.
Queued – sets the alert tone to be used for routing to a extension with an active
queue. The incoming call has to be queued, otherwise the normal alert tone is
used.
No–port extension – sets the alert tone to be used for routing to the user with
a no–carrier extension (external extension). Such user has to be assigned an
external extension and another internal (active) extension at least. Otherwise,
you will hear another alert tone.
Default destination
Here select a destination to be used whenever the call is rejected on the last bundle
destination, the next row proceeding timeout expires, or the call cannot be delivered
for any other reasons (all destinations are busy or logged out). Default destination
routing depends on the
settings. Bundle conduct
In addition to the above mentioned parameters, an object adding table is available.