VCS EXPRESSWAY IP ADDRESS DIALING

KRISHNA K V · ‎11-07-2013

Hi,

We have a VCS control and VCS experssway cluster setup with Cisco endpoints. We are able to dial out via the vcs expressway by dialing the URI address of endpoints in the internet. But We are not able to dialout using the ip address of the endpoints. All the configuraitons are as per the cofniguraiton guide.

when i changed the sip udp mode to on in the vcs sip protocol page we are able to dialout to some of the ip address. But failure rate is high.

let me know if anyone has faced this issue and found out a solution.

Krishna.

Jens Didriksen · ‎11-07-2013

I take it you have the "Any IP Address" search rule pointing to the traversal zone in place on the VCS-C?

H.323/SIP interworking enabled?

Are the end-points you are trying to call the same end-points you can connect to using URI, or are they stand-alone end-points with a public IP address?

What error message do you get for the failed calls?

Can you connect to a known "good" IP address, such as 72.14.2.158 ? (See http://vtctest.pointsofdata.com/ )

/jens

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

KRISHNA K V · ‎11-08-2013

Hi Jens,

I have the "any ip address search rule" and the call is reaching the vcs expressway.when i dial the uri of the endpiont, call is getting connected but when i dial the IP address of the endpoint its not getting connected. the error message i receive is request timed out or no route to destination.

when i change the SIP udp option to on, sometimes its getting connected when we dial the IP address.

is there any compatability issues between the cisco and other Vendor endpoints when we dial the ip address?

Krishna

Jens Didriksen · ‎11-08-2013

KRISHNA VEERAMANI wrote:

..when i dial the uri of the endpiont, call is getting connected but when i dial the IP address of the endpoint its not getting connected. the error message i receive is request timed out or no route to destination.

So, you are trying to connect to the same end-point using both URI and IP address?

If that's the case then using the IP address shouldn't really work at all unless they have configured the infrastructure at their end to allow this - even if they have, then the outcome can be highly erratic as using IP addresses are normally used to connect to end-points which are not registered to a VCS, Gatekeeper etc.

Hence using this dialling method to connect to a registered end-point is not recommended.

If you are trying to connect to a stand-alone end-point, and these calls are failing, then you could have a problem, or the problem could be with the system you are trying to connect to. That is why I asked if you can connect to 72.14.2.158 as this is a "known good IP address".

If you can connect to the above address from you C60 using H.323 - and if you have interworking enabled - also SIP, then your end is fine.

Calling from JabberVideo client is a different story as this is a SIP client, so you either need to have interworking in place, which means the call will go SIP-->H323 as going SIP-->SIP won't work in this case.

JabberVideo, being a SIP client, will add your SIP domain to the address, so you might be dialling 123.122.12.3, JabberVideo will try to dial this as 123.122.12.3@mysipdomain.com

Yes, there are ways around this, but these are not part of "basic" configuration as such.

is there any compatability issues between the cisco and other Vendor endpoints when we dial the ip address?

No, an IP address is an IP address, regardless of the vendor.

"I have the "any ip address search rule" and the call is reaching the vcs expressway."

The "Any IP address" rule is for calls using IP addresses, you should also have a rule pointing to DNS which takes care of the URI dialling - that's part of the configuration guide and since you are able to connect using URI, then that would indicate you have this in place. There is a difference between the two though.

/jens

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

Martin Koch · ‎11-07-2013

It would also be helpful if you know and also tell us what kind of communication you expect.

In general the typical "IP call" are h323 calls, connecting to the remote site on port 1720/tcp.

What you said you enabled which made it better is SIP 5060/udp. This most often complicates things

as if you initate a call with sip and the remote site does not answer it adds 30sec of delay

The basic vcs-c/-e deployment guide has the setup, in short:

* proper traversal zone for h323 and sip

* proper firewall rules in place

* generic deployment ok

* Calls to unknown IP addresses: indirect on vcs-c

* the AnyIP search rules Jan mentioned

* Calls to unknown IP addresses: direct on vcs-e

* interworking might need to be enabled

The success might also be dependent on the endpoint type, software version, (default / ) used call protocol,

type on how you dialed (manual, with the touchpad, remote, from the phonebook, call history, api, ...) ...

So if you could tell us a bit more about that and show us the search details of this call then we can say more.

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

Please remember to rate helpful responses and identify

KRISHNA K V · ‎11-08-2013

Hi Martin,

All the configuration as pe the deployment guide is in place. the endpoint which we are using to dial out is c60 and Jabber video. I tried c60 default call protocol as h323 as well as sip. I will provide the searche rules tomorrow when i visit the

site.

Krishna.

KRISHNA K V · ‎11-09-2013

Hi Jens,

Please find below the search history. in the h323 (lrq) message the result is found. But in the H323 setup message i am getting the error no route to the desintation.

Search (219)
- State: Completed
- Found: True
- Type: H323 (LRQ)
- CallRouted: True
- CallSerial Number: 60fe593c-492d-11e3-a1d9-0010f32c89b2
- Tag: 60d11b20-492d-11e3-883a-0010f32d00dc
- Source (1)
- - Authenticated: True
- - Aliases (1)
  - - Alias (1)
    - - Type: H323Id
    - - Origin: Endpoint
    - Value: 7001@example.com
- - Zone (1)
  - - Name: Traversal Zone
  - - Type: TraversalServer
- - Path (1)
  - - Hop (1)
    - - Address: 10.0.200.20
  - - Hop (2)
    - - Address: 10.0.91.11:5061
- Destination (1)
- - Alias (1)
  - - Type: H323Id
  - - Origin: Unknown
  - - Value: 71.14.2.158
- StartTime: 2013-11-09 13:55:00
- Duration: 0.01
- SubSearch (1)
- - Type: Transforms
- - Action: Not Transformed
- - ResultAlias (1)
  - - Type: H323Id
  - - Origin: Unknown
  - - Value: 71.14.2.158
- - SubSearch (1)
  - - Type: Admin Policy
  - - Action: Proxy
  - - ResultAlias (1)
    - - Type: H323Id
    - - Origin: Unknown
    - - Value: 71.14.2.158
  - - SubSearch (1)
    - - Type: FindMe
    - - Action: Proxy
    - - ResultAlias (1)
      - Type: H323Id
      - Origin: Unknown
      - Value: 71.14.2.158
    - - SubSearch (1)
      - Type: Search Rules
      - CallsToUnknownIPAddresses (1)
        
        Mode: Direct
        
        Zone (1)
        
        Name: DefaultZone
        
        Type: Default
        
        Protocol: H323
        
        Found: True
        
        StartTime: 2013-11-09 13:55:00
        
        Duration: 0
        
        Gatekeeper (1)
        
        Address: 71.14.2.158:1720
        
        Alias (1)
        
        Type: H323Id
        
        Origin: Unknown
        
        Value: 71.14.2.158

Search (220)
- State: Completed
- Found: False
- Reason: No route to destination - Unreachable destination
- Type: H323 (Setup)
- CallSerial Number: 60fe593c-492d-11e3-a1d9-0010f32c89b2
- Tag: 60d11b20-492d-11e3-883a-0010f32d00dc
- Source (1)
- - Authenticated: False
- - Aliases (1)
  - - Alias (1)
    - - Type: H323Id
    - - Origin: Unknown
    - - Value: 7001@example.com
  - - Alias (2)
    - - Type: E164
    - - Origin: Unknown
    - - Value: 7001
- - Zone (1)
  - - Name: Traversal Zone
  - - Type: TraversalServer
- Destination (1)
- - Alias (1)
  - - Type: H323Id
  - - Origin: Unknown
  - - Value: 71.14.2.158
- StartTime: 2013-11-09 13:55:00
- Duration: 32.32
- SubSearch (1)
- - Type: Transforms
- - Action: Not Transformed
- - ResultAlias (1)
  - - Type: H323Id
  - - Origin: Unknown
  - - Value: 71.14.2.158
- - SubSearch (1)
  - - Type: Admin Policy
  - - Action: Proxy
  - - ResultAlias (1)
    - - Type: H323Id
    - - Origin: Unknown
    - - Value: 71.14.2.158
  - - SubSearch (1)
    - - Type: FindMe
    - - Action: Proxy
    - - ResultAlias (1)
      - Type: H323Id
      - Origin: Unknown
      - Value: 71.14.2.158
    - - SubSearch (1)
      - Type: Search Rules
      - CallsToUnknownIPAddresses (1)
        
        Mode: Direct
        
        Zone (1)
        
        Name: DefaultZone
        
        Type: Default
        
        Protocol: H323
        
        Found: False
        
        Reason: No route to destination - Unreachable destination
        
        StartTime: 2013-11-09 13:55:00
        
        Duration: 0.01
        
        Gatekeeper (1)
        
        Address: 71.14.2.158:1720
        
        Alias (1)
        
        Type: H323Id
        
        Origin: Unknown
        
        Value: 71.14.2.158
        
        Zone (2)
        
        Name: DefaultZone
        
        Type: Default
        
        Protocol: SIP
        
        Found: False
        
        Reason: Bad Extension
        
        StartTime: 2013-11-09 13:55:00
        
        Duration: 0.29
        
        Gatekeeper (1)
        
        Alias (1)
        
        Type: H323Id
        
        Origin: Unknown
        
        Value: 71.14.2.158

Krishna.

KRISHNA K V · ‎11-09-2013

Hi Jens,

Now i am able to make a call by dialling the ip address. Firewall rules are not configured properly. port 1720 was blocked in the firewall.

But if i call from SIP endpoint to h323 endpoint call is getting disconnected. Interworking call is not working.

Krishna.

Jens Didriksen · ‎11-09-2013

Hi Krishna,

Glad to see you got it working

I take it interworking is enabled on all VCS-C and VCS-E and all set to the same, most probably "Registered only"?

The call should be interworked on the VCS-C so it'll go SIP-->H323 and be sent to the VCS-E as H.323.

/jens

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

KRISHNA K V · ‎11-09-2013

Hi Jens,

Yes interworking is turned on. The settings is ON in Control and Expressway. As suggested by you will change it to regisstered only and check.

Krishna.

Jens Didriksen · ‎11-09-2013

Also use the "locate" tool on the VCS-C and see if it actually transforms the call from SIP to H.323 as it should;

Search (13)
- State: Completed
- Found: True
- Type: SIP (OPTIONS)
- CallRouted: False
- CallSerial Number: 7b8e7780-49d9-11e3-b058-0010f319dbfc
- Tag: 7b8e79c4-49d9-11e3-9c2e-0010f319dbfc
- Source (1)
- - Authenticated: True
- - Aliases (1)
  - - Alias (1)
    - - Type: Url
    - - Origin: Unknown
      - Value: jens.xxx.xxx@mydomain.com
- - Zone (1)
  - - Name: Movi
  - - Type: Local
- - Path (1)
  - - Hop (1)
    - - Address: 127.0.0.1
- Destination (1)
- - Alias (1)
  - - Type: Url
  - - Origin: Unknown
  - - Value: sip:71.14.2.158
- StartTime: 2013-11-10 17:26:58
- Duration: 0.04
- SubSearch (1)
- - Type: Transforms
- - Action: Not Transformed
- - ResultAlias (1)
  - - Type: Url
  - - Origin: Unknown
  - - Value: 71.14.2.158
- - SubSearch (1)
  - - Type: Admin Policy
  - - Action: Proxy
  - - ResultAlias (1)
    - - Type: Url
    - - Origin: Unknown
    - - Value: 71.14.2.158
  - - SubSearch (1)
    - - Type: FindMe
    - - Action: Proxy
    - - ResultAlias (1)
      - Type: Url
      - Origin: Unknown
      - Value: 71.14.2.158
    - - SubSearch (1)
      - Type: Search Rules

/jens

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

KRISHNA K V · ‎11-10-2013

Hi Jens,

When i tried to dial 72.14.2.158 now its not working. It worked in the morning from my office. I want to know if the endpoint is working fine. Could you please let me knwo if is this working

Krishna.

KRISHNA K V · ‎11-10-2013

Now i am receiving the error no route to destination unreachable destination.

Krishna.

Jens Didriksen · ‎11-10-2013

It's 71, not 72 - so 71.14.2.158 - just dialled it now from home using JabberVideo, connected right away.

/jens

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

KRISHNA K V · ‎11-10-2013

Hi Jens,

I tried with teh correct ip address. But calls are disconencting. Checked the debug and found the following in the expressway logs.

2013-11-10T11:51:08+03:00 qmavcse1 tvcs: UTCTime="2013-11-10 08:51:08,546" Module="network.tcp" Level="DEBUG": Src-ip="10.0.200.20" Src-port="15394" Dst-ip="192.168.4.20" Dst-port="2776" Detail="TCP Connecting"

2013-11-10T11:51:08+03:00 qmavcse1 tvcs: UTCTime="2013-11-10 08:51:08,547" Module="network.tcp" Level="DEBUG": Src-ip="10.0.200.20" Src-port="15394" Dst-ip="192.168.4.20" Dst-port="2776" Detail="TCP Connection Established"

2013-11-10T11:51:08+03:00 qmavcse1 tvcs: UTCTime="2013-11-10 08:51:08,547" Module="network.tcp" Level="DEBUG": Src-ip="192.168.5.20" Src-port="15178" Dst-ip="71.14.2.158" Dst-port="49160" Detail="TCP Connecting"

2013-11-10T11:51:08+03:00 qmavcse1 tvcs: UTCTime="2013-11-10 08:51:08,547" Module="network.tcp" Level="ERROR": Src-ip="192.168.5.20" Src-port="15178" Dst-ip="71.14.2.158" Dst-port="49160" Detail="TCP Connection Failed"

2013-11-10T11:51:08+03:00 qmavcse1 tvcs: UTCTime="2013-11-10 08:51:08,547" Module="network.h323" Level="ERROR": Dst-ip="71.14.2.158" Dst-port="49160"

Detail="Failed to connect outbound H.245 TCP connection. Rejecting inbound H.245 TCP connection."

2013-11-10T11:51:08+03:00 qmavcse1 tvcs: UTCTime="2013-11-10 08:51:08,547" Module="network.tcp" Level="DEBUG": Src-ip="10.0.200.20" Src-port="15394" Dst-ip="192.168.4.20" Dst-port="2776" Detail="TCP Connection Closed"

We have a rule in the firewall to allow ports >1024 from the expressway second interface to endpionts in the internet.

Krishna.