It seems like new MeshPhone PBXs are popping up often.
Perhaps there is a little latency in these new PBXs appearing in Mark's global meshphone.conf file.
A few PBX operators have been adding trunks to these fresh PBXs to our local meshphone.conf
file so that these new extensions can dial-out to the global MeshPhone network, but alas, the rest
of the 80+ MeshPhone PBXs and their extensions cannot dial-in to these new PBXs.
For the time being, there is a way to keep the global meshphone.conf file unmodified, yet add
fresh PBX extensions to your PBX's dial plan.
There are 3 web services for discussion/hints/tips of MeshPhone PBXs:
Perhaps there is a little latency in these new PBXs appearing in Mark's global meshphone.conf file.
A few PBX operators have been adding trunks to these fresh PBXs to our local meshphone.conf
file so that these new extensions can dial-out to the global MeshPhone network, but alas, the rest
of the 80+ MeshPhone PBXs and their extensions cannot dial-in to these new PBXs.
For the time being, there is a way to keep the global meshphone.conf file unmodified, yet add
fresh PBX extensions to your PBX's dial plan.
There are 3 web services for discussion/hints/tips of MeshPhone PBXs:
- Here
- slack.com AREDN Community pbx-networking-voip-meshphone (may need an invite)
- MeshPhone-PBX-Operators_+_subscribe@groups.io (remove the underscores)