Lucent Technologies 555-230-220 Facility Restriction Levels FRLs, Forced Entry of Account Codes

ASAI and Feature Interactions

Facility Restriction Levels (FRLs)

Third Party Make Calls are placed using the originator’s COR, the station’s COR, or the split’s COR.

Forced Entry of Account Codes

Third Party Auto Dial or Third Party Make Call call attempts to Trunk Groups with the Forced Entry of Account Codes feature assigned are allowed. It is up to the originating station user to enter the account codes via the touch-tone pad. Account codes may not be provided via the ASAI. If the originator of such a call is logged into an adjunct-controlled split (and therefore has the voice set locked), such a user is unable to input the required codes and will eventually get denial treatment.

Hold

Manually holding a call (either by using the Hold, Conference, Transfer buttons, or switch-hook flash) results in the Hold Event Report being sent to all active associations for this call, including the held extension. A held party is considered connected on the call for the purpose of receiving events relevant to that call.

A party (listener) who is listen-disconnected can concurrently be put on hold and reconnected from the hold state. A party may be listen-disconnected while on hold. In this case, reconnecting from the held state will preserve the connections (no changes with respect to listen-disconnection).

Hot Line

A Third Party Auto Dial or a Third Party Make Call request made on behalf of an extension that has this feature administered is denied by the ECS. A station with hot line administered, will not be eligible for a Single-Step Conference request.

Hunt Groups

Groups used for originating Phantom calls should not mix such calls with real-time voice calls. Rather, separate hunt groups should be used. These hunt groups should not be ACD hunt groups.

Issue 7 May 1998 12-43