Displays the CTI user name. This field is read-only.

Displays the CTI user common name. This field is read-only.

Assigns a worktop to the CTI user.

Enables unrestricted access for the CTI user. When you enable this option, you grant the CTI user all permission types for all device groups.

Sets device groups on which the CTI user has Call Origination and Termination permissions.

Call Origination and Termination permissions include any operation that the user can perform on a phone. The CTI user can make calls and activate features, such as call forwarding and call transfer. By default, all CTI users have this permission for the devices associated with their worktop.

Sets device groups on which the CTI user has device monitoring permissions.

Applications monitor devices to receive event reports. For example, if a device receives an incoming call or makes an outgoing call, the application receives an event report. By default, all CTI users have this permission for the devices associated with their worktop.

Sets device groups on which the CTI user has call monitoring permissions.

Applications monitor calls on devices to track all events for a call when the monitored device receives it. Such applications usually monitor the extensions that receive a call to the contact center before distributing it to an agent. After the first extension receives the call, the monitoring application receives reports for all further events, such as transfers to queues and disconnecting calls. The applications that track the efficiency of contact center operations use this type of call monitoring.

Grants call monitoring permissions to the CTI user.

Applications use call monitoring to track events for a call using a call ID, a unique identifier of the call that the Routing Core Server handles.

Sets device groups on which the CTI user has routing control permissions.

When a routing application starts, it sends route registration requests to Routing Core Server. Each request contains a device ID. Routing Core Server sends all incoming calls from the required devices to the TSAPI service and then to the application for routing. Routing Core Server does not route calls. Before the route registration request is passed to the Routing Core Server, the TSAPI service checks if the routing application has permission to route calls for this device.