Handling API Overflow
Recovers call handling when the API connection between CCaaS and RC/ACO drops, so agents stop receiving calls they cannot answer.
When the API connection between CCaaS and RC/ACO drops, agents can be presented with calls they're unable to answer. The primary symptom of this scenario is agents receiving ringing calls that cannot be picked up. Recovering from it requires a change on both sides.
Recovering from the Outage
Recovery requires a matching change on both the CCaaS and RC/ACO sides
- In CCaaS, navigate to
Admin (System) > System Settings > Voice Agent - Set
Queue is PluggedtoTrue - In
Admin (System) > SIP Extensions, identify the affected extension — the primary extension is listed in bold at the top of the list - In the RC/ACO admin portal, navigate to
Users > User List > Users with Extensionsand select the affected extension - Under
Call Forwarding and Voicemail > Missed Calls, selectForward to extensionand set the destination and ring time - Select
Save
Symptom to Watch ForThis condition is identifiable by agents being presented calls they are unable to answer. Reverting
Queue is Pluggedto its default once the API connection recovers restores normal routing.
Updated about 9 hours ago
