Low upload bandwidth (Audio Bw Tx) and Bufferbloat advice please

[raychew]

I thought FTTN uses fiber optics, not copper wires as in the old telco technology. Check to see if either of you is using DSL (internet through copper telco pairs). JK doesn't work that well (high latency) via DSL.

Funny - here in Canada it appears that DSL works better than cable!

"Funny - here in Canada it appears that DSL works better than cable!"

>>>
That is my experience as well here in NL.
I found there to be significantly more 'jitter' on cable (COAX/TV) connections as opposed to copper or fiber.
So speeds and stability are not the issue on cable but there seems to be more 'noise' (jitter). I've stopped investigating since we're being hooked up to fibre/fiber (glass) any day now (and can't wait ;-))

That’s good info. But sad. Here in Australia if you are in an area where cable exists, fibre will never be rolled out. Very sad. I wonder if trying a new router might help? My current router doesn’t have QOS

>>>
In the early days of this mass use of Jamkazam, QOS was seen as a bad thing for Jamkazam. Not sure where the community stands nowadays on the issue.
With cable a newish modem/router, dedicated IPv4, PF and making sure there's not much (read nothing) else happening on your LAN (WiFi!) and WAN connection while using Jamkazam, seem to be most one can do.
I'm doing pretty good on cable atm (sub 20ms with band members) but jitter and jitter que do vary and can mess things up.

QOS isn't really possible over the Internet, at least not now; maybe never. QOS works by marking the every data packet with priority information. This marking has to be respected across all routers from all ISP's on the Internet. This is where the problem lies. All ISP's would have to agree on a standard which is unlikely to happen. QOS can work in an enterprise network where traffic can be controlled end to end. 

Here is a good article that provides more detail...

https://www.nojitter.com/qos-becoming-irrelevant

/rc