08-21-2013 05:58 AM - edited 03-18-2019 01:40 AM
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....
08-21-2013 06:28 AM
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.
08-21-2013 07:08 AM
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
08-21-2013 07:21 AM
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-0010f321e6ee | CallSerial 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 | |||||||||||
08-21-2013 07:22 AM
also - we have only VCS-E - our MCU & the the gateways register directly to the VCS-E they are in local(default)zone.
08-21-2013 07:30 AM
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.
08-21-2013 07:42 AM
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.
08-21-2013 07:48 AM
Hi John,
what's your setting for interworking "registered only" or "on" ??
Rgds
Alok
08-21-2013 07:50 AM
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.
08-21-2013 08:03 AM
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"?
08-21-2013 08:18 AM
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.
08-21-2013 08:23 AM
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 - ?
08-21-2013 08:40 AM
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.
08-21-2013 09:09 AM
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.
08-22-2013 03:02 AM
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!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide