
8 Creating the policy file
25
</address-switch>
</address>
<otherwise>
<!-- no origin address, just route normally -->
<proxy/>
</otherwise>
</address-switch>
</not-present>
<otherwise>
<!-- always check destination first -->
<address-switch field="destination">
<address regex="CAREC[.](.*)">
<!-- This rule is required to avoid an infinite policy loop repeatedly adding the CAZonePrefix -->
<proxy/>
</address>
<address regex="[email protected]|[email protected]">
<!-- Start compliant destination address, route the destination to the TCA -->
<address-switch field="destination" subfield="alias-type">
<address regex="URI|url-ID">
<!-- SIP addresses -->
<taa:location clear="yes" regex="(.*)@([A-Z,a-z,0-9,.,-]+)([:;]*)(.*)"
replace="CAREC.\1@\2.CAXXX\3\4">
<proxy/>
</taa:location>
</address>
<otherwise>
<!-- H.323 addresses -->
<taa:location clear="yes" regex="(.*)" replace="CAREC.\1">
<proxy/>
</taa:location>
</otherwise>
<!-- End compliant destination address -->
</address-switch>
</address>
<otherwise>
<!-- now we look at origin addresses -->
<address-switch field="origin">
<address regex="[email protected]|[email protected]">
<!-- compliant origin address, route the destination to the TCA -->
<address-switch field="origin" subfield="alias-type">
<address regex="URI|url-ID">
<!-- SIP addresses -->
Summary of Contents for Compliance Appliance
Page 1: ...Compliance Appliance Deployment Guide...
Page 31: ...9 Deployment scenarios 27 9 Deployment scenarios 9 1 Scenario 1 basic deployment...
Page 32: ...28 9 2 Scenario 2 deployment across a WAN...
Page 34: ...30 9 4 Scenario 4 non participating VCS...
Page 35: ...9 Deployment scenarios 31 9 5 Scenario 5 external organization...
Page 36: ...32 9 6 Scenario 6 VCS cluster...
Page 38: ...34 11 Call Flow within TCA...
Page 41: ......