Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

VCS-E: calls to unknown IP address not happening for gateway device

Hi All - we have a VCS-E that has been working fine for most calls - however, have run into the following problem:

We are dialing an endpoint that’s behind a Polycom VBP - : 20614667@xxx.xxx.xxx.xxx – it’s actually a bridge entrance “lobby”

If I dial that string from our MCU or Movi, it connects.

If I dial it from our Vidyo H.323 gateway, it fails.

The two searches are almost identical, except the first one (that works), says  the destination is a H.323id, then goes to “CallstoUnknownIPAddresses and finds it.

The one that fails, defines the destination as a Url, ends up in DNS zone, and gets a “Request Denied” – from what /who I don’t know.

Any ideas on why this is happening or how to make them both work the same? Our system needs to be able to work from either.

Both are being launched as H.323 calls to the exact same string : 20614667@xxx.xxx.xxx.xxx


I dial from the gateway a straight IP address - xxx.xxx.xxx.xxx - it goes out as a Type:IPAddress  and actually goes to "calls to unknownIP address" search and connects fine.  Just the "URL" format screws it up....

23 REPLIES

Re: VCS-E: calls to unknown IP address not happening for gateway

Hi,

Your DNS search rule propably is configured with the "source" parameter, which is used to limit which endpoints can reach this route. Or the parameter "request must to be authenticated" is enable. Please check your DNS search rule configuration. But If you find that one of those parameters is enable, I don't suggest you to simply disable them, because there are good resons for using those parameters, normally security issues. So, check the configuration and let us know.

Furthermore, let us know, is your H323 gateway integrated with VCS Control? Is it registered to VCS Control or integrated via Neighbor Zone?

Regards

Paulo Souza

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

Paulo Souza Was my response helpful? Please rate useful replies and remember to mark any solved questions as "answered".

Re: VCS-E: calls to unknown IP address not happening for gateway

Hi John,

its important to see when the call reaches to exp in non-working scenario what is your called number looks like.

can you paste the search for the call in non-working scenarion. Also more details are good to know about your setup.

Rgds

Alok

Community Member

VCS-E: calls to unknown IP address not happening for gateway dev

DNS search rules have "any" as source parameters, the two searches are below - right column is the "worked" search. Iinserted some spaces so things lined up a bit...

Search (299)



Search (302)















State:   Completed


State: Completed














Found:   False



Found: True















Reason: Request   denied




Type: H323   (ARQ)














Type:   H323 (ARQ)


CallRouted: True















CallSerial   Number: 220f9d4a-f9d6-11e2-a0a1-0010f321e6eeCallSerial Number: b7defa5a-f9d6-11e2-aaf4-0010f321e6ee












Tag:   220f9ea8-f9d6-11e2-99e3-0010f321e6ee
Tag: b7defbae-f9d6-11e2-b0fb-0010f321e6ee












Source (1)




Source (1)














Authenticated: True




Authenticated: True














Aliases (1)




Aliases (1)














Alias (1)




Alias (1)














Type: H323Id




Type: H323Id














Origin: Endpoint




Origin: Endpoint














Value: OEGateway2




Value: OE














Zone (1)




Alias (2)














Name: DefaultSubZone




Type: E164














Type: Local




Origin: Endpoint














Path (1)




Value: 5875000006777














Hop (1)




Zone (1)














Address: 10.20.20.6




Name: DefaultSubZone



















Type: Local



















Path (1)



















Hop (1)



















Address: 10.20.20.14














Destination (1)




Destination (1)














Alias (1)




Alias (1)














Type: Url




Type: H323Id














Origin: Unknown




Origin: Unknown














Value: 20614667@122.98.28.101




Value: 20614667@122.98.28.101














StartTime: 2013-07-31   07:41:26




StartTime: 2013-07-31 07:45:37














Duration: 32.27




Duration: 0.01
















SubSearch (1)



SubSearch (1)













Type: Transforms



Type: Transforms













Action: Not   Transformed



Action: Not Transformed













ResultAlias (1)



ResultAlias (1)













Type: Url



Type: H323Id













Origin: Unknown



Origin: Unknown













Value: 20614667@122.98.28.101



Value: 20614667@122.98.28.101













SubSearch (1)



SubSearch (1)













Type: Admin   Policy



Type: Admin Policy













Action: Proxy



Action: Proxy













ResultAlias (1)



ResultAlias (1)













Type: Url



Type: H323Id













Origin: Unknown



Origin: Unknown













Value: 20614667@122.98.28.101



Value: 20614667@122.98.28.101













SubSearch (1)



SubSearch (1)













Type: FindMe



Type: FindMe













Action: Proxy



Action: Proxy













ResultAlias (1)



ResultAlias (1)













Type: Url



Type: H323Id













Origin: Unknown



Origin: Unknown













Value: 20614667@122.98.28.101



Value: 20614667@122.98.28.101















SubSearch (1)

SubSearch (1)













Type:   Search Rules

Type: Search   Rules


















CallsToUnknownIPAddresses (3)
















Mode: Direct


















Zone (1)



















Name: DefaultZone

















Type: Default


















Protocol: H323


















Found: True



















StartTime: 2013-07-31 07:45:37
















Duration: 0


















Gatekeeper (1)


















Address: 122.98.28.101:1720

















Alias (1)




















Type: H323Id




















Origin: Unknown



















Value: 20614667@122.98.28.101












SearchRule (1)


SearchRule (1)














Name:   LocalZoneMatch

Name: LocalZoneMatch













Zone (1)



Zone (1)















Name:   LocalZone


Name: LocalZone














Type:   Local


Type: Local














Protocol:   H323


Protocol: H323














Found:   False


Found: False














Reason:   Not Found

Reason: Not Found













StartTime:   2013-07-31 07:41:26
StartTime: 2013-07-31 07:45:37












Duration:   0


Duration: 0














Gatekeeper (1)


Gatekeeper (1)














Address:   10.20.7.7:0

Address: 10.20.7.7:0













Alias (1)


Alias (1)














Type:   Url


Type: H323Id














Origin:   Unknown

Origin: Unknown













Value:   20614667@122.98.28.101
Value: 20614667@122.98.28.101












Zone (2)



Zone (2)















Name:   LocalZone


Name: LocalZone














Type:   Local


Type: Local














Protocol:   SIP


Protocol: SIP














Found:   False


Found: False














Reason:   Not Found

Reason: Not Found













StartTime:   2013-07-31 07:41:26
StartTime: 2013-07-31 07:45:37












Duration:   0


Duration: 0














Gatekeeper (1)


Gatekeeper (1)














Address:   10.20.7.7:0

Address: 10.20.7.7:0













Alias (1)


Alias (1)














Type:   Url


Type: H323Id














Origin:   Unknown

Origin: Unknown













Value:   20614667@122.98.28.101
Value: 20614667@122.98.28.101












SearchRule (2)




















Name:   DNS




















Zone (1)





















Name:   DNS




















Type:   DNS




















Protocol:   H323




















Found:   False




















Reason:   Request denied



















StartTime:   2013-07-31 07:41:26


















Duration:   0.27




















Gatekeeper (1)




















Alias (1)




















Type:   Url




















Origin:   Unknown



















Value:   20614667@122.98.28.101


















Zone (2)





















Name:   DNS




















Type:   DNS




















Protocol:   SIP




















Found:   False




















Reason:   Request Timeout



















StartTime:   2013-07-31 07:41:26


















Duration:   31.99




















Gatekeeper (1)




















Alias (1)




















Type:   Url




















Origin:   Unknown



















Value:   20614667@122.98.28.101


















Community Member

VCS-E: calls to unknown IP address not happening for gateway dev

also - we have only VCS-E - our MCU & the the gateways register directly to the VCS-E they are in local(default)zone.

Re: VCS-E: calls to unknown IP address not happening for gateway

Hi,

It seems VCS is trying to interwork the call, that's why you have the destination as "URI" and not as H323id, which is the correct. Well, just for testing, could you please turn off interworking on VCS and remake the test? Could you post the search result for this new call?

Regards

Paulo Souza

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

Paulo Souza Was my response helpful? Please rate useful replies and remember to mark any solved questions as "answered".
Community Member

