Thanks so much for the breakdown of your setup!
and sorry, I meant to write a preemptive "thanks" in the previous
email and sign-off, but accidentally hit control+enter to send the
message prematurely.
So a double helping of thanks here,
-tim
On March 5, 2020, Scott Granados wrote:
Great questions.===========================================================
First, I’m running incredible PBX for raspberry Pi. It’s basically
an Asterisk based environment with a graphical front end that’s
quite accessible. Totally open source and very flexible. In my
case I’m SIP all the way through so things like Grandstream phones
and a SIP provider upstream. Vitelity.net is a decent option,
Gafachi if you have decent volume especially off shore or IP
Innovations for wholesale if you have enough volume. There are
many good options spends on your volume and price points etc. I
have several DIDs routed to the inbound trunks and route them to
auto attendants or extensions as needed.
In terms of volume, depends on the CODECs used and if
you’re transcoding etc. I’ve done more than 24 parallel channels
so supporting something similar to a DS1 should be more than
doable.
Hope that helps
On Mar 5, 2020, at 12:37 PM, Tim Chase
<raspberry-vi@xxxxxxxxxxxxxxxxx> wrote:
On March 5, 2020, Scott Granados wrote:
running small phone systems
Could I trouble you share more about your configuration? I've
had an itching to do this for a long time and never actually
moved forward with it. So I've got a bunch of questions (smile):
- Are you using traditional phones with special POTS hardware
attached to your RPi? Or are you using VoIP phones (possibly with
PoE) or soft-phones?
- Do you have any recommendations on choosing a VoIP backend
provider to route calls to the POTS network? Or more generically,
how are you connecting to the outside POTS world?
- How many internal phones does your RPi setup handle?
- Are you running more than one direct-inward-dial-in (DID)
number, or do you share a smaller pool of DID numbers across a
greater number of internal phones?
===========================================================
The raspberry-vi mailing list
Archives: //www.freelists.org/archives/raspberry-vi
Administrative contact: <mike.ray@xxxxxxxxxxxxxx>
-----------------------------------------------------------
Raspberry Pi and the Raspberry Pi logo are trademarks of the
Raspberry Pi Foundation.
This list is not affiliated to the Raspberry Pi Foundation and
the views and attitudes expressed by the subscribers to this list
do not reflect those of the Foundation.
Mike Ray, list creator, January 2013
===========================================================
The raspberry-vi mailing list
Archives: //www.freelists.org/archives/raspberry-vi
Administrative contact: <mike.ray@xxxxxxxxxxxxxx>
-----------------------------------------------------------
Raspberry Pi and the Raspberry Pi logo are trademarks of the
Raspberry Pi Foundation.
This list is not affiliated to the Raspberry Pi Foundation and the
views and attitudes expressed by the subscribers to this list do
not reflect those of the Foundation.
Mike Ray, list creator, January 2013