Deploying Voice Over Ip; Vlan Configuration On Non-Lldp-Med Capable Devices - HP MSM317 Deployment Manual

Deploying Voice over IP

The following sections offer guidelines for deploying VoIP telephones with the MSM317. These
sections cover IP phones requiring manual VLAN configuration, as well as those that support Link
Layer Discovery Protocol Media Endpoint Discovery (LLDP-MED).

VLAN configuration on non-LLDP-MED capable devices

The MSM7xx Controller interface allows you to specify a primary VLAN to which you can designate
tagged or untagged network traffic, depending on the types of VoIP phones you plan to
deploy. Some phones are dual-stage; that is, the initial communication is untagged. Following receipt
of vendor-specific DHCP options to set voice VLAN, QoS, and DSCP, the phone switches to sending
tagged traffic for voice prioritization. In most VoIP Installations, the primary VLAN may remain at its
default untagged setting, and the secondary VLAN may designate the tagged VLAN to be used for
voice communications.
The MSM7xx Controller interface allows you to configure a primary VLAN to handle upstream
untagged IP phone traffic sent to the configuration server and a secondary VLAN to carry tagged
traffic once configuration is complete.
Figure 11: The MSM7xx Controller interface lets you specify a primary and secondary VLAN to handle upstream untagged IP
phone traffic as well as tagged traffic once the phone has received its configuration settings. The Quarantine VLAN and allow
dynamic VLAN assignment checkboxes apply to installations where the VoIP phone is authenticated with either 802.1X or
MAC authentication.
Note:
For more information on configuring VLANs for non-LLDP-MED capable
devices, see the HP MSM317 Access Device Installation and Getting
Started Guide, configuration chapter.
15