Unspecified traffic prioritisation

[#1]

Does anyone else use Mumble for internet voice communications?  Mumble is a lightweight alternative to Ventrillo and Teamspeak, which is very low latency and therefore ideal for interactive multi-speaker comms.
Over the past couple of weeks I've noticed that whereas during the day, it work brilliantly, during the evening speech becomes very robotic, metallic and broken - at times making it unusable.
I decided to take a quick look at the data packets on WireShark, and it seems that Mumble VOIP data is being given an unlisted service field identifier - 0xe0; I have no idea how this would be prioritised through the Plusnet network.  Isn't all VOIP traiffic supposed to be the highest priority i.e 0xa0?
What is 0xe0?  Is this likely to be the cause of the speech problems and, if so, how do I go about getting it fixed?
Thanks in advance,  Neil

[#2]

I may be reading this wrong but that looks like the traffic is originating on your PC and going out to the Mumble server. You need to look at the traffic going the other direction as that's what we prioritise.
I've used Mumble a few times but I have a local server set up at home for it so the traffic isn't going far for me to test.

[#3]

Thanks for the quick reply Chris.
That SIr, was a complete fail on my part    You are 100% correct, I looked at the outgoing packets!!!
Ok, so here's the correct snapshot - and it's not an unlisted type, it looks like it's being classified as Silver, which I believe is wrong and could well account for the poor performance I get during the evening.
I'm assuming that mumble packets are not being correctly identified by your traffic prioritisation since it is a relatively new protocol, and only just beginning to gain widespread usage.

[#4]

Hi webwisehost,
If you raise a ticket with the wireshark capture and an explanation of what the issue is I'll get it passed to our networks department to sort out for you. Give me a shout when you've done it.
Jojo

[#5]

Hmmm.
I've raised the ticket, but I get an error trying to attach the wireshark capture :

Quote

There's a problem with the file you're trying to attach. You can only upload images, text files, pdfs and spreadsheets. Please try again with a different type of file.

It seems your ticket system won't accept the filetype.

[#6]

Try uploading it again without any spaces in the file name, that should do it

[#7]

Or try renaming it as a .pcap.txt file

[#8]

There were no spaces, only underscores, which are allowed.
I removed those, and it still gives an error.  See screenies.
I'll try changing the filetype...

[#9]

OK, if FINALLY worked, after the 7th time of retyping the ticket 
.txt doesn't work ether.
I had to retype the file as a PDF to get it accepted.  Surely the system should accept .pcap filetypes if you're going to ask for those to be submitted!!!!

[#10]

Sorry you had so much trouble uploading that. I'll get it picked up now for you

[#11]

Hi Jojo,
I've just seen your note about the file not having got attached to my ticket, so I'm trying to attach it here to see if that works.

[#12]

Can you read the Personal Message I sent you?

[#13]

Sorry - just noticed that after I replied on the forum.
I'm following your instruction in the PM right now.

[#14]

Make sure you put it back to a pcap

[#15]

Thanks, I've attached that now