Search VCS rule

Similar Questions

• Looking for a method to search for rules that use a particular registry variable

  Hello

  I have a series of registry variables that hold email lists effectively different specific alarms.  Is there a way to query to use what are the rules that save variables?  His most difficult when several people create rules and lists.

  THX

  "mark".

  Mark,

  One method would be to export the foglight configuration to a file using the fglcmd program. You can find the file in the registry variable that interests you. You will see references to registry variables in the section rules.

  Example of export of the foglight management server bin directory:

  C:\Quest_Software\Foglight\bin>fglcmd.bat - usr - pwd foglight cmd - foglight util:configexport f filexxx

  David Mendoza

  Foglight Consultant

• Understanding search rules - Source.

  I have a scenario very very simple just to learn more about the rules of research & transformations and how they work.

  I can't get the search rules to work with areas sources of some how restrict conversions based on the source.

  I understand the benefits of using one or the other for simple conversions, etc.

  At the moment I only use search with no transformations on the VCSC rules.

  Scenario:

  EX90 - [email protected]/ * / (recorded with VCSC)

  VCSC - 172.16.246.92

  VCSe - 172.16.246.93

  VCSe - 10.0.0.230 (NAT - PublicIP)

  FWLocal - 10.0.0.1

  FWInet - publicIP

  Jabber - [email protected] / * / (recorded with VCSe)

  Jabber - [email protected] / * / (Findme on VCSe)

  EX90--CSCV--VCSe--FW--Internet--Jabber Video.

  Everything works fine if I dial for example 8095556631 Jabber in the EX90 video.

  Demand of the VCSe to the VCSC happens like this: [email protected] / * /(VCSe)--> [email protected]/ * / (VCSC).

  This work without any intervention from the rules of the VCSC research because join '@172.16.246.92' of the VCSe.

  Everything works fine if I dial for example * EX90 6631 to video of Jabber.

  The request of the VCSC to the VCSe arrives like this: [email protected]/ * / (VCSC)--> [email protected] / * /.

  This is done using search with localZone.GetDaylightChanges source rules to the destination TraversalZone.

  It does not work! If I dial for example 6631 (Extension) to the EX90 Jabber video.

  Demand of the VCSe to the VCSC happens like this: [email protected] / * / (VCSe)--> [email protected]/ * / (VCSC). (That's what I want to change to [email protected]/ * / without using transformations on the VCSC and using the rule of research with source TraversalZone).

  The rule search:

  Name Desde VCSe

  40 priority (like right now)

  Any protocol

  Source TraversalZone

  Auth                            No

  Alias fashion model

  Model Regex

  Pattern string (\d{4})(@172.16.246.92)

  Replace patter behavior - 809555\1\2

  To stop the game

  Target localZone.GetDaylightChanges

  Newspapers:

  Detail = "" send H.225 ReleaseComplete Q.931 Cause: absent subscriber, H.225 Cause: non-registered party called, Info: not found additional Destination "(!)" @# $ I understand this one. $# @!)

  "Module-level =" Network.Search' = 'INFO': detail = "given to search the rule"LocalZoneMatch"objective 'LocalZone.GetDaylightChanges' to '100' of priority with alias [email protected]/ * /' ' (! @# $ I understand this one. $# @!)

  "Module-level =" Network.Search' = 'INFO': detail = "search rule"Hacía CUCM"does not match destination alias [email protected]/ * /' ' (! @# $ I understand this one. $# @!)

  "Module-level =" Network.Search' = 'INFO': detail = "search rule 'Hacía VCSe' does not match destination alias [email protected]/ * /' ' (! @# $ I understand this one. $# @!)

  Module level = "Network.Search' = 'INFO': detail = 'Rule"Desde VCSe"ignored due to the filtering of search source' (! @# $ I DO NOT understand this one. $# @!)"

  Module level = "Network.Search' = 'INFO': detail = 'search"Hacía CUCM - Extension"rule ignored due to the filtering source' (! @# $ I understand this one. $# @!)"

  Module = "Network.H323" Level = "INFO": Dst - ip = "172.16.246.93" Dst-port = "15070" detail = "Send H.225 procedure" "

  Module = "Network.H323" Level = "INFO": ip - Src = "172.16.246.93" Src-port "15070" = "

  Detail = "kbps of bandwidth: 5952 H.225 Setup H.323v6 DestAlias receipt:[email protected]/ * / DestCSAddr: ['IPv4"TCP"172.16.246.92:1720']" vendor: TANDBERG ' "

  I do not understand how to select Source: TraversalZone the source of the application gives me "ignored due to filtering of the source.

  Seems I am missing some basics on how to find work for incoming requests not generated rules locally.

  THX in adv.

  The guides were less concerning research and own deployment, which also lie to the use of the domain

  To quote the guide:

  
  The routing configuration in this document searches for destination aliases that have valid SIP URIs (that is, using a valid SIP domain, such as [email protected]/* */).
  
  

  Please set up and use a domain name, your rules might address and test again.

  I would stick to a - z, 0-9,-. for the part of the user and the domain of the sip uri!

  I will most likely see because without a propert domain name it does not.

  I would also be careful with many changes, rewrites and search you may see problems with the presence and other things.

• Video Jabber for TelePresence, VCS-E connection problem

  Hello

  I recently configured control VCS, VCS Expressway and TMS. Two VCS servers are software X7.2 and TMS is on 14.1.1 commissioning is configured between the VCS control and TMS, everything works OK internally and users can log in their Jabber client of telepresence video.

  When you try to connect via the highway-VCS I get the following question: "connection refused by the server. Try to connect again later"

  Area authentication is configured like this:

  VCS-Highway

  Sub-area by default: do not check the credentials

  Area Sefault: Do not check the credentials

  Crossing area: Do not check the credentials

  VCS-control

  Default subfield: treat as authenticated

  Area by default: credentials check

  Subarea: Credentials Check {area which movi users register to regex function}

  Crossing area: Do not check the credentials

  Search the rules between the two VCS game [email protected] / * / OK.

  The only port of the restrictions in place here are between the VCS control and VCS Expressway, outgoing ports open to the highway of the SANCTION.

  It seems to me that there is a connection problem, as opposed to an authentication problem. also, do I need to configure a SIP domain local VCS-Highway even if I try to proxy, registration to the VCS control.

  Would be appreciated if someone can verify my authentication area also...

  Thank you

  Simon,

  to do this, you re normally the area on VCS - C as "check credentials.

  If you want to proxy of VCS VCS-C-E records, you should not add the SIP domain name to the VCS-E.

  "Rejected by the login server" sounds weird in this case, however, could you share what you use for this deployment, the SIP domain name so that we can verify that your DNS SRV records are fine?

  -Andreas

• VCS VCS - E, TMS, TMSPE, Jabber/Movi authentication

  Just trying to figure the best way to approach this.

  I have read the documentation and the best approach seems to get to the VCS VCS-E to Active Directory and the synchronization of the TMS with AD for user account creation. This would avoid the need to records movi proxy for control of VCS and would ensure that all (SIP and H323) registration for the VCS-E would be authenticated.

  I don't think that my client will allow the VCS-E talk to AD.

  So, what are my options?

  If I SIP proxy of VCS-E records the VCS control, how are they managing H323? I don't want just any point endpoint h323 register with the VCS-E. I need to authenticate them. The customer has exernal h323 endpoints that they would like to sign up for VCS - E. I know I could put registration rules to restrict only some URI SIP, H323 IDs etc but it's really just security by obscurity.

  The local on VCS and VCS-E database can be used for authentication Movi/SIP and H323 records? I know that I would have to duplicate accounts and passwords on both.

  What books commissioning and address through registration to the VCS-E? Would it still work?

  Any suggestions on the best way to handle this in the safest way possible without breaking things?

  If I go with the control of VCS and VCS Expressway with authentication Active Directory (directly) on the control method of the VCS as described in the guide of authentication devices, I'm looking for the reality that I will not be able to restrict who can register for the VCS-E? At this time should I just seek to restrict the search for rules to only authenticated users?

  Thank you

  Jon

  Hey Jon,

  MOVI/Jabber you won't have to worry about authenticating H323. With your endpoints however you can just use the database local to authenticate or H350 (more can be read about in the guide of the Provisioning device referred to as Tomo). You can create a different generic for all your endpoints (less secure if which is discovered). But by combining this feature with a political appeal will ensure better security.

  I highly doubt that your client will allow you to leave the talk VCSE in AD. For movi/jabber users, you can create another subfield and use a regex pattern for point movi/jabber users to authenticate it as. * (\.movi)@domain.com. In addition, you can refer to this fragment and others have used in the past.

  In a secure design, the VCS (control and Highway) would require identification for registration information.

  The Control of VCS would have Active Directory Service active and joins the Active Directory domain. For VCS authenticate the credentials of Movi/Jabber on Active Directory before the SUBSCRIPTION for the supply is sent to the service of commissioning, the default Zone would be set to verify the credentials. For requests for SUBSCRIPTION from the highway, the area on the VCS control would also to verify the credentials. It handles authentication for the provision.

  The next part is the record of the Movi/Jabber client. The subzone to which the customer will register must also be set to verify the credentials. Here's everything you need for internal records (registration to the VCS control).

  For the Highway, things get a little more complicated. For commissioning subscription, the SUBSCRIPTION is forwarded to the VCS control. With the area on the VCS game to check the credentials, you're all set. Now on registration to the highway. The subzone to which the customer will register to must be defined to check credentials. From the motorway VCS don't have direct access to Active Directory, we use local credentials on the highway. A set of credentials should be configured in VCS Configuration > authentication > devices > local database. You will create a single name and password all Movi/Jabber clients will use. The end user has NO need to know these credentials. The username and password is provided to the Movi/Jabber client via configuration data it has received. To set up these data, MSDS, you must configure a SIP of authentication user name and password for SIP authentication in the configuration of the commissioning. For these options to be available, you must ensure that you have downloaded the configuration template xml for the Movi/Jabber version you are using. The xml file is included in the zip package full of the client which can be downloaded on www.cisco.com. So, who will be recording from the highway. Now, this creates an interesting situation with VCS control. The internal Movi/Jabber client will receive the same provisioning configuration and will attempt to use those same credentials when you register for the control of VCS. The VCS control is already set to authenticate against Active Directory and Active Directory ONLY registration.

  You will need to create an account in Active Directory corresponding to these credentials. The Active Directory account didn't need special access. It is used only for authentication purposes. A few things to keep in mind: SIP authentication user name and password for SIP authentication are stored in clear text configuration configuration. This means that the data is sent in clear text. To be sure that these data are not compromised on the wire, do not forget that you are using for your communication SIP Movi/Jabber TLS.

  With this directories will always work as jabber should be authenticated in order to receive directories. Your physical endpoint points will work differently with how they receive books and whether or not they are able to communicate with MSDS (unless you choose to configure endpoints also if those you are capable).

  It is in no way the design as safe as possible. It is to you to ensure that your environment is as secure as possible and therefore tested. The best way to fix everything is a well-defined appeal policy designed with your specific needs.

  The foregoing is in no way a recommendation but just a little more information to chew while looking to choose and implement what is best for you.

  Adam

• Pattern string in the correspondence of Alias on VCS

  Hi all

  Since the creation of rules of research on the RESUME, we can select Alias Pattern Match as a mode.

  (VCS configuration > dial plan > search rules > Search Create rule)

  In this mode 'Alias Pattern Match', about H.323 and SIP, which is alias match?

  H.323

  1. 'the called party number' in Q931?

  2. "destinationAddress' of userinformation in H.225?

  3. "destcallsignaladdress" of userinformation in H.225?

  4. neither of the above?

  SIP

  1. "request-URI" of the line of the query?

  2 "sip to address" header of the Message?

  3. "contact-URI" in the header of the Message?

  4. neither of the above?

  Kotaro

  Search for the appeal process rule.

  [H323]

  ARQ-RAS: destinationInfo

  Q.931: destinationAddress

  * The 'Party number called' cannot include in Q.931 Setup message if call initiated with H.323 ID.

  [SIP}

  INVITE: Request-URI

• VCS called Ip address routing

  Hello

  I have a question about my VCS control configuration.

  In my scenario, I have control of Vcs and Vcs Express Way.

  I implemented the rule in VCS control:

  .. .the problem: same end point not working with a record keeper and only receive an IP calls. The ip call go all in internet (from the Expressway)

  -----------------------------------------------------------------------------

  Source: AllZones

  Mode: All IP addresses

  On correspondence: continue

  Target: Path (VCS Express Way area)

  ------------------------------------------------------------------------------

  If I call a point of endpoints in the Internet, everything works fine, but if I have to call via ip address, endpoint Internel network (with ip address 10.x.x.x), he call go Express Way.

  I want to put in the control of VCS, rules that use the direct dial plan for all internel ip address (which begins 10.*) and use the indirect numbering plan for the call "unknow ip address."

  Thanks for your help

  FCostalunga

  Hi FC,.

  You can solve this problem by creating a subarea on the VCS control where the subzone membership rule contains subnets with the range of the IP intern (s). For subareas containing the IP address ranges, IP addresses that fall within these ranges is considered known to the VCS, and when endpoint composed one of these addresses IP control VCS will try to set up the call to the IP address itself rather than attempt to transmission by proxy, the call through highway.

  To do this, you must also a rule of search "AnyIPAddress" on your VCS control that points to the local area.

  For reference, I recommend you read through the "Component IP" section in the Administrator's guide from the VCS for X 7, which explained further on the subject.

  Out of curiosity, why you prefer calling IP addresses rather than h.323/SIP URI?

  Hope this helps,

  Andreas

• About VCS Express hack attack

  Hello

  I have a pirate constantly trying to hack our VCS and it (his robot) is not giving up.

  It happens on our express VCS and or to order with the id 'cisco' and is calling through the communication manager various combinations of dialing numbers, I would just add a CPL entry to block anything arriving with "cisco".

  Someone at - it an example of how to add a source like this in the cpl file and it ships to nirvana?

  Any help would be appreciated.

  Randy

  One I downloaded should be used on the VCS-E since these call attempts originate from the wild, that's where I also ISDN blocks in place to prevent external sites to access our ISDN gateways.

  However, I do not use CPL for this, search only 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 is of course nothing wrong with using the CPL.  :)

  One you use is neither here nor there, you'll have to edit anyway :) - just open it in Notepad and insert the additional rules and download on the VCS-E.

  The VCS - C and VCS-E use the same format, so to create a new rule, you would do something like this:

  You need not specify the reason, but sometimes it is good to send them a personalized message, although they probably won't be read or see. :)

  You must include a rule of origin thus unauthenticated however.

  It is basic XML, each rule starts with

  There is some discussion in the support of telepresence forum on fraud without ISDN costs that may be of interest to you - this one shows how to break the dial string.

  /Jens

  Please note the answers and score the questions as "answered" as appropriate.

