You previously learned about remote access conditions and permissions. Now it’s time to take a look at the last element that makes up a remote access policy. The profile of a policy determines the properties that a connection attempt must match. Once a connection attempt has been authorized, meaning the remote access user has the required permission, the profile settings are then applied to the connection attempt.

A remote access profile can include the following settings, each of which are outlined below.

• Dial-in Restraints Used to configure the Idle-Timeout and Session-Timeout values, the day and time restrictions, as well as number and media restrictions.
• IP Used to specify how remote access clients are assigned IP addresses and to configure inbound and outbound packet filters.
• Multilink Used to enable and configure multilink connections and the Bandwidth Allocation Protocol (BAP).
• Authentication Specifies that various authentication methods that can be used by remote access users.
• Encryption Specifies the levels of encryption that can be used by remote access clients.
• Advanced Settings Used to specify additional connection parameters.

Various settings can also be configured through the properties of a user account. For example, using the Dial-in tab from the account properties window you can configure the call back options. For example, you can configure a specific number that the remote access server will call the user back at, thereby limiting where the user can gain remote access from. So if the remote access user is calling from a number other than the one specified, the connection attempt will be denied.

Now that you are familiar with the different elements that make up a remote access policy, you are ready to move on to the next step - understanding how policies are applied. This topic will be tackled in a later article.