Connection establishment using CTLS has the following restrictions
(in contrast to LCR):
- If SLMA stations are seized, any active transfers of ringing, call forwarding
no answer, call pickup groups and intercept cases are disregarded, provided
the SLMA station is configured in the same PBX as the station used for
CTLS or if the PBX where the SLMA station is configured is reached via
CorNet-NQ.
- Hunting group number: Any attempt to reach a station by dialing the
hunting group number is rejected if the station is configured in the
same PBX as the station used for CTLS or if this PBX was reached via
CorNet-NQ. Master hunting group: The master is seized if the hunting
group number is dialed. The hunting group function is ignored, if the
station is configured in the same PBX as the station used for CTLS or
if this PBX was reached via CorNet-NQ.
- If an interim destination reached using CTLS is busy, the connection
can only be reestablished, after the caller goes on-hook. Rerouting is
not performed.
- A CTLS entry cannot be saved for number redial. Strings, and parts
thereof, with a maximum length of 22 characters can be saved under destination
and repertory keys.
- Callback on busy and free is not possible.
- During an active CTLS connection all third-party features such as
consultation hold, transfer, broker's call, conference, etc.) are
blocked for the dialing station.
- It is not possible to establish a CTLS connection from a third-party
connection.
- The destination reached using CTLS cannot activate any third-party
features during the connection if the destination is configured in the
same PBX as the station using CTLS or if this PBX was reached via CorNet-NQ.