PPPoE and VoIP via trunk WAN

Technical Support for Routers
1

I'm planning to purchase the Flint 2 GL-MT6000 and have a few technical questions before I go ahead.

My ISP's Fiber ONU router provides both VoIP and Internet connections via VLANs. The ONU can be bridged, requiring the router to handle the VLANs for these services. The ISP has been kind enough to provide me the VLAN IDs for both the VoIP service (including a static IP to their SIP server) and the Internet (including a PPPoE username and password).

So my questions are:

  1. Can the WAN port be configured to use a VLAN for the PPPoE connection?
  2. Using the WAN port can I also setup a static route to VOIP vlan ID for the ISP's SIP server?
2

That sounds like a case for you @LupusE :smile:

3

In general, yes. OpenWrt should provide all the needed option. But as far as I know it is not easily to configure through a wizard.
The VLAN is at a lower level as the PPPoE. This are two different configurations.

This is just a recap out of my mind. I have no chance to check it right now.

You need to configure the device first, then attach it to the VLAN

config device
    option name 'wanif'

config interface 'wan'
    option device 'wanif.100' #for VLAN 100
    option proto 'pppoe'
    option username 'username'
    option password 'very secret'
    option ipv6 'auto'

Now you should be able to use the router at your providers account.
A good starting point for some providers is always [OpenWrt Wiki] ISP Configurations

The SIP part is a little harder. Because no GL.iNet router got DECT, I still let this on my Fritz!Box. But maybe the former mentioned page already answers all your question.

4

Thank you for the PPPoE solution.

The SIP part is a little harder. Because no GL.iNet router got DECT, I still let this on my Fritz!Box. But maybe the former mentioned page already answers all your question.

I have a VOIP cordless phone with me therefore I donot require any FXS port on the router. The VOIP phone will connect to the ISP SIP server. What I want to achieve is as soon as the router sees someone sending packets destined to a specific IP address (ISP SIP server), it should redirect all packets onto the VoIP VLAN. Obviously this IP is out of range for the LAN DHCP. Is this setup possible? Also, note in my case there is no DNS for the SIP server sitting on the VOIP VLAN, it's all IP to IP comm.

If the above situation is possible, then configuring IPTV will also be dead simple.

5

Just went through the link you provided, I believe something could be achieved using static routing. Might just order the router to get my hands dirty.

Thank you!

6

VoIP should work directly out of the box. Does your ISP allow SIP to register from anywhere? In that case, your phone just needs to be inside the VoIP VLAN (which has access to the internet, I guess?) and do a SIP registration.

7

I see your point. My planning of topology is kinda different.

LAN DHCP should just be VLAN less. Anyone requesting the SIP server should smoothly get rerouted to ISP's SIP VLAN and establish a connection. There should no need for the client to be on a different local VLAN to access the ISP SIP VLAN.

Say, router's LAN DHCP is 192.168.1.0/24

A local PC (192.168.1.5/31) wants example.com, fetch DNS and IP via PPPoE (WAN VLAN 10)

A local VOIP Phone (192.168.1.10/31) wants 10.1.50.50 which is ISP SIP server, directly get out using WAN VLAN 50 and establish connection

8

You could create a bridge. To redirect the phones port to the ISP assigned VOIP VLAN. And configure some tweaks, if necessary.

9

I don't really see how this should work. SIP itself will be used for registration and call signaling only.
After SIP is done, RTP will transfer the voice data itself - and this could be even a point-to-point connection, depending on who is calling.

So rerouting isn't possible, it need to be a fixed route - I would say.

10

Pppoe also has a nice wizard now in the gl ui :wink:

As for sip, usually it's via lan like other already said, but if for some reason it becomes to difficult there are also voip stations.

But there are also very specific sip setups which are rare, they require a different vlan as dhcp client, and you need siproxd and kinda have to build a very similar setup as how some iptv setups are setup.

I have used N300A in the past, but i guess there are more moderner solutions and compatible with your voip brands, for me it was a outcome because it turned the rj45 jacket into a rj11.

11

Okay, I'd even supports VLAN ID. I was not sure about this one. See: Ethernet - GL.iNet Router Docs 4

You are talking about VoIP via sip provider. Give inet via DHCP, enter credentials at SIP endpoint, everything is okay.
But if the ISP provider also delivers VOIP, and decide to split it to the same (already authenticated) port with a different VLAN, there will be no credentials. The router needs to redirect the VoIP endpoint, or forward everything (untagged port) and let the endpoint device do the VLAN crap.

Every szenario needs more details.

2 Likes
12

Great to see PPPoE via VLAN is native in firmware.

Here's my current setup VoIP setup on Mikrotik, that works well.

image
image1323×800 44.5 KB

  1. Create a new VLAN interface tagged with VLAN ID from the SFP Port (ISP bridged router)
  2. Assign an address (given by ISP) to the VLAN interface
  3. Setup static route to their VoIP infrastructure (given by ISP, use blanket CIDR because media and SIP servers are on different subnets)
  4. On a VOIP phone use the SIP server's IP address, login ID and password
  5. VOIP trunk gets registered, SIP handles tcp signaling while media servers handle udp voice

Now, I've to find a way to translate step 1 to step 3 in openwrt parlance.

13

Step 1 to 2,5 should be done by the GL.iNet interface. So I ternet is up and running fast
For the SIP configuration maybe some testing is needed.
At the moment I'm on the road, tomorrow I will have a look, when I am at a full featured laptop.