Falcon
M-Class
| User Guide
282
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.
It should be noted that LLDP-MED is not intended to run on links other than
between Network Connectivity Devices and Endpoints, and therefore 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 shall be used when selecting the
polices that shall be mapped to the specific interfaces
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 Signalling
(conditional) - for use in network topologies that require a
different policy for the voice signalling 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 Signalling
(conditional) - for use in network topologies that
require a different policy for the guest voice signalling 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 has
relevance.
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 Signalling
(conditional) - for use in network topologies that require a
separate policy for the video signalling 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.
Summary of Contents for Falcon Gen-3 M-Class
Page 90: ...Falcon M Class User Guide 90...
Page 107: ...Falcon M Class User Guide 107 Figure 4 57 DSCP Translation...
Page 139: ...Falcon M Class User Guide 139...
Page 187: ...Falcon M Class User Guide 187 Figure 4 99 RADIUS Statistics for Server...
Page 197: ...Falcon M Class User Guide 197 4 11 6 SyncCenter Status Figure 4 104 Sync Center Status...
Page 214: ...Falcon M Class User Guide 214...
Page 227: ...Falcon M Class User Guide 227...
Page 234: ...Falcon M Class User Guide 234...
Page 358: ...Falcon M Class User Guide 358 Figure 4 216 sFlow Configuration displays...
Page 376: ...Falcon M Class User Guide 376...
Page 403: ...Falcon M Class User Guide 403...