cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1876
Views
5
Helpful
7
Replies

Video call disconnects frequently.

JavidHasan
Level 1
Level 1

Hi All,

My video call (point to point) disconnects frequently and when i try to call again it gives an error "No route to destination - Unknown reason" . When The call connects it stays for some time and then again disconnects.

The other endpoint im calling is on the remote location. We have IPVPN link with very good bandwith between these locations.

I searched the call history on the VCS control and could see the below message. Sometimes i also see packet loss when i ping the endpoint when in call. Need you support to know where exactly the problem is. I suspect it to be a network issue.

  • Search (304)
  • State: Completed
  • Found: False
  • Reason: No route to destination - Unknown reason
  • Type: H323 (Setup)
  • CallSerial Number: 9bea533e-6304-11e3-86a0-0010f31da2a0
  • Tag: 9bea5488-6304-11e3-afb7-0010f31da2a0
  • Source (1)
    • Authenticated: False
    • Aliases (1)
    • Zone (1)
      • Name: LocalZone
      • Type: Local
  • Destination (1)
    • Alias (1)
      • Type: IPAddress
      • Origin: Unknown
      • Value: 10.1.27.13
  • StartTime: 2013-12-12 11:08:39
  • Duration: 10.85
  • SubSearch (1)
    • Type: Transforms
    • Action: Not Transformed
    • ResultAlias (1)
      • Type: IPAddress
      • Origin: Unknown
      • Value: 10.1.27.13
    • SubSearch (1)
      • Type: Admin Policy
      • Action: Proxy
      • ResultAlias (1)
        • Type: IPAddress
        • Origin: Unknown
        • Value: 10.1.27.13
      • SubSearch (1)
        • Type: FindMe
        • Action: Proxy
        • ResultAlias (1)
          • Type: IPAddress
          • Origin: Unknown
          • Value: 10.1.27.13
        • SubSearch (1)
          • Type: Search Rules
          • SearchRule (1)
            • Name: LocalZoneMatch_AnyIPAddress_H323
            • Zone (1)
              • Name: LocalZone
              • Type: Local
              • Protocol: H323
              • Found: False
              • Reason: No route to destination - Unknown reason
              • StartTime: 2013-12-12 11:08:39
              • Duration: 7.74
              • Gatekeeper (1)
                • Address: 10.1.27.13:1720
                • Alias (1)
                  • Type: IPAddress
                  • Origin: Unknown
                  • Value: 10.1.27.13
            • Zone (2)
              • Name: LocalZone
              • Type: Local
              • Protocol: SIP
              • Found: False
              • Reason: Request Timeout
              • StartTime: 2013-12-12 11:08:47
              • Duration: 0.02
              • Gatekeeper (1)
                • Alias (1)
                  • Type: IPAddress
                  • Origin: Unknown
                  • Value: 10.1.27.13
          • SearchRule (2)
            • Name: MOE_VCSE_AnyIPAddress
            • Zone (1)
              • Name: MOE_travs_C
              • Type: TraversalClient
              • Protocol: H323
              • Found: True
              • StartTime: 2013-12-12 11:08:47
              • Duration: 0.02
              • Gatekeeper (1)
                • Address: 195.246.104.43:6001
                • Alias (1)
                  • Type: IPAddress
                  • Origin: Unknown
                  • Value: 10.1.27.13
    1 Accepted Solution

    Accepted Solutions

    Do a network trace on both sides. If what is send is not what is expected to be received

    some other magic must have happened to the packets.

    In general the VCS is quite stable, so if it does not work the likeliness of being a network issue

    is quite high.

    If you post a question please alsway mention the used components and software versions used.

    For a Cisco/Tandberg only setup I am pretty sure its the network, if you have some third party

    device it might be some incompatiblity as well, ...

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

    Please remember to rate helpful responses and identify

    View solution in original post

    7 Replies 7

    Martin Koch
    VIP Alumni
    VIP Alumni

    Yes, it sounds like a network issue for me as well.

    Check if your VPN has either some short TCP timeouts, if some NAT / load balance is done,

    some firewall is blocking something or if there is some kind of h323 application awareness.

    Does the same happen if you use sip/5061/tls?

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

    Please remember to rate helpful responses and identify

    JavidHasan
    Level 1
    Level 1

    Thanks for the reply. Is there anyway I can confirm that this issue is related to network and not endpoint or VCS control. Any idea?

    Sent from Cisco Technical Support iPhone App

    Do a network trace on both sides. If what is send is not what is expected to be received

    some other magic must have happened to the packets.

    In general the VCS is quite stable, so if it does not work the likeliness of being a network issue

    is quite high.

    If you post a question please alsway mention the used components and software versions used.

    For a Cisco/Tandberg only setup I am pretty sure its the network, if you have some third party

    device it might be some incompatiblity as well, ...

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

    Please remember to rate helpful responses and identify

    Hi Martin

    Thanks for your support. I did a network trace on both sides from endpoint to endpoint :

    traceroute 10.100.50.126 TANDBERG Profile 6000MXP

    OK
    1 10.1.27.3        time=0.7 ms
    2 10.1.7.33        time=0.7 ms
    3 10.1.100.84      time=1.1 ms
    4 172.31.158.93    time=1.2 ms
    5 172.31.171.18    time=1.4 ms
    6 10.100.5.235     time=1.9 ms
    7 10.100.7.18      time=7.6 ms
    8 10.100.50.126    time=3.6 ms
    Done

    traceroute 10.1.27.102 TANDBERG Edge 95MXP

    OK
    1 10.100.50.1      time=0.7 ms
    2 10.100.7.17      time=7.2 ms
    3 10.100.5.241     time=0.9 ms
    4 172.31.171.17    time=1.4 ms
    5 172.31.158.94    time=1.4 ms
    6 10.1.100.1       time=2.4 ms
    7 10.1.7.34        time=1.9 ms
    8 10.1.27.102      time=2.4 ms
    Done

    Do you think there is some delay in between. The VCS Version:X7.2.2 is being used.

    hehe, no I did not think of a traceroute, though it has some hops inbetween that looks fine.

    I though of a network trace, like capturing network packets with a mirror port and a tool

    like wireshark/tcpdump or some sniffing appliance.

    That can show and analyze the data send over, and if you can see that some device

    is behaving not as you expect, you know there is the problem.

    But the traceroute is also ok, as you might take it and try to figure out which ip is

    what kind of device and is doing what.

    Most likely one of these devices is doing more than just to forward packages.

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

    Please remember to rate helpful responses and identify

    Hi Martin

    It was indeed a network issue and network guys solved it. Thanks for your support.

    Sent from Cisco Technical Support iPhone App

    Hi! Thank you for setting it to answered and giving a feedback! +5 for you!

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

    Please remember to rate helpful responses and identify

    Getting Started

    Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: