Curri and authorization codes

We have an implementation that requires to use curri and authorization codes at the same time. The desired configuration is actually very simple depending on conditions (who is calling, from which DN, device, Location etc):

-allow a call and use an authorization code

-allow a call without the usage of authorization code

-deny a call

We have tried to configure the above, but it seems that CUCM won't allow to use at the same time CURRI and Authorization codes. Is there a workaround or known configuration for the above?

----------------------------------------------------------------------------------------------------

You could trigger CURRI at another point in the call flow, such as a Translation Pattern that doesn't translate anything, it just triggers a CURRI interaction.

----------------------------------------------------------------------------------------------------

I have done the following and still not working:

1. When I trigger Curri using and empty Translation Pattern, I receive within Curri the correct calling number and an empty field for the called number.

2. So, then, I made a real translation pattern that works properly (when call 5XXXXXXXXXX to translated it to 9XXXXXXXXXX). The call is established OK. Moreover, I have a Route Pattern 7X! that uses authorization codes. This also works properly.

3. When I trigger Curri at the 5XXXXXXXXXX translation pattern, if I direct the call within Curri to 9XXXXXXXXX it works properly. If the calls is directed to 7X!, instead of asking for an authorization code, I get a busy signal. If I remove the authorization code from the 7X! route pastern, it works OK.

Any suggestions?

Is there any alternative or did I do something wrong with the above configuration?

----------------------------------------------------------------------------------------------------

Because FAC requires device support to work, it looks like you would have to send the call through that process first. You should still be able to trigger a CURRI request after the FAC is completed.

The implementation that our customer would like to have is to trigger Curri first, select the right route pattern with Curri, and then use FAC for some of the patterns. So Curri should run prior of FAC.

Do you think that there is a work-around for this to work?

----------------------------------------------------------------------------------------------------

I think that we have resolved the issue.

The configuration is:

-Trigger Curri within a valid translation-pattern

-Trigger FACs withing a route-pattern

-Route-patterns with FACs and without FACs should be in the same gw. If the gws are different it will not work.

-Use the Continue Directive within Curri response to send the call to the appropriate route-pattern

----------------------------------------------------------------------------------------------------