Configuring Remote Extensions

Introduction

MyPBX supports remote extensions that help you to use your extension when you are home or on a business trip. With remote extensions, you can work wherever you are and still be seamlessly integrated with the head office.
In this guide, we introduce how to register a remote extension using Yealink IP Phone.
As the following figure shows, MyPBX and users in different locations are in different network with their own private IP addresses.

Step 1. Configure port forwarding on the router.

Example: The router’s public IP is 110.80.23.43.

Since MyPBX is behind the router, register to MyPBX remotely, you need to forward the SIP port on the router which is connected to MyPBX, so that all the packets received on the router WAN port (110.80.23.43:5060) will be forwarded to the MyPBX (192.168.5.150:5060). Below is the setting page in a Linksys router:

Note: we must map UDP port 5060 and UDP port 10000-12000.

Step 2. Configure NAT settings in MyPBX.

Login MyPBX web interface and go to PBX→Advanced Settings→NAT, configure the NAT settings according to the directions below.

External IPFill in the router’s public IP address

External Host: Fill in a host name if there is no static public IP address for your router and a DDNS is configured.

External refresh: Fill in the refresh time if you use a host name

Local Network AddressFill in your local network segment and subnet mask

i.e.192.168.5.0/255.255.255.0 

NAT mode: Yes

Allow RTP Reinvite: No

Step 3Setup up an extension in MyPBX (i.e. 301).

NAT: Yes

Register Remotely: Yes

You have to enable this option in the following cases:

  1. Register extension remotely.
  2. Register extension using the IP address of WAN port.
  3. The IP address of IP phone and that of MyPBX are in different network segment.

Step 4: Register the extension 301 on the IP Phone which is setup in a branch office

If connect correctly, the Register status will be “Registered”. 

Note: You have to set use the public IP address or host name of the router to register the extension.

Have more questions? Submit a request

31 Comments

  • 0
    Avatar

    Hi, if I'm forwarding ports UDP 5060 and 10000-12000 on router to MyPBX IP isn't an invitation to hackers to connect to PBX and make SIP traffic? Is it secure just to have a strong user password? How can I put PBX in security against hackers? Thanks.

  • 0
    Avatar

    Hello Walter,

    I think it is not enough to just have a strong user password. For more security settings on MyPBX, please take this article for reference:

    https://support.yeastar.com/hc/en-us/articles/217539837-MyPBX-Security-Configuration-Guide-Summary-

  • 0
    Avatar

    Thank you for your quick answer. What happen if I have to register a remote extension that usually connects to internet with a dinamic public IP? Thanks.

  • 0
    Avatar

    Hello Walter, this is a good question. If the remote extension with a dynamic public IP, I would suggest you to setup a password for outbound route and you can also setup office hours then only allow call out during working hours.

    See this article for reference:

    https://support.yeastar.com/hc/en-us/articles/217722297-How-to-Control-the-Outgoing-Calls

     

  • 0
    Avatar

    hi. i need to extension  with  dynamic for mobile phone outside calling and i register  my pbx with mobile phone 

  • 0
    Avatar

    Hello Sohrab,

    If you would like to use the extension on the mobile phone, you can consider Zopier, X-Lite, Bria, Linphone and so on.

  • 0
    Avatar

    Hi, this is my Case:

    The remote extension (let's call it 1007) is correctly registered. The PBX is an S20.  Ext.1007 can make calls perfectly well, both to extensions and outbound.

    But ext.1007 cannot receive calls.  When you call ext.1007, for instance from another extension, you hear silence and after 30 secs. the call drops.  Looking at Wireshark, when calling 1007 you receive 100 Trying but never 180 Ringing. 

    What may be missing on S20 ?  Thank you, Gustavo.

     

  • 0
    Avatar

    Hello Gustavo,

    For your issue, please check if you have configured proper NAT settings on the S20, specially the external IP address of S20. It is strange that the S20 can receive 100 trying but not 180 ringing. I would suggest you to submit a ticket and attached pcap logs(captured at the same time both on the IP phone and on the S20)

    Edited by Yeastar Support Team
  • 0
    Avatar

    Ok thank you, I will check that. Regards.

  • 0
    Avatar

    Hi. Definitely it was a router issue not S20 issue. The easiest way to go was to define the remote extension as IAX, that solved NAT connectivity.

  • 0
    Avatar

    Thanks for your feedback, Gustavo. Yes, if we choose IAX, there will be no NAT issues. IAX use one port(UDP 4569 by default) for both signalling and voice.

  • 0
    Avatar

    Hi support,

    My Router is ASUS AC1200G+, the configuration is different from your screenshot. In my router there is (local port) wherein you cannot range the port for RTP. My friend help me instead port forward it he trigger it. And It was connected, the only problem is my Phone has no mic/audio (Yes i download zoiper on my phone).

    Can you help me with this, please excuse my english. If there is something I can clarify just inform me.

    Thanks!!

  • 0
    Avatar

    Carmelo,

    If your router couldn't do port forwarding for a range of ports, I would suggest you to use IAX phone (Zoiper supports for IAX protocol) and do port forwarding for IAX (which is 4569 by default). With IAX, you don't need to do port forwarding for the RTP port range as IAX use only one port for both signalling and voice.

  • 0
    Avatar

    it can range, but there is local port that is different with your screenshot above.


    what i meant that on "local port" I cannot set range.

  • 0
    Avatar

    Hi Yeastar Support Team!

     

    How should we configure the Extension/PBX when a VPN is used instead of port forward.

     

    In my scenario, I have a VPN Server (OPEN VPN) running in the ROUTER, and connect my client to it (the client is a computer with x-lite soft phone).

     

    The regular NW works fine, but I have some issues configuring the Soft-phone.

     

    Please, can you create a nice guideline for this scenario, just like you create for regular internet access?

     

    Thanks

    Henrique

  • 0
    Avatar

    hi i am using raspbx with a local network 192.168.0.103 by tplink wifi router... but my internet line has a public ip. can i use this Raspbx with public ip to use remote extensions... from my office to house..? pls help me sir

  • 0
    Avatar

    Hi Team,

     

    I setup the remote extension step by step as per your instructions and it worked like a beauty. I can see the handset registered,

    When I call from the remote extension to a local extension, the phone rings, but when the call gets picked up there is no audio both ways.

    Can you please advise what might be the issue?

     

    Regards,

    Gus Salha

  • 0
    Avatar

    Hi Gus,

    Please check the port forwarding for the RTP on your router. Note it is a range of ports.

    Also, please make sure the NAT settings are correct and the NAT setting on extension page is enabled.

    If still no luck, I would suggest you to create a ticket for your issue.

  • 0
    Avatar

    Thanks for your quick response, I have managed to get two way speech from remote to local extension (RTP port forwarding on remote router was the issue)

    However, when I use remote extension to dial out via SIP trunk on PABX, there is no audio??

    :(

  • 0
    Avatar

    Hi Ezra here,

    This is my case. My PBX is S100 and the set up is the main office calls is okay, but when they set up a remote extension and I follow the steps in configuring it. Their inbound call cannot hear their voice but the caller can hear them. But when the main branch call the Local number their voices are okay. that is the case when I set up the Public IP in the NAT tab in SIP Settings. When I took away the NAT settings, their inbound call suddenly turns okay. Hope to hear from tech support soon.

    Buy the way the remote extension set up is successful. But when I take out the Config in NAT from SIP Settings no voice but the call is successful.

    Edited by Ezra Gerald Malinao
  • 0
    Avatar

    Hi Ezra,

    We have created a ticket for your case, our support agents will response your ticket as soon as they can.

  • 0
    Avatar

     

    Dear Yeastar team,

    I have done all the above configuration steps for the "MyPBX-Standard V3" and the IP phone Yealink 7.0.0.60, and here is my router configuration as below, the problem that the remote extensions registration is failed, the router settings for port forwarding do not accept port range, so what do you think about this, what us the solution?

    Thanks and best regards

  • 0
    Avatar

    Hello Tariq,

    We have created a support ticket for you, your ticket number is 201814796. Yeastar Support team will response you in 24 hours.

  • 0
    Avatar

    Dear Yeastar team,

    I'm trying to configure remote extension on our Yeastar S412 without success.

    My ISP router is able to accept bridge so the Yeastar S412 is acting like a bridge having the same external IP as the router one and can be pingged from the outside.Port forwarding has been enabled as per recommendations on the router.

    On the same LAN registration is OK but not for the remote site.

    Is there any change to be done to the remote site router where the IP phone is sitting?(Yealink T41S)

    Is there a minimal bandwidth requirement from the remote site as the phone stay on registering for ever?

     

    Best Regards,

     

    Samuel BENGA DIM

  • 0
    Avatar

    Hello Samuel,

    We have created a support ticket for you, your ticket number is 201939109. Yeastar Support team will response you in 24 hours.

  • 0
    Avatar

    tariq sando

    i have the same porblem

     

    I have done all the above configuration steps for the "MyPBX-Standard V3" and the IP phone Yealink 7.0.0.60, and here is my router configuration as below, the problem that the remote extensions registration is failed, the router settings for port forwarding do not accept port range, so what do you think about this, what us the solution? pleas

     

    thank you

  • 0
    Avatar

    Dear Yeastar team, i have spend one week to configure the Yeastar S100 extend to my remote office in Thailand and Penang. I manage to call via Yeastar S100 and extend the call to Penang Office, and it work both side. But for Thailand office, they pick the call hear no voice, while my side phone still ringing without knowing they already pick up phone.

    I have a fortigate firewall before the yeastar S100 at my Malaysia HQ office. I configure fix Public IP with 1 to 1 NAT to my yeast S100 ip address. I allow all services (previously i configure port forwarding for 5060 and RTP 10000-12000, to isolate problem i just do 1 to 1 NAT since i have few public ip address), also disable SIP ALG. I configure my S100 with External IP address, NAT and Local Network and Extension to Thailand and Penang with NAT and remote registration,

    Weird thing, it work on my Penang branch office but it dont work on my Thailand office. I also disable the ALG SIP at my Thailand Huawei router and even configure port forwarding to ip phone at huawei router for port 5060 but no luck.

    Please help and really appreciate it.

  • 0
    Avatar

    Hello Eric,

    We have created a ticket for you, your ticket number is 202011607, normally, Yeastar team will response in 24 hours.

  • 0
    Avatar

    Hi yeastar.

    I try remote extension configurate  a public IP 1 to 1 -Disable  SIP ALG in fortigate outbound call works but inbound  in pcap just ring but never ring the remote extensión.

    My model is S100- I probe the same with linkus and tht works fine. But with a sip phone doesnt.

     

    Pls, i need this help. For my company.

  • 0
    Avatar

    Hello Centro,

    We have create a ticket for you, your ticket number is 202012949, our team will guide you how to trouble shooting this issue.

Please sign in to leave a comment.