Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

Regex problem from VCSc X7.1

Unanswered Question
Aug 28th, 2013
User Badges:


On our VCS Control X7.1, I try to create a rule with regex to limit IP range for the communications. For exemple, when I put on regex string, the regex :


And, when I do a locate from VCS Control with IP address "", I have an response "Not found".

Doing an other test, I replace the previous regex by :


The result is that when I put in locate "1.2.3.", the response is good. Even if that's not an IP address , but it was just for the test.

An other test with the regex :


The result of the locate with "1.2.3.test" is good also.

On the first regex "(\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3})", I have the impression that VCS doesn't take into account the fourth digit of the IP address, wheareas the regex seems good.

Is it an error of me (on the regex rule), or is someone receive a same result that me?

Thanks for your help.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Patrick Sparkman Wed, 08/28/2013 - 07:05
User Badges:
  • Purple, 4500 points or more
  • Cisco Designated VIP,

    2017 TelePresence

I just did a test with..


I left the last digit of the IP address off as well as replacing it with a word as in your tests, and all scenarious I got the same results as you.  All of your regex examples and what your searching for against them all look correct, and I don't see an issue with them.

What is it you're looking to accomplish?  Do you want it to just check a 4 octect IP address containing only numbers, or let any combination of addresses such as #.#.#.#, #.#.#, or #.#.#.text allowed?

If the later, try..


Using (\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}) in regex, the end result will affect all IP addresses.  The \d(1,3) will match any number ranging from 1 to 3 digits.

CMONJARET Wed, 08/28/2013 - 08:42
User Badges:

Hello again,

Thanks for you quick response.

I know that "(\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3})" result all IP address and even 999.999.999.999...

In fact, I would like to create IP address ranges on the regex rule, in order to inhibit some IP address.

Also, I test to create a regex test with in pattern string :

And the result (locate) is "Not found", whereas the pattern "1.2.3.", the locate is true.

Other test with pattern string :


The locate is true.

It's strange, because it's like if the VCS refuses a fourth digit, whereas a fourth alphacharacter is allowed.

Martin Koch Wed, 08/28/2013 - 11:23
User Badges:
  • Red, 2250 points or more

I am not sure if this is the right way to go.

IP dialing can be a bit strange on the vcs

Are these internal ip addresses or external ones, sip or h323?

Can you descibe a complete use case?

If its on the VCSc / internal network I would most likely check if I could use

local sub zone member ship rules and then use a CPL to allow specific zones

to be able to talk to each other or forbid it.

For external calls also a cpl might also be possible.

Also: IP address aliases are not supported for pattern matching

But to really say what to do I would have to understand what you want and then see what you really need ;-)

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

CMONJARET Thu, 08/29/2013 - 00:27
User Badges:


The idea will be to restrain some IP address from VCSc which dial on H323, in order that the users can't dial those IP address, but others so.

For exemple, IP address from to work, and the others don't work. Thus, the users can dial only the IP address to, and an other dialling, they will have a message "Connection impossible".

After, there is no property on publics IP address or private IP address.

CMONJARET Thu, 08/29/2013 - 00:28
User Badges:

I take back my last sentence :

After, there is no priority on publics IP address or private IP address.

CMONJARET Thu, 08/29/2013 - 04:35
User Badges:


Thank you for your answer. I'm going to look that.


This Discussion