VCS neighbour with Cisco IOS gatekeeper issue

[xuetao han]

I am testing VCS neighbouring with an IOS gatekeeper.  But having issues.

Following are what I did:

A "custom" zone is created on VCS, a search rule for anything begin with 4 shall be route to this neighbour zone

The IOS gatekeeper has a local zone prefix as 4 and remote zone VCS has prefix 5 and 6

Then an H323 endpoint with E164 number 12345 is registered with IOS GK

However, using locate tool on VCS searching 412345 showing such:

• • Zone (1)
  • • Name: IOS GK
  • • Type: Neighbor
  • • Protocol: H323
  • • Found: False
  • • Reason: Undefined reason
  • • StartTime: 2015-11-25 11:15:29
  • • Duration: 0
  • • Gatekeeper (1)
    • • Address: 10.129.0.10:1719
    • • Alias (1)
      • • Type: E164
      • • Origin: Unknown
      • • Value: 412345

BTW, I tried both with and without "use-proxy" command on the IOS GK 

Shall VCS work with IOS GK ?

[Jens Didriksen]

The type of zone you create on the VCS should be a "Neighbor Zone", and I take it the IP address of the IOS GK is showing as active in this neighbour zone?

The system is registered with 12345, but as you can see from the search result, it shows 412345, which it can't find as it doesn't exist. So you need to strip the prefix.

I've called the Neighbor Zone "IOS GK" and the relevant search rule should look something like this;

Rule name: IOS GK

Priority: 100

Protocol: "H323", "SIP" or "Any"

Source: "Any", "All Zones", "Local Zone" or "Named"

Request must be authenticated: "Yes" or "No"

Mode: Alias pattern match

Pattern type: "Prefix"

Pattern string: 4

Pattern behavior: Strip

On successful match: Stop

Target: IOS GK

State: Enabled

/jens

Please rate replies and mark question(s) as "answered" if applicable.

[xuetao han]

Hi Jens

Thanks for your response.

If I do not strip off zone prefix "4" on VCS, but register the endpoint on IOS GK as 412345

Will this okay ?

Thanks

[Jens Didriksen]

Yes, but then you need to change "Pattern behavior" to "Leave"

/jens

Please rate replies and mark question(s) as "answered" if applicable

[xuetao han]

when endpoint registered as 12345, the error is "undefined reason" as such:

• • SearchRule (4)
  • • Name: IOS GK
  • • Zone (1)
    • • Name: IOS GK
    • • Type: Neighbor
    • • Protocol: H323
    • • Found: False
    • • Reason: Undefined reason
    • • StartTime: 2015-11-26 12:55:25
    • • Duration: 0.01
    • • Gatekeeper (1)
      • • Address: 10.129.0.10:1719
      • • Alias (1)
        • • Type: E164
        • • Origin: Unknown
        • • Value: 412345

if the endpoint is registered as 412345 , the error is "request denied" as such:

• • SearchRule (4)
  • • Name: IOS GK
  • • Zone (1)
    • • Name: IOS GK
    • • Type: Neighbor
    • • Protocol: H323
    • • Found: False
    • • Reason: Request denied
    • • StartTime: 2015-11-26 12:59:01
    • • Duration: 0
    • • Gatekeeper (1)
      • • Address: 10.129.0.10:1719
      • • Alias (1)
        • • Type: E164
        • • Origin: Unknown
        • • Value: 412345

I can confirm the IOS GK received LRQ from VCS then rejected it

[xuetao han]

following are part of Cisco Docu:

Resolution for LRQ Messages

When a gatekeeper receives an LRQ message from a gateway, it performs either of the following steps:

If there is no technology prefix or the technology prefix is not a hopoff technology prefix, the gatekeeper uses the exact E.164 alias in the LRQ message to search its zone prefix table and the registered E.164 aliases.

If the destination zone is local and the destination address is registered, the gatekeeper sends a location confirm (LCF) message.

In my case, VCS sends LRQ regarding 412345 to IOS GK , which has local zone prefix 4 and an endpoint registered as 12345.    What is wrong ?

[Jens Didriksen]

It will not find 412345 when the end-point is registered as 12345 without removing the prefix "4" - see my previous post with the search rule example.

/jens

Please rate replies and mark question(s) as "answered" if applicable.

[xuetao han]

Okay,  here is what I got.

the "locate" tool built in VCS does not work with IOS-GK.

I was able to dial between the endpoint 12345 registered on IOS-GK and endpoints registered on VCS, although locate fails every single time to find 412345 !

[Jens Didriksen]

The first with "undefined reason" is understadable as it's registered as 12345, but the prefix is not being stripped so it's looking for 412345, which it doesn't  find.

As for the second where it is registered as 412345, but being rejected, I would expect to see a reason for the rejection in the event log which could give you a hint as to what's going on.

"Request denied" sounds more like it's caused by a policy or config issue on the IOS GK though.

/jens

Please rate replies and mark question(s) as "answered" if applicable.