The Limit Number of Concurrent Calls (LNCC) feature causes a multi-call appearance endpoint to behave as a single line appearance endpoint. When the LNCC feature is enabled and the user is active/busy on one call appearance, subsequent incoming calls receive a busy signal or follow normal busy treatment such as coverage and are tagged as missed calls.
LNCC works on all H.323 and DCP endpoints and any SIP endpoint that supports call appearances.
A user controls this feature using a feature button or feature access code (FAC). Normal operation allows two incoming calls. The user must enable LNCC to allow only one call.
LNCC allows:
outgoing calls, incoming priority calls, and emergency callback for SIP stations.
outgoing calls, incoming priority calls, emergency callback, and crisis alert for H.323 and DCP stations.
LNCC works with the Dual Registration and Multiple Device Access features. The user applies LNCC at the user level, and all devices associated with the user inherit the LNCC feature. For example:
Most of the time, Steve wants to be active on only one call at a time, so he activates LNCC.
Andy calls Steve, and they talk for 15 minutes.
During their conversation, Cindy calls Steve. Because LNCC is active, Cindy’s call goes straight to coverage.
Cindy does not leave a message, but Steve’s endpoint still records her call as a missed call. Steve calls Cindy after he finishes his conversation with Andy.
The LNCC feature administration field appears on the station screen and is saved as part of the station record by the save translations command. Subsequent resets restore the LNCC settings to the state when the save translations was performed. A user activates and deactivates the feature by using the limit-call feature button or by using two Feature Access Codes: Limit Number of Concurrent Calls Activation/Deactivation. The limit-call button indicates whether the LNCC feature is active or not.
For more information about LNCC, see Avaya Aura® Communication Manager Feature Description and Implementation.
