Cause
The endpoint called has indicated an inability to accept another call.
This cause value has end-to-end significance and must always be passed back through the network to the user.
Proposed Solution
Procedure
- Wait and redial the number later.
- Check the cause value Information Element (LOC).
- If the Location Information of the cause value is 0 (User), the endpoint is busy.
- If the Location information of the cause value is 4 (Public Network Serving Remote User), neither the trunk group to the remote endpoint location is experiencing an all-trunks-busy condition or insufficient channels are allocated to a virtual group for the particular NSF of the call.
- If Communication Manager generates this cause value and the endpoint is free or available, the following translations and features affect the call:
- Trunk or station Class of Restriction (COR) or both prevent the call from terminating at the called endpoint.
- The endpoint is call-forwarded and this is the second call within the 30-second time limit on a station that is forwarding this call.
- Trunk group form: CBC service type: The Usage Allocation field is y. The usage allocation plan has not allocated enough incoming channels for the NSF associated with this call.
- VDNs and Call Vectoring: The vector associated with the VDN is incorrectly programmed, and the call is inappropriately sent to a busy vector step. The skill/Automatic Call Distribution (ACD) group that the call attempts to join has a full queue and cannot accept any more calls. Look Ahead Interflow/Best Service Routing (LAI/BSR) has received an inappropriate ISDN response while checking other sites for available agents and has inadvertently returned busy feedback to the caller. The LAI/BSR attempt is interacting with the public network features Egress on busy – overflow to POTS, Alternate Destination Routing (ADR), or Alternate Destination Call Redirection (ADCR). Analyze the vector processing of the call and the call flow to determine the cause of the failure.