Publication date: Sept, 2015
Revision A1
137
VLAN configuration, along with the associated Layer 2 and Layer 3 attributes, that apply for a set of
specific protocol applications on that port. Improper network policy configurations are a very
significant issue in VoIP environments that frequently result in voice quality degradation or loss of
service.
Policies are only intended for use with applications that have specific “real-‐time” network policy
requirements, such as interactive voice and/or video services.
The network policy attributes advertised are:
1. Layer 2 VLAN ID (IEEE 802.1Q-‐2003)
2. Layer 2 priority value (IEEE 802.1D-‐2004)
3. Layer 3 Diffserv code point (DSCP) value (IETF RFC 2474)
This network policy is potentially advertised and associated with multiple sets of application types
supported on a given port. The application types specifically addressed are:
1. Voice
2. Guest Voice
3. Softphone Voice
4. Video Conferencing
5. Streaming Video
6. Control / Signalling (conditionally support a separate network policy for the media types above)
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.
Delete:
Check to delete the policy. It will be deleted during the next save.
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
Summary of Contents for LPB2910A
Page 7: ...Publication date Sept 2015 Revision A1 ii ...
Page 65: ...Publication date Sept 2015 Revision A1 53 SMTP Enable Select this Group Name in SMTP ...
Page 69: ...Publication date Sept 2015 Revision A1 57 The number of data to be saved in the RMON ...
Page 74: ...Publication date Sept 2015 Revision A1 62 ...
Page 278: ...Publication date Sept 2015 Revision A1 266 Refresh Click to refresh the page ...
Page 365: ...Page 353 Figure 9 21 Restore Configuration option ...