Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Distributing inbound calls using SIP forking

Discussion in '3CX Phone System - General' started by RichardCrabb1, Dec 31, 2012.

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

    RichardCrabb1 New Member

    Mar 7, 2009
    Likes Received:
    Dear Forum,
    I felt that this may be useful, so wanted to share it with you all. This solution allows more calls by simply adding additional SIP trunk ADSL lines.

    We had an issue where we had one dedicated SIP trunk line with Spitfire (in the UK), but found that we were losing lots of calls due to the customer demand. The way around this was to increase the number of calls from 9 to 16. No bandwidth was available to handle all 16 at once, so we used a second SIP trunk ADSL line instead. A second 3CX was connected to this line. By using "forking" at the SIP trunk level we found that there was an even split of calls between both SIP trunks. This was ideal for obtaining the number of calls that we needed to achieve. The 2nd 3CX was needed as the IP addressing of both trunks is the same. It connects to the first main 3CX using a bridge. If more calls are needed, then a third Spitfire SIP trunk can be added - but that would need either a third 3CX, or an alternative softswitch such as Freeswitch.

    We have used forking with extensions before, but this is the first time that we have used it with trunks. It seems to work very well.

    The application is a digital receptionist using VAD to allow the renewal of concessionary travel cards in the UK. Councils all over the country are using this for their card holders. Card holders call a number and validate their details. If they validate then their card is automatically renewed.
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.