Cannot connect to Tunnel

Discussion in '3CX Phone System - General' started by Natural, Jun 11, 2009.

Thread Status:
Not open for further replies.
  1. Natural

    Joined:
    May 10, 2009
    Messages:
    11
    Likes Received:
    0
    I have provided the following below to see if someone might help me find out why we cannot connect to Tunnel.

    3CX Firewall Checker, v1.0. Copyright (C) 3CX Ltd. All rights reserved.

    <02:03:51>: Phase 1, checking servers connection, please wait...
    <02:03:51>: Stun Checker service is reachable. Phase 1 check passed.
    <02:03:51>: Phase 2a, Check Port Forwarding to UDP SIP port, please wait...
    <02:03:56>: UDP SIP Port is set to 5060. Response received WITH TRANSLATION 61581::5060. Phase 2a check passed with WARNINGS. Some functionality will be LIMITED. For more information, please visit http://www.3cx.com/support/firewall-checker.html

    <02:03:56>: Phase 2b. Check Port Forwarding to TCP SIP port, please wait...
    <02:04:01>: TCP SIP Port is set to 5060. Response received WITH TRANSLATION 61581::5060. Phase 2b check passed with WARNINGS. Some functionality will be LIMITED. For more information, please visit http://www.3cx.com/support/firewall-checker.html

    <02:04:01>: Phase 3. Check Port Forwarding to TCP Tunnel port, please wait...
    <02:04:05>: TCP TUNNEL Port is set to 5090. Response received correctly with no translation. Phase 3 check passed.

    <02:04:05>: Phase 4. Check Port Forwarding to RTP external port range, please wait...
    <02:04:12>: UDP RTP Port 9000. Response received correctly with no translation. Phase 4-01 check passed.
    <02:04:16>: UDP RTP Port 9001. Response received correctly with no translation. Phase 4-02 check passed.
    <02:04:21>: UDP RTP Port 9002. Response received correctly with no translation. Phase 4-03 check passed.
    <02:04:25>: UDP RTP Port 9003. Response received correctly with no translation. Phase 4-04 check passed.
    <02:04:30>: UDP RTP Port 9004. Response received correctly with no translation. Phase 4-05 check passed.
    <02:04:34>: UDP RTP Port 9005. Response received correctly with no translation. Phase 4-06 check passed.
    <02:04:39>: UDP RTP Port 9006. Response received correctly with no translation. Phase 4-07 check passed.
    <02:04:43>: UDP RTP Port 9007. Response received correctly with no translation. Phase 4-08 check passed.
    <02:04:48>: UDP RTP Port 9008. Response received correctly with no translation. Phase 4-09 check passed.
    <02:04:52>: UDP RTP Port 9009. Response received correctly with no translation. Phase 4-10 check passed.
    <02:04:57>: UDP RTP Port 9010. Response received correctly with no translation. Phase 4-11 check passed.
    <02:05:01>: UDP RTP Port 9011. Response received correctly with no translation. Phase 4-12 check passed.
    <02:05:06>: UDP RTP Port 9012. Response received correctly with no translation. Phase 4-13 check passed.
    <02:05:10>: UDP RTP Port 9013. Response received correctly with no translation. Phase 4-14 check passed.
    <02:05:15>: UDP RTP Port 9014. Response received correctly with no translation. Phase 4-15 check passed.
    <02:05:19>: UDP RTP Port 9015. Response received correctly with no translation. Phase 4-16 check passed.
    <02:05:24>: UDP RTP Port 9016. Response received correctly with no translation. Phase 4-17 check passed.
    <02:05:28>: UDP RTP Port 9017. Response received correctly with no translation. Phase 4-18 check passed.
    <02:05:33>: UDP RTP Port 9018. Response received correctly with no translation. Phase 4-19 check passed.
    <02:05:37>: UDP RTP Port 9019. Response received correctly with no translation. Phase 4-20 check passed.
    <02:05:42>: UDP RTP Port 9020. Response received correctly with no translation. Phase 4-21 check passed.
    <02:05:46>: UDP RTP Port 9021. Response received correctly with no translation. Phase 4-22 check passed.
    <02:05:51>: UDP RTP Port 9022. Response received correctly with no translation. Phase 4-23 check passed.
    <02:05:55>: UDP RTP Port 9023. Response received correctly with no translation. Phase 4-24 check passed.
    <02:06:00>: UDP RTP Port 9024. Response received correctly with no translation. Phase 4-25 check passed.
    <02:06:04>: UDP RTP Port 9025. Response received correctly with no translation. Phase 4-26 check passed.
    <02:06:09>: UDP RTP Port 9026. Response received correctly with no translation. Phase 4-27 check passed.
    <02:06:13>: UDP RTP Port 9027. Response received correctly with no translation. Phase 4-28 check passed.
    <02:06:18>: UDP RTP Port 9028. Response received correctly with no translation. Phase 4-29 check passed.
    <02:06:22>: UDP RTP Port 9029. Response received correctly with no translation. Phase 4-30 check passed.
    <02:06:27>: UDP RTP Port 9030. Response received correctly with no translation. Phase 4-31 check passed.
    <02:06:31>: UDP RTP Port 9031. Response received correctly with no translation. Phase 4-32 check passed.
    <02:06:36>: UDP RTP Port 9032. Response received correctly with no translation. Phase 4-33 check passed.
    <02:06:40>: UDP RTP Port 9033. Response received correctly with no translation. Phase 4-34 check passed.
    <02:06:45>: UDP RTP Port 9034. Response received correctly with no translation. Phase 4-35 check passed.
    <02:06:49>: UDP RTP Port 9035. Response received correctly with no translation. Phase 4-36 check passed.
    <02:06:54>: UDP RTP Port 9036. Response received correctly with no translation. Phase 4-37 check passed.
    <02:06:58>: UDP RTP Port 9037. Response received correctly with no translation. Phase 4-38 check passed.
    <02:07:03>: UDP RTP Port 9038. Response received correctly with no translation. Phase 4-39 check passed.
    <02:07:07>: UDP RTP Port 9039. Response received correctly with no translation. Phase 4-40 check passed.
    <02:07:12>: UDP RTP Port 9040. Response received correctly with no translation. Phase 4-41 check passed.
    <02:07:16>: UDP RTP Port 9041. Response received correctly with no translation. Phase 4-42 check passed.
    <02:07:21>: UDP RTP Port 9042. Response received correctly with no translation. Phase 4-43 check passed.
    <02:07:25>: UDP RTP Port 9043. Response received correctly with no translation. Phase 4-44 check passed.
    <02:07:30>: UDP RTP Port 9044. Response received correctly with no translation. Phase 4-45 check passed.
    <02:07:34>: UDP RTP Port 9045. Response received correctly with no translation. Phase 4-46 check passed.
    <02:07:39>: UDP RTP Port 9046. Response received correctly with no translation. Phase 4-47 check passed.
    <02:07:43>: UDP RTP Port 9047. Response received correctly with no translation. Phase 4-48 check passed.
    <02:07:48>: UDP RTP Port 9048. Response received correctly with no translation. Phase 4-49 check passed.
    <02:07:52>: UDP RTP Port 9049. Response received correctly with no translation. Phase 4-50 check passed.
     
  2. bluetel2

    bluetel2 Member

    Joined:
    Oct 16, 2008
    Messages:
    377
    Likes Received:
    5
    hello,

    what's your version of 3cx system ? the last ? and client too ?

    can you send the log file when 3cx tunnel try to connect ?

    the log of router too please.

    thanks
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,360
    Likes Received:
    226
    If you are using the (new) VoIP phone (softphone) there is a debug "button" that lets you see all the connect attempts from the remote phone. Then can pinpoint if, perhaps your password isn't being accepted or it is a port issue.
     
  4. Natural

    Joined:
    May 10, 2009
    Messages:
    11
    Likes Received:
    0
    Thanks for the quick response. We cannot connect to host when trying to use Telnet from the command prompt either. It says that it cannot connect to host at 5090. What is strange is that we have all ports open that are suggested on your website. We even shut off the windows firewall as well. Below are the logs requested.

    ******************* Soft Phone Debug *************************

    Attempting to connect 24.148.249.199
    Using network interface 127.0.0.1
    Tunnel got as listening port 52949
    Tunnel got as local SIP port 52950
    Phone got as local port 52951
    RTP engine OK
    SIP engine OK
    Sound mic device OK
    Sound ring device OK
    Sound play device OK
    Tunnel required cfg file:C:\Users\R R Sales\AppData\Local\3CX VoIP Phone\3CxVoipPhone.ini
    Tunnel logfile output:C:\Users\R R Sales\AppData\Local\3CX VoIP Phone\Logs
    Tunnel logging: off
    Tunnel connection created OK
    Attempting to start the tunnel
    Tunnel started
    Tunnel is attempting to connect remote end
    Tunnel connection attempt failed
    Tunnel is attempting to connect remote end

    ***************** Router Log ***********************************

    [Admin login] from source 192.168.1.3, Thursday, Jun 11,2009 09:30:14
    [UPnP set event: Public_UPNP_C5] from source 192.168.1.3, Thursday, Jun 11,2009 09:20:09
    [DHCP IP: (192.168.1.3)] to MAC address 00:1F:E2:98:22:96, Thursday, Jun 11,2009 09:20:00
    [UPnP set event: Public_UPNP_C5] from source 192.168.1.3, Thursday, Jun 11,2009 05:01:09
    [DHCP IP: (192.168.1.3)] to MAC address 00:1F:E2:98:22:96, Thursday, Jun 11,2009 05:01:03
    [DHCP IP: (192.168.1.4)] to MAC address 00:0B:82:12:07:29, Thursday, Jun 11,2009 01:48:44
    [UPnP set event: Public_UPNP_C5] from source 192.168.1.3, Wednesday, Jun 10,2009 23:36:09
    [DHCP IP: (192.168.1.3)] to MAC address 00:1F:E2:98:22:96, Wednesday, Jun 10,2009 23:36:02
    [Internet connected] IP address: 192.168.15.2, Wednesday, Jun 10,2009 23:35:12
    [Internet disconnected] Wednesday, Jun 10,2009 23:34:02
    [Admin login] from source 192.168.1.3, Wednesday, Jun 10,2009 22:27:18
    [Admin login] from source 192.168.1.3, Wednesday, Jun 10,2009 21:45:57
    [UPnP set event: Public_UPNP_C5] from source 192.168.1.3, Wednesday, Jun 10,2009 14:06:02
    [DHCP IP: (192.168.1.3)] to MAC address 00:1F:E2:98:22:96, Wednesday, Jun 10,2009 14:05:17
    [DHCP IP: (192.168.1.4)] to MAC address 00:0B:82:12:07:29, Wednesday, Jun 10,2009 13:47:39
    [DHCP IP: (192.168.1.4)] to MAC address 00:0B:82:12:07:29, Wednesday, Jun 10,2009 13:43:19
    [DHCP IP: (192.168.1.4)] to MAC address 00:0B:82:12:07:29, Wednesday, Jun 10,2009 12:25:26
    [DHCP IP: (192.168.1.4)] to MAC address 00:0B:82:12:07:29, Wednesday, Jun 10,2009 12:12:43
    [DHCP IP: (192.168.1.4)] to MAC address 00:0B:82:12:07:29, Wednesday, Jun 10,2009 12:11:19
    [DHCP IP: (192.168.1.4)] to MAC address 00:0B:82:12:07:29, Wednesday, Jun 10,2009 12:06:59
    [DHCP IP: (192.168.1.4)] to MAC address 00:0B:82:12:07:29, Wednesday, Jun 10,2009 12:06:16
    [UPnP set event: Public_UPNP_C5] from source 192.168.1.3, Wednesday, Jun 10,2009 12:00:50
    [DHCP IP: (192.168.1.3)] to MAC address 00:1F:E2:98:22:96, Wednesday, Jun 10,2009 11:58:56
    [DHCP IP: (192.168.1.4)] to MAC address 00:0B:82:12:07:29, Wednesday, Jun 10,2009 08:07:04
    [UPnP set event: Public_UPNP_C5] from source 192.168.1.3, Wednesday, Jun 10,2009 07:01:08
    [DHCP IP: (192.168.1.3)] to MAC address 00:1F:E2:98:22:96, Wednesday, Jun 10,2009 07:01:02
    [DHCP IP: (192.168.1.5)] to MAC address 00:1D:25:D0:AB:21, Tuesday, Jun 09,2009 20:40:35
    [DHCP IP: (192.168.1.5)] to MAC address 00:1D:25:D0:AB:21, Tuesday, Jun 09,2009 20:37:45
    [Admin login] from source 192.168.1.3, Tuesday, Jun 09,2009 20:36:06
    [DHCP IP: (192.168.1.5)] to MAC address 00:1D:25:D0:AB:21, Tuesday, Jun 09,2009 20:32:04
    [DHCP IP: (192.168.1.4)] to MAC address 00:0B:82:12:07:29, Tuesday, Jun 09,2009 20:02:53
    [DHCP IP: (192.168.1.4)] to MAC address 00:0B:82:12:07:29, Tuesday, Jun 09,2009 19:53:23
    [DHCP IP: (192.168.1.4)] to MAC address 00:0B:82:12:07:29, Tuesday, Jun 09,2009 19:51:51
    [DHCP IP: (192.168.1.4)] to MAC address 00:0B:82:12:07:29, Tuesday, Jun 09,2009 19:49:12
    [DHCP IP: (192.168.1.4)] to MAC address 00:0B:82:12:07:29, Tuesday, Jun 09,2009 19:42:36
    [DHCP IP: (192.168.1.4)] to MAC address 00:0B:82:12:07:29, Tuesday, Jun 09,2009 19:37:17
    [DHCP IP: (192.168.1.4)] to MAC address 00:0B:82:12:07:29, Tuesday, Jun 09,2009 19:27:18
    [DHCP IP: (192.168.1.4)] to MAC address 00:0B:82:12:07:29, Tuesday, Jun 09,2009 19:24:56
    [DHCP IP: (192.168.1.4)] to MAC address 00:0B:82:12:07:29, Tuesday, Jun 09,2009 19:23:28
    [DHCP IP: (192.168.1.4)] to MAC address 00:0B:82:12:07:29, Tuesday, Jun 09,2009 19:19:10
    [DHCP IP: (192.168.1.4)] to MAC address 00:0B:82:12:07:29, Tuesday, Jun 09,2009 19:12:56
    [DHCP IP: (192.168.1.4)] to MAC address 00:0B:82:12:07:29, Tuesday, Jun 09,2009 19:11:22
    [DHCP IP: (192.168.1.4)] to MAC address 00:0B:82:12:07:29, Tuesday, Jun 09,2009 19:01:33
    [DHCP IP: (192.168.1.4)] to MAC address 00:0B:82:12:07:29, Tuesday, Jun 09,2009 18:54:46
    [DHCP IP: (192.168.1.4)] to MAC address 00:0B:82:12:07:29, Tuesday, Jun 09,2009 18:51:19
    [DHCP IP: (192.168.1.4)] to MAC address 00:0B:82:12:07:29, Tuesday, Jun 09,2009 18:48:01
    [DHCP IP: (192.168.1.4)] to MAC address 00:0B:82:12:07:29, Tuesday, Jun 09,2009 18:25:01
    [DHCP IP: (192.168.1.4)] to MAC address 00:0B:82:12:07:29, Tuesday, Jun 09,2009 18:19:55
    [DHCP IP: (192.168.1.4)] to MAC address 00:0B:82:12:07:29, Tuesday, Jun 09,2009 18:11:37
    [DHCP IP: (192.168.1.4)] to MAC address 00:0B:82:12:07:29, Tuesday, Jun 09,2009 17:09:09
    [DHCP IP: (192.168.1.4)] to MAC address 00:0B:82:12:07:29, Tuesday, Jun 09,2009 17:07:42
    [UPnP set event: Public_UPNP_C5] from source 192.168.1.3, Tuesday, Jun 09,2009 16:59:17
    [DHCP IP: (192.168.1.3)] to MAC address 00:1F:E2:98:22:96, Tuesday, Jun 09,2009 16:59:07
    [UPnP set event: Public_UPNP_C5] from source 192.168.1.2, Tuesday, Jun 09,2009 16:52:27
    [DHCP IP: (192.168.1.2)] to MAC address 00:21:9B:CF:89:EE, Tuesday, Jun 09,2009 16:52:22
    [Time synchronized with NTP server] Tuesday, Jun 09,2009 16:42:34
    [Internet connected] IP address: 192.168.15.2, Tuesday, Jun 09,2009 16:42:34
    [Internet disconnected] Tuesday, Jun 09,2009 16:42:32
    [Initialized, firmware version: V1.1.11_6.0.36NA] Tuesday, Jun 09,2009 16:42:31
     
  5. Natural

    Joined:
    May 10, 2009
    Messages:
    11
    Likes Received:
    0
    Ok I think I have found the problem. Please help me with this. I have two different ip address 1 for local and 1 for wireless. I am running the machine on wireless so I can use the ethernet to connect my Grandstream handy Tone 286. So how would I set this up to use the tunnel? With local ip 192.168.1.2 or the wirless 192.168.1.3 ?

    Thanks for your help.
     
  6. garethb_83

    Joined:
    Oct 11, 2007
    Messages:
    25
    Likes Received:
    0
    Make sure you only have a gateway address on the adapter you want to conntact to your 3cx on. Having a gateway on both adapters may cause conflict.

    go to command prompt and run "route print" and post back result. Unless of course it works by making only one adapter to have gateway address...The interface which connects to the internet must have gateway specified. If the other interdace just talks locally, no GW is required. (Unless you have a requirement)
     
  7. Natural

    Joined:
    May 10, 2009
    Messages:
    11
    Likes Received:
    0
    Microsoft Windows [Version 6.0.6001]
    Copyright (c) 2006 Microsoft Corporation. All rights reserved.

    C:\Users\R R Sales>route print
    ===========================================================================
    Interface List
    16 ...00 22 69 c4 cf ea ...... Bluetooth Device (Personal Area Network)
    11 ...00 21 9b cf 89 ee ...... Marvell Yukon 88E8040 PCI-E Fast Ethernet Contro
    ller
    10 ...00 1f e2 98 22 96 ...... Dell Wireless 1395 WLAN Mini-Card
    1 ........................... Software Loopback Interface 1
    22 ...00 00 00 00 00 00 00 e0 isatap.{8F1D077F-AFE2-4991-8000-2993538CD505}
    12 ...02 00 54 55 4e 01 ...... Teredo Tunneling Pseudo-Interface
    23 ...00 00 00 00 00 00 00 e0 isatap.{D91F33C7-F03F-4E74-A6BE-691BC3E91690}
    25 ...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #4
    24 ...00 00 00 00 00 00 00 e0 6TO4 Adapter
    ===========================================================================

    IPv4 Route Table
    ===========================================================================
    Active Routes:
    Network Destination Netmask Gateway Interface Metric
    0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.2 20
    0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.3 25
    127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
    127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
    127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
    169.254.0.0 255.255.0.0 On-link 192.168.1.2 296
    169.254.255.255 255.255.255.255 On-link 192.168.1.2 276
    192.168.1.0 255.255.255.0 On-link 192.168.1.2 276
    192.168.1.0 255.255.255.0 On-link 192.168.1.3 281
    192.168.1.2 255.255.255.255 On-link 192.168.1.2 276
    192.168.1.3 255.255.255.255 On-link 192.168.1.3 281
    192.168.1.255 255.255.255.255 On-link 192.168.1.2 276
    192.168.1.255 255.255.255.255 On-link 192.168.1.3 281
    224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
    224.0.0.0 240.0.0.0 On-link 192.168.1.2 276
    224.0.0.0 240.0.0.0 On-link 192.168.1.3 281
    255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
    255.255.255.255 255.255.255.255 On-link 192.168.1.2 276
    255.255.255.255 255.255.255.255 On-link 192.168.1.3 281
    ===========================================================================
    Persistent Routes:
    None

    IPv6 Route Table
    ===========================================================================
    Active Routes:
    If Metric Network Destination Gateway
    11 276 ::/0 fe80::8f1:ea8c:220f:5584
    12 18 ::/0 On-link
    1 306 ::1/128 On-link
    12 18 2001::/32 On-link
    12 266 2001:0:4137:9e50:1c6f:696:3f57:fefd/128
    On-link
    11 276 fe80::/64 On-link
    10 281 fe80::/64 On-link
    12 266 fe80::/64 On-link
    10 281 fe80::8f1:ea8c:220f:5584/128
    On-link
    12 266 fe80::1c6f:696:3f57:fefd/128
    On-link
    11 276 fe80::ac5b:b931:4ef7:6991/128
    On-link
    1 306 ff00::/8 On-link
    12 266 ff00::/8 On-link
    11 276 ff00::/8 On-link
    10 281 ff00::/8 On-link
    ===========================================================================
    Persistent Routes:
    None

    C:\Users\R R Sales>
     
  8. Discovery Technology

    Joined:
    Apr 19, 2008
    Messages:
    278
    Likes Received:
    0
    Looks like you are using two default gateways...

    ie:
    0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.2 20
    0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.3 25

    If 192.168.1.1 is your firewall, and 192.168.1.3 is connected via wireless to your firewall then this is what you would use and you should remove the gateway setting from your wireless interface.

    Are you actually getting external VoIP calls going with your current setup?

    Regarding the firewall, generally you would only need to port-forward TCP 5090 then aim your remote site at the outside IP (do the same on the other side) and it should work.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  9. Natural

    Joined:
    May 10, 2009
    Messages:
    11
    Likes Received:
    0
    I think this is our problem. The stun server.
    Take a look at the server log. Mind you this is after we have uninstalled the server and did a fresh install.

    00:16:16.640 [CM506004]: STUN request to STUN server 75.101.138.128:3478 has timed out; used Transport: 192.168.1.2:5060

    00:16:13.640 [CM506004]: STUN request to STUN server 75.101.138.128:3478 has timed out; used Transport: 192.168.1.2:5060

    00:16:13.240 IP(s) added:[192.168.1.2]

    00:16:10.540 [CM506004]: STUN request to STUN server 75.101.138.128:3478 has timed out; used Transport: 192.168.1.2:5060

    00:16:07.435 [CM506004]: STUN request to STUN server 75.101.138.128:3478 has timed out; used Transport: 192.168.1.2:5060

    00:16:05.025 [CM112000] Media Server is connected

    00:16:04.744 [CM504008]: Fax Service: registered as sip:888@192.168.1.2:5060 with contact sip:888@192.168.1.2:5100;user=phone

    00:16:04.394 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 75.101.138.128:3478 over Transport 192.168.1.2:5060

    00:16:03.169 [CM501006]: Default Local IP address: [192.168.1.2]

    00:16:03.159 [CM501007]: *** Started Calls Controller thread ***

    00:16:03.158 [CM501002]: Version: 7.1.7060.0

    00:16:03.157 [CM501001]: Start 3CX PhoneSystem Call Manager

    00:16:02.454 Unknown system [DBProvider] tries to connect!
    00:16:02.388 [CM501010]: License Info: Load Failed
     
  10. Natural

    Joined:
    May 10, 2009
    Messages:
    11
    Likes Received:
    0
    Could someone please tell me why we are getting this error? We are using the firewall checker.

    <14:39:26>: Phase 1, checking servers connection, please wait...
    <14:39:26>: Stun Checker service is reachable. Phase 1 check passed.
    <14:39:26>: Phase 2a, Check Port Forwarding to UDP SIP port, please wait...
    <14:39:46>: UDP SIP Port is set to 5060. NO RESPONSE received. Phase 2a check FAILED.


    Application exit code is -2
     
Thread Status:
Not open for further replies.