I have an issue on how can i implement some queues in order to make the voip work correctly
The setup is like this:
We have a main office with a 3Com NBX (unfortunately for me cause i was forced to use EOIP in order to make it work for ppl using connections from home)
All the employees who work from home have a mikrotik 750G router which has a pptp connection to the main office and a EOIP tunnel over that pptp for their 3com phones to work with all the features
All the home routers are configured like this: ether1 - public ether 2 master port , ether 3 and 4 lan slave for ether 2, ether 5 is in the same bridge with the Eoip tunnel
The lan subnet is 192.168.0.0/24 and the voip subnet is 10.1.1.0/24 10.1.1.254 is the NBX at the main office and the rest of the ip addresses are assigned to the phones.
I have read all the examples i could find for qos/Traffic prioritization, but still i have no clue on how could i configure raffic prioritization for the home routers so that the ether 5 traffic gets prioritized over all the other traffic.
I don’t know where the rules should be placed… on the pptp interface as the out interface, on the bridge interface, on the eoip interface, etc
If anyone knows how to set me up on the right track please let me know.
The only traffic going through the pptp is the Eoip traffic for the NBX. Nothing else. The rest is the home use internet of the employees for which i don’t care. The internet line is ether1 on all routers.
Should be vaguely doable. Here are your challenges, and some thoughts on it all:
You can take two approaches: dynamically reserve bandwidth for the VoIP traffic on the WAN interface but allow the rest of the interfaces to consume all WAN bandwidth when there isn’t any VoIP traffic present, or statically and always rate limit all other interfaces to a traffic rate that leaves enough WAN bandwidth for the VoIP traffic. That ensures there is always enough room for VoIP, but when there isn’t any VoIP traffic, that bandwidth goes unused.
The problem with dynamically reserving bandwidth is that you have to make your queues on the WAN interface. RouterOS has no provisions for transferring the priority of packets that are being encapsulated to the carrier protocol, so any marks of packets coming into ether5 are going to be lost leaving through the WAN interface as by that time they are wrapped first in EoIP and then in PPTP. However, you can just mark all PPTP traffic as priority. That would break once your users establish other PPTP tunnels, of course. I don’t know how like that scenario is.
The problem with rate limiting all other traffic to always reserve bandwidth for VoIP is that you can’t use nice, clean interface queues as they only see packets leaving through that interface. You need to rate limit as traffic enters the router, so you’ll need to use the slightly messier global queues.
Also be aware that there isn’t much you can do about QoS coming into the router from the WAN. Once the packets are at that interface it’s already too late, and the ISP may have already thrown away VoIP/EoIP/PPTP packets because of contention. There’s no way of getting those back. QoS in the DiffServ model fundamentally only works well if all nodes that the traffic traverses participate according to the same QoS policy.