Response If Unobtainable - Aastra 400 Series System Manual

Call routing
6. 3. 4

Response if unobtainable

Various redirection destinations can be configured for each user so that ideally no
calls are left to idle for whatever technical reasons. The call is then redirected de-
pending on why the terminal is unobtainable and the call's origin (internal/exter-
nal). A user is considered to be unobtainable only if none of his allocated terminals
can be reached. Possible redirection destinations include internal and external us-
ers, PISN users, abbreviated dialling numbers, user groups, call distribution ele-
ments, etc.
There are three categories of reasons why a terminal may be unobtainable:
Category 1: Terminal not running or out of DECT coverage range
• A desk phone is not connected
• A cordless phone
– is outside the coverage range
– is switched off or its battery is empty
– is not logged on
• A softphone (IP terminal) is not started up or not connected to the IP network
Note:
Analogue terminals that are not connected cannot be detected.
Examples of sensible redirection destinations:
user's voice mailbox, switching centre.
Category 2: No VoIP channel available at present
An IP terminal or a user on a different node in an AIN cannot be reached momen-
tarily because
• the configured bandwidth between the nodes in accordance with the band-
width model is being used to capacity.
• all VoIP channels of the DSP chips are occupied.
• the licence limit for the number of simultaneously active VoIP channels has been
reached.
Examples of sensible redirection destinations:
User's external call number, user's mobile number, general voice mailbox, switch-
ing centre.
200
System functions and features as of R3.0
syd-0367/1.3 – R3.0 – 03.2013