07-31-2012 02:43 PM - edited 03-16-2019 12:28 PM
Hello,
In an Call Handler, I've enabled allow transfer to "Default System Transfer to block calls to certain extensions. However, these extensions are configured as extensions within Call Handlers. I've determined that for some reason, the Restriction Table is not blocking calls to patterns that are configured as Call Handler extensions.
Is there a way to block those as well?
Thanks.
-Dave
Solved! Go to Solution.
07-31-2012 05:31 PM
Not to the best of my knowledge, the legacy behavior from Unity was that you only could transfer to something that was known to Unity (subscriber, call handlers, etc). This translated the same into CUC but with the enhancement of that checkbox to allow anything else that is unknown to CUC. The transfer tables only apply to those DNs which are unknown to CUC. If you already have those configured in CUC I don't know any way to block them unless you use search scopes.
You could just remove the DN from them and configure direct call/transfer rules if necessary for call routing.
HTH
java
if this helps, please rate
www.cisco.com/go/pdihelpdesk
07-31-2012 05:31 PM
Not to the best of my knowledge, the legacy behavior from Unity was that you only could transfer to something that was known to Unity (subscriber, call handlers, etc). This translated the same into CUC but with the enhancement of that checkbox to allow anything else that is unknown to CUC. The transfer tables only apply to those DNs which are unknown to CUC. If you already have those configured in CUC I don't know any way to block them unless you use search scopes.
You could just remove the DN from them and configure direct call/transfer rules if necessary for call routing.
HTH
java
if this helps, please rate
www.cisco.com/go/pdihelpdesk
08-01-2012 06:46 AM
That's what I thought. I couldn't figure out why my restriction table was not blocking the patterns that I programmed. Then I realized that patterns not matching the Call Handlers were blocked, while patterns configured as externsions in the Call Handlers were not, even though they matched the restriction rule...
This Unity CN cluster has over 1000 Call Handlers that was pulled in from Unity 5.x. It will be a slow migration process to Forwarding rules...
08-01-2012 07:23 AM
Hi Dave,
Just thought I might add that you can use ATM (Audio text manager) from the
great Unity Tools suite to create Routing Rules. It may be a fair bit quicker than
using the SA
Cheers!
Rob
"Always movin' ahead and never lookin' back" - Springsteen
08-01-2012 07:45 AM
Very helpful! Thanks Rob.
5 Stars assigned, not that you need anymore to pad your stats.
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