How to deploy 3CX PBX for both LAN & WAN

Discussion in 'Windows' started by zhangjx99, Jul 4, 2010.

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

    Joined:
    May 26, 2010
    Messages:
    51
    Likes Received:
    0
    Hi helper, I am going to deploy 3CX PBX system for VOIP calling needs.
    for big remote site(and local HQ site), we will use LAN connection (MPLS link directly),
    while for small remote office (1 or 2 extension only) and mobile users, we would like to use WAN connection.

    Option 1:
    As there are 2 NIC cards on the server available, I will link LAN/WAN using NIC cards, but not sure extension registerred to different NIC can talk each other?
    Pros: simplest deploayment, less setting
    Cons: the WAN port is open to public, may get security issues

    Option 2:
    use LAN NIC only, portforward 5060/5090 and all other ports (specified on the 3CX manual) to public IP address.
    On my test setup, it can't work, extensions can make the call but no audio once connected. (I setup TCP/UDP port forward in both way already).
    ===================================
    any suggestion? which option is better?

    Thank you.
    JX
     
  2. carolinainnovative

    Joined:
    May 4, 2009
    Messages:
    369
    Likes Received:
    6
    Option 2 is best in my opinion...

    Does the firewall checker run cleanly in option 2?
     
  3. zhangjx99

    Joined:
    May 26, 2010
    Messages:
    51
    Likes Received:
    0
    We are using Cisco PIX to publish below ports to a public fixed IP:

    • Port 5060 (TCP and UDP) – Used for SIP protocol transmission – must be a static mapping, no port translation
    • Port 5090 (TCP and UDP) – Used for 3CX tunnel (if tunnel is enabled)
    • Port 9000-9049 (UDP) – Used for RTP protocol for incoming and outgoing calls
    • Port 10000 (UDP) – Used for inbound faxes coming from a VoIP Provider

    No issue to audio call if 2 parties both register to WAN IP or both register to LAN IP, but no voice transmit between WAN registered Extern extensions and LAN registered internal ext.

    I have not enabled Windows Firewall service on the 3CX server (WIN2003 Std Edition).

    Thank you. JX
     
  4. carolinainnovative

    Joined:
    May 4, 2009
    Messages:
    369
    Likes Received:
    6
    That didn't answer the question.

    Run the 3cx firewall checker. Does it run cleanly?
     
  5. DeWild1

    Joined:
    Oct 31, 2008
    Messages:
    86
    Likes Received:
    0
    use this, http://social.technet.microsoft.com/Forums/en-US/winserverNIS/thread/c2abf8e7-06b2-4699-bcd5-ba8039dfb11d/#fe7b101f-c503-4b1c-a543-e19e096dc364 it is faster, better quality and I have used it from day one in 2003, never been hacked, many servers.
    I have a script that will change all the posts too.
    dl http://www.autohotkey.com
    save this as blabla.ahk and run from server.
    Open up the WAN properties, go to the service -port mapping part of it, then run it.
    change wan adapter name to WAN change ip below to your internal ip or if you are using 3cx on the server, you can use 127.0.0.1
    making a 2003 server into a router is better than any store bought router and may be better and faster than any cisco because the hardware is much faster. 8)

    Code:
    winactivate, WAN Properties 
    winwaitactive, WAN Properties 
    sleep, 3000
    setbatchlines, -1
    ip = 192.168.1.1
    
    controlclick, Button1, WAN Properties 
    sleep, 1000 
    controlclick, Edit1, Add Service 
    sleep, 100 
    send, voip_sip_tcp
    sleep, 100 
    controlclick, Edit6, Add Service 
    sleep, 100 
    send, 5060
    sleep, 100
    controlclick, Button5, Add Service 
    sleep, 100
    controlclick, Edit7, Add Service 
    sleep, 100 
    send, %ip%
    sleep, 100 
    controlclick, Edit11, Add Service 
    sleep, 100 
    send, 5060
    sleep, 100 
    controlclick, Button7, Add Service 
    sleep, 1000 
    
    winwaitactive, WAN Properties 
    
    controlclick, Button1, WAN Properties 
    sleep, 1000 
    controlclick, Edit1, Add Service 
    sleep, 100 
    send, voip_sip_udp
    sleep, 100 
    controlclick, Edit6, Add Service 
    sleep, 100 
    send, 5060
    sleep, 100
    controlclick, Button6, Add Service 
    sleep, 100
    controlclick, Edit7, Add Service 
    sleep, 100 
    send, %ip%
    sleep, 100 
    controlclick, Edit11, Add Service 
    sleep, 100 
    send, 5060
    sleep, 100 
    controlclick, Button7, Add Service 
    sleep, 1000 
    
    winwaitactive, WAN Properties 
    
    controlclick, Button1, WAN Properties 
    sleep, 1000 
    controlclick, Edit1, Add Service 
    sleep, 100 
    send, voip_tunnel
    sleep, 100 
    controlclick, Edit6, Add Service 
    sleep, 100 
    send, 5090
    sleep, 100
    controlclick, Button5, Add Service 
    sleep, 100
    controlclick, Edit7, Add Service 
    sleep, 100 
    send, %ip%
    sleep, 100 
    controlclick, Edit11, Add Service 
    sleep, 100 
    send, 5090
    sleep, 100 
    controlclick, Button7, Add Service 
    sleep, 1000 
    
    Port 9000-9015 (UDP) - Used for RTP protocol for incoming and outgoing calls
    
    loop, 15
    { 
    winwaitactive, WAN Properties 
    
    controlclick, Button1, WAN Properties 
    sleep, 1000 
    controlclick, Edit1, Add Service 
    sleep, 100 
    send, voip_RTP%A_index% 
    sleep, 100 
    controlclick, Edit6, Add Service 
    sleep, 100 
    send, 900%A_index% 
    sleep, 100
    controlclick, Button6, Add Service 
    sleep, 100
    controlclick, Edit7, Add Service 
    sleep, 100 
    send, %ip%
    sleep, 100 
    controlclick, Edit11, Add Service 
    sleep, 100 
    send, 900%A_index% 
    sleep, 100 
    controlclick, Button7, Add Service 
    sleep, 1000 
    }
    
    
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. zhangjx99

    Joined:
    May 26, 2010
    Messages:
    51
    Likes Received:
    0
    I run the 3cx firewall checker, every thing ok. see attachment for detail. but still not able to call each other in between WAN and LAN extension.
     

    Attached Files:

Thread Status:
Not open for further replies.