Operation Manual

Timeout Transfer Loop
s
A31003-S2330-B692-3-7619, August 2003
HiPath Xpressions V3.0 Automated Attendant, User Guide
11
Introduction
2.9 Timeout Transfer Loops
Timeout transfer loops can occur if a caller does not answer (or stops answering) using DTMF
inputs, but also does not replace the handset. The timeout call transfers take the caller into a
loop within the CPA.
To avoid leaving a connection in a timeout transfer loop endlessly, the maximum number of di-
rectly consecutive timeout call transfers from CPM to CPM can be set in the CPAA under Sys-
tem Settings. If this number is exceeded during a connection, the connection is lost.
In addition, the CPAA testing function recognizes existing timeout transfer loops in the CPA de-
sign.
2.10 Testing Function
The testing function checks CP system data, such as the attendant name and number, default
fax mailbox, CPA-specific fax mailbox, etc.
When checking a CPA, the function tests all CPMs in use starting from the CPA start node (start
nodes if there are several).
This includes the following checks:
If the number of times an announcement should be played for a CPM is not zero, the
relevant announcement files must be available. Note here that if a CPM language has
not been entered, (i. e. Retain language is set for the CPM), all available CP system
languages are considered necessary. If a language has been set for the CPM, the
function just tests whether the announcement files exist for this language.
If a call transfer names another CPM as its destination, this CPM must exist.
If alternative destinations are in use, the relevant CPMs must exist.
For a "Listen/Respond" CPM, the relevant Xpressions mailbox, i. e. an Xpressions
user with the CPM name, must exist.
For access to an Xpressions mailbox in guest access mode, the Xpressions mailbox,
i.e. an Xpressions user with the given Xpressions mailbox name, must exist.
A CPM must not reference a "dead-end" and must define at least the timeout call trans-
fer. In addition, the function checks that the CPM is stored without timeout call transfers
at this point, although the setting interface does not allow this to happen.
Timeout transfer loops are recognized.