When you divert a call with CURRI, you're doing so using the permissions of your ECC profile - thus bypassing whatever permissions the original destination of the call.
Am I really the only one thinking this is less than ideal? The divert from an app is similar to a CFWDAll on the line, and there's permissions on that.
I wrote a solution for this - using a different ECC per line CSS, but that has major scalability issues (the keepalives keep hammering my system because CUCM doesn't get that it's talking to the same host and app). Opened a DevNet case - that ended up in the 'you're the only one ever asking for that, so we're not gonna change it'.
And I have a hard time believing that. Sure it's nice to use css_all to divert to wherever you like, but you bypass the entire permission system on CUCM. And since I have no contacts to other ISVs I figured I'd ask here.. anybody using CURRI in their apps ever though a permission system would come in handy?
