109
1.877.877.2269
BLACKBOX.COM
NEED HELP?
LEAVE THE TECH TO US
LIVE 24/7
TECHNICAL
SUPPORT
1.877.877.2269
CHAPTER 2: CONFIGURATION
A large network may support multiple VoIP policies across the entire organization, and different policies per application type.
LLDP-MED allows multiple policies to be advertised per port, each corresponding to a different application type. Different ports
on the same Network Connectivity Device may advertise different sets of policies, based on the authenticated user identity or port
configuration.
NOTE: LLDP-MED is not intended to run on links other than between Network Connectivity Devices and Endpoints, and does not need
to advertise the multitude of network policies that frequently run on an aggregated link interior to the LAN.
Policy ID: ID for the policy. This is auto generated and will be used when selecting the polices that will be mapped to the specific ports.
Application Type: Intended use of the application types:
1. Voice - for use by dedicated IP Telephony handsets and other similar appliances supporting interactive voice services. These devices
are typically deployed on a separate VLAN for ease of deployment and enhanced security by isolation from data applications.
2. Voice Signaling (conditional) - for use in network topologies that require a different policy for the voice signaling than for the
voice media. This application type should not be advertised if all the same network policies apply as those advertised in the Voice
application policy.
3. Guest Voice - support a separate “limited feature-set” voice service for guest users and visitors with their own IP Telephony
handsets and other similar appliances supporting interactive voice services.
4. Guest Voice Signaling (conditional) - for use in network topologies that require a different policy for the guest voice signaling than for
the guest voice media. This application type should not be advertised if all the same network policies apply as those advertised in the
Guest Voice application policy.
5. Softphone Voice - for use by softphone applications on typical data centric devices, such as PCs or laptops. This class of endpoints
frequently does not support multiple VLANs, if at all, and are typically configured to use an ‘untagged’ VLAN or a single ‘tagged’ data
specific VLAN. When a network policy is defined for use with an ‘untagged’ VLAN (see Tagged flag below), then the L2 priority field is
ignored and only the DSCP value is relevant.
6. Video Conferencing - for use by dedicated Video Conferencing equipment and other similar appliances supporting real-time
interactive video/audio services.
7. Streaming Video - for use by broadcast or multicast based video content distribution and other similar applications supporting
streaming video services that require specific network policy treatment. Video applications relying on TCP with buffering would not be
an intended use of this application type.
8. Video Signaling (conditional) - for use in network topologies that require a separate policy for the video signaling than for the
video media. This application type should not be advertised if all the same network policies apply as those advertised in the Video
Conferencing application policy.
Tag: Tag indicating whether the specified application type is using a ‘tagged’ or an ‘untagged’ VLAN.
Untagged indicates that the device is using an untagged frame format and as such does not include a tag header as defined by IEEE
802.1Q-2003. In this case, both the VLAN ID and the Layer 2 priority fields are ignored and only the DSCP value is relevant.
Tagged indicates that the device is using the IEEE 802.1Q tagged frame format, and that both the VLAN ID and the Layer 2 priority
values are being used, as well as the DSCP value. The tagged format includes an additional field, known as the tag header. The tagged
frame format also includes priority tagged frames as defined by IEEE 802.1Q-2003.
VLAN ID: VLAN identifier (VID) for the port as defined in IEEE 802.1Q-2003.
L2 Priority: L2 Priority is the Layer 2 priority to be used for the specified application type. L2 Priority may specify one of eight priority
levels (0 through 7), as defined by IEEE 802.1D-2004. A value of 0 represents use of the default priority as defined in IEEE 802.1D-
2004.
DSCP: DSCP value to be used to provide Diffserv node behavior for the specified application type as defined in IETF RFC 2474. DSCP
may contain one of 64 code point values (0 through 63). A value of 0 represents use of the default DSCP value as defined in RFC 2475.
Adding a new policy: Click to add a new policy. Specify the Application type, Tag, VLAN ID, L2 Priority and DSCP for the new policy.
Click “Save.”
