| more topics
|
The Transfer and Conference features, when activated manually (using the telephone) at a non-operator extension, do not provide the original caller's information to the recipient who has screen pop capability.
Transferred calls fom non-local extensions can only initiate the correct screen pop when the transfer is without consultation and the private network systems are connected by PRI tandem trunks. Otherwise, only the transfer originator information is available for screen pop. If the private network trunks are tandem tie trunks, they do not convey screen pop information over the private network.
When a DLC is not using a CTI application, calls transferred from a DLC's programmed Cover button do not initiate screen pop, even when the destination is a screen pop-capable extension.
The CTI link programming requires that you busy-out the control unit slot where the MLX module with the CTI link is being added or removed. If the slot that is being programmed is the slot used for the system programming console, you must use the WinSPM software to program the CTI link. The busy-out programming procedure is available from the system's Maintenance menu. For details about busying-out a slot in the control unit, see the Maintenance and Troubleshooting guide.
You cannot program the first or fifth port on an MLX module as the CTI link extension, because these ports are reserved for operator positions. On the 016 MLX module there are potential operator positions on the ninth and thirteenth ports, as well as on the first and fifth ports.
If you program a CTI link for a jack that is already programmed for 2B data, the CTI programming overrides the 2B data programming, and a 2B data device that you later connect to the jack will not function as such. You cannot use a system programming port as the CTI link extension.
You cannot program a port as a CTI link if it has a telephone or other device connected to it. However, the port may have the CTI link hardware plugged in.
Because CTI link programming requires that you busy-out the control unit slot where the MLX module with the CTI link is being added or removed, either you must use SPM software to program the CTI link, or the link must be located on a different module from the one where the system programming MLX-20L console is connected. The busy-out programming procedure is available from the system's Maintenance menu. For details about busying-out a slot in the control unit, see the System Manager's Guide.
An extension programmed as a CTI link should not be used as a phantom extension (an extension that does not serve equipment plugged into the system but used for a special purpose--for example, coverage by a voice messaging system).
If you are on a client extension with a call on an analog Centrex loop-start line and you attempt to transfer that call to an extension with Centrex Transfer via Remote Call Forwarding activated, the call is immediately transferred without consultation. The originator is disconnected.
