Using the PSA associate command

Last Updated : Nov 27, 2012 |

About this task

To use the PSA associate command, perform the actions shown in the table.

Table 1: PSA associate commands

Step

User action

System response

Result

1

Dial the Feature Access Code (FAC) for PSA associate.

Dial tone

The request is successful.

Intercept tone

  • The request is unsuccessful, because the request was not made at an analog, a hybrid, or a DCP telephone.

  • The request is unsuccessful because the telephone is associated with or assigned to a station that does not have PSA permission in its COS.

2

Dial an extension, and then press #.

No response

If the user is at a telephone with a display, this pound sign (#) is the last character that the system displays until the PSA sequence is complete.

3

Dial the Station Security Code (SSC) for the user extension, and then press #.

Confirmation tone

The command sequence is successfully complete. The system queues the request.

Intercept tone immediately after the confirmation tone.

The request is unsuccessful, because:

  • Terminal translation initialization (TTI) is disabled for voice.

  • Either the dialed extension or the originating extension has an add, a change, or a remove action in progress.

  • You dialed more than 15 digits before you pressed #.

Issue the PSA request again.

Intercept tone

The request is unsuccessful because:

  • The extension and the SSC are incompatible.

    • The extension is invalid.

    • The SSC is invalid for the extension.

    • Both the extension and the SCC are invalid.

      The Security Violation Notification (SVN) feature logs this unsuccessful use of PSA as an invalid attempt.

  • The Class of Service (COS) of the extension does not allow PSA.

  • An extension in one tenant partition cannot be associated with a telephone in another tenant partition.

Reorder tone

The request is unsuccessful because:

  • The extension that was entered is in use.

  • An agent is logged in at the dialed extension.

  • The system load is too heavy for the request to occur.

The user can try again later.