Comparison Of Ip Precedence And Diffserv Values - NEC Univerge SV9100 Manual

Issue 2.0
User Datagram Protocol, Src Port: 10020 (10020), Dst Port: 10022
(10022)
Real-Time Transport Protocol
7.6
SV9100 Networking Manual
Figure 5-9 Ethernet Frame Example - Containing one RTP (Speech) Packet (Continued)
Total Length: 44
Identification: 0x0069 (105)
Flags: 0x00
0... = Reserved bit: Not set
.0.. = Don't fragment: Not set
..0. = More fragments: Not set
Fragment offset: 0
Time to live: 30
Protocol: UDP (0x11)
Header checksum: 0x431e (correct)
Source: 172.16.0.21 (172.16.0.21)
Destination: 172.16.0.101 (172.16.0.101)
Source port: 10020 (10020)
Destination port: 10022 (10022)
Length: 24
Checksum: 0x5293 (correct)
Stream setup by SDP (frame 112)
Setup frame: 112
Setup Method: SDP
10.. .... = Version: RFC 1889 Version (2)
..1. .... = Padding: True
...0 .... = Extension: False
.... 0000 = Contributing source identifiers count: 0
0... .... = Marker: False
.001 0010 = Payload type: ITU-T G.729 (18)
Sequence number: 30885
Timestamp: 20560
Synchronization Source identifier: 732771006
Payload: 3ED0
Padding data: 00
Padding count: 2

Comparison of IP Precedence and Diffserv Values

As stated earlier, IP Precedence and Diffserv use the same 8-bit ToS field in the
IP header to mark packets. It is possible to have the same ToS value for either
method which means that the two methods can work alongside each other.
For example, if the VoIP equipment supports IP Precedence and the router can
prioritize only using the DSCP they can be set to the same value. Refer to
5-3 IP Precedence and Diffserv Values Comparison
Table
for the values.
5-25