Filter
Top Products
TANDBERG Gatekeeper User Guide
Page 56 of 105
13.3.2. proxy
On executing a proxy node the Gatekeeper will attempt to forward the call to the locations specified in
the current location set. If multiple entries are in the location set then they are treated as different
aliases for the same destination and are all placed in the destination alias field. If the current location
set is empty the call will be forwarded to its original destination.
It is important to note that when a proxy node is executed script execution stops immediately i.e. there is
currently no support for the proxy outputs busy, noanswer etc.
13.3.3. reject
If a reject node is executed the Gatekeeper stops any further script processing and rejects the current
call.
13.4. Unsupported CPL Elements
The Gatekeeper 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 Gatekeeper 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
13.5. CPL Examples
13.5.1. Call screening of authenticated users
This example shows how to allow calls from only those users with authenticated source addresses.
See Authentication (section 8.2) for details on how to enable authentication.
<cpl>
<incoming>
<address-switch field="origin">
<not-present>
<reject/>
</not-present>
</address-switch>
</incoming>
</cpl>