The not-present node is executed when the address specified in the address-switch was not present in the call setup message. This form is most useful when authentication is being used. With authentication enabled the VCS will only use authenticated aliases when running policy so the not-present action can be used to take appropriate action when a call is received from an unauthenticated user (see the example call screening of unauthenticated users).
D 14049.01
07.2007
7
TANDBERG VIDEO COMMUNICATION SERVER
ADMINISTRATOR GUIDE
Text goes here
Introduction StartedGetting OverviewSystem ConfigurationSystem ConfigurationH.323 & SIP Registration Control Zones and Neighbors ProcessingCall TraversalFirewall Bandwidth Control Maintenance Appendices
TANDBERG VIDEO COMMUNICATION SERVER
ADMINISTRATOR GUIDE
Appendices
Field
Within the address-switch node, the mandatory field parameter specifies which address is to be considered. The supported attributes and their interpretation are as follows:
Authentication Mode: On Authentication Mode: Off
Field SIP H.323 SIP H.323
origin The “From” and “ReplyTo” fields of the message if it authenticated correctly, otherwise not-present.
The source aliases from the original LRQ or ARQ that started the call if it authenticated correctly otherwise not- present. Since SETUP messages are not authenticated if we receive a setup without a preceding RAS message the origin will always be not-present.
The “From” and “ReplyTo” fields of the
incoming message. The source aliases from the original LRQ or ARQ that started the call. If a SETUP is received without a preceding RAS message then the origin is taken from the SETUP.
unauthenticated-origin The “From” and “ReplyTo” fields of the incoming message.
The source aliases from the original LRQ or ARQ that started the call. If a SETUP is received without a preceding RAS message then the origin is taken from the SETUP.
The “From” and “ReplyTo” fields of the incoming message.
The source aliases from the original LRQ or ARQ that started the call. If a SETUP is received without a preceding RAS message then the origin is taken from the SETUP.
authenticated-origin The “From” and “ReplyTo” fields of the message if it authenticated correctly, otherwise not-present.
The source aliases from the original LRQ or ARQ that started the call if it authenticated correctly otherwise empty. Since SETUP messages are not authenticated if we receive a setup without a preceding RAS message the origin will always be not-present.
not-present
originating-zone The name of the zone or subzone for the originating leg of the call. If the call originates from a Neighbor, Traversal Server or Traversal Client zone then this will equate to the zone name. If it comes from an endpoint within one of the local subzones this will be the name of the subzone. If the call originates from any other locally registered endpoint this will be “DefaultSubZone”. In all other cases this will be “DefaultZone”.
originating-user The username used for authentication. not-present
registered-origin If the call originates from a registered endpoint this is the list of all aliases it has registered, otherwise not-present. destination The destination aliases.
original-destination The destination aliases.
If the selected field contains multiple aliases then the VCS will attempt to match each address node with all of the aliases before proceeding to the next address node i.e. an address node matches if it matches any alias.
CPL Reference
TANDBERG VIDEO COMMUNICATION SERVER
ADMINISTRATOR GUIDE
Text goes here
Introduction StartedGetting OverviewSystem ConfigurationSystem ConfigurationH.323 & SIP Registration Control Zones and Neighbors ProcessingCall TraversalFirewall Bandwidth Control Maintenance Appendices
TANDBERG VIDEO COMMUNICATION SERVER
ADMINISTRATOR GUIDE
Appendices
Subfield
Within the address-switch node, the optional subfield parameter specifies which part of the address is to be considered. The following table gives the definition of subfields for each alias type. If a subfield is not specified for the alias type being matched then the not-present action will be taken.
address-type Either h323. or sip, based on the type of endpoint that originated the call.
user For URI aliases this selects the username part. For H.323 IDs it is the entire ID and for E.164 numbers it is the entire number.
host For URI aliases this selects the domain name part. If the alias is an IP address then this subfield is the complete address in dotted decimal form. tel For E.164 numbers this selects the entire string of digits.
alias-type Gives a string representation of the type of alias. The type is inferred from the format of the alias. Possible types are: Address Type Result URI url-ID H.323 ID h323-ID Dialled Digits dialedDigits
•
•
•
•
•
•
•
•
CPL Reference
Overview
D 14049.01
07.2007
73
TANDBERG VIDEO COMMUNICATION SERVER
ADMINISTRATOR GUIDE
Text goes here
Introduction StartedGetting OverviewSystem ConfigurationSystem ConfigurationH.323 & SIP Registration Control Zones and Neighbors ProcessingCall TraversalFirewall Bandwidth Control Maintenance Appendices
TANDBERG VIDEO COMMUNICATION SERVER
ADMINISTRATOR GUIDE
Appendices
Unsupported CPL Elements
The VCS does not currently support some elements that are described in the CPL RFC. If an attempt is made to upload a script containing any of the following elements an error message will be generated and the VCS will continue to use its existing policy.
The following elements are not currently supported: time-switch string-switch language-switch priority-switch redirect mail log subaction lookup remove-location
•
•
•
•
•
•
•
•
•
•
CPL Script Actions
location
As the CPL script is evaluated it maintains a list of addresses (H.323 IDs, URLs and E.164 numbers) which will be used as the destination of the call if a proxy node is executed. The location node allows the location set to be modified so that calls can be redirected to different destinations. At the start of script execution the location set is initialized to empty for incoming calls and to the original destination for outgoing calls.
The following attributes are supported on location nodes. It supports the use of Regular Expressions (see Regular Expression Reference for further information).
Clear = “yes” |
“no” Specifies whether to clear the current location set before adding the new location. The default is to append this location to the end of the set.
url=string The new location to be added to the location set. The given string can specify a URL (e.g. [email protected]), H.323 ID or an E.164 number.
priority=<0.0..1.0>
| “random” Specified either as a floating point number in the range 0.0 to 1.0, or random, which assigns a random number within the same range. 1.0 is the highest priority. Locations with the same priority are searched in parallel.
regex=”<regular expression>” replace=”<string>”
Specifies the way in which a location matching the regular expression is to be changed.
proxy
On executing a proxy node the VCS will attempt to forward the call to the locations specified in the current location set. If multiple entries are in the location set then this results in a forked call. If the current location set is empty the call will be forwarded to its original destination.
reject
If a reject node is executed the VCS stops any further script processing and rejects the current call. The custom reject strings status=string and reason=string options are supported here.