9.8.4 |
Intercept / Attendant |
| The attendant is configured via Intercept / Attendant. When an incoming call cannot be completed, either because the number is incorrect or because the called party does not answer, the call is forwarded in accordance with the criteria established in the Call Management (see Settings | Incoming calls). The call is then diverted to the intercept position. |
9.8.4.1 |
Area: Intercept position |
| The call number of the intercept position is defined here. The intercept position can be a single station or group. A UCD group may not be selected as an intercept position. The handling of the call forwarding occurs via Settings | Incoming calls. Then the intercept is made to the intercept position. |
| On S0-lines, an evaluation takes place only when no day/night intercept position has been set up. |
| As of Hicom 150 E Office Rel. 2.0, default key assignments are automatically given for the intercept places (both day and night) that are defined here. This happens only when the intercept position is a telephone, not when it's a group. In the latter case, the same functionality can be achieved by defining the telephone as an intercept position for a short time. The default key assignment has also the Number of calls key. This can be assigned to only 6 telephones. If the limit has been reached, no more default key assignments are made. The assigned default keys are not cancelled when a device is no longer defined as an intercept position. |
|
Day, Night |
| The intercept position can be defined separately for Day and Night. In addition, it is also possible to enter any destination when activating the night service (variable night service). |
9.8.4.2 |
Area: Central intercept position (not in the USA) |
| This is a European feature that is not in use in the United States. |
| It is possible to define a central intercept position. The central intercept position defines the (common) intercept position for QSIG- and CorNet networked communication systems. It is necessary to add a trunk group index to the call number first. Note that when the digit repetition between the trunk group index and the call number is active, a valid seizure code should be inserted for the trunk group selected. |
|
9.8.4.3 |
Area: Intercept to intercept position |
| Six different intercept conditions exist. You can choose which of these criteria should be active. You can select any number of criteria. |
On RNA |
| When on RNA (Ring No Answer) is activated, the call follows the defined procedure (see Settings | Incoming calls). If the end of the table is reached and does not answer, the system checks to see whether or not intercept after timeout applies. In this case, the intercept position is called after the number of rings specified under Call forwarding. |
| A call is not intercepted from a hunt group. The call is forwarded again to the first hunt group station and continues to remain in the hunt group. |
On Busy |
| If a line is on Busy, the system first checks to see whether or not a waiting call can be signaled. If it is not possible to signal a waiting call (call waiting rejection or intercept criterion), then the call follows the Call Management procedure (see Settings | Incoming calls). |
| If the call cannot be signaled at any station, the system checks to see whether intercept or clear-down applies (B signal to CO). If an analog telephone with call waiting rejection is busy, the call is cleared down, regardless of trunk type. In the case of DTMF direct inward dial and MSI, the call is always intercepted. |
On Invalid |
| If this flag is on, when a wrong number is dialed, the system checks to see whether intercept or clear-down applies. In the case of DTMF direct dial, the call is always intercepted. |
On Incomplete |
| If the station number dialed is incomplete, the intercept position is called at the end of the time defined in the End-of-Selection for Incomplete Dialing field under Time parameters. |
On Unanswered Recall |
| If an external call is not picked up by the B subscriber after the A subscriber implements Transfer before answering to the B subscriber, and the call is still not picked up after a recall to the A subscriber is implemented, the intercept position defined in the Intercept time for recall field under Time parameters is called after a defined period. |
| If this flag is not set, the call is cleared down after the defined period. |
On More Than Two Calls to P.O.T. (France only) |
| This feature is available only in France. |
| If call waiting is signaled during an ongoing call with an analog telephone, any further call is rejected. |
9.8.4.4 |
Area: Codelock intercept |
| If the telephone lock for a station is active and a trunk group code is dialed from that station, the call is immediately forwarded to the intercept destination entered here. This means that if a user dials a number that is not authorized, the call will be signaled on the station number assigned here. The Codelock intercept function is set individually for each station via Station view: Flags. |
9.8.4.5 |
Area: Attendant code |
| The intercept defined under system parameters can be reached using both the internal extension number or the DID number and the console code (internal and external calls). |
Call Number Internal |
| This is the number used by internal devices to reach the Intercept position. |
| After changing the internal call number of the attendant and transferring the CDB, a download to the IVM is triggered automatically. |
Call Number External |
| This is the number used by DID or network (CorNet-N or CorNet-NQ) to reach the Intercept position. |
9.8.4.6 |
Area: Attendant |
| There are several parameters regarding the attendant. |
Queued Calls |
| In the Queued Calls field, you define the maximum number of calls that can wait in the Attendant queue. If the number of stations waiting in the queue of the attendant reaches this numerical value, the calls are forwarded to a Configurable overflow destination. |
Wait Time |
| Here you enter the number of seconds that a call can wait in the queue. When calls exceed this time, they are diverted to Call forwarding defined via the Call Management (see Settings | Incoming calls). |
Speed Extending |
| If this flag is set, the attendant can transfer the call to another party by entering the station number for that party. This speed call transfer can only be used when the system flag DTMF automatic is deactivated. |
Extend undialed lines (up to Release 1.0) |
| If the 'extend undialed lines' flag is set, an undialed trunk can be transferred to a subscriber via the local attendant console (AC) so that this subscriber is able to conduct an external call. |
| The subscriber to whom an undialed trunk is transferred also receives the toll restriction of the attendant console for this call. This means: |
| 1. | If, for example, the attendant console has unrestricted local area access, then this access is also assigned to the subscriber to whom a trunk is transferred. |
| 2. | If a trunk is transferred to a subscriber, this transferred trunk is valid for only one dialing operation. |
| The feature can be used from the local attendant console (not for the entire network) or from any attendant console, from an attendant console group, or from the night station. |
Extend undialed lines (as of Release 2.2) |
| An authorized subscriber (attendant console AC) can transfer an undialed trunk to an internal subscriber who does not have sufficient direct trunk access so that this subscriber can conduct exactly one external call. |
| After the trunk is transferred to the subscriber without sufficient direct trunk access, toll restriction takes place based on an additional direct trunk access for transferred trunks. The outgoing external call is allowed only if this additional direct trunk access is sufficient, for example, if the subscriber dials a valid number according to the denied or allowed list for transferred trunks. |
| The subscriber must dial the seizure code on a transferred trunk. |
| A CO call privilege can be configured in the communication system for each trunk group via a reference subscriber. The default reference subscriber is the first logical subscriber port or the attendant console. The default setting is set to unrestricted trunk access for all trunk groups. |
9.8.4.7 |
Area: Other criteria |
| Call Waiting on Busy |
| This flag activates the Call Waiting feature for all stations in the communication system. The following are two examples of how the call waiting feature operates (see also Station view: Flags). |
Example 1: |
| When Call waiting on busy is activated, an external caller (A) hears the ring tone when calling the busy station (B). Station B is notified by a display message that a call is waiting and hears the call waiting tone on the voice channel. Station B can now answer the waiting call using the Accept call waiting function. This action automatically places the existing call on exclusive hold. |
Example 2: |
| If the station is busy and intercept on busy is active, the caller will be intercepted at the attendant which can then call the destination station and signal call waiting in order to switch the call. This only works if the destination station has not activated Call waiting rejection. |
Call waiting only for intercept |
| This flag is only relevant for CorNet networked systems. |
| • | If the flag is set, call waiting is only allowed when an attendant console (system A) calls station B (system B). All other stations of system A cannot reach system B via call waiting. For the stations in System B, the condition for call waiting rejection (see Station view: Flags) applies to the respective stations. |
| • | If the flag is not set, all calls to busy stations in another system are switched through via call waiting, provided the station has not turned on the call waiting rejection option. |
| This flag must be set if you want to place the calling intercept on hold immediately and enable call waiting when a station is busy. If this flag is not set, the intercept receives the busy signal and is only placed on hold after a few seconds. |
Intercept with serial FWD (Call forwarding) |
| It is not possible to chain calls for forwarding; an attempt to initiate this procedure is rejected on activation. For example, if a station has activated external call forwarding and the call destination has also forwarded its calls, you have a chained calls situation. This is not allowed by the communication system. If this flag is turned on, these calls are intercepted. As of Hicom 150 E Office Rel. 2.2 (Version 159; SMR-J), this flag ihas been deleted. A chain of call forwarding instances is now possible. |
| HiPath 3000/5000 V8, Manager E, Administrator Documentation, Issue 11 | up  |
|
 |
||
| Disclaimer & Copyright | ID: P31003H3580M1000176A9 | 2011-03-18 |
