Not a very usefull picture ... You could at least have enlarged the column widths so that the statistics could be read. Too many "...". How am I to see what ratio of dropped packets you have when half of the number is hidden? You went through all of that trouble, and didn't spend the last 5 seconds to post a usefull picture.
Please don't be so mean to me. I though it was use full info since the picture was only to show you that I have dropped packets.Not a very usefull picture ... You could at least have enlarged the column widths so that the statistics could be read. Too many "...". How am I to see what ratio of dropped packets you have when half of the number is hidden? You went through all of that trouble, and didn't spend the last 5 seconds to post a usefull picture.
You also did not show a print out of parent queue "BR-WIFI", or "ether1-WAN1". And you also did not mention if you have any other QOS enabled, or higher priority traffic in other queues, what types of WAN internet lines you have (fiber, dsl, cable), if they are dedicated/guaranteed or can vary ... All very usefull information that is missing, and that could have been included in less time than it is taking me to respond ...
Reread @checito's request ... Had you posted what he asked for, maybe we could help you.
Based on the few details that have been correctly communicated, try increasing queue size, default-small leads to a lot of dropped packets, especially with high latency internet lines.
/ip firewall mangle add action=mark-connection chain=forward dst-address-list=Voip_Network \ new-connection-mark=RTP-CON passthrough=yes protocol=udp add action=mark-packet chain=forward connection-mark=RTP-CON dst-address-list="" \ new-packet-mark=RTP-VOIP passthrough=yes add action=mark-connection chain=forward connection-state=new dst-address-list=\ Voip_Network new-connection-mark=SIP-CON passthrough=yes protocol=tcp add action=mark-packet chain=forward connection-mark=SIP-CON dst-address-list="" \ new-packet-mark=SIP-VOIP passthrough=yes add action=change-dscp chain=postrouting new-dscp=46 out-interface=BR-WIFI \ passthrough=yes src-address-list=Voip_Network
/queue tree add max-limit=45M name=Upload parent=ether1-WAN1 add max-limit=250M name=Download parent=BR-WIFI add bucket-size=0.01 limit-at=10M max-limit=10M name=D_RTP-Voip packet-mark=RTP-VOIP \ parent=Download priority=1 add bucket-size=0.01 limit-at=10M max-limit=10M name=U_RTP-Voip packet-mark=RTP-VOIP \ parent=Upload priority=1 add bucket-size=0.05 limit-at=10M max-limit=10M name=D_SIP-Voip packet-mark=SIP-VOIP \ parent=Download priority=2 queue=synchronous-default add bucket-size=0.05 limit-at=10M max-limit=10M name=U_SIP-Voip packet-mark=SIP-VOIP \ parent=Upload priority=2 queue=synchronous-default add limit-at=225M max-limit=225M name=D_no-mark packet-mark=no-mark parent=Download add limit-at=30M max-limit=30M name=U_no-mark packet-mark=no-mark parent=Upload
@ checito is referring to Queue size. I also mentioned this in my last post. In winbox look at "Queue Types" tab under Queues menu item. Also read:50 to 5000 , are you talking about bucket size?
Queue size is the maximum number of packets that the queue can have. IT IS NOT the packet size. Packets that come into the queue in excess of the queue size get dropped, and therefore do not consume any more cpu resources, and do not add more to latency. You should give high priority (low priority value, like 1 or 2) to voip queues so that they get processed more quickly and therefore do not get very long, and choose the lowest queue size that results in very few dropped packets. You should give lower priority to non-voip traffic, and a much lower queue size. That way, when there is a lot of non-voip traffic, the non-voip packets get dropped, and need to be re-transmitted, thereby not clogging up the queue processing.I though that smaller pkts help voip for low jitter and less delay. Ill give it a try and post results here.