vcs expressway search rules

[gavin han]

Hi,

we've vcs expressway and vcs control. I want to configure vcs expressway in such a way that if incoming call matches 12xxxxx@domain.com pattern than vcs expressway should drop that call (it shouldn't forward that call). how to do that?

can we configure authentication in such a way that vcs expressway authenticates each incoming call (from locally registered endpoints on vcs expressway as well as incoming 3rd party calls from internet) going out for 12xxxxx@domain.com. if that incoming call isn't authenticated than vcs expressway should drop that call (shouldn't send it to vcs-control)?

Thanks all.

[Haydn von Imhof]

Hi Gavin

You can create rules to block or allow specific call patterns on your VCS control and Expressway

VCS Configuration > Call Policy > Rules

You can specify a source pattern as well as destination pattern and set the rule to either allow or deny the call.

The Help File on the VCS and Expressways is also very helpful and explains each field better.

Eg: If you create the below rule on the expressway if will block any calls to 123XXXXXX@domain.com

Source Pattern: (Leave Blank)

Destination Pattern: 123(.*)@domain.com

Action: Reject

[eric.ho]

Hi Gavin,

Just to be clear, two Call Policy Rules (not Search Rules) are required.

Haydn already told you how to create a Call Policy Rule to reject calls to specific alias pattern.

If you do it exactly as Haydn points out, the blank source pattern will match an unauthenticated user only.

If you had used (.*)  as the source pattern, then that would match both authenticated and unauthenticated users.

For incoming calls, you can do the reverse:

Source Pattern: 123(.*)@domain.com

Destination Pattern: (.*)

Hope this helps,

Eric

[Justin Ferello]

Eric,

Correction, (.*) will not include unauthenticated users, only authenticated.  Yes I just tested it, just to make sure.

Thanks,

Justin

[eric.ho]

You're right. I just tried it as well.

Thanks!

Eric