You are here

mesh to telco gateway

13 posts / 0 new
Last post
w8erd
mesh to telco gateway
What is the recommended method of creating a bidirectional gateway between mesh phones and a telco line?
nc8q
nc8q's picture
mesh to telco gateway
Hi, Bob:
 
Me too.
I would like to compare my 2 VoIP gateway services with what is recommended.
Folks in our local AREDN network can dial out to POTS by prefixing either '76' or '79' to a 10 or 7 digit number.
Dialed 7 digit numbers are prefixed with 937 for easier local area calls.
Dialed in calls from POTS hear a message and then can dial by extension number.

73,
Chuck

 
w8erd
It is very disappointing that
It is very disappointing that nobody has offered and suggestions here.
N8RLW
IP phone services.
W8erd, For telephone service I just used the unifi telephone switch and connected it to the ARDEN network. I have found out through trial and error that you have to look at this network as a adhoc system. While I have never had a conversation with the developers of the ARDEN system I get the feeling some services we are trying to provide might been in the initial plans. Unifi system which is a commercial system does provide lots of the same services and is geared for a more permanent network solution. I'm open to any input or comments. Best Regards, Steven N8RLW
nc8q
nc8q's picture
What is the recommended method

"What is the recommended method ..."
"It is very disappointing that nobody has offered and suggestions here."

There are 40+ threads in this forum dealing with each of:
'PBX', 'FreePBX', 'Phones', 'VoIP', 'RasPBX'.
I assume that there is a suggestion or two in them.

Hi, Bob:

 You did not ask for 'suggestions'...you asked for a 'recommended method'.
Please rephrase your post for better clarity.

73, Chuck

 

KE0RSX
KE0RSX's picture
I don't think there's a
I don't think there's a "recommended" method, although I think most of us are using something like FreePBX/RasPBX and some type of trunk inside of that. In our case, the mesh phones can call out, but the outside callers aren't able to call in. But we're also using an OBI-talk node as our link, so it might be the problem. As Chuck mentioned above, if you're looking for a "How did you do this?" or a "Why isn't this working?" answer, you might need to clarify it. Or you might need to move this to a subforum where it might get more interest.

Have a great day. :)
Patrick.
nc8q
nc8q's picture
mesh phones can call out, but the outside callers aren't able to
"mesh phones can call out, but the outside callers aren't able to call in."
"using an OBI-talk node as our link"

Hi, Patrick:

 My home phone services does use an OBIHAI Obi-200, so there is a FXS device for that.

 AREDN PBX:
I am using RasPBX at my end of the AREDN PBX, so there is no FXS/FXO device in use there.
Inbound calls are sent to an IVR wherein they are prompted to dial by extension number.

3s, Chuck

 
KE0RSX
KE0RSX's picture
I would love to see how you
I would love to see how you have that configured. That's almost exactly what we're using here. We have the Obi-200 connected to the LAN port of a MikroTik hAP ac lite and a RasPBX connected to another LAN port. The outbound side works, but when someone calls in, it doesn't work at all.

For clarification, the actual network looks like this: Fiber ONT --> switch --> MikroTik hAP ac lite (provides Internet to the mesh) -> OBi-200/RasPBX (which might be connected to a dumb switch).

The Fiber ONT to switch to MikroTik is because my ISP allows us to have two separate IP Addresses. So, my home network is on one port of the switch and the mesh is on another. Completely isolated from each other.

Have a great night. :)
Patrick.
nc8q
nc8q's picture
I would love to see how you have that configured.

Internet
  |
PFSense firewall router
; Because I needed to NAT by both incoming IP address and port.
; OTS Home routers cannot NAT by incoming IP address.
; Herein lies the magic of routing VoIP SIP:5060 accounts with different providers.
: Primary-A is SIP:5060 to Obi-200 HOME PSTN, Sub-A is IAX2:4569 NAT'ed toward RasPBX (AREDN)
; VoIP service B SIP also gets NAT'ed to RasPBX for another PSTN in/out
; 2 incoming SIP ports; Each routed differently.
; VoIP-A:5060 goes to OBI-200-HOME, VoIP-B:5060 goes toward RasPBX (AREDN).
  |
Home LAN switch: Obihai Obi-200 SIP, home workstations, home LAMP server, ...
  |
WAN
VLAN switch in home
Individual LAN ports for VLAN 10, 20, 30, 40, 50
VLAN 10: locoM2: NC8Q-SERVICES: RasPBX, phone, teamtalk, meshchat, WSJT-X, BPQ, ADS-B, another LAMP server
VLAN 50: Mikrotik hAP: Tunnels.
VLAN 70: locoM2: NC8Q-SERVICES1: Playground
Individual LAN ports for VLAN 10, 20, 30, 40, 50
Trunk port: VLANS 10, 20, 30, 40, 50, ...
 |
Trunk port: VLANS 10, 20, 30, ...
VLAN switch in garage near tower
Individual LAN ports for VLAN 10, 20, 30, 40, 50
VLAN 20: Ubiquiti PBE-M5-400: A former attempt to RF link to local AREDN network. Tx Mbps: 10-20 Summer, 20-40 Winter
VLAN 30: Mikrotik LHG-HP5-XL: Current attempt to RF link to local AREDN network. Tx Mbps: 20-40 Summer, 40-80 Winter.
.
Patrick:
 I think you could route: Internet -> PBX -> Obi-talk.
If you had IP phones, you would not need the Obi-talk:FXS port for POTS phones.
IOW, you only need a FXS port for legacy POTS phone equipment.

I hope this helps,
Chuck
 

KE0RSX
KE0RSX's picture
So, in theory, I could remove
So, in theory, I could remove the Obi-Talk completely then? What we have is a Google number for our ARES team. That's what will be routed into the rasPBX. One of our members used an Obi-Talk to set his PBX up, which is why we went that route. But yes, we all have digital phones (GrandStreams and Cisco phones). So, we *should* be able to just set up the incoming trunk without the Obi-Talk? We don't have any legacy POTS lines or equipment other than a phone that I hooked up to the Obi-Talk before I bought a Grandstream phone.

Have a great day. :)
Patrick.
nc8q
nc8q's picture
What we have is a Google number

Hi, Patrick:
 
If that 'google number' is a SIP or IAX2 account, yes.
Can you view the account settings?

One of my VoIP accounts is $0.85/month + 1 cent a minute 'off-hook'.

I started my VoIP journey with Mark N2MH's "MeshPhone" which uses an unique 'prefix' for 'special features'.
'78' dial-out of area
'73' dial by callsign (last 4 characters of callsign is unique enough around here).
- a. A 'registered' IP phone can dial an active unregistered IP phone.
- b. Naturally, unregistered phones have no features via the PBX, except can receive ala (a.)

I added,
'79' for dial-out to VoIP account 'A'.
'76' for dial-out to VoIP account 'B'.
So, to dial 555-499-1212, a user would dial
79-555-499-1212

 

K5DLQ
K5DLQ's picture
CallCentric.com is super
CallCentric.com is super-cheap. (SIP provider)
km6zpo
km6zpo's picture
FreePBX Works
I’m not going to get into the specifics but I will say that I have a FreePBX server connected to the MESH AND to an outside VOIP provider: voip.ms. —- with that people can call from external numbers and any extension on the network can call out. So yes it can be done. —-mark, KM6ZPO

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer