Cisco Cisco Expressway Maintenance Manual
Configuring Call Policy rules using the web interface
The
Call Policy rules
page (
Configuration > Call Policy > Rules
) lists the web-configured (rather than
uploaded via a CPL file) Call Policy rules currently in place and allows you to create, edit and delete rules. It
provides a mechanism to set up basic Call Policy rules without having to write and upload a CPL script.
provides a mechanism to set up basic Call Policy rules without having to write and upload a CPL script.
You cannot use the Call Policy rules page to configure Call Policy if a CPL file is already in place. If this is the
case, on the
case, on the
Call Policy configuration
page (
Configuration > Call Policy > Configuration
) you will have
the option to Delete uploaded file. Doing so will delete the existing Call Policy that was put in place using a
CPL script, and enable use of the
CPL script, and enable use of the
Call Policy rules
page for Call Policy configuration.
Each rule specifies the Action to take for all calls from a particular Source alias to a particular Destination
alias. If you have more than one rule, you can Rearrange the order of priority in which these rules are applied.
alias. If you have more than one rule, you can Rearrange the order of priority in which these rules are applied.
If rules are not configured, the default policy is to allow all calls, regardless of source or destination.
The configurable options are:
Field
Description
Usage tips
Source
pattern
pattern
The alias or IP address that the calling endpoint used to identify itself when
placing the call. If this field is blank, the policy rule applies to all incoming
calls from unauthenticated users, meaning calls where the endpoint making
the call is not registered and authenticated to a neighbor which in turn has
authenticated with the local Expressway.
placing the call. If this field is blank, the policy rule applies to all incoming
calls from unauthenticated users, meaning calls where the endpoint making
the call is not registered and authenticated to a neighbor which in turn has
authenticated with the local Expressway.
This field supports
.
Destination
pattern
pattern
The alias or IP address that the endpoint dialed to make the call.
This field supports
.
Action
Whether or not a call that matches the source and destination is permitted.
Allow: if both the Source and Destination aliases match those listed, call
processing will continue.
processing will continue.
Reject: if both the Source and Destination aliases match those listed, the
call will be rejected.
call will be rejected.
Rearrange
Each combination of Source and Destination is compared, in the order
shown on the
shown on the
Call Policy rules
page, with the details of the call being made
until a match is found, at which point the call policy is applied. To move a
particular item to higher or lower in the list, thus giving the rule a higher or
lower priority, click on the and icons respectively.
particular item to higher or lower in the list, thus giving the rule a higher or
lower priority, click on the and icons respectively.
Click on the rule you want to configure (or click New to create a new rule, or click Delete to remove a rule).
Configuring Call Policy using a CPL script
You can use CPL scripts to configure advanced Call Policy. To do this, you must first create and save the
CPL script as a text file, after which you upload it to the Expressway. However, due to the complexity of
writing CPL scripts you are recommended to use an external
CPL script as a text file, after which you upload it to the Expressway. However, due to the complexity of
writing CPL scripts you are recommended to use an external
Cisco Expressway Administrator Guide (X8.1.1)
Page 127 of 343
Dial plan and call processing
About Call Policy