RSVP
policy. The TOS byte is an OSI model Layer 3 solution, and works on IP packets on the LAN and possibly the WAN, depending upon the service provider.
Table 55: Original TOS specification
Bit | Value | Use |
description |
|
|
|
|
|
| 000 | Routine |
Bits | 001 | Priority |
010 | Immediate | |
precedence | 011 | Flash |
100 | Flash Override | |
| 101 | CRITIC/ECP |
| 110 | Internetwork control |
| 111 | Network control |
|
|
|
Bit 3 | 0 | Normal |
delay | 1 | Low |
Bit 4 | 0 | Normal |
Throughput | 1 | High |
|
|
|
Bit 5 | 0 | Normal |
reliability | 1 | High |
Bit 6 | 0 | Normal |
monetary cost | 1 | Low |
|
|
|
Bit 7 |
| Always set to 0 |
reserved |
|
|
|
|
|
RSVP
Resource Reservation Protocol (RSVP) is a protocol that hosts can use to request specific QoS parameters through the network for a particular application data stream. A host can request guaranteed service through a network. If all routers have RSVP support enabled, and if there exists sufficient unreserved bandwidth, a reservation is established throughout the network. If insufficient bandwidth exists, the reservation fails and notifies the hosts. At that point, hosts can choose to send traffic without a reservation, or drop the connection.
RSVP is supported in Communication Manager beginning with Release 1.3. RSVP can be enabled per network region on the network region form. If RSVP is enabled, endpoints including IP Telephones and media processors attempt to establish a reservation for each call. If the reservation fails, Avaya endpoints still try to place a call, but lower the DiffServ priority of the call
