/mcp• Recording and playback by phone from Cisco Unity Connection applications, when the phone is the designated recording and playback device in the Media Player. • Delivering faxes to a fax machine. • Sending message notifications. • Creating user-defined alternate extensions—including the extensions that Unity Connection offers to add automatically on behalf of users. For example, you can specify that users have calls transferred only to internal extensions or that faxes are delivered only to local phone numbers. (Restriction tables do not affect the phone numbers that users can dial directly from their phones when they are not interacting with Unity Connection.) Each class of service specifies for its members a restriction table for call transfers, one for message notification, and one for fax deliveries. The restriction table can be the same for all three, or different for each. How Restriction Tables Work When a user uses the Messaging Assistant or the Unity Connection conversation to attempt to change a phone number that is used for call transfer, message notification, or fax delivery, or when signed-in users use the Unity Connection conversation to perform User system transfers to a number that they specify, Unity Connection applies the restriction table associated with the class of service of the user to verify that the phone number entered is allowed. For example, if a user uses the Unity Connection Messaging Assistant to enter a phone number to set up a message notification device, Unity Connection applies the restriction table that is associated with the class of service of that user, and displays an error message if the phone number is not allowed.But when an administrator changes 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 System Administration Guide 100 Call Management How Restriction Tables Work