Account codes are commonly used to control cost allocation and out-going call restriction. The IP Office can use account codes in a number of ways.
When making calls, users can voluntarily enter an account code.
On phones that support programmable buttons, users can do this using an Account Code Entry button.
A short code set to Set Account Code can also be used to enter an account code before making a call.
If the number dialed for an outgoing call matches a short code set to Forced Account Code, the user is required to enter a valid account code in order to continue the call.
Individual users can be set to Forced Account Code (). They then need to enter an account code for any outgoing external calls.
Incoming calls can also be associated with an account code by matching the Caller ID stored with the account code settings. That account code is then included in the call's SMDR call log.
When an account code is entered during a call:
The IP Office checks the code entered for a match against those account codes set in its configuration. For Forced Account Code calls, the call is not allowed until a valid code is entered.
If the code is valid, it is included in the information output by the system's SMDR call log.
The account code used on a call is not included in the user's personal call log. This means that re-dial functions will not re-enter the account code.
If more than one account code is entered during a call, only the last code entered is included in the SMDR call log.
An IP Office system can support up to 1500 configured account codes.
Wildcards can be used in the account codes configured to expand the supported range. For example, a single account code entry 9?? allows dialing any number between 900 and 999 to be treated as a valid account code.
By default, in Server Edition/Select networks, account codes are configured at the network level and automatically replicated in the configuration of all systems in the network. That is, the 1500 account code limit applies to the whole network. They can only be seen and edited at the individual system configuration level if record consolidation is switched off. See Record Consolidation.