elemental

Whenever someone in our company makes a long distance call related to a client matter they are supposed to dial the FAC, 10-digit account code, then the number. Unfortunatly, there are quite a few people who are not doing this and as a result we cannot bill these calls back to the client. I've been given the task of setting it up to force any non-administration person to enter an account code for long distance calls. Now I know how to set it up so someone has to enter an account code for every call, but I would like to refine it so they only have to do this for long distance calls.

I thought that it could be done through the COR assigned to a trunk group, but per Avaya, "With the Forced Entry of Account Codes (FEAC) capability, the system does not use the class of service (COR) of the trunk group to determine if the user must enter an account code, if the system uses ARS to access the trunk." We do use ARS to access the trunk.

Any ideas on how I can get this to work. It's driving me crazy.

Thanks!


System Info: S8500-012-02.0.111.4

__________________
Ace Tech

jordy5535

PBXtech.info

 

elemental

That will work if I want them to use an account code for all calls, but what I would like to do is just have them forced to enter an account code for the long distance calls.
I was looking at giving the users their separate COR that would route them to their own partition on the ARS table which in turn would send them to the long distance trunk that required an account code. What I am wondering is, how can I set up the trunk group to force the use of an account code? Having the COR for the trunk group set to force account code doesn't work as the system does not look at the COR for the trunk when the call is routed via ARS.

__________________
Ace Tech

jordy5535

You can also set the COR of the trunk groups to require forced entry of account codes

elemental

Not if the call is routed through ARS. Per Avaya:

"With the Forced Entry of Account Codes (FEAC) capability, the system does not use the class of service (COR) of the trunk group to determine if the user must enter an account code, if the system uses ARS to access the trunk."

I don't know why Avaya set it up this way but they did. As a result, I'm stuck. This is what I'm trying to get around.

__________________
Ace Tech

jordy5535

PBXtech.info

 

bwilch

Correct me if I'm wrong, but can't you set the forced account calls to Yes, then use the "change toll ana" so that only the long distances numbers are set for account codes?

Not positive, but I thought you could.

elemental

But wouldn't "change toll ana" affect ALL calls or can it be partitioned?

__________________
Ace Tech

bwilch

I thought, and again I may very well be wrong, I've not gotten that deep into this before, that using the toll ana you could set the numbers for account codes and that would reference if the "forced account codes" was enabled.

Again, I'm not 100% on this, but you could test by adding your telephone number in there, trying calling with a COR that doens't have forced account codes set and see if it restricts.

elemental

Ok, I think I got it now. It can be handled on the Toll Analysis table. You need to set the user's COR "Forced Entry of Account Codes" to yes, then on the toll analysis table make sure the the numbers you want to restrict are entered (much like the ARS table) and that "CDR FEAC has an "x" marked on that number. Now for my next question, where is the "Unrestricted Call List" administered? It used to be on the COR page but it isn't any longer and I can't find it. Any ideas?

__________________
Ace Tech

elemental

I just figured out the unrestricted call list. On the COR form, "Calling Party Restriction" needs to be set to TAC-TOLL or TOLL-ALL, then the unrestricted call list appears.

Thank you all for helping me get this figured out.

__________________
Ace Tech