Cisco Cisco Expressway Maintenance Manual
CPL
If you are using the Call Policy rules generator on the Expressway, source matches are carried out against
authenticated sources. To specify a match against an unauthenticated source, just use a blank field. (If a
source is not authenticated, its value cannot be trusted).
authenticated sources. To specify a match against an unauthenticated source, just use a blank field. (If a
source is not authenticated, its value cannot be trusted).
If you use uploaded, handcrafted local CPL to manage your Call Policy, you are recommended to make your
CPL explicit as to whether it is looking at the authenticated or unauthenticated origin.
CPL explicit as to whether it is looking at the authenticated or unauthenticated origin.
n
If CPL is required to look at the unauthenticated origin (for example, when checking non-authenticated
callers) the CPL must use unauthenticated-origin. (However, if the user is unauthenticated, they
can call themselves whatever they like; this field does not verify the caller.)
callers) the CPL must use unauthenticated-origin. (However, if the user is unauthenticated, they
can call themselves whatever they like; this field does not verify the caller.)
n
To check the authenticated origin (only available for authenticated or “treat as authenticated” devices) the
CPL should use authenticated-origin.
CPL should use authenticated-origin.
Note that due to the complexity of writing CPL scripts, you are recommended to use an external policy
service instead.
service instead.
Authentication policy configuration options
Authentication policy behavior varies for H.323 and SIP messages.
The primary authentication policy configuration options and their associated behavior are as follows:
n
Check credentials: verify the credentials using the relevant authentication method. Note that in some
scenarios, messages are not challenged, see below.
scenarios, messages are not challenged, see below.
n
Do not check credentials: do not verify the credentials and allow the message to be processed.
n
Treat as authenticated: do not verify the credentials and allow the message to be processed as if it is has
been authenticated. This option can be used to cater for endpoints from third-party suppliers that do not
support authentication within their registration mechanism. Note that in some scenarios, messages are
allowed but will still be treated as though they are unauthenticated, see below.
been authenticated. This option can be used to cater for endpoints from third-party suppliers that do not
support authentication within their registration mechanism. Note that in some scenarios, messages are
allowed but will still be treated as though they are unauthenticated, see below.
Authentication policy is selectively configurable for different zone types, based on whether they receive
messaging:
messaging:
n
The Default Zone, Neighbor zones, traversal client zones, traversal server zones and Unified
Communications traversal zones all allow configuration of authentication policy
Communications traversal zones all allow configuration of authentication policy
n
DNS and ENUM zones do not receive messaging and so have no authentication policy configuration.
To edit a zone's Authentication policy, go to
Configuration > Zones > Zones
and click the name of the
zone. The policy is set to Do not check credentials by default when you create a new zone.
The behavior varies for H.323 and SIP messages as shown in the tables below:
H.323
Policy
Behavior
Check
credentials
credentials
Messages are classified as either authenticated or unauthenticated depending on whether any
credentials in the message can be verified against the authentication database.
credentials in the message can be verified against the authentication database.
If no credentials are supplied, the message is always classified as unauthenticated.
Do not check
credentials
credentials
Message credentials are not checked and all messages are classified as unauthenticated.
Cisco Expressway Administrator Guide (X8.5.2)
Page 110 of 403
Device authentication
About device authentication