cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
439
Views
15
Helpful
5
Replies

Courtesy Callback Exception Error Message

joerunning
Beginner
Beginner

On my test bench I've recently configured Courtesy Callback, but I cannot get past an error message that says "Contact id: 59548, Contact is inactive when getting channel".

All the steps work correctly up until the agent presses any digit to initiate the courtesy callback. Using active debugging, when the agent accepts the callback and the routing script moves to the successful step and attempts the "Call Redirect (--Triggering Contact-- to CallingNumber)" it invariably fails with an Exception popup with "contact is inactive when getting channel" and I cannot figure out why. I've searched and am not able to find out anything that defines that error message enough to direct me to a solution.

I am using UCCX version 12.5 and I have two call control groups configured, one inbound and one outbound. I am able to use the Call Redirect step successfully in any other routing script except for this one.

1 Accepted Solution

Accepted Solutions

joerunning
Beginner
Beginner

Success: this does work in UCCX 12.5!!!

The exception error message ("contact is inactive when getting channel") is not very clear in trying to point you toward the actual issue until you understand the logic.

When the inbound caller successfully chooses to receive a call back, their CallingNumber is stored as a String and their call is terminated. Because they have been disconnected a --TriggeringContact-- no longer exists.

In the next step a NEW call is originated by the Place Call step to await an agent. When an agent receives this NEW call they are prompted