Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Network setup, two nics, 3CX tunnel problem

Discussion in '3CX Phone System - General' started by Hermos, Jun 7, 2017.

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

    Joined:
    Jun 7, 2017
    Messages:
    3
    Likes Received:
    0
    Hi,

    we have problems to setup our 3CX environment.

    Our current setup:
    • LAN: 172.21.3.0
    • WAN: 192.168.1.0
    • 3CX has two nics, one for LAN (172.21.3.1) and one for WAN (192.168.1.1)
    • FQDN is defined
    • Local DNS resolves FQDN to 172.21.3.1
    • Router (192.168.1.254) is forwarding all relevant ports to 192.168.1.1; 3CX firewall check is OK.
    We'd like to use 3CX clients and 3CX tunnel for internal and external usage.

    But: We can't call internal extensions when connected via tunnel - if we connect via SIP from external it works. Tunnel to tunnel doesn't work, too.

    Any hints?

    Thanks in advance,
    Michael
     
  2. Panayiotis_3CX

    Panayiotis_3CX Support Team
    Staff Member 3CX Support

    Joined:
    Apr 26, 2017
    Messages:
    165
    Likes Received:
    7
    Hello @Hermos,

    Can you please explain from which network you're trying to connect through the tunnel?
    Also, from which network is the server routed?
     
  3. Hermos

    Joined:
    Jun 7, 2017
    Messages:
    3
    Likes Received:
    0
    Hello panayiotis_3CX,

    thanks for your reply.

    To make these things more clear we made a reinstall with only one NIC (192.168.1.1) which is behind our WAN router.
    We added two extensions 301 and 302 and connect from outside via 3CX tunnel. Both clients have established connections using port 5001 and 5090.

    302 can call 301 BUT 301 cannot call 302:

    08.06.2017 10:54:21 - Leg L:27.1[Extn:301] is terminated: Cause: BYE from PBX
    08.06.2017 10:54:21 - [CM503020]: Call(C:27): Normal call termination. Call originator: Extn:301. Reason: Not found
    08.06.2017 10:54:21 - Leg L:27.2[Extn:302] is terminated: Cause: 404 Not Found/INVITE from 127.0.0.1:5080
    08.06.2017 10:54:21 - [Flow] No office hours set, office hours assumed
    08.06.2017 10:54:21 - L:27.1[Extn:301] failed to reach Extn:302, reason Not Found
    08.06.2017 10:54:21 - Call to T:Extn:302@[Dev:sip:302@172.26.9.110:50195;transport=TCP;rinstance=1-5f1a6db50624403687a76b772cbaff28;ob] from L:27.1[Extn:301] failed, cause: Cause: 404 Not Found/INVITE from 127.0.0.1:5080
    08.06.2017 10:54:21 - [CM503003]: Call(C:27): Call to <sip:302@***FQDN***:5060> has failed; Cause: 404 Not Found/INVITE from 127.0.0.1:5080
    08.06.2017 10:54:20 - [CM503025]: Call(C:27): Calling T:Extn:302@[Dev:sip:302@172.26.9.110:50195;transport=TCP;rinstance=1-5f1a6db50624403687a76b772cbaff28;ob] for L:27.1[Extn:301]
    08.06.2017 10:54:20 - [CM503027]: Call(C:27): From: Extn:301 ("User 301" <sip:301@***FQDN***:5060>) to T:Extn:302@[Dev:sip:302@172.26.9.110:50195;transport=TCP;rinstance=1-5f1a6db50624403687a76b772cbaff28;ob]
    08.06.2017 10:54:20 - [CM503004]: Call(C:27): Route 1: from L:27.1[Extn:301] to T:Extn:302@[Dev:sip:302@172.26.9.110:50195;transport=TCP;rinstance=1-5f1a6db50624403687a76b772cbaff28;ob]
    08.06.2017 10:54:20 - [Flow] No office hours set, office hours assumed
    08.06.2017 10:54:20 - [Flow] Call(C:27): has built target endpoint: Extn:302 for call from L:27.1[Extn:301]
    08.06.2017 10:54:20 - [Flow] Target endpoint for 302 is Extn:302
    08.06.2017 10:54:20 - [CM503010]: Call(C:27): Making route(s) from Extn:301 to <sip:302@***FQDN***:5060>
    08.06.2017 10:54:20 - [CM505001]: Endpoint Extn:301: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXPhone for Windows 15.5.1694.0] PBX contact: [sip:301@127.0.0.1:5060]
     
  4. Panayiotis_3CX

    Panayiotis_3CX Support Team
    Staff Member 3CX Support

    Joined:
    Apr 26, 2017
    Messages:
    165
    Likes Received:
    7
    Hello @Hermos,

    Do you have the ability to open a ticket in our Support Portal?
     
Thread Status:
Not open for further replies.