Call policy on VCS

[tufan.kabacioglu]

Hello,

We have a customer. They have a lot of videoconferencing systems and a few Cisco VCSes. We created two zones (for example Zone A and Zone B) in the VCSes. So we want to prevent a videoconferencing system in the Zone A to call the other systems in the Zone A. But they should be able to call the videoconferencing systems in the Zone B. The videoconferencing systems in the zone B should be able to call everyone. I tried a lot of thing but I couldn't make it possible. By the way none of the videoconferencing systems are authenticated systems.

Your help will be really appreciated,

Regards,

Tufan

[Joe Vallender]

Can't you do this with Dial Plan->Search Rules?

[tufan.kabacioglu]

No I can't. Because in Search rules I can not specify the named target zones.

[Martin Koch · Accepted solution]

You can not select the named zone on the target but you could use the source and see how far you get with that.

In general you answered your question in the topic. The most flexible way is a CPL.

You could either upload a custom one or make yourself a policy server (like a php script

on an external server handling your requests).

The build in vcs gui configured call controll part is not really made for this.

If you have more advanced needs like this please also look into moving towards CUCM,

there you have Partitions and Calling Search spaces:

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a0080094b53.shtml

Please remember to rate helpful responses and identify helpful or correct answers.

[tufan.kabacioglu]

Actually I can not use call policy feature on the VCS, because the endpoints are not authenticated users. I see that in order to specify source alias pattern on the call policy the users must be authenticated. It is very difficult for the customer. The customer has more than 4000 endpoints.

By the way, unfortunately, it is not possible to change the infrastructure like moving to CUCM or other VCSes.

[Martin Koch · Accepted solution]

Hi!

There are multiple ways to handle call policies on the vcs:

* via the wizzard (there it might be true regards the unautenticated origin

but I refer to:

* using an external policy server:

http://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/config_guide/Cisco_VCS_External_Policy_Deployment_Guide_X7.pdf

* or, possibly easier in the first step, generate a xml cpl file which matches your needs.

Check out the VCS admin guide for more info, note the "unauthenticated-origin"

http://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/admin_guide/Cisco_VCS_Administrator_Guide_X7-2.pdf

Tufan: Please remember to rate helpful responses and identify helpful or correct answers.

[Joe Vallender]

So the VCS's are NOT defined as neighbor zones in each other?  If they were, they should show up as a 'target' zone when defining a search rule.  One being the 'local' zone and the other being a 'neighbor' zone.