Not 100% sure exactly what you're asking. limit-at is the guaranteed bandwidth. max-limit is the max bandwidth allowed, as long as it is available. So a connection can use up to max-limit, but during congestion periods is guaranteed no less than limit-at. (This is assuming you did your sums right and didn't oversubscribe your available bandwidth when you set up these numbers.)
Assuming the 18/1 figure is for your interface, the sums you have to do is to make sure that data limit-at times number of data connections, plus VOIP limit-at times number of VOIP connections, does not exceed 1M (assuming I have the traffic directions correct). That is not many connections. You can't run more than two VOIP sessions without reducing your data limit-at to 256 or lower. > On Nov 5, 2017, at 10:22 AM, Gabriel Rincon via Mikrotik-users > <[email protected]> wrote: > > Good morning. > > Is it a better practice to configure "limit at" and "max-limit". The queues > that handle the VoIP traffic (marked with mangle rules" or to restrict the > data queue to a certain bandidth as mount? > > For example diwnliad is 18M and upload is 1M > voip-queue_out. Max-limit 512k. Limit at 256k > > Or > > Data-queue_out. Max-limit 768k. Limit-at 512k > > > Is there a better way to guarantee bandwidth to guarantee VoIP gets a piece > of the upload and download bandwidth? > > Thanks, > > Gabriel E. Rincon > Mobius Internet, IT & Communications > 225'490-5600 > > _______________________________________________ > Mikrotik-users mailing list > [email protected] > http://lists.wispa.org/mailman/listinfo/mikrotik-users -- Grand Avenue Broadband -- Wireless Internet Service Circle City to Wickenburg and surrounding areas http://grandavebb.com
_______________________________________________ Mikrotik-users mailing list [email protected] http://lists.wispa.org/mailman/listinfo/mikrotik-users
