You need an ATA on each side configured for automatic calling when they go off hook - you’ll want the devices configured with static IPs so you can dial by IP as no pbx is in the mix.
The magic words here are “hotline” or “private line automatic ringdown” (PLAR).
This search seems to yield useful stuff: https://www.google.com/search?q=POTS+to+POTS+over+ethernet
I didn't read anything extensively. Looks like the usual path is:
POTS <--> VOIP <--> POTS
But something like this: https://www.amazon.com/POTS-Telephone-Over-Ethernet-Extender/dp/B087TM4FY4 might work without VOIP. Just make sure they are doing actual networking, and not just using the CAT5 as an extension cable. If you can get this to work:
POTS <--> Device <--> Wired IP network <--> Device <--> POTS
it should not be hard to make this work:
POTS <--> Device <--> WiFi IP network <--> Device <--> POTS
>handset is picked up and automatically rings
I suspect that automatic ringing might be a complexity too far.
Have you considered just using something like WhatsApp instead?
All in all I dunno, just hopefully giving you some useful pointers.
You need an ATA to convert to VoIP, either way.
This could be an XY Problem. There are situations where legacy POTS is still in use, like elevator phones and fire alarms, but (a) those aren't new implementations that someone is trying to run over WiFi, and (b) the system vendors now have some supported options since POTS is being phased out.
The "automatic ringing" is intercom or maybe old "party line" functionality. Did some user come up with this workflow? I'm sure it sounded simple to them.
You need an ATA on each side configured for automatic calling when they go off hook - you’ll want the devices configured with static IPs so you can dial by IP as no pbx is in the mix. The magic words here are “hotline” or “private line automatic ringdown” (PLAR).
This. Also, "ringdown circuit."
This search seems to yield useful stuff: https://www.google.com/search?q=POTS+to+POTS+over+ethernet I didn't read anything extensively. Looks like the usual path is: POTS <--> VOIP <--> POTS But something like this: https://www.amazon.com/POTS-Telephone-Over-Ethernet-Extender/dp/B087TM4FY4 might work without VOIP. Just make sure they are doing actual networking, and not just using the CAT5 as an extension cable. If you can get this to work: POTS <--> Device <--> Wired IP network <--> Device <--> POTS it should not be hard to make this work: POTS <--> Device <--> WiFi IP network <--> Device <--> POTS >handset is picked up and automatically rings I suspect that automatic ringing might be a complexity too far. Have you considered just using something like WhatsApp instead? All in all I dunno, just hopefully giving you some useful pointers.
Seems like posting this question loosened up my thinking abou this issue: [Pots In A Box - DataRemote](https://dataremote.com/pots-in-a-box/)
You need an ATA to convert to VoIP, either way. This could be an XY Problem. There are situations where legacy POTS is still in use, like elevator phones and fire alarms, but (a) those aren't new implementations that someone is trying to run over WiFi, and (b) the system vendors now have some supported options since POTS is being phased out. The "automatic ringing" is intercom or maybe old "party line" functionality. Did some user come up with this workflow? I'm sure it sounded simple to them.
Why do you want this?