FusionPBX getting started : Receiving an inbound call

In this part we are going to set up inbound calling. I have purchased a number from voip.ms that is an Athens, Georgia number – based in the US. However, this number could be anywhere that voip.ms provides numbers. It does not have to be in the same country as your server. The number should be routed to voip.ms SIP account that you are using with your FusionPBX server (this will send the call to the registered server). The telephone number I have is 1-706-765-2072.

This assumes we have done the previous part and set up a trunk to voip.ms and have the call forwarded to the registered server.

First click on Dialplan / Inbound Routes –
FusionPBX Inbound Route

Next click on the add button on the right of the screen –

FusionPBX Inbound Route - add

Now type in the number details. The Destination Number should be in the same format as it is being presented by the call provider. You may need to do a test call and check the Freeswitch logs to check how it is being sent. Also be aware that if you’re forwarding the call to a SIP URI you should send it to port 5080 (not 5060) on your FusionPBX server as this is the port that FusionPBX expects external call –

FusionPBX Inbound Route - Inbound Call Routing

I set the destination to be the extension that I configured earlier.

I can now call the number and the call comes through to extension 1234 –

FusionPBX Inbound Route -taking call on x-lite

5 thoughts on “FusionPBX getting started : Receiving an inbound call

  1. Lou


    Thanks for those useful tips around fusionPBX configuration.
    I’ve tried to configure inbound calls using your guide but unsuccessfully, I can only hear re-order tone.
    I then assigned my public ip address to ext-rtp-ip and ext-sip-ip in External Profile but still no luck.
    Any tips of getting this working would be appreciate.
    The outbound calls worked nicely however.

    Thanks for your time and help.

  2. Matt Newcombe Post author

    Hi Lou

    I think the only thing to do would be to check the debug logs and see how far the call is getting.

    Cheers, Matt

  3. JJ


    Thanks for the instructions. Unfortunately, inbound calling is not working for me either. I’m on FusionPBX 3.5 rc2.
    I’m behind a NAT, so freeswitch was binding to my local ip, not good. I simply put my external ip address in external_rtp_ip and external_sip_ip in vars.xml. Now freeswitch binds to my external ip. Good.

    I tested the freeswitch echo conference. It passed. I could hear back my voice echo.

    I’m using voip.ms and teliax. Observing the fs_cli, the call does not even make into freeswitch for some reason with voipms.
    With teliax, I see activity on the fs_cli, freeswitch answers the call, but then hangs up immediately.

    Any ideas? Thanks.

  4. JJ

    Okay. I’m good now. Incoming calls are working for all 3 of my providers: Teliax, Callcentric and voip.ms

    On FusionPBX v3.4 and v3.5 RC, there is already an inbound template in Dialplan => Destinations. I just specify inbound phone number and for the action field, I route directly to the extension number in the dropdown. This template sets everyting for you and it works great. Thanks.

  5. Msprobe

    you may need to check your codec settings – most providers uses the preferred G729 and in most cases when you can see the call hit the softswitch/fusionpbx it boild down to 2 things dial plan (dial pattern) is not right – you may need to check the amount of digits and obviously codec (the hidden criminal i called it) This article is very simple whoever put it together simplified it in these easy steps.
    To quickly find out what is going on is to setup and extension – register it with a normal softphone, setup your gateway and outbound parameters. make some test calls it may not need to complete but if you dialing a correct number at lease you should see if it hit the outbound leg. Check the cdr to see if the call did attempt and what respond you get (normal clearing) – if you make the call and you dont get a RBT and in your cdr profile it says normal clearing you may have a trans coding or codec issue but if everything goes well therefore it will be much easier to setup and test your inbound route – without touching the outbound leg because you already estb it works (internal to external)

Comments are closed.