Home › Forums › PBXSync (PBX Synchronizer) › Configuration & Optimization › Mixing internal and external hosts in PBXSync federation

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • Avatar photoCustomer Inquiry
    Member
    May 31, 2019 at 9:01 pm
    Post count: 197
    #6583

    We have created a federation of 15 PBXSync hosts. All of the PBXSync hosts on internal networks work fine, but we have one external host that can’t connected to the internal hosts.

    Since the internal hosts have internal (private) IP addresses, how will the external PBXSync host ever connect to the internal host?

    Avatar photoTelium Support Group
    Member
    May 31, 2019 at 9:06 pm
    Post count: 258
    #6830

    PBXSync is designed to handle a mix of internal and external hosts. When you setup your pbxsync.conf file, you will notice that the rsync and MySQL IP address entries allow for up to 3 IP addresses. These three addresses represent:

    1. Public IP – this is the IP address that PBXSync will publish to other PBXSync hosts not on your local subnet.
    2. Private IP – this is the IP address that PBXSync will publish to other PBXSync hosts on your local subnet.
    3. Local IP – this is the IP address that PBXSync uses when connecting to itself.

    So for the Public IP use the IP address of your firewall, and for your Private IP use the internal (non-routable) IP address of an internal host. The local IP should probably be set to ‘localhostipv4’. Also be sure to set the localsubnets setting to match your internal network(s).

    Next, on your firewall setup porting mapping from the public IP address to the internal private IP addresses & port. After that the external host will be able to reach the internal host as well.

  • Author
    Posts
Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.