The figure below shows a sample solution in which application ID support is used. In this example, bandwidth is allocated
between the voice and video sessions that are being created by Cisco Unified Communications Manager (CUCM). Video requires
much more bandwidth than voice, and if you do not separate the reservations, the video traffic could overwhelm the voice traffic.
CUCM uses the RSVP Application ID Support feature. In this example, when CUCM makes the RSVP reservation, CUCM can specify
whether the reservation should be made against a video RSVP bandwidth pool or a voice RSVP bandwidth pool. If not enough bandwidth
remains in the requested pool, even though there is enough bandwidth in the total RSVP allocation, RSVP signals CUCM that
there is a problem with the reservation. The figure below shows some of the signaling and data traffic that is sent during
the session setup.
IMAGE MISSING; embedded not referenced
In this scenario, the IP phones and IP video devices do not directly support RSVP. In order to allow RSVP to reserve the
bandwidth for these devices, the RSVP agent component in the Cisco IOS router creates the reservation. While setting up the
voice or video session, CUCM communicates with the RSVP agent and sends the parameters to reserve the necessary bandwidth.
When you want to make a voice or video call, the device signals CUCM. CUCM signals the RSVP agent, specifying the RSVP application
ID that corresponds to the type of call, which is voice or video in this example. The RSVP agents establish the RSVP reservation
across the network and communicate to CUCM that the reservation has been made. CUCM then completes the session establishment,
and the Real-Time Transport Protocol (RTP) traffic streams flow between the phones (or video devices). If the RSVP agents
are unable to create the bandwidth reservations for the requested application ID, they communicate that information back to
CUCM, which signals this information back to you.