VCS-E: calls to unknown IP address not happening for gateway dev

sorry, no we cannot turn off interworking, being used by customers. Don't understand why the gateway - when it calls to 123@xxx.xxx.xxx.xxx -  is apparently telling the VCS-E that its a Url, rather than a h323ID, like the MCU does.

VCS-E: calls to unknown IP address not happening for gateway dev

Hi John,

what's your setting for interworking "registered only" or "on" ??

Rgds

Alok

Re: VCS-E: calls to unknown IP address not happening for gateway

Hi John,

Ok, no problem.

My hint is, VCS is trying to interwork the call, that's why you see destination as URI and not as H323id. I don't think it should happen, because the source alias is H323id just like the MCU.

Well, turning off the Interworking is the best option to validate the behavior of VCS in this case.

Paulo Souza

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

Paulo Souza Was my response helpful? Please rate useful replies and remember to mark any solved questions as "answered".
Community Member

VCS-E: calls to unknown IP address not happening for gateway dev

Our setting for Interworking is Registered Only".    I'll try turning off interworking off-hours, maybe tonight. Anyway to force a call to "calls to Unknown IP addresses"?

Re: VCS-E: calls to unknown IP address not happening for gateway

Well, VCS macthes "Call to Unknown IP address" rule when you set the dial plan to "direct" mode, and when you dial a unknown IP Address or SIP URI. You cannot force a call to reach this rule exactly, VCS takes this decision based upon the current dial plan configuration and the destination number dialed.

Paulo Souza


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

Paulo Souza Was my response helpful? Please rate useful replies and remember to mark any solved questions as "answered".
Community Member

VCS-E: calls to unknown IP address not happening for gateway dev

thats what is frustrating - clearly the "left" search goes through all the search rules and ends up in DNS rule, and doesn't find it - shouldn't it go to "CalltoUnknownIP address" then - ?

Re: VCS-E: calls to unknown IP address not happening for gateway

In fact, the call should match "Call to Unknown IP Address" rule alone.  =/

Paulo Souza

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

Paulo Souza Was my response helpful? Please rate useful replies and remember to mark any solved questions as "answered".

Re: VCS-E: calls to unknown IP address not happening for gateway

Hi John,

I just replicated your issue in my lab. I have made several tests from SIP and H323 endpoints registered to VCS-E dialling this number 20614667@122.98.28.101. For all the tests the result were ok, even when the destination is SIP URI 20614667@122.98.28.101 dialed from a SIP endpoint. In all the tests the search result was "Call to Unknown IP Address". I also have interworking set to "Registered only".

Well, I really think there is some strange behavior going on here, so I would suggest you to make the test again by turning off the interworking feature on VCS (when you can). If it works when interworking is off, so I suggest you to upgrade your VCS to the latest software version, 7.2.2 (I am using that version), then you can re-enable interworking and test again.

If you keep having the same issue even with lastest software version, it will be necessary to analyse the logs in VCS in order to figure out what is causing the issue, in this case, I suggest you to open a TAC request. You can open the case from this discussion, so that TAC team will have the initial history of your case, it can be helpfull.

And John, if TAC resolves your problem (I believe they will), please, post the result here to help another people with similar problem.  =)

I hope this help

Paulo Souza

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

Paulo Souza Was my response helpful? Please rate useful replies and remember to mark any solved questions as "answered".
Community Member

VCS-E: calls to unknown IP address not happening for gateway dev

Hi Paulo - I turned off interworking and it was denied:. I guess I'll upgrade SW - currently at 7.2 I'll return to this discussion then - Thanks all!

  • Search (288)
    • State: Completed
    • Found: False
    • Reason: Request denied
    • Type: H323 (ARQ)
    • CallSerial Number: 71864062-0b11-11e3-9e2d-0010f321e6ee
    • Tag: 718641ac-0b11-11e3-a83f-0010f321e6ee
    • Source (1)
      • Authenticated: True
      • Aliases (1)
        • Alias (1)
          • Type: H323Id
          • Origin: Endpoint
          • Value: OEGateway3
      • Zone (1)
        • Name: DefaultSubZone
        • Type: Local
      • Path (1)
        • Hop (1)
          • Address: 10.20.20.5
    • Destination (1)
      • Alias (1)
        • Type: Url
        • Origin: Unknown
        • Value: 20614667@122.98.28.101
    • StartTime: 2013-08-22 05:58:49
    • Duration: 0.28
    • SubSearch (1)
      • Type: Transforms
      • Action: Not Transformed
      • ResultAlias (1)
        • Type: Url
        • Origin: Unknown
        • Value: 20614667@122.98.28.101
      • SubSearch (1)
        • Type: Admin Policy
        • Action: Proxy
        • ResultAlias (1)
          • Type: Url
          • Origin: Unknown
          • Value: 20614667@122.98.28.101
        • SubSearch (1)
          • Type: FindMe
          • Action: Proxy
          • ResultAlias (1)
            • Type: Url
            • Origin: Unknown
            • Value: 20614667@122.98.28.101
          • SubSearch (1)
            • Type: Search Rules
            • SearchRule (1)
              • Name: LocalZoneMatch
              • Zone (1)
                • Name: LocalZone
                • Type: Local
                • Protocol: H323
                • Found: False
                • Reason: Not Found
                • StartTime: 2013-08-22 05:58:49
                • Duration: 0
                • Gatekeeper (1)
                  • Address: 10.20.7.7:0
                  • Alias (1)
                    • Type: Url
                    • Origin: Unknown
                    • Value: 20614667@122.98.28.101
            • SearchRule (2)
              • Name: DNS
              • Zone (1)
                • Name: DNS
                • Type: DNS
                • Protocol: H323
                • Found: False
                • Reason: Request denied
                • StartTime: 2013-08-22 05:58:49
                • Duration: 0.26
                • Gatekeeper (1)
                  • Alias (1)
                    • Type: Url
                    • Origin: Unknown
                    • Value: 20614667@122.98.28.101

VCS-E: calls to unknown IP address not happening for gateway dev

Hi John,

i believe since the calls is generated from a neighour zone and that could be a reason VCS treatingit differently but not sure untill we see logs on VCS control and exp.

did you opened the TAC case? can you tell me the SR number

Rgds

Alok

Re: VCS-E: calls to unknown IP address not happening for gateway

Alok

In fact, the gateway is registered to VCS, just like the MCU. This is the most strange thing here.  =/

Please, if you take the case, post the result here when you find a solution, that would be nice.

Regards

Paulo Souza

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

Paulo Souza Was my response helpful? Please rate useful replies and remember to mark any solved questions as "answered".
Community Member

VCS-E: calls to unknown IP address not happening for gateway dev

The call is generated from the local default zone, not a neighbor zone. Same zone as the MCU is in (whose call to same destination works).

    • Zone (1)
      • Name: DefaultSubZone
      • Type: Local
Community Member

VCS-E: calls to unknown IP address not happening for gateway dev

Hi Alok - I have not opened a TAC case because I just learned our maintenence contract expired in May!  It's thru a partner in any case so I'll have to open it with Viju when we get the PO cut.  Thanks for your help...I'll keep you updated.

VCS-E: calls to unknown IP address not happening for gateway dev

Hi John,

i will give a try in my lab and see if i can replicate or not. i sent you a message can you check and reply.

Rgds

Alok

Community Member

Re: VCS-E: calls to unknown IP address not happening for gateway

Hi All - just renewed maintenence & we will be upgrading SW soon. But, I have a serious need to dial two endpoints from this gateway using the 123@IPaddress format in the near future.

Can anyone think of a way I can fool the VCS-E to send these out rather than going off to DNS zone and getting "Request Denied"?

I can make specific search rule just for these addresses, but don't even know where to point them...Ideas?

Re: VCS-E: calls to unknown IP address not happening for gateway

Hi John,

In this case, as workaround, I think you can try to create a neighbor zone in VCS that points to the remote, then you create a search rule that matches that destination alias and send it through that neighbor zone.

When you create the neighbor zone, please, pay attention to the neighbor zone profile type, may you will have to try some different options, the right choice depends upon the kind of system you have on the remote side (gatekeeper, sip server, endpoint, gateway and so son).

Paulo Souza

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

Paulo Souza Was my response helpful? Please rate useful replies and remember to mark any solved questions as "answered".
Community Member

Re: VCS-E: calls to unknown IP address not happening for gateway

Thanks, Paulo - I tried that, didn't work - neighbor zone kept denying call.  BUT what did work, I created a pre-search transform that took any call in this format (alias@IPaddress) and pre-pends "sip:" in front of it - that effectifly turns the url into a h323id and the call gets routed to "callstoUnknownIP address" and woks fine - see search below:

  • Search (474)
    • State: Completed
    • Found: True
    • Type: H323 (Setup)
    • CallRouted: True
    • CallSerial Number: 616c0a58-1170-11e3-8925-0010f321e6ee
    • Tag: 616c0bac-1170-11e3-a76b-0010f321e6ee
    • Source (1)
      • Authenticated: False
      • Aliases (1)
        • Alias (1)
          • Type: H323Id
          • Origin: Unknown
          • Value: OEGateway3
      • Zone (1)
        • Name: LocalZone
        • Type: Local
    • Destination (1)
      • Alias (1)
        • Type: Url
        • Origin: Unknown
        • Value: 20614667@122.98.28.101
    • StartTime: 2013-08-30 08:33:32
    • Duration: 0.82
    • SubSearch (1)
      • Type: Transforms
      • Action: Transformed
      • ResultAlias (1)
        • Type: H323Id
        • Origin: Unknown
        • Value: sip:20614667@122.98.28.101
      • SubSearch (1)
        • Type: Admin Policy
        • Action: Proxy
        • ResultAlias (1)
          • Type: H323Id
          • Origin: Unknown
          • Value: sip:20614667@122.98.28.101
        • SubSearch (1)
          • Type: FindMe
          • Action: Proxy
          • ResultAlias (1)
            • Type: H323Id
            • Origin: Unknown
            • Value: 20614667@122.98.28.101
          • SubSearch (1)
            • Type: Search Rules
            • CallsToUnknownIPAddresses (3)
              • Mode: Direct
              • Zone (1)
                • Name: DefaultZone
                • Type: Default
                • Protocol: H323
                • Found: True
                • StartTime: 2013-08-30 08:33:32
                • Duration: 0.8
                • Gatekeeper (1)
                  • Address: 122.98.28.101:1720
                  • Alias (1)
                    • Type: H323Id
                    • Origin: Unknown
                    • Value: 20614667@122.98.28.101
            • SearchRule (1)
              • Name: LocalZoneMatch
              • Zone (1)
                • Name: LocalZone
                • Type: Local
                • Protocol: H323
                • Found: False
                • Reason: Not Found
                • StartTime: 2013-08-30 08:33:32
                • Duration: 0
                • Gatekeeper (1)
                  • Address: 10.20.7.7:0
                  • Alias (1)
                    • Type: H323Id
                    • Origin: Unknown
                    • Value: 20614667@122.98.28.101
              • Zone (2)
                • Name: LocalZone
                • Type: Local
                • Protocol: SIP
                • Found: False
                • Reason: Not Found
                • StartTime: 2013-08-30 08:33:32
                • Duration: 0
                • Gatekeeper (1)
                  • Address: 10.20.7.7:0
                  • Alias (1)
                    • Type: H323Id
                    • Origin: Unknown
                    • Value: 20614667@122.98.28.101

Re: VCS-E: calls to unknown IP address not happening for gateway

Hi John,

It is nice to see that your issue has been resolved!

However, I am really surprise with that strange behavior of VCS. It should not be necessary to add "sip:" in order to the call to be treated as "Call To Unknown IP Address", the call should be routed that way simply by dialling an IP address or SIP URI with an IP address in the domain portion.

Well, if you can, please, try to update your VCS just to see if something changes, because, as I stated, in my VCS 7.2.2, I have it working without any issue. I am really curious about this matter.

Thanks for your feed back.

Regards

Paulo Souza

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

Paulo Souza Was my response helpful? Please rate useful replies and remember to mark any solved questions as "answered".
765
Views
0
Helpful
23
Replies
CreatePlease to create content