Quote:
|
Originally Posted by dkounal All RTP packets leaving my asterisk box for broadvoice had the flag TOS set to 0x10. The same when using my Internet provider's voip service.
The difference was in the packets coming to my asterisk box.
Broadvoice's RTP packets had flag TOS set to 0x00 but my Internet provider's RTP traffic had TOS set to 0x10.
I tried the same thing with two other providers but for all packets from broadvoice had TOS set to 0x00. |
Well it leaves your Asterisk box fine but it never gets to anyone with the tos either way!!
All respective ISP's have there clients on
untrusted ports (except if you pay them to trust you)
The QoS and tos is only for your own network or the network(s) that you control. This is by choice of-course but think what will happen if I was a spammer and I marked all my emails with a tos 0x10 or my uploads or when I play an online game I setup my firewall/router to mark the packets with a tos 0x10. Simple I'll eat up all the bandwidth of the ISP and you will not even able to place a call. :cry:
So it is not BroadVoice miss-configuration and not yours. You can have your Asterisk to contact a friend of yours that runs ethereal and see your packets getting to him. They will not have the tos. If they do have it then it is just ignored on the ISP and everyone in the middle.
Most ISP's to cut costs use strange routing. You can simple do a trace route and see after how many hops you get to the BroadVoice, or to see which router has the problem and delays your traffic. If you get to BroadVoice with more than 17 hops then change ISP.
Ποιό ISP έχεις;
[/b]