{"id":8839,"date":"2026-08-13T12:03:17","date_gmt":"2026-08-13T09:03:17","guid":{"rendered":"https:\/\/www.flannetworks.co.ke\/?p=8839"},"modified":"2026-08-13T12:03:20","modified_gmt":"2026-08-13T09:03:20","slug":"yeastar-pabx-interbranches","status":"publish","type":"post","link":"https:\/\/www.flannetworks.co.ke\/?p=8839","title":{"rendered":"How to Interconnect Branches for Yeastar PABX Through Port Forwarding"},"content":{"rendered":"\n

Businesses with multiple offices often need their branches to communicate seamlessly without paying for every inter-office call. Yeastar PABX inter-branch connectivity<\/strong> makes it possible to connect offices over the internet so users can call extensions at another branch as if they were on the same telephone system.<\/p>\n\n\n\n

One practical way to achieve this is by using port forwarding on the internet routers<\/strong> at each branch. This guide explains how to connect Yeastar P-Series PABX systems between branches using public IP addresses and SIP peer trunks.<\/p>\n\n\n\n

What Is Yeastar Inter-Branch Connectivity?<\/h2>\n\n\n\n

Yeastar inter-branch connectivity allows two or more Yeastar PABX systems installed at different physical locations to communicate with each other over an IP network.<\/p>\n\n\n\n

For example:<\/p>\n\n\n\n

    \n
  • Head Office: Yeastar PABX \u2013 Nairobi<\/li>\n\n\n\n
  • Branch 1: Yeastar PABX \u2013 Mombasa<\/li>\n\n\n\n
  • Branch 2: Yeastar PABX \u2013 Kisumu<\/li>\n<\/ul>\n\n\n\n

    Users at Head Office can dial an extension at Mombasa or Kisumu without making a conventional external telephone call.<\/p>\n\n\n\n

    A typical setup looks like this:<\/p>\n\n\n\n

    Head Office Yeastar PABX \u2192 Internet \u2192 Branch Yeastar PABX<\/strong><\/p>\n\n\n\n

    Port forwarding allows SIP traffic arriving at a branch’s public IP address to be forwarded to the Yeastar PABX on its private LAN address.<\/p>\n\n\n\n

    Benefits of Connecting Yeastar PABX Branches<\/h2>\n\n\n\n

    Interconnecting your Yeastar systems can provide several benefits:<\/p>\n\n\n\n

      \n
    • Free internal calls between branches<\/li>\n\n\n\n
    • Extension-to-extension dialing between offices<\/li>\n\n\n\n
    • Centralized call management<\/li>\n\n\n\n
    • Reduced communication costs<\/li>\n\n\n\n
    • Easier communication between departments<\/li>\n\n\n\n
    • Ability to transfer calls between branches<\/li>\n\n\n\n
    • Scalability for additional offices<\/li>\n\n\n\n
    • Integration of remote offices into one business telephone environment<\/li>\n<\/ul>\n\n\n\n

      What You Need Before Starting<\/h2>\n\n\n\n

      For a reliable setup, each branch should have:<\/p>\n\n\n\n

        \n
      1. A Yeastar PABX.<\/li>\n\n\n\n
      2. A stable internet connection.<\/li>\n\n\n\n
      3. A router\/firewall that supports port forwarding.<\/li>\n\n\n\n
      4. A static public IP address, preferably.<\/li>\n\n\n\n
      5. A fixed private IP address for the Yeastar PABX.<\/li>\n\n\n\n
      6. Administrator access to the Yeastar PABX.<\/li>\n\n\n\n
      7. Administrator access to the branch router.<\/li>\n<\/ol>\n\n\n\n

        Static Public IP vs Dynamic IP<\/h3>\n\n\n\n

        A static public IP<\/strong> is strongly recommended because the PABX needs to remain reachable from the other branch.<\/p>\n\n\n\n

        If your ISP provides a dynamic public IP, you can consider using a DDNS service<\/strong>, provided your Yeastar and network configuration support it.<\/p>\n\n\n\n

        Step 1: Give Each Yeastar PABX a Static LAN IP<\/h2>\n\n\n\n

        First, make sure each Yeastar PABX has a fixed IP address on its local network.<\/p>\n\n\n\n

        For example:<\/p>\n\n\n\n

        Location<\/th>Yeastar IP<\/th>Public IP<\/th><\/tr>
        Head Office<\/td>192.168.1.10<\/td>41.x.x.x<\/td><\/tr>
        Branch 1<\/td>192.168.2.10<\/td>102.x.x.x<\/td><\/tr>
        Branch 2<\/td>192.168.3.10<\/td>105.x.x.x<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

        The actual IP addresses will depend on your network.<\/p>\n\n\n\n

        Avoid allowing the PABX’s LAN IP to change because this can cause port-forwarding rules to stop working.<\/p>\n\n\n\n

        Step 2: Configure Port Forwarding<\/h2>\n\n\n\n

        Log into the router at the branch where the Yeastar PABX is installed.<\/p>\n\n\n\n

        Look for a menu such as:<\/p>\n\n\n\n

        NAT \u2192 Port Forwarding<\/strong><\/p>\n\n\n\n

        or:<\/p>\n\n\n\n

        Virtual Server \u2192 Port Forwarding<\/strong><\/p>\n\n\n\n

        Create rules forwarding the required Yeastar services from the router’s public interface to the internal Yeastar PABX IP address.<\/p>\n\n\n\n

        For example:<\/p>\n\n\n\n

        Port<\/td>Protocol<\/td>Purpose<\/td><\/tr>
        5060<\/td>UDP\/TCP<\/td>SIP signaling, depending on configuration<\/td><\/tr>
        RTP range<\/td>UDP<\/td>Voice\/audio traffic<\/td><\/tr>
        HTTPS management port<\/td>TCP<\/td>Web access, if remote management is required<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

        Important:<\/strong> Do not blindly expose every Yeastar service to the internet. The exact SIP and RTP ports depend on your Yeastar model and configuration. Check the Yeastar documentation and the ports configured under the PABX’s SIP\/RTP settings.<\/p>\n\n\n\n

        For security, it is preferable to restrict source IP addresses where possible.<\/p>\n\n\n\n

        Step 3: Configure NAT and SIP Settings<\/h2>\n\n\n\n

        Port forwarding alone is not always sufficient for VoIP.<\/p>\n\n\n\n

        The Yeastar PABX must correctly advertise its public address when communicating with the remote PABX.<\/p>\n\n\n\n

        Check the Yeastar network\/SIP settings for options relating to:<\/p>\n\n\n\n

          \n
        • NAT<\/li>\n\n\n\n
        • External IP address<\/li>\n\n\n\n
        • Local network identification<\/li>\n\n\n\n
        • SIP transport<\/li>\n\n\n\n
        • RTP port range<\/li>\n<\/ul>\n\n\n\n

          Make sure the external\/public IP address is correctly configured where required.<\/p>\n\n\n\n

          Incorrect NAT settings can result in situations where:<\/p>\n\n\n\n

            \n
          • Calls connect but there is no audio.<\/li>\n\n\n\n
          • Audio works in one direction only.<\/li>\n\n\n\n
          • Calls disconnect after a few seconds.<\/li>\n\n\n\n
          • Extensions cannot register.<\/li>\n<\/ul>\n\n\n\n

            Step 4: Create a Peer Trunk Between the PABXs<\/h2>\n\n\n\n

            Once the network and port forwarding are working, create a trunk between the two Yeastar systems.<\/p>\n\n\n\n

            For example:<\/p>\n\n\n\n

            Head Office \u2192 Branch 1<\/strong><\/p>\n\n\n\n

            On the Head Office Yeastar PABX, create a peer\/SIP trunk pointing to the Branch 1 public IP address.<\/p>\n\n\n\n

            The configuration will generally include:<\/p>\n\n\n\n

              \n
            • Trunk name<\/li>\n\n\n\n
            • Remote host\/public IP<\/li>\n\n\n\n
            • SIP port<\/li>\n\n\n\n
            • Transport protocol<\/li>\n\n\n\n
            • Authentication, where applicable<\/li>\n\n\n\n
            • Outbound routing<\/li>\n<\/ul>\n\n\n\n

              The exact menu names vary depending on the Yeastar P-Series firmware version.<\/p>\n\n\n\n

              Repeat the process in the opposite direction if your design requires bidirectional peer connectivity.<\/p>\n\n\n\n

              Step 5: Create Outbound Routes<\/h2>\n\n\n\n

              After creating the trunk, tell the Head Office PABX which numbers should be sent to the branch.<\/p>\n\n\n\n

              For example, you could allocate:<\/p>\n\n\n\n

                \n
              • Head Office extensions: 1XX<\/strong><\/li>\n\n\n\n
              • Branch 1 extensions: 2XX<\/strong><\/li>\n\n\n\n
              • Branch 2 extensions: 3XX<\/strong><\/li>\n<\/ul>\n\n\n\n

                A user at Head Office could then dial:<\/p>\n\n\n\n

                201 \u2192 Branch 1<\/strong><\/p>\n\n\n\n

                while a Branch 1 user could dial:<\/p>\n\n\n\n

                101 \u2192 Head Office<\/strong><\/p>\n\n\n\n

                The outbound routes determine which calls are sent through the inter-branch trunk.<\/p>\n\n\n\n

                Step 6: Configure Inbound Routes<\/h2>\n\n\n\n

                The receiving PABX also needs to know what to do with calls arriving from the other branch.<\/p>\n\n\n\n

                Create appropriate inbound routes so calls coming through the inter-branch trunk are delivered to the correct extension, department, ring group or IVR.<\/p>\n\n\n\n

                For example:<\/p>\n\n\n\n

                Head Office \u2192 Branch 1 \u2192 Extension 201<\/strong><\/p>\n\n\n\n

                The Branch 1 PABX receives the SIP call and routes it to extension 201.<\/p>\n\n\n\n

                Step 7: Test Inter-Branch Calling<\/h2>\n\n\n\n

                Once both systems are configured, test the connection.<\/p>\n\n\n\n

                Try:<\/p>\n\n\n\n

                  \n
                1. Head Office extension \u2192 Branch extension.<\/li>\n\n\n\n
                2. Branch extension \u2192 Head Office extension.<\/li>\n\n\n\n
                3. Two-way voice communication.<\/li>\n\n\n\n
                4. Call transfer between branches.<\/li>\n\n\n\n
                5. Hold and resume.<\/li>\n\n\n\n
                6. Caller ID.<\/li>\n\n\n\n
                7. Ring groups, if required.<\/li>\n<\/ol>\n\n\n\n

                  If the call connects but there is no audio, investigate the RTP\/NAT configuration first.<\/p>\n\n\n\n

                  Common Yeastar Inter-Branch Problems<\/h2>\n\n\n\n

                  1. Calls Do Not Connect<\/h3>\n\n\n\n

                  Check:<\/p>\n\n\n\n

                    \n
                  • Public IP addresses<\/li>\n\n\n\n
                  • Port forwarding<\/li>\n\n\n\n
                  • SIP port<\/li>\n\n\n\n
                  • Firewall rules<\/li>\n\n\n\n
                  • Trunk configuration<\/li>\n\n\n\n
                  • SIP authentication<\/li>\n\n\n\n
                  • Whether the ISP is using CGNAT<\/li>\n<\/ul>\n\n\n\n

                    2. Call Connects but There Is No Audio<\/h3>\n\n\n\n

                    This is usually related to RTP or NAT configuration<\/strong>.<\/p>\n\n\n\n

                    Check:<\/p>\n\n\n\n

                      \n
                    • RTP port range<\/li>\n\n\n\n
                    • RTP port forwarding<\/li>\n\n\n\n
                    • Yeastar external IP\/NAT settings<\/li>\n\n\n\n
                    • Firewall rules<\/li>\n\n\n\n
                    • Router SIP ALG<\/li>\n<\/ul>\n\n\n\n

                      3. Audio Works Only One Way<\/h3>\n\n\n\n

                      This is another common NAT problem.<\/p>\n\n\n\n

                      Check the RTP path in both directions and make sure the routers are not blocking UDP traffic.<\/p>\n\n\n\n

                      4. Public IP Does Not Work<\/h3>\n\n\n\n

                      Your ISP may be using Carrier-Grade NAT (CGNAT)<\/strong>.<\/p>\n\n\n\n

                      In this situation, normal port forwarding on your router may not make the PABX accessible from the internet.<\/p>\n\n\n\n

                      Ask your ISP for a public\/static IPv4 address<\/strong>.<\/p>\n\n\n\n

                      5. SIP ALG Causes Problems<\/h3>\n\n\n\n

                      Some routers have SIP ALG<\/strong> enabled. SIP ALG can modify VoIP packets and sometimes interfere with Yeastar SIP communication.<\/p>\n\n\n\n

                      If you experience strange registration, call connection or audio problems, check whether SIP ALG can be disabled on the router.<\/p>\n\n\n\n

                      Security Considerations<\/h2>\n\n\n\n

                      Exposing a PABX directly to the internet requires careful security configuration.<\/p>\n\n\n\n

                      Never use simple SIP passwords or expose unnecessary services.<\/p>\n\n\n\n

                      Recommended measures include:<\/p>\n\n\n\n

                        \n
                      • Use strong SIP passwords.<\/li>\n\n\n\n
                      • Keep Yeastar firmware updated.<\/li>\n\n\n\n
                      • Restrict allowed source IP addresses where possible.<\/li>\n\n\n\n
                      • Forward only required ports.<\/li>\n\n\n\n
                      • Avoid exposing the PABX web interface unnecessarily.<\/li>\n\n\n\n
                      • Use firewall rules.<\/li>\n\n\n\n
                      • Monitor SIP registration and call activity.<\/li>\n\n\n\n
                      • Disable unused accounts and services.<\/li>\n\n\n\n
                      • Consider VPN-based connectivity for higher security.<\/li>\n<\/ul>\n\n\n\n

                        Is Port Forwarding the Best Way to Connect Yeastar Branches?<\/h2>\n\n\n\n

                        Port forwarding can work well, especially for businesses that have static public IP addresses and properly configured firewalls.<\/p>\n\n\n\n

                        However, for a business environment, a site-to-site VPN<\/strong> can often provide a more secure architecture because the PABXs communicate through a private network rather than exposing SIP services directly to the internet.<\/p>\n\n\n\n

                        For example:<\/p>\n\n\n\n

                        Head Office LAN \u2192 VPN Tunnel \u2192 Branch LAN<\/strong><\/p>\n\n\n\n

                        With a VPN, the Yeastar systems can communicate using their private IP addresses, reducing the need to expose SIP services publicly.<\/p>\n\n\n\n

                        The best solution depends on the company’s network architecture, internet connections, security requirements and number of branches.<\/p>\n\n\n\n

                        Yeastar PABX Inter-Branch Installation in Kenya<\/h2>\n\n\n\n

                        If your company operates multiple offices in Nairobi, Westlands, Mombasa, Kisumu or other parts of Kenya<\/strong>, Yeastar PABX inter-branch connectivity can provide a cost-effective way to link your telephone systems.<\/p>\n\n\n\n

                        A professional installation can include:<\/p>\n\n\n\n

                          \n
                        • Yeastar PABX supply and installation<\/li>\n\n\n\n
                        • Inter-branch SIP trunk configuration<\/li>\n\n\n\n
                        • Router and firewall configuration<\/li>\n\n\n\n
                        • Port forwarding<\/li>\n\n\n\n
                        • Site-to-site VPN<\/li>\n\n\n\n
                        • Extension planning<\/li>\n\n\n\n
                        • Call routing<\/li>\n\n\n\n
                        • Remote troubleshooting<\/li>\n\n\n\n
                        • Yeastar P-Series configuration<\/li>\n\n\n\n
                        • Ongoing PABX maintenance and support<\/li>\n<\/ul>\n\n\n\n

                          Conclusion<\/h2>\n\n\n\n

                          Interconnecting Yeastar PABX branches through port forwarding<\/strong> allows businesses to establish communication between offices over the internet. By assigning static LAN addresses, configuring NAT and port forwarding, creating SIP peer trunks, and setting appropriate inbound and outbound routes, users can make extension-to-extension calls between branches.<\/p>\n\n\n\n

                          For improved security, businesses should also consider VPN-based Yeastar inter-branch connectivity<\/strong>, particularly when several offices are involved.<\/p>\n\n\n\n

                          If you need professional Yeastar PABX installation, inter-branch configuration, SIP trunking, networking or VoIP support in Kenya<\/strong>, working with an experienced Yeastar installer can help ensure that both the voice and network infrastructure are configured correctly.<\/p>\n\n\n\n

                          SEO Keywords<\/h3>\n\n\n\n

                          Primary keywords:<\/strong><\/p>\n\n\n\n

                            \n
                          • Yeastar PABX inter-branch connection<\/li>\n\n\n\n
                          • Yeastar PABX port forwarding<\/li>\n\n\n\n
                          • Yeastar inter-branch SIP trunk<\/li>\n\n\n\n
                          • How to connect Yeastar PABX branches<\/li>\n\n\n\n
                          • Yeastar PABX branch connectivity<\/li>\n<\/ul>\n\n\n\n

                            Secondary keywords:<\/strong><\/p>\n\n\n\n

                              \n
                            • Yeastar P-Series inter-branch<\/li>\n\n\n\n
                            • Yeastar SIP trunk configuration<\/li>\n\n\n\n
                            • Yeastar PABX installation Kenya<\/li>\n\n\n\n
                            • Yeastar PABX Nairobi<\/li>\n\n\n\n
                            • Yeastar PABX configuration Kenya<\/li>\n\n\n\n
                            • Yeastar VoIP inter-office calling<\/li>\n\n\n\n
                            • Yeastar PABX VPN<\/li>\n\n\n\n
                            • Yeastar port forwarding setup<\/li>\n\n\n\n
                            • Yeastar SIP trunk between branches<\/li>\n\n\n\n
                            • Yeastar PABX networking<\/li>\n<\/ul>\n\n\n\n

                              Suggested SEO title:<\/strong>
                              How to Interconnect Yeastar PABX Branches Through Port Forwarding<\/p>\n\n\n\n

                              Suggested meta description:<\/strong>
                              Learn how to connect Yeastar PABX branches through port forwarding, SIP peer trunks, NAT and call routing for reliable inter-office communication.<\/p>\n\n\n\n

                              Suggested URL slug:<\/strong>
                              \/yeastar-pabx-inter-branch-port-forwarding\/<\/code><\/p>\n","protected":false},"excerpt":{"rendered":"

                              Businesses with multiple offices often need their branches to communicate seamlessly without paying for every inter-office call. Yeastar PABX inter-branch connectivity makes it possible to connect offices over the internet<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[130],"tags":[],"class_list":["post-8839","post","type-post","status-publish","format-standard","hentry","category-ip-phones-and-pabx"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.flannetworks.co.ke\/index.php?rest_route=\/wp\/v2\/posts\/8839","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.flannetworks.co.ke\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.flannetworks.co.ke\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.flannetworks.co.ke\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.flannetworks.co.ke\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=8839"}],"version-history":[{"count":1,"href":"https:\/\/www.flannetworks.co.ke\/index.php?rest_route=\/wp\/v2\/posts\/8839\/revisions"}],"predecessor-version":[{"id":8840,"href":"https:\/\/www.flannetworks.co.ke\/index.php?rest_route=\/wp\/v2\/posts\/8839\/revisions\/8840"}],"wp:attachment":[{"href":"https:\/\/www.flannetworks.co.ke\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=8839"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.flannetworks.co.ke\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=8839"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.flannetworks.co.ke\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=8839"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}