Unsupported cpl elements, Cpl examples, 3 unsupported cpl elements – Tandberg Data N3 User Manual

Page 34: 4 cpl examples, Call screening

Advertising
background image

TANDBERG Gatekeeper User Manual

28

an E.164 number.

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.

reject

If a reject node is executed the Gatekeeper stops any further script processing and rejects the
current call.

3.11.3 Unsupported CPL Elements

The Gatekeeper does not currently support the following 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.

time-switch

string-switch

language-switch

time-switch

priority-switch

redirect

mail

log

subaction

lookup

remove-location

3.11.4 CPL Examples

Call screening

Only allow calls from users with authenticated source addresses. See section 3.8 H.235
Authentication, for details on how to enable authentication.

<cpl>
<incoming>
<address-switch field=

origin

>

<not-present>

<reject/>

</not-present>

</address-switch>

</incoming>
</cpl>

Selective Call Screening

Advertising