Hi

I am setting up QOS allocation for our SIPP service.

For WAN1 (ADSL to Zen internet) I want to set values to 85% or less of the given ADSL connection values (as per your manual).

I cannot set the values, they are pre-filled by the router.

Unfortunately the router is using the exact 100% value of the connection as seen in the online status / physical connection page - pasted below

The values in LAN1 QOS settings is 7808.00Kbps/960.00Kbps, which is too high, but self set and not changeable.

Is this a mistake? Is there a workaround. I have read that if you use 100% values then QOS is unworkable.

Thanks - Nathan

ADSL Information ( ADSL Firmware Version: 2471201_A)
ATM Statistics TX Cells RX Cells TX CRC errs RX CRC errs
9429111 16138173 0 870
ADSL Status Mode State Up Speed Down Speed SNR Margin Loop Att.
G.DMT SHOWTIME 960000 7808000 11 39

I have now been informed that these boxes show the ADSL rate
The router uses 80% of this value.

To see / set what percentage is used you can use the telnet commands as shown below in the reply from tech support

Sorry, I forgot to mention that QoS rate for inbound/outbound traffic is already set to 80 or 85% on router for wan1(ADSL).If you want to check the status or reduce the percentage then run the following telnet command.

adsl txpct ?(outbound)
adsl rxpct ? (inbound)

Please also run 'adsl reboot' to apply the settings.

I now have a different problem. The QOS rule never matches any traffic. Its always in "others" under status.

It doesnt matter how I set the match. One port, small port range, huge port range, any IP, or single IP(with full port range) it never matches anything.

I've read it might be the firmware 3.3.7.1 which has a bug.

I am considering going back to 3.3.6.1 as this has been found to help
http://www.forum.draytek.co.uk/posting.php?mode=reply&f=18&t=17651

Is this a known bug?

OK this firmware 3.6.3_RC4a

the built in feature for QOS on SIPP/VOIP matches and the graph shows a result when a call is being made.

My rules still dont match anything (not even the catch all tester!), but that could be configuration.

The result is my VOIP is now QOS prioritised so I can leave it here - job done

There is a throughput effect on other streams when enabling QOS - with or without a call in progress

With QOS
21/09/12 08:18:23
Speed Down 3876.38 Kbps ( 3.8 Mbps )
Speed Up 418.16 Kbps ( 0.4 Mbps )
Port 8095
Server speedtest2.thinkbroadband.com

QOS disabled (VIOP QOS still turned on)

Speed Test Results
Date 21/09/12 08:20:15
Speed Down 5857.37 Kbps ( 5.7 Mbps )
Speed Up 789.47 Kbps ( 0.8 Mbps )
Port 8095
Server speedtest2.thinkbroadband.com

All QOS turned off
Date 21/09/12 08:21:23
Speed Down 5671.40 Kbps ( 5.5 Mbps )
Speed Up 788.14 Kbps ( 0.8 Mbps )
Port 8095
Server speedtest2.thinkbroadband.com



Results using the VOIP QOS has no effect on overall throughput. However my QOS setup does impact throughput. It could be because I have catchall rules in place across wide port ranges and IP ranges.