/mcpchanges a message notification number for a user using Cisco Unity Connection Administration, Unity Connection does not apply any restriction table to the number. Therefore, an administrator can, when necessary, override the limitations of the class of service of a particular user. The User-Defined and Automatically-Added Alternate Extensions restriction table functions similarly to other restriction tables in that it restricts the numbers the users can use to create alternate extensions for themselves through interfaces such as the Cisco Personal Communications Assistant or via an API call. It can also restrict a number from being offered as an alternate extension when a user frequently calls Unity Connection and signs in from the number. (The table is named Excluded Extensions for Automatically-Added Alternate Extensions, and does not apply to alternate extensions that users create for themselves in Cisco PCA.) Unlike other restriction tables, this restriction table applies to all users and therefore is not associated with a class of service. It also applies when administrators use Unity Connection Administration to change user-defined alternate extensions, but does not apply when administrators enter or change administrator-defined alternate extensions. Each row of a restriction table is made up of a dial string. Each dial string consists of a call pattern and a setting that specifies whether numbers that match the call pattern can be called. In most cases, the restriction table is applied when a user attempts to change a number that is controlled by a restriction table, not when Unity Connection tries to complete a transfer or delivery. In the case of Caller system transfers, which allow unauthenticated callers to transfer to a number that they specify, Unity Connection checks the specified number against the Default System Transfer table. By default, this table blocks all numbers, in order to protect against toll fraud and unauthorized use. When a restriction table is applied to a number (such as a pager number for a message notification), Unity Connection compares the number with the call pattern of the first dial string in the restriction table. If the number does not match the call pattern, Unity Connection then compares the number with the call pattern in the second dial string, and so on, until it finds a match. When Unity Connection finds a match, it either permits or restricts calling the number as specified in the dial string. Restriction tables are commonly used to permit or restrict calls to the following: • Specific numbers, such as an extension. • Numbers that are greater than or less than a specific length. • Numbers that contain a specific digit or pattern of digits, such as an external access code followed by a long-distance access code. For example, the restriction table below restricts most long distance phone numbers, but permits extensions starting with “91.” In this case, if a user enters “9123” as a transfer number, Unity Connection first compares the number to the call pattern in Dial String 0, which restricts all numbers that begin with “91” and are followed by at least seven digits. Because the number entered does not match the call pattern, Unity Connection then compares the number to Dial String 1, which restricts all numbers that begin with “9011” and are followed by at least seven digits. Finally, Unity Connection compares the number to the last dial string, which contains the wildcard character that matches all numbers of any length. Because the Allow This String field is set to Yes for this dial string, Unity Connection permits this number to be used. Table 6: Example 1 Allow This String Call Pattern Dial String No 91???????* 0 No 9011???????* 1 System Administration Guide 105 Call Management How Restriction Tables Work