• Text search without wildcards - for example 'Howe' but not 'how '.

  A lot of old messages to go without finding common words such as 'how' and «and' instead of simply 'Howard' or «candles»

  From your description, I suspect you use the global search, which I agree is a bit lame.

  There is an older search tool, accessed by ctrl + shift + f, which allows a more precise search. And because it is based on the same set of tools such as Message filters, additional such as FiltaQuilla modules and search for term / Gmail UI that enhance the capabilities of filtering are also available in your research.

  The main disadvantage with ctrl + shift + f search is that it is based on records; She looks in the current folder only. One way to work around this is to use a saved, search where you have so much stronger search/filtering rules and the ability to select which folders to search in.

• SIP calls failing

  Hello

  I've implemented VCS in both sites, Site A and site B and I did the neighbors between Site A and Site B VCS rules. Search and transformations are configured and implemented and applied.

  Calls from Site B to establish a (H323 and SIP) work well, but calls from Site A to Site B work only for H323. Strange things here is localisation tools show the address cannot be resolved and true for this research nevertheless calls SIP of the Site A to Site B do not work when calls is launched of a Cisco endpoint. I already spent a few days and double checked everything but can't break this case, someone knows what's the problem?

  Thanks in advance. Mark

  Hi Mark,

  Since you are able to make SIP calls to internet via MCU and the zones are configured as donotcheckcredential, I think that the problem is with your endpoints rather than VCS. try this:

  -check the DNS configuration on your terminals (EX-series, etc.) and make sure that is correct and the connectivity is here

  -Make sure that the outgoing setting is set to off

  -Make sure the VCS FULL domain name are correct and not poorly spelled and solvable

  s ' there is no proxy between VCS and endpoints server, make sure that this field is empty.

  -I don't think issues of NTP server for SIP calls, make sure however NTP server is configured and works for endpoints

  -one last thing, try saving the end point that is already registered for site A to site B and try to make a call internet SIP, would this work?

  Best regards, Ahmad

• Duplication of the SIP URIs with prefix GW

  Hello Techies,

  I recorded an ISDN gateway with VCS control with prefix 7. So, when the user wants to dial call ISDN, it includes 7followed by number and call routes to the ISDN gateway which bands of 7 and sends the call to the public network.

  However, when the same user dials SIP URI [email protected] / * /, instead of going to VCSexpressway call, he goes to the ISDN gateway.

  How can I work around this problem?

  thnx

  -wala

  Wala Hi, welcome to the Cisco support community!

  You should implement a dial in VCS who avoid that kind of shift. I don't know what rules of research and transformations that you configured, but here are some points you should consider:

  1 - alias [email protected] / * / not must be sent to the local VCS control, if this happens, you probably have a search rule 'any alias' that points don't localZone.GetDaylightChanges, that is not correct, you must create specific search models rules correspond to your alias of local endpoints registered

  2. with regard to the ISDN gateway, you should have a search rule specific to the call of the road to ISDN. For example, SIP endpoints reached ISDN, you should have a rule of research pointing to localZone.GetDaylightChanges whose model is (\1 7\d +) @localdomain.com and replace. This remove only the domain part of the URI and send only the 7XXXX recorded localZone.GetDaylightChanges ISDN bridge. In this case, I am assuming that you have a transformation with the model ([^ @] *) and replace-[email protected] / * /. If you have not this turn, you must create a different search rules to match route endpoints H323 ISDN dial only the number, it would be something like this: 7\d + and route to the local area.

  3 - Furthermore, when the creation of roads, prefer to use regex strings of preffix and suffix, regex is the best option to avoid the incompatibility of numbering plan. Rather than use the prefix 7, use regex 7\d +. For example, the prefix 7 Games [email protected] / * /, but 7\d regex + does not work.

  4 - there is an important thing to consider when registering gateway ISDN to VCS, especially when you have VCSe. You must implement a free fraud prevention mechanism in order to avoid external users to use your system as a free phone system. You can do this by using the strategy to call him; or using the rules of search + authentication + subzones. You can take a look at this thread:

  https://supportforums.Cisco.com/message/3971947#3971947

  I hope this helps.

  Paulo Souza

  Please note the answers and mark it as "answered" as appropriate.

• Several files palette in a library/class file problems

  All developing a labview class, I wanted to put the default palette, so I added the relevant dir.mnu file to the class. Unfortunately, the class had a dir.mnu in her file. On the addition of the file, I received an error message on a dependency change * (which makes no sesne, how a palette file can have dependencies!). On the recording of the class and any attempt to reopen it, LabVIEW argues that it is corrupt. Inspect the .lvclass xml files reveals that when I added the new file paletee, LabVIEW actually just added a second reference to the file already in the project palette, he then considered a problem when it tries to load the class. This is clearly a bug on several levels:

  1. It should not possible for the user to induce LabVIEW to create files xml corrupted through such simple attempts to use the documented features.
  2. The underlying problem is that LabVIEW seems to use the classic search/link rules to load the library items, be they a vi (which must have a unique name) or another file (which might well be legitimately not unique).
  3. Almost impossible to rename a palette file without breaking the links palette this bug in particular is very annoying.

  I was able to reproduce the behavior described.

  This was reported to R & D (AUTO ID: 181638) for further investigations.

  Thanks for the comments!

• Zero records send from ProductCatalogOutputConfig

  Hello

  I use ATG - 10.2

  Phase	Component	Documents sent	Records failed	Status
  PreIndexing (duration: 0:00:00)
  	/ ATG/commerce/short/index/CategoryTreeService			COMPLETE (successfully)
  RepositoryExport (duration: 0:05:09)
  	/ ATG/commerce/short/index/SchemaExporter	101	0	COMPLETE (successfully)
  	/ ATG/commerce/short/index/CategoryToDimensionOutputConfig	1517	0	COMPLETE (successfully)
  	/ ATG/commerce/short/index/RepositoryTypeDimensionExporter	47	0	COMPLETE (successfully)
  	/ ATG/commerce/Search/ProductCatalogOutputConfig	0	0	COMPLETE (successfully)
  EndecaIndexing (duration: 0:00:05)
  	/ ATG/commerce/short/index/EndecaScriptService			COMPLETE (successfully)

  I notice the logs of bellows with BulkLoader.

  Jump bookProduct:146135 point, because said IndexingOutputConfig should not be included (probably becase it is not member of a referential element group).

  -------

  Error Wed Oct 01 12:50:59 IST 2014 1412148059021/atg/commerce/search/ProductCatalogOutputConfig cannot generate the paged query because can not get the repository group item query.

  -------

  Debug Wed Oct 01 12:42:16 IST 2014 1412147536125/atg/search/repository/BulkLoader ThreadDispatcher: runningThreads = 2, maxThreads = 10, requestQueue = 1, numQueued = 26090, numProcessed = 26087

  Debug Wed Oct 01 12:42:16 IST 2014 1412147536125/atg/search/repository/BulkLoader ThreadDispatcher: runningThreads = 2, maxThreads = 10, requestQueue = 0, numQueued = 26090, numProcessed = 26088

  Debug Wed Oct 01 12:42:16 IST 2014 1412147536126/atg/search/repository/BulkLoader ThreadDispatcher: runningThreads = 2, maxThreads = 10, requestQueue = 0, numQueued = 26090, numProcessed = 26089

  Debug Wed Oct 01 12:42:16 / atg/search/repository/BulkLoader IST 2014 1412147536126 ignore point bookProduct:146135, said IndexingOutputConfig should not be included (probably becase it is not member of a referential element group).

  This system was working fine a few days before with no problems.

  Does anyone know why this kind of question that's happened?

  We found this evil with this... We can set up a rule to filter the items to be indexed. Rule is in the component ' / ' atg/commerce/search/IndexedItemsGroup.rules

  ex:

  I did a bad here.

• strange behavior on the procedure

  Hello
  
  Today, in my class I came across a very mysterious behavior of Oracle DB without logical explanation. If anyone knows what this could mean that it would be useful.
  
  
  Some cases of training:
  
  SELECT name
  Employees
  WHERE id_employee IN (SELECT id_employee
  Of employees_seminars
  natural join seminars
  WHERE seminar_name = 'PHP');
  
  -> This works, lists employees who participated in PHP seminar
  
  same case with NOT IN:
  
  SELECT name
  Employees
  WHERE id_employee NOT IN (SELECT id_employee
  Of employees_seminars
  natural join seminars
  WHERE seminar_name = 'PHP');
  
  -> This works, employees of lists who NOT attended the PHP seminar
  
  And now comes the interesting - even put in the procedure with cursor + loop + fetch dbms_output (not paste complete SQL here, but would be also possible if necessary) and execution of the procedure, only the variant with NOT IN worked, the other (with only IN) shows nothing!
  
  Any ideas what could be wrong with that?
  
  I don't need to work, I was wondering as even the professor asked himself with me, so I decided try to check if this is a bug or what is magic.
  
  Thanks a lot if anyone would be interested in solving this mystery :-)
  
  (we use version 10.2.0.1.0 XE)
  
  Filip

  Hello

  905502 wrote:
  And now comes the interesting - even put in the procedure with cursor + loop + fetch dbms_output (not paste complete SQL here, but would be also possible if necessary) and execution of the procedure, only the variant with NOT IN worked, the other (with only IN) shows nothing!

  In your last post, you posted a procedure of NOT IN. Why, after the procedure which worked and not one that you don't understand?

  Any ideas what could be wrong with that?

  Yes:

  CREATE TABLE "STUDENT2"."SKOLENI"
  ( "ID_SKOLENI" NUMBER(*,0),
  "NAZEV" CHAR(25 BYTE), ...
  

  I suspect that the problem is the CHAR data type.
  Here's everything you need to know about the datayype TANK: do not use it. Use rather VARCHAR2.

  There are rules on how tanks are compared to the VARCHAR2s, and there is probably a subtle difference between what you do one place (where you get them expected results) and somewhere else (where you have not), such as the use of a literal in one place and a variable in another. Such a difference would not matter with a VARCHAR2, but it might with a TANK.
  You can search comparison rules in the manual of the SQL language if you really want to, but it is simpler, just to avoid the completely CHAR data type.

• VCS - numbering of the IPS 'known' search rules

  Hello

  We have a standard configuration of VCS-C/VCS-E, with VCS - C, the value 'indirect', VCS-E the 'direct' for calls to unknown IP addresses. It works very well.

  The problem is we have a second remote desktop on MPLS which points of Polycom endpoints (not enrolled in the VCS) and they can be reached via IP address, but they are inside the LAN. I can only call them if I change the 'direct' VCS - C since I see no way to create a search rule targeting a specific range of IP addresses - it will not allow the models for comparison with IP addresses!

  Am I missing something here?

  (Edit: Alok beat me to it)

  Thomas,

  on the VCS - C, you can create one or more subfields with 'subnet' membership of type rules where you add IP addresses or subnets that you want to be able to deal directly via the VCS - C.

  No matter what IP address that corresponds to a membership rule subarea for a subzone is considered "Known" VCS in question, which allows VCS to make the call to this IP address directly.

  This is described in the VCS Administrator's guide in component IP "section:

  The VCS considers that an IP address to be "known" if she is:

  -is the IP of a locally registered endpoint
  -Beach one of the membership rules configured subarea on the VCS to address intellectual property statement

  In addition to this, need a search rule "AnyIPAddress" for the local area on the RESUME said.

  Hope this helps,

  Andreas