QoS for VOIP in Mikrotik - Historie editací

Dulik v 21. 5. 2009, 23:14

2009-05-21T23:14:06Z

← Starší verze		Verze z 21. 5. 2009, 23:14
Řádek 17:		Řádek 17:

	/ip firewall mangle		/ip firewall mangle
	add chain=prerouting dscp=~~104~~ action=mark-packet new-packet-mark=voip-sip passthrough=yes		add chain=prerouting dscp=26 action=mark-packet new-packet-mark=voip-sip passthrough=yes
	add chain=prerouting dscp=~~184~~ action=mark-packet new-packet-mark=voip-rtp passthrough=yes		add chain=prerouting dscp=46 action=mark-packet new-packet-mark=voip-rtp passthrough=yes

Dulik v 21. 5. 2009, 23:12

2009-05-21T23:12:51Z

← Starší verze		Verze z 21. 5. 2009, 23:12
Řádek 7:		Řádek 7:

	If your central internet gateway router handles/restores the DSCP-marked packets correctly (see the [[HTB]] script that we use on our gateway), then implementing QoS for VOIP packets at your Mikrotik routers is easy - see the following script:		If your central internet gateway router handles/restores the DSCP-marked packets correctly (see the [[HTB]] script that we use on our gateway), then implementing QoS for VOIP packets at your Mikrotik routers is easy - see the following script:

			Mikrotik 2.9:

	/ip firewall mangle		/ip firewall mangle
	add chain=prerouting tos=104 action=mark-packet new-packet-mark=voip-sip passthrough=yes		add chain=prerouting tos=104 action=mark-packet new-packet-mark=voip-sip passthrough=yes
	add chain=prerouting tos=184 action=mark-packet new-packet-mark=voip-rtp passthrough=yes		add chain=prerouting tos=184 action=mark-packet new-packet-mark=voip-rtp passthrough=yes

			Mikrotik 3:

			/ip firewall mangle
			add chain=prerouting dscp=104 action=mark-packet new-packet-mark=voip-sip passthrough=yes
			add chain=prerouting dscp=184 action=mark-packet new-packet-mark=voip-rtp passthrough=yes


	If your central router does NOT restore the DSCP marks for packet incoming from the VOIP providers (and the providers do not mark packets with DSCP), you must implement the same things as in the [[HTB]] script - mark connection, then mark unmarked packets with the connection mark and use the packet marks in the queues (note that Mikrotik 2.9.x can't use connection mark in queue rules)		If your central router does NOT restore the DSCP marks for packet incoming from the VOIP providers (and the providers do not mark packets with DSCP), you must implement the same things as in the [[HTB]] script - mark connection, then mark unmarked packets with the connection mark and use the packet marks in the queues (note that Mikrotik 2.9.x can't use connection mark in queue rules)

10.143.51.4 v 11. 12. 2007, 17:21

2007-12-11T17:21:41Z

← Starší verze		Verze z 11. 12. 2007, 17:21
Řádek 17:		Řádek 17:

	/queue simple		/queue simple
	name="VOIP-SIP" interface=all packet-marks=voip-sip priority=1		add name="VOIP-SIP" interface=all packet-marks=voip-sip priority=1
	name="VOIP-RTP" interface=all packet-marks=voip-rtp priority=0		add name="VOIP-RTP" interface=all packet-marks=voip-rtp priority=1

	Note that:		Note that:

Dulik v 24. 11. 2007, 08:13

2007-11-24T08:13:17Z

← Starší verze		Verze z 24. 11. 2007, 08:13
Řádek 12:		Řádek 12:
	add chain=prerouting tos=184 action=mark-packet new-packet-mark=voip-rtp passthrough=yes		add chain=prerouting tos=184 action=mark-packet new-packet-mark=voip-rtp passthrough=yes

	~~Alternatively, if~~ your central router does ~~not~~ restore the DSCP marks, you ~~should~~ mark ~~connections~~, ~~not~~ packets:		If your central router does NOT restore the DSCP marks for packet incoming from the VOIP providers (and the providers do not mark packets with DSCP), you must implement the same things as in the [[HTB]] script - mark connection, then mark unmarked packets with the connection mark and use the packet marks in the queues (note that Mikrotik 2.9.x can't use connection mark in queue rules)

	~~add chain=prerouting tos=104 action=mark-connection new-~~connection-mark~~=voip-sip passthrough=yes~~
	~~add chain=prerouting tos=184 action=mark-~~connection ~~new-connection-~~mark~~=voip-rtp passthrough=yes~~

	Finally, the queues:		Finally, the queues:

Dulik v 24. 11. 2007, 07:58

2007-11-24T07:58:01Z

← Starší verze		Verze z 24. 11. 2007, 07:58
Řádek 11:		Řádek 11:
	add chain=prerouting tos=104 action=mark-packet new-packet-mark=voip-sip passthrough=yes		add chain=prerouting tos=104 action=mark-packet new-packet-mark=voip-sip passthrough=yes
	add chain=prerouting tos=184 action=mark-packet new-packet-mark=voip-rtp passthrough=yes		add chain=prerouting tos=184 action=mark-packet new-packet-mark=voip-rtp passthrough=yes

			Alternatively, if your central router does not restore the DSCP marks, you should mark connections, not packets:

			add chain=prerouting tos=104 action=mark-connection new-connection-mark=voip-sip passthrough=yes
			add chain=prerouting tos=184 action=mark-connection new-connection-mark=voip-rtp passthrough=yes

			Finally, the queues:

	/queue simple		/queue simple
Řádek 16:		Řádek 23:
	name="VOIP-RTP" interface=all packet-marks=voip-rtp priority=0		name="VOIP-RTP" interface=all packet-marks=voip-rtp priority=0

	Note that the default pfifo queueing discipline~~, used on ethernet interfaces in Linux and Mikrotik,~~ prioritize the DSCP marks automatically, so theoretically, if the central internet gateway restores the DSCP marks on incoming packets from VOIP providers, everything could work OK even without any QoS settings on the router.		Note that:
			* only one queue is necessary if you have DSCP marks on packets in both directions (DSCP marks for incoming packets can be restored on the central internet gateway - see the [[HTB]] script). The reason for one queue is that
			* the default '''pfifo''' queueing discipline prioritize the DSCP marks automatically, so theoretically, if the central internet gateway restores the DSCP marks on incoming packets from VOIP providers, everything could work OK even without any QoS settings on the router. The pfifo is defaultly used on HTB leafs and also on ethernet interfaces in Linux and Mikrotik which do not have any qdisc assigned.

	But if you already do some QoS (e.g. using HTB in Linux or "queues" on Mikrotik)on your routers, you should add also these 2 queues dedicated to VOIP.		But if you already do some QoS (e.g. using HTB in Linux or "queues" on Mikrotik)on your routers, you should add also these 2 queues dedicated to VOIP.

Dulik v 23. 11. 2007, 08:43

2007-11-23T08:43:22Z

← Starší verze		Verze z 23. 11. 2007, 08:43
Řádek 6:		Řádek 6:
	These are the default values for SPA-XXXX VOIP gateways, but also SW clients should be able to make these settings. E.g., in XLite, just divide these values by 4 (DSCP for SIP=26, for RTP=46)		These are the default values for SPA-XXXX VOIP gateways, but also SW clients should be able to make these settings. E.g., in XLite, just divide these values by 4 (DSCP for SIP=26, for RTP=46)

	If your central internet gateway router handles/restores the DSCP-marked packets correctly, then implementing QoS for VOIP packets at your Mikrotik routers is easy - see the following script:		If your central internet gateway router handles/restores the DSCP-marked packets correctly (see the [[HTB]] script that we use on our gateway), then implementing QoS for VOIP packets at your Mikrotik routers is easy - see the following script:

	/ip firewall mangle		/ip firewall mangle

Dulik v 23. 11. 2007, 08:41

2007-11-23T08:41:07Z

← Starší verze		Verze z 23. 11. 2007, 08:41
Řádek 1:		Řádek 1:
	Prerequisities:		Prerequisities:
	Your VOIP SW/HW can set the DSCP/TOS field in the IP packet in such a way that:		Your VOIP SW/HW client can set the DSCP/TOS field in the IP packet in such a way that:
	*SIP signaling messages will be marked by DSCP=0x68 (=104)		*SIP signaling messages will be marked by DSCP=0x68 (=104)
	*RTP voice audio data will be marked by DSCP=0xB8 (=184)		*RTP voice audio data will be marked by DSCP=0xB8 (=184)

Dulik: Nová stránka: Prerequisities: Your VOIP SW/HW can set the DSCP/TOS field in the IP packet in such a way that: SIP signaling messages will be marked by DSCP=0x68 (=104) RTP voice audio data will ...

2007-11-23T08:40:45Z

Nová stránka: Prerequisities: Your VOIP SW/HW can set the DSCP/TOS field in the IP packet in such a way that: *SIP signaling messages will be marked by DSCP=0x68 (=104) *RTP voice audio data will ...

Nová stránka

Prerequisities:
Your VOIP SW/HW can set the DSCP/TOS field in the IP packet in such a way that:
*SIP signaling messages will be marked by DSCP=0x68 (=104)
*RTP voice audio data will be marked by DSCP=0xB8 (=184)

These are the default values for SPA-XXXX VOIP gateways, but also SW clients should be able to make these settings. E.g., in XLite, just divide these values by 4 (DSCP for SIP=26, for RTP=46)

If your central internet gateway router handles/restores the DSCP-marked packets correctly, then implementing QoS for VOIP packets at your Mikrotik routers is easy - see the following script:

/ip firewall mangle
add chain=prerouting tos=104 action=mark-packet new-packet-mark=voip-sip passthrough=yes
add chain=prerouting tos=184 action=mark-packet new-packet-mark=voip-rtp passthrough=yes

/queue simple
name="VOIP-SIP" interface=all packet-marks=voip-sip priority=1
name="VOIP-RTP" interface=all packet-marks=voip-rtp priority=0

Note that the default pfifo queueing discipline, used on ethernet interfaces in Linux and Mikrotik, prioritize the DSCP marks automatically, so theoretically, if the central internet gateway restores the DSCP marks on incoming packets from VOIP providers, everything could work OK even without any QoS settings on the router.

But if you already do some QoS (e.g. using HTB in Linux or "queues" on Mikrotik)on your routers, you should add also these 2 queues dedicated to VOIP.