AT&T 555-230-520 manual Eas, Vector Initiated Service Observing Security

EAS

capabilities described in the previous section can also be used. Instead of routing to the remote access extension, the vector collects digits from the caller and then routes to the given destination if there is a match on the password.

Again, multiple VDNs can be created for individuals or groups with different security checks and different permissions and/or restrictions. Destination numbers provided by callers can be screened by the vectors and denied if the user does not have permission to access that destination. For example, an individual user could be restricted to placing calls to numbers beginning with area codes ‘‘303’’and ‘‘908.’’

EAS

With EAS, agents’ voice terminals can be locked when the terminal is not staffed. This is accomplished by assigning the voice terminals a Class of Restriction that does not allow outbound calls or it could be restricted from toll calls.

EAS agents have an optional password of up to nine digits to log in. This password is not displayed on DCP terminals when the agent is entering the password on the dial pad.

Vector Initiated Service Observing

Security

The following restrictions can be used with vector initiated Service Observing (G3V4 and later releases) to guard against unauthorized use.

■Call prompting commands can be used in Service Observing vectors to provide passcode protection, and to limit access to observing specific destinations or verified caller entered digits.

■Time of Day/Day of Week checks can be incorporated in Service Observing vectors.

■A vector can be created to be used exclusively for Service Observing.

■For a VDN to be observed as the result of a route-to command, the VDN must have a COR that allows it to be observed.

■The calling permissions of the COR assigned to the Service Observing VDN in conjunction with the “can be observed” settings of the COR assigned to the destination determine what agents, stations, or VDNS can be observed.

Issue 4 September 1995 I-3