08-18-2014 12:38 PM - edited 03-15-2019 06:01 AM
Hello,
I have created a script with exits to different extensions. I have noticed during testing, that the on exits to a Shared Line aI am getting Fast Bussy. My question would be: it is possible to have exits from UCCX scripts to Shared Lines in CUCM?
Solved! Go to Solution.
08-18-2014 01:56 PM
Hi,
from a technical point of view, nothing prevents you to send a call to any extension - including one configured as a shared line.
Can you tell us more about the error? Did you check the log files? Are you sure it's not a partition/CSS issue?
G.
08-18-2014 01:56 PM
Hi,
from a technical point of view, nothing prevents you to send a call to any extension - including one configured as a shared line.
Can you tell us more about the error? Did you check the log files? Are you sure it's not a partition/CSS issue?
G.
08-18-2014 03:11 PM
Hi Gergely,
And thank you for your reply. i have found the issue. I have multiple triggers for the same script, and I had the xferToSharedLine varialble set up when getting into the script from one trigger, but not when triggering the script via a different trigger, and therefore the variable was having no value, and getting Fast Busy.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide