VOGONS

Tutorial: Setup a low-cost home dialup connection without a real telephone line

Topic actions

First post, by matti157

Posted on 
User metadata
Rank Member
Rank
Member

This guide is for making a DIAL-UP connection without having an actual phone line.

You can connect your old computer to the Internet, and thanks to a local IP address and the magic of routing, you can also browse everything on your LAN (I tried to access my NAS)

In this guide I have combined and summarized what I have learned from these guides, which are definitely better made than mine. So, a thank you to the original authors; it's all thanks to them.

References:
https://web.archive.org/web/20240324110826/ht … ata-dialup.html
https://web.archive.org/web/20240304210734/ht … ata-config.html
https://web.archive.org/web/20240304210356/ht … es/ras_2k3.html
https://web.archive.org/web/20240324110840/ht … ticles/ras.html
https://web.archive.org/web/20240418214026/ht … m-isp-in-a-box/ - Thanks also to Mark of serialport.org for the suggestions sent by email.

What do you need?

  • A DIAL-UP server, which can be of 3 types, many devices can serve as DIAL-UP servers, types I know of includes:

-----Any computer or virtual machine running Windows Server 2000-2022, connected to your LAN (also in wifi) and with access to a physical modem
-----An old CISCO router with a 56K modem card (they can be found on ebay for very little money)
-----A raspberry PI with 56K RS232 modem connected with USB-RS232 adapter (not covered by this guide)

In this tutorial we will look at the first 2 server types (Win and Cisco), I have not had time to try it with raspberry but I know it is fattible. You are free to supplement the guide

  • A telephone line simulator, which is responsible for providing both 56K modems with the illusion that they are connected to a real telephone line. To do this you can use small devices that were used to connect traditional telephones to a VOIP line.

You can find them on ebay for a few €.
Some models:

  • Cisco SPA2102
  • Linksys SPA2102
  • Linksys PAP2T
  • Cisco SPA122
  • Sipura SPA2100

I found one Linksys SPA2102 for €10

Connection scheme

The attachment scheme.png is no longer available

Server setup
The server takes care of providing authentication for the connection (you set the user and password here) and takes care of routing the traffic between the dialup connection and your LAN network.
Choose one of the 2 solutions listed here

Windows Server as dialup server
If you have chosen to use a Windows server, you must configure the RRAS (routing and remote access) role. It’s easy! Connect your server to your LAN via cable or WiFi and Follow this guide step by step https://web.archive.org/web/20240304210356/ht … es/ras_2k3.html
Notes:

  • The steps are very similar for newer Windows servers too
  • Follow the "preamble", "procedures" sections in order and before finishing read "troubleshooting". The "authentication" section is useful to know, I left MS-CHAP and MS-CHAP V2 as I only connected with Windows clients)
  • If you are on Windows 2008 or higher, the "Remote Access Policies" section has been changed to "Remote access logging & policies", right-click on the folder and click on "launch nps", the options are then very similar to 2000/2003
  • In the properties of the RRAS server (right click on the name of your server, properties, IPv4 tab, at the bottom "adapter" make sure that the network card connected to your LAN is selected, by doing so your home router will assign the IP addresses of your LAN to the devices you connect in dialup.
Setting up NPS policies

image.png
1.png
2.png
3.png
4.png
5.png
6.png
7.png
8.png

Cisco router as dialup server
Source of this configuration: https://web.archive.org/web/20240418214026/ht … m-isp-in-a-box/ - Thanks also to Mark of serialport.org for the suggestions sent by email.
Notes:

  • I use a Cisco 1841 IOS 12.4 with 2 built-in Ethernet ports + a wic-1am-v2 card (but wic-1am also works)
  • The router has 2 Ethernet ports, the 0 is configured as WAN and has to be connected to your home router. The 1 is configured as an additional LAN port and can remain disconnected
  • My home LAN is class 192.168.0.X
  • 192.168.0.1 is my router
  • 192.168.1.X is the ip class assigned to devices connected to LAN1 port (which can remain disconnected - useless for this tutorial)
  • Devices that connect via dialup get an IP 172.16.1.X, which with this configuration can still access resources on your LAN
SHOW configuration
show run
Building configuration...

Current configuration : 2918 bytes
!
! No configuration change since last restart
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname cisco1841
!
boot-start-marker
boot-end-marker
!
!
aaa new-model
!
!
aaa authentication login default local
aaa authentication ppp default if-needed local
aaa authorization exec default local 
aaa authorization network default local 
!
aaa session-id common
ip cef
!
!
no ip dhcp use vrf connected
ip dhcp excluded-address 192.168.1.2 192.168.1.25
!
ip dhcp pool DHCP-LAN-Pool-1
   network 192.168.1.0 255.255.255.0
   default-router 192.168.1.1 
   dns-server 192.168.0.1 1.1.1.1 8.8.8.8 
!
ip dhcp pool dialup
   network 172.16.1.0 255.255.255.0
   dns-server 192.168.0.1 1.1.1.1 8.8.8.8 
   default-router 172.16.1.1 
!
!
ip name-server 1.1.1.1
ip name-server 8.8.8.8
ip auth-proxy max-nodata-conns 3
ip admission max-nodata-conns 3
!
!
!
username [here username for router and dialup connection] privilege 15 password 0 [here password for router and dialup connection]
!
!
! 
!
!
!
interface Loopback0
 ip address 172.16.1.1 255.255.255.0
…Show last 65 lines
!
interface FastEthernet0/0
 description WANPORT
 ip address dhcp
 ip nat outside
 ip virtual-reassembly
 duplex auto
 speed auto
!
interface FastEthernet0/1
 description LANPORT
 ip address 192.168.1.1 255.255.255.0
 ip nat inside
 ip virtual-reassembly
 duplex auto
 speed auto
!
interface Async0/0/0
 ip unnumbered Loopback0
 ip nat inside
 ip virtual-reassembly
 encapsulation ppp
 ip tcp header-compression
 dialer in-band
 dialer-group 1
 async mode dedicated
 peer default ip address dhcp-pool dialup
 ppp authentication pap chap
 routing dynamic
!
ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 192.168.0.1
!
!
no ip http server
no ip http secure-server
ip nat inside source list 1 interface FastEthernet0/0 overload
!
access-list 1 permit 192.168.1.0 0.0.0.255
access-list 1 permit 172.16.1.0 0.0.0.255
dialer-list 1 protocol ip permit
!
!
!
control-plane
!
!
!
line con 0
line aux 0
line 0/0/0
 modem Dialin
 modem autoconfigure type default
 transport input all
 autoselect ppp
 stopbits 1
 speed 115200
 flowcontrol hardware
line vty 0 4
!
scheduler allocate 20000 1000
ntp clock-period 17179870
ntp update-calendar
ntp server 193.204.114.232
end

VOIP device setup

You need to access the WEB interface of the device and then follow this guide, section “Using a single ATA”
https://web.archive.org/web/20240304210734/ht … ata-config.html
Notes:

  • As the guide says, the device must be left connected to any LAN, otherwise for some reason the telephone part does not work.
  • The part we are interested in is: “Using a single ATA”
  • When you configure the “dialplan” you will see a number inside the string “9095551010”, replace it with the number you want to call

Start!
Now take an old pc, old laptop or PDA with a modem card and connect them to the free phone port of the VOIP device. Configure the connection with the number set up on the VOIP, put in the user and password you chose when you set up the server, and connect!
I connected with an old Thinkpad with Windows 2000 and via dialup I was able to surf internet and even open a shared folder on the NAS at home!
Please note that the connection will never reach 56K, but will always be 33K

PDF version: https://archive.org/download/setup-a-low-cost … hone%20line.pdf

Last edited by matti157 on 2024-05-19, 23:28. Edited 1 time in total.

Reply 1 of 55, by matti157

Posted on 
User metadata
Rank Member
Rank
Member

A photo of the setup 😁
With the Cisco router acting as a server

The attachment IMG_0028.jpeg is no longer available

Reply 2 of 55, by pengan

Posted on 
User metadata
Rank Newbie
Rank
Newbie

VoIP networks have their complications, I remember having to set voice codec to G.711 instead of G.729 if I wanted the Modem to get through. fax seems to have a bit of other problems, T.38 doesn't always work.
For someone want PSTN/PABX experience, "Excelltel" PABX on Aliexpress is the straightforward and budget firendly option, a 8 extensions SOHO PABX only $45 USD
I was used it to mimic a full function teleco in classroom, the Excelltel(blue box in the video) paired with a Nitsuko Portrait as "long distance exchange" to each other.
Check the working video here: https://zhuanlan.zhihu.com/p/452451018

The Conexant ACF modem on Aliexpress around $15 worked fine on the Raspberry Pi. A modem pool can be built very cheaply and mimics early 90's unix shell providers, pppd also works.

Reply 3 of 55, by matti157

Posted on 
User metadata
Rank Member
Rank
Member
pengan wrote on 2024-05-10, 20:42:
VoIP networks have their complications, I remember having to set voice codec to G.711 instead of G.729 if I wanted the Modem to […]
Show full quote

VoIP networks have their complications, I remember having to set voice codec to G.711 instead of G.729 if I wanted the Modem to get through. fax seems to have a bit of other problems, T.38 doesn't always work.
For someone want PSTN/PABX experience, "Excelltel" PABX on Aliexpress is the straightforward and budget firendly option, a 8 extensions SOHO PABX only $45 USD
I was used it to mimic a full function teleco in classroom, the Excelltel(blue box in the video) paired with a Nitsuko Portrait as "long distance exchange" to each other.
Check the working video here: https://zhuanlan.zhihu.com/p/452451018

The Conexant ACF modem on Aliexpress around $15 worked fine on the Raspberry Pi. A modem pool can be built very cheaply and mimics early 90's unix shell providers, pppd also works.

The Cisco SPA122 device and all its similar ones are used to simulate the telephone line, at the voip level there is nothing to manage

I put here a screenshot of the parameters set, in the end it is a matter of disabling all the items related to fax and to enable the tick that it is a modem line

As a codec I left the default G711u

The attachment Screenshot 2024-05-16 212229.png is no longer available

Reply 4 of 55, by kingcake

Posted on 
User metadata
Rank Oldbie
Rank
Oldbie

Cathode Ray Dude (CRD) on Youtube has good videos and blogs on this topic.

The devices you listed are VOIP POTS gateways, NOT phone line simulators. Phone line simulators are old analog devices that have nothing to do with VOIP.

Reply 5 of 55, by matti157

Posted on 
User metadata
Rank Member
Rank
Member
kingcake wrote on 2024-05-16, 21:50:

Cathode Ray Dude (CRD) on Youtube has good videos and blogs on this topic.

The devices you listed are VOIP POTS gateways, NOT phone line simulators. Phone line simulators are old analog devices that have nothing to do with VOIP.

I was using the wrong term. Yes basically they receive a call on one of the telephone ports and through the software they forward it to the other port where there is the modem ready to answer

Reply 6 of 55, by kotel

Posted on 
User metadata
Rank Oldbie
Rank
Oldbie

Anyone got this to work on Windows server 2012 r2? I'm having troubles finding the correct settings and with dial up.

"All my efforts were in vain...
Let that be my disappointment."
-Kotel

Reply 7 of 55, by matti157

Posted on 
User metadata
Rank Member
Rank
Member
kotel wrote on 2024-05-17, 18:04:

Anyone got this to work on Windows server 2012 r2? I'm having troubles finding the correct settings and with dial up.

I did it on 2008 R2, what problem do you have in detail?

I expect no or very little difference on RRAS role between 2008 and 2012

Reply 8 of 55, by kotel

Posted on 
User metadata
Rank Oldbie
Rank
Oldbie
matti157 wrote on 2024-05-17, 20:33:
kotel wrote on 2024-05-17, 18:04:

Anyone got this to work on Windows server 2012 r2? I'm having troubles finding the correct settings and with dial up.

I did it on 2008 R2, what problem do you have in detail?

I expect no or very little difference on RRAS role between 2008 and 2012

I think I screwed up the add role/features part and/or create group part since I couldn't find the remote access policies in routing and remote access. I also pretty much don't know how to dial in and log in (I am extremely new to windows server os)

"All my efforts were in vain...
Let that be my disappointment."
-Kotel

Reply 10 of 55, by matti157

Posted on 
User metadata
Rank Member
Rank
Member
kotel wrote on 2024-05-18, 06:10:
matti157 wrote on 2024-05-17, 20:33:
kotel wrote on 2024-05-17, 18:04:

Anyone got this to work on Windows server 2012 r2? I'm having troubles finding the correct settings and with dial up.

I did it on 2008 R2, what problem do you have in detail?

I expect no or very little difference on RRAS role between 2008 and 2012

I think I screwed up the add role/features part and/or create group part since I couldn't find the remote access policies in routing and remote access. I also pretty much don't know how to dial in and log in (I am extremely new to windows server os)

Here a series of screenshots with the steps in order, as soon as the policy is saved the clients authenticate themselves

Setting up NPS policies

image.png
1.png
2.png
3.png
4.png
5.png
6.png
7.png
8.png

Reply 11 of 55, by kotel

Posted on 
User metadata
Rank Oldbie
Rank
Oldbie
matti157 wrote on 2024-05-19, 23:20:

Here a series of screenshots with the steps in order, as soon as the policy is saved the clients authenticate themselves

Setting up NPS policies

image.png
1.png
2.png
3.png
4.png
5.png
6.png
7.png
8.png

Thanks. I will check if I have done that correctly once I find some spare time.

"All my efforts were in vain...
Let that be my disappointment."
-Kotel

Reply 12 of 55, by Veeb0rg

Posted on 
User metadata
Rank Member
Rank
Member

I have used a Cisco ATA-191 as a phone line simulator as well using the same settings. I used it to call from a dos machine to another dos machine running a BBS software using 2 usr courier modems.

Reply 13 of 55, by kotel

Posted on 
User metadata
Rank Oldbie
Rank
Oldbie

Done the same steps. Now I can't dial in using any os. Could you help me with that?

"All my efforts were in vain...
Let that be my disappointment."
-Kotel

Reply 14 of 55, by NRoach44

Posted on 
User metadata
Rank Newbie
Rank
Newbie
kotel wrote on 2024-05-21, 09:09:

Done the same steps. Now I can't dial in using any os. Could you help me with that?

Not OP, but what happens when you do try to dial in?

Reply 15 of 55, by kotel

Posted on 
User metadata
Rank Oldbie
Rank
Oldbie
NRoach44 wrote on 2024-07-17, 13:45:
kotel wrote on 2024-05-21, 09:09:

Done the same steps. Now I can't dial in using any os. Could you help me with that?

Not OP, but what happens when you do try to dial in?

No signal.
I have gave up on using 2012 r2, so I'm using 2k3 r2 as the tutorial said. When I got to creating an access policy it couldn't find "Dial-In Users" in groups, so I used Dial-In. Dialling in just lands me with no dialup signal, the same as in 2012 r2. I also couldn't make a new dialup connection on xp. Any ideas?

"All my efforts were in vain...
Let that be my disappointment."
-Kotel

Reply 16 of 55, by kotel

Posted on 
User metadata
Rank Oldbie
Rank
Oldbie

98se also fails to make an connection (no dialup signal).

"All my efforts were in vain...
Let that be my disappointment."
-Kotel

Reply 17 of 55, by rev0ntul3t

Posted on 
User metadata
Rank Newbie
Rank
Newbie

I've created a setup with a LinkSys PAP2T and an Apple AirPort Extreme with PPPoE support. It gets through most of the handshake until it fails with an Error 777 (Windows XP). I suspect it might be a faulty PPPoE device (The Apple one).

For reference, I'm using Windows XP on a HP EliteBook 8730w (from 2008, give or take).

I'll try other devices soon and report back.

Reply 18 of 55, by NRoach44

Posted on 
User metadata
Rank Newbie
Rank
Newbie
kotel wrote on 2024-10-03, 15:40:

98se also fails to make an connection (no dialup signal).

That sounds like you've got a line issue - do you have a POTS phone to try dialling with and making sure you connect through to the modem on your server? The PPP and auth stuff happens after the modems scream at each other, so you should be able to hear that.

Reply 19 of 55, by kotel

Posted on 
User metadata
Rank Oldbie
Rank
Oldbie

Sorry for the veery late reply.
It looks like I also need the box type modems to make this work (forgot the technical name of it), which I don't own 🙁 I heard you could also use an Linksys PAP2T, although that costs a kidney where I live so it's not an valid option. I think any other VoIP gate would work, but I am not sure since my knowledge on modems is close to none.

"All my efforts were in vain...
Let that be my disappointment."
-Kotel

Go to top of page Go to top of page
Back to General Old Hardware
Close window
Close window