[MVMA] Another PBX solution in search of a problem. ;-)
Chuck Gelm
nc8q-mesh at gelm.net
Tue May 5 11:10:45 EDT 2020
Staying home. No golf. No tennis. Lots of time.
I had an idle Raspberry Pi and a ham in California interested in mesh
and IP phones (and with an idle RPi).
Around March 26th we started trying to trunk 2 PBXs.
I wanted to achieve this over the internet rather than via a mesh-tunnel.
I started trying to link my internet PBX to my mesh PBX and to my
PBX-go-box.
I wanted to use IAX2 for the trunk, but I already had port 4569 being
forwarded to my mesh PBX for the phone patch.
I needed to set up port forwarding and include specific IP addresses on
the WAN (internet) and the LAN:
1 WAN<>LAN address for the phone patch and 1 WAN<>LAN address for the
PBX.
Success using PFSense firewall.
I have 3 Raspberry Pi PBXs:
1. nc8q-rasPBX on the local mesh
2. nc8q-rasPBX-go on a Mikrotik hAP that can tunnel with available
internet access
3. nc8q-rasPBX-home on my home internet ISP; trunked with nc8q-raspbx
and k6dlc-rasPBX (California)
* Extensions on any of these PBXs may dial each other by 4-digit
extension.
* Extensions on any of these PBXs may dial long distance into N2MH's
MeshPhone network via mesh tunnels.
Using N2MH's PBX configuration files, any PBX on the internet may be
trunked into the local (and N2MH's) MeshPhone network.
So, something as simple and as portable as a Raspberry Pi with
internet or mesh-tunnel access,
with (or without) an IP phone or a softphone, can access the local (and
N2MH's) MeshPhone network.
I am now wondering of my mesh-phone-patch service can be extended to
extensions of trunked PBXs.
:-|
I would like to provide the phone patch feature to extensions of
nc8q-raspbx-go (and, maybe, other PBXs).
--
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qth.net/pipermail/mvma/attachments/20200505/a0cc26f6/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sig.gif
Type: image/gif
Size: 3641 bytes
Desc: not available
URL: <http://mailman.qth.net/pipermail/mvma/attachments/20200505/a0cc26f6/attachment-0001.gif>
More information about the MVMA
mailing list