Cisco VCS - routing IP addresses to multiple Zones

[David Anstee]

I have an environment where I have a VCS Control that is neighboured to 2x VCS Expressways on 2 different IP networks.

In call routing, I want to be able to route calls destined for a defined network e.g. 10.134.x.x to VCS-E 1 and ALL other IP addresses to VCS-E 2 - however in the SearchRules you can only configure "AnyIPAddress" - is their a way to be a bit more specific so that I can route IP addresses to the correct VCS-E neighbour?

[Alok Jaiswal]

David,

if you can calssify the users who would be dialing a certian set of ip's then we can club then in different subzone and awork around solution could be on x7.2 where in you can control the routing based on source zone as well..

you can write two different search rules for ip-address destined to two different expressway and say when the subzone 1 users calls to ip-address it should go to expressway 1 and subzone 2 users calls to ip-address it will go to expressway 2.

Cheers

Alok

[David Anstee]

Hi Alok,

Unfortuantely the same set of devices needs access to both VCS-E networks, so that wouldnt work, but thank-you for the suggestion.

I have never had such a requirement in the past, but seems such a simple request, that I cannot find an answer for

[Martin Koch]

I am not sure if it was you before, but we had some posting before.

In general I would have said, place an IP GW in the different zones, but the IPGW seems to be

EOL without a replacement, ...

If you just need to reach specific ips you could also do some search rule mappings or use enum.

Anyhow, review if such a strange setup is really needed or if there is a way to register these devices

and at least use e164 numbers or better propper uris.

A simple request is also "make coffee", doubt that the VCS will be able to do this :-)

[David Anstee]

Regular expression or matches in Search Rules do not appear to work with IP addresses, otherwise this would be an easy fix.

What's required here is when selecting IPaddress in Search Rules that you can also use regular expression or ranges to accommodate this.

Transforms do not work either.

So I guess the answer is 'this isn't currently supported by VCS'

Agree with the coffee comment, but more chance of my simple request being implemented than VCS making coffee

Sent from Cisco Technical Support iPad App

[Tomonori Taniguchi]

VCS doesn't support Regex search with IPv4 format (i.e. 10\.134\.\d{3}\.\d{3}) and also doesn't support IP address dialing include "0" front of any octet IP address (i.e. 10.134.200.005, where 005 has "0" front of valid "5").

However using alias format dialing and replace it at search rule(s), it's possible to archive what you are looking for although this will be a bit mess, I mean it not really nice way to archive but still doable (because VCS doesn't support IP address dialing with "0" front of each octet address).

User dial 12 digits number (type IP address of far end device without "." but add "0" to make 3 digits for each octet) when making IP address call via VCS-E2.

For example, call out to 10.134.10.5, then dialing string will be 010134010005 (or this specific case you may remove first "0" and dial "10134010005" if remove "0" front of "(10)" in search rule).

Last search rule will handle any IP address dialing outside of 10.134.x.x via VCS-E2.

Also in case VCS-E1 is out of service for any reason, user can dial 10.134.x.x network by dialing standard IP format (i.e. 10.134.10.5) which will matchup last dialing rule and process it via VCS-E2.

Here is sample search rules configuration.

==========================================================

Priority: 50

Type:   Regex

Pattern: 0(10)(134)[0][0](\d)[0][0](\d)

Behavior: Replace

Replace Strin: \1\.\2\.\3\.\4

Target: VCS-E 1

## This convert "10134001001" to "10.134.1.1" ##

Priority: 50

Type:   Regex

Pattern: 0(10)(134)[0][0](\d)[0]([^0])(\d)

Behavior: Replace

Replace Strin: \1\.\2\.\3\.\4\5

Target: VCS-E 1

## This convert "10134001021" to "10.134.1.21" ##

Priority: 50

Type:   Regex

Pattern: 0(10)(134)[0]([^0])(\d)[0][0](\d)

Behavior: Replace

Replace Strin: \1\.\2\.\3\4\.\5

Target: VCS-E 1

## This convert "10134021001" to "10.134.21.1" ##

Priority: 55

Type:   Regex

Pattern: 0(10)(134)[0]([^0])(\d)[0]([^0])(\d)

Behavior: Replace

Replace Strin: \1\.\2\.\3\4\.\5\6

Target: VCS-E 1

## This convert "10134021021" to "10.134.21.21" ##

Priority: 55

Type:   Regex

Pattern: 0(10)(134)[0][0](\d)(\d{3})

Behavior: Replace

Replace Strin: \1\.\2\.\3\.\4

Target: VCS-E 1

## This convert "10134001121" to "10.134.1.121" ##

Priority: 55

Type:   Regex

Pattern: 0(10)(134)[0]([^0])(\d)(\d{3})

Behavior: Replace

Replace Strin: \1\.\2\.\3\4\.\5

Target: VCS-E 1

## This convert "10134021121" to "10.134.21.121" ##

Priority: 60

Type:   Regex

Pattern: 0(10)(134)(\d{3})[0][0](\d)

Behavior: Replace

Replace Strin: \1\.\2\.\3\.\4

Target: VCS-E 1

## This convert "10134201001" to "10.134.201.1" ##

Priority: 60

Type:   Regex

Pattern: 0(10)(134)(\d{3})[0][^0](\d)

Behavior: Replace

Replace Strin: \1\.\2\.\3\.\4\5

Target: VCS-E 1

## This convert "10134201021" to "10.134.201.21" ##

Priority: 65

Type:   Regex

Pattern: 0(10)(134)(\d{3})(\d{3})

Behavior: Replace

Replace Strin: \1\.\2\.\3\.\4

Target: VCS-E 1

## This convert "10134201201" to "10.134.201.201" ##

Priority: 70

Type:   Any IP address

Target: VCS-E 2

==========================================================

You may modify the search rule priority but please carefully change it as some of search rule(s) can't have same priority to avoid converting IP address with "0" front of each octet (i.e. 005 => .05).