Each dialed number is compared against the user’s call permissions. If the call is denied, the calling party will be routed to a “fast busy” intercept tone. If the call is allowed, the routing continues.
Figure 7-1 Call Permissions Edit Page To define call permissions:
Step 1 Open the Call Permissions edit page (Figure 7-1).
Step 2 Select the Scope. Scope allows you to set a general permission level and is presented from the most restrictive to the most permissive. The Restrictions and Permissions listed are applied in addition to the general scope setting for the Class of Service.
• Internal Only allows calls only to internal extensions and to the
configured emergency number.
• Local Only allows calls only to local or additional local area codes,
as defined on the site edit page. The call permission does not apply to any of the trunk group area codes.
• National Long Distance also allows calls to long-distance numbers
within the country, as defined on the Site edit page.
• National Mobile allows calls to mobile phones in countries (e.g.
Ireland) with “caller pays” billing plans.
• International Long Distance also allows calls to international num-
bers, as defined on the Site edit page.
• All Calls allows calls to any number, including 1900, Operator
Assisted, and Carrier Select numbers, as well as use of Vertical Ser- vice Codes. This is the default.
Step 3 Enter restriction and permission rules. The Restrictions and
Permissions listed are applied in addition to the general scope setting. The comma separated restriction expressions are limited to a total of 50 characters.
Follow these guidelines for entering restrictions:
• In general, numbers must be entered in canonical format including the international designation “+” and country code. For example, to restrict calls to the 408 area code in the U.S., use +1408. All 7-digit and 10-digit numbers must be entered in canonical format (+Country Code, Area Code, and Subscriber Number).
• Non-routable calls (311, 411, etc.) for a country must be desig- nated by the country code plus the “/” character. For example, to restrict 311 in the U.S., use 1/311.
• Each field can contain multiple entries as long as they are separated by commas or semicolons.
• Each entry must consist of numbers only.
• Access codes, such as 9, must not be included.
• To simplify the entering of call permissions, the wild-card character “x” can be used to represent any number. For instance, to block all calls to 976 prefixes, enter “+1xxx976” as a restriction.
When a call is both restricted and permitted, it is permitted. For example, restricting +1 408 and permitting +1 408 331 restricts all calls to the 408 area code except those to 408 331-xxxx.
Account Codes
If Account Code Collection Service is enabled, when a user dials a number that is outside the scope of his or her call permissions, the call is automatically routed to the Account Code Collection Service extension on the HQ server. The Account Code Collection Service captures call details that can be reviewed in the call detail reports. For more information on these reports, see the ShoreTel 7.5 Administration Guide. The collection of account codes is enabled on a per-user group basis and can be set to be one of three states: disabled, optional, or forced.
The Account Code Collection Service is associated with a configurable extension and has a dedicated user group that defines ultimate call permissions and trunk group access.
When account code collection is enabled or forced for a member of the user group, calls placed via the telephone or the Call Manager are first filtered by call permissions. Calls restricted by call permissions are automatically routed to the extension associated with the Account Code Collection Service. Upon receiving the call, the Account Code Collection Service prompts the user to enter an account code and press the pound (#) key.
If the user enters an account code that does not match the digits in a stored account code, the system plays a message explaining the problem and prompts the user to re- enter the account code. When the user enters an account code that matches one of the stored codes, the code is collected, and the call is completed.
Call Permissions specifies the dialed numbers that are directed to the Account Code Collection Service for any user groups configured for account codes.
Calls redirected to the account codes extension are completed using the trunk access and call permissions associated with the Account Code Collection Service.
The Account Code Collection Service examines outbound calls against two sets of permissions:
1 Checks call permissions for the caller’s user group to determine if an account code must be collected.
2 If user group permissions specify the collection of an account code, a check is performed on the call permissions for the Account Code Collection Service to determine whether call will be permitted or rejected.
If the call is rejected, the intercept tone is played.
The Account Code Collection Service is associated with a system extension hosted on a SoftSwitch that only runs on the headquarters (HQ) server.
If the Headquarters SoftSwitch is unavailable to the ShoreGear switch from which a call originates, the call is handled according to the permissions set for the caller’s user group. Calls placed by users who are configured for optional account code collection are placed. Calls placed by users who are configured for forced account code collection are rejected.
Wildcard characters (represented with a question mark) can be used in place of DTMF digits in the account code. When wildcards are used, a length check is performed instead of a more thorough validation of the code. Although this reduces the stringency of the validation process, it allows the sytem to support far more than 50,000 account codes – the previous account code limitation.
Refer to the chapter on Call Control in the ShoreTel 7.5 Administration Guide for more information about account codes and account code wildcards.