The one I uploaded should be used on the VCS-E since these call attempts are originating from the wild, this is where I also have ISDN blocks in place to prevent external sites from accessing our ISDN gateways.
However, I do not use CPL for that, only search rules, see page 39 of the deployment guide http://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/vcs/config_guide/X8-5/Cisco-VCS-Basic-Configuration-Control-with-Expressway-Deployment-Guide-X8-5.pdf - having said that, there's obviously nothing wrong with using CPL. :)
Which one you use is neither here nor there, you'll have to edit it anyway :) - just open it in Notepad and insert the additional rules and upload on the VCS-E.
Both VCS-C and VCS-E use the same format, so to create a new rule you would do something like this:
<taa:rule authenticated-origin="insert pattern here" destination="insert pattern here">
<reject status="insert here" reason="insert here">
</taa:rule>
You don't need to specify the reason, but some times it is satisfying to send them a customised message even though they probably won't read or see it. :)
You should include a rule for unauthenticated origin as well though.
It's basic XML, each rule begins with <taa:rule and ends with </taa:rule>
There's quite a few threads in the Telepresence support forum about isdn toll fraud which may be of interest to you - this one shows how to break the dial string.
/jens
Please rate replies and mark question(s) as "answered" if applicable.
Please rate replies and mark question(s) as "answered" if applicable.
