After enabling "Force Account Code" cannot forward calls outside line 1

[ega218]

I enabled the "Force Account Code" box on my [9]1N; sc.

Aftwards, users that attempt to forward their calls to a number which requires an account code, cannot. Instead the call is answered by their voicemail.

Is there a specific format that the number forwarded to needs to be entered with the account code. I can't find any documentation on how to resolve this.

Thanks in advance for your assitance.

IP Office 403 v2.1(15)

 

[IPGuru]

Known Bug
may be fixed in V2.1(27)

 

[kristiandg]

Maybe I'm missing something here, but how is that a bug? Large PBXs are the same way. You can't call forward your phone to a number you couldn't call yourself (with or without an access/account code).

On large systems if you need the ability to call forward to a long distance number, you need to be able to make that call yourself w/o any need for an auth code, so we make your COR (definity) or NCOS (Nortel) appropriate.

If you're using LCR, which we are, you could build a specific entry for the call forward feature code in the User Restriction Tables. If you REALLY build out your LCR and User Restriction tables, you can do it there. Although 1N would require a code, *72 wouldn't, hence solving that problem.

Hope this helps...

Kris

 

[ega218]

Since it is only a few long long distance numbers which we would be forwarding to, I have just created a SC for the actual long distance numbers and removed the "Forced Account" option. This will allow users to forward their numbers to these specified numbers. Forwarding to local numbers is not problem.

 

[IPGuru]

Avaya Seem to think there is a problem with this feature.
It is mentioned in the bulleten of bugs "fixed" in the V2.1(27) trial software.

"17783 Remote call forward doesn't work when forced account code is enabled"

 

[kristiandg]

I think what they mean is, if I've got phone "A" forwarded to my cell phone and Isomeone calls phone "A" directly from the outside world (via DID or whatever), as long as phone "A"s user restriction doesn't require an Auth Code, it works. However, if I'm, say, the receptionist and I try to transfer a call to phone "A", and the receptionist normally needs auth codes to call out, then I need an auth code as well. The bug is that the system isn't looking at the forwarding phone's Restrictions, but the individual who is doing the calling/transferring.

Kris G.