Dual WAN with BSNL FTTH and VoIP

Messages
22
Location
NA
ISP
BSNL
So I was hoping someone here could help or provide advice on something I'm looking to do:
I recently got BSNL FTTH as a back up broadband connection. It came bundled with a new BSNL number, delivered over VoIP.

I have an Asus ac87u set up to do dual WAN with failover between my primary broadband provider and BSNL FTTH as secondary. The primary connection comes in as PPPoE on an incoming ethernet cable, and goes directly into the ac87u's WAN port. The secondary (BSNL FTTH) is an incoming optical cable, terminated by a BSNL provided Optilink ONT cum router. The Optilink router plugs into the ASUS ac87u on one of the ASUS' LAN ports. I use 192.168.2.XXX as the subnet for all my devices; the ASUS is the gateway for this. I've put the Optilink on 192.168.1.XXX and it serves as the gateway for the secondary connection.

There is VoIP set up in the Optilink and an RJ-11 jacked cable that come out of the Optilink and into a POTS instrument for calls on the number that came with the FTTH.
From what I can make out, the Optilink VoIP end point is given a static IP on a 10.XXX.YYY.ZZZ private network, with the SIP server it's supposed to talk to also on the same 10.XXX.YYY.ZZZ private network

All of this works right now; I can make and received calls on the new number and the broadband fails over to the secondary when the primary fails.

What I'd like to do:
1. I'd like to avoid the additional hop (ASUS --> Optilink --> Internet) for the failover case, and get rid of the 192.168.1.XXX subnet entirely.
I'm assuming this would involve putting the Optilink into bridge mode and having the ASUS do the PPPoE etc.

2. I'd like to be able to use the VoIP number with VoIP apps on smartphones or IP phones on the 192.168.2.XXX subnet, and do the fancy things that SIP/VoIP allows.
In particular receive incoming calls on the VoIP number on any chosen device, and call out from any device etc.

So on to the questions:

0. It is possible to do both (1)and (2) together, correct? (Obviously I'm assuming it is)
1. A route between 192.168.2.XXX and 10.XXX.YYY.ZZZ will need to be added, correct? Is this all that's needed for a VoIP client on 192.168.2.XXX to reach the BSNL SIP server and make/receive calls ? (Assuming route is necessary but not sufficient...)
2. Will I need to run my own SIP server or something? (Does/can the Optilink act as a SIP Server or proxy by the way? I can see a Dialplan as an advanced configurable option in the Optilink's configuration interface)

What's primarily causing confusion for me right now is how to set up for the effectively two outgoing networks for the BSNL (the internet one and the VoIP one) in bridge mode, while not messing up the dual WAN etc...

Any tips/advice/pointers appreciated !
 
Been tinkering with the setup and TL;DR: It isn't working yet. In the process I managed to go through phases where neither internet nor voice worked. Now the internet part is restored but voice is still out, so starting again ab-initio.

This time I left the Internet WAN on the ONT as it was.

For the voice WAN, I put the ONT into bridge mode, checked the LAN2 port for binding and chose service mode "INTERNET". I connected LAN2 into my ER-X's eth0, and assigned it the static IP with the associated netmask and gateway that I'd got for the voice WAN from the original BSNL config (10.116.X.Y, 255.255.254.0,) All the other ER-X ports are assigned to the same LAN switch and the ER-X has an IP on 192.168.2.XXX

If I now connect my computer to the ER-X (with another IP on the same 192.168.2.XXX subnet) I can ping the 10.116 IP assigned to the ER-X WAN port, but not the gateway or any of the IPs for the SIP server etc (also from the original BSNL config). I assume I'm missing a route or something.
Any pointers?
 
Upvote 0
That's strange. You wouldn't need a route and it should have let you ping atleast the gateway. I wonder if they have enabled Mac binding for the voice interface as well. You could try cloning the mac address of the voice interface to the ERX WAN interface and see if it helps.

Also, could you pls show screenshots of the config on the ONT side, the WAN profiles.
 
Upvote 0
Attached (thanks !)
 

Attachments

  • Screenshot 2020-03-11 at 9.01.04 AM.webp
    Screenshot 2020-03-11 at 9.01.04 AM.webp
    57 KB · Views: 482
  • Screenshot 2020-03-11 at 10.18.00 AM.webp
    Screenshot 2020-03-11 at 10.18.00 AM.webp
    46.5 KB · Views: 358
  • Screenshot 2020-03-11 at 9.01.22 AM.webp
    Screenshot 2020-03-11 at 9.01.22 AM.webp
    53.7 KB · Views: 341
Upvote 0
For what it's worth: I tried putting the voice WAN back into Route (i.e. non bridge) mode, and used the diagnostics function tab to ping the gateway.
It doesn't seem to work from there either (though I don't know if that is significant; perhaps BSNL just turns off ICMP for SIP servers?)
 

Attachments

  • Screenshot 2020-03-11 at 12.49.10 PM.webp
    Screenshot 2020-03-11 at 12.49.10 PM.webp
    42 KB · Views: 362
Upvote 0
I am able to ping the voice interface gateway and the SIP gateway.

Code:
root@varkey:~# ping -c 4 192.168.149.78
PING 192.168.149.78 (192.168.149.78): 56 data bytes
64 bytes from 192.168.149.78: seq=0 ttl=60 time=48.391 ms
64 bytes from 192.168.149.78: seq=1 ttl=60 time=48.960 ms
64 bytes from 192.168.149.78: seq=2 ttl=60 time=48.410 ms
64 bytes from 192.168.149.78: seq=3 ttl=60 time=49.902 ms

--- 192.168.149.78 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 48.391/48.915/49.902 ms
root@varkey:~# ping -c 4 10.105.200.1
PING 10.105.200.1 (10.105.200.1): 56 data bytes
64 bytes from 10.105.200.1: seq=0 ttl=64 time=2.729 ms
64 bytes from 10.105.200.1: seq=1 ttl=64 time=1.951 ms
64 bytes from 10.105.200.1: seq=2 ttl=64 time=2.491 ms
64 bytes from 10.105.200.1: seq=3 ttl=64 time=1.572 ms

--- 10.105.200.1 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 1.572/2.185/2.729 ms
root@varkey:~# mtr -w 192.168.149.78
Start: 2020-03-11T12:59:06+0530
HOST: varkey         Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 10.104.92.1     0.0%    10   11.9   3.0   1.4  11.9   3.2
  2.|-- 172.16.103.246  0.0%    10    2.1   2.2   1.7   2.7   0.3
  3.|-- ???            100.0    10    0.0   0.0   0.0   0.0   0.0
  4.|-- ???            100.0    10    0.0   0.0   0.0   0.0   0.0
  5.|-- 192.168.149.78  0.0%    10   48.7  48.9  48.3  49.5   0.4
root@varkey:~# mtr -w 192.168.149.78
Start: 2020-03-11T13:00:32+0530
HOST: varkey         Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 10.104.92.1     0.0%    10    6.1   2.9   1.4   6.1   1.6
  2.|-- 172.16.103.246  0.0%    10    2.2   2.1   1.7   2.6   0.3
  3.|-- ???            100.0    10    0.0   0.0   0.0   0.0   0.0
  4.|-- ???            100.0    10    0.0   0.0   0.0   0.0   0.0
  5.|-- 192.168.149.78  0.0%    10   48.6  48.9  48.5  49.4   0.3
root@varkey:~#
 
Upvote 0
Nope; Can't ping that either.
I'm checking with the BSNL guy in case I messed up the server IPs etc (but probably not as I was somewhat paranoid about noting down the existing conf and taking a copy of lastgood.xml)

In between the ONT seems to have updated its firmware spontaneusly so it now needs a stronger password (with special characters and upper case etc) and a Captcha on the login screen...go figure
 
Upvote 0
Some progress: I managed to put the ONT into bridge mode for the Internet WAN, with PPPoE being handled by the Edgerouter ER-X.
The Internet WAN is bound to LAN2 on the ONT which plugs into eth0 on the ER-X. The ER-X is on the 192.168.2.XXX subnet. With this
setup Internet access works (I can plug a laptop into the ER-X and have it go out to the Internet).

I can also create a virtual interface eth0.1380 for the Voice WAN, assigned the static IP that BSNL assigned (on 10.116.174...)
I can ping this IP when I'm on 192.168.2.XXX. I still can't ping the Voice WAN gateway though, so something is still off...

@varkey:
If the Voice assigned static IP from BSNL is 10.116.174.YYY, gateway 10.116.174.1 and netmask of 255.255.254.0 does anything look off?
The SIP server is on 10.187.5.ZZZ...I can't ping either the Gateway or the SIP server...
 
Upvote 0
Okay, so I've got the routing working, and can now reach the Voice gateway and SIP Server from any machine on the internal 192.168.X.1/24 network. Now for the actual calling bit; anyone has config advice for siproxd for the following target setup?

1. Router say on 192.168.2.1, doing dual WAN-ing and with one interface (not one of the dual WANs) given the voice static IP and set up to route to the SIP server via the assigned voice gateway
1. Running siproxd on a machine with say 192.168.2.2
2. Want to use a softphone or SIP client on another machine, say 192.168.2.X (not necessarily the same one as the siproxd box so X != 2 necessarily)

(I've verified that calling works when I plug in a machine to the voice-bound port on the bridged ONT, and give it the static IP/gateway etc from BSNL...)
 
Upvote 0
Back