started today - maybe last week on sone numbers - all numbers now
tried voip2
switched to backup freepbx - same
have other trunk with voip.ms, working fine
fairly sure this is a freephoneline issue
[FreePBX] all circuits busy
-
mkaye
- Active Poster
- Posts: 52
- Joined: 05/28/2017
- SIP Device Name: Freepbx
- Firmware Version: v16
- ISP Name: bell fiber
- Computer OS: windows 11
- Router: ubiquiti udmpro
-
Liptonbrisk
- Technical Support
- Posts: 3702
- Joined: 04/26/2010
- SIP Device Name: Obihai 202/2182, Groundwire
- Firmware Version: various
- ISP Name: no CGNAT
- Computer OS: Windows 11 Pro (25H2)
- Router: Asuswrt-Merlin & others
Re: all circuits busy
Incoming and outgoing work on 4 different FPL accounts I tested using voip2.freephoneline.ca:5060 just now, registered in different provinces.
I tested calling to Telus and Bell carrier numbers. Telus to FPL and FPL to FPL worked as well. I used MicroSIP app (which is free to use and test with) and Obihai devices.
The problem could be specific to an area code with a specific carrier (or isolated to a specific carrier). I would probably need some examples of business phone numbers I could call to test, since I numbers I am calling work fine. Call/SIP logs may be useful.
However, visit viewtopic.php?t=21062. So, I don't know if troubleshooting is worthwhile during the call platform migration period. If the SIP error code is 503, that may indicate a trunk-capacity or interconnect issue on Freephoneline's platform-migration side.
Then again, I see that you had the same issue back in 2024 with pjsip: viewtopic.php?p=81393#p81393. Having hit a similar "all circuits busy" problem with FreePBX/PJSIP before suggests this could be a recurring pattern with a PBX-side configuration interacting poorly with certain trunk conditions. That is, the new failure could reflect either a Freephoneline platform change or a pre-existing Freepbx quirk that the migration exposed.
I tested calling to Telus and Bell carrier numbers. Telus to FPL and FPL to FPL worked as well. I used MicroSIP app (which is free to use and test with) and Obihai devices.
The problem could be specific to an area code with a specific carrier (or isolated to a specific carrier). I would probably need some examples of business phone numbers I could call to test, since I numbers I am calling work fine. Call/SIP logs may be useful.
However, visit viewtopic.php?t=21062. So, I don't know if troubleshooting is worthwhile during the call platform migration period. If the SIP error code is 503, that may indicate a trunk-capacity or interconnect issue on Freephoneline's platform-migration side.
Then again, I see that you had the same issue back in 2024 with pjsip: viewtopic.php?p=81393#p81393. Having hit a similar "all circuits busy" problem with FreePBX/PJSIP before suggests this could be a recurring pattern with a PBX-side configuration interacting poorly with certain trunk conditions. That is, the new failure could reflect either a Freephoneline platform change or a pre-existing Freepbx quirk that the migration exposed.
Please do not send me emails; I do not work for nor represent Freephoneline or Fongo. Post questions on the forums so that others may learn from responses or assist you. Thank you. If you have an issue with your account or have a billing issue, submit a ticket here: https://support.fongo.com/hc/requests/new. Visit http://status.fongo.com/ to check FPL/Fongo service status. Freephoneline setup guides can be found at http://forum.fongo.com/viewforum.php?f=15.