You can configure voice over IP (VoIP) on an EX Series switch to support IP telephones. The Link Layer Discovery Protocol–Media Endpoint Discovery (LLDP-MED) protocol is sometimes used with IP phones to forward VoIP parameters from the switch to the phone. Not all IP phones support LLDP-MED, however.
This example describes how to configure VoIP on an EX Series switch without LLDP-MED and without 802.1X:
This example uses the following hardware and software components:
Before you configure VoIP, be sure you have:
Instead of using a regular telephone, you connect an IP telephone directly to the switch. An IP phone has all the hardware and software needed to handle VoIP. You also can power an IP telephone by connecting it to one of the Power over Ethernet (PoE) interfaces on the switch.
To configure VoIP on an EX Series switch to support an IP phone that does not support LLDP-MED, add the port to which you want to connect the IP phone as a member of the voice VLAN and configure the data VLAN as the native VLAN on the EX Series switch. This configuration ensures that the voice traffic and data traffic do not affect each other.
In this example, the interface ge-0/0/2 on the EX4200 switch is connected to a non-LLDP-MED IP phone.
![]() | Note: The implementation of a voice VLAN on an IP telephone is vendor-specific. Consult the documentation that came with your IP telephone for instructions on configuring a voice VLAN. For example, on an Avaya phone, you can ensure that the phone gets the correct VoIP VLAN ID even in the absence of LLDP-MED by enabling DHCP option 176. |
To configure VoIP without LLDP-MED or 802.1X authentication:
To quickly configure VoIP, copy the following commands and paste them into the switch terminal window:
[edit]set vlans data-vlan vlan-id 77 set vlans voice-vlan vlan-id 99set vlans data-vlan interface ge-0/0/2.0 set ethernet-switching-options voip interface
ge-0/0/2.0 vlan voice-vlanset ethernet-switching-options voip interface
ge-0/0/2.0 forwarding-class assured-forwardingset interfaces ge-0/0/2 unit 0 family ethernet-switching
vlan members voice-vlanset interfaces ge-0/0/2 unit 0 family ethernet-switching
native-vlan-id data-vlanConfigure VoIP:
[edit vlans]
user@switch# set data-vlan vlan-id 77
user@switch# set voice-vlan vlan-id
99 [edit vlans]
user@switch# set data-vlan interface ge-0/0/2.0
[edit ethernet-switching-options]
user@switch# set voip interface ge-0/0/2.0 vlan voice-vlan
user@switch# set voip interface ge-0/0/2.0 forwarding-class assured-forwarding
[edit interfaces]
set
ge-0/0/2 unit 0 family ethernet-switching vlan members voice-vlan [edit interfaces]
user@switch# set ge-0/0/2 unit 0 family ethernet-switching native-vlan-id data-vlan
Display the results of the configuration:
To confirm that the configuration is working properly, perform the following task:
Display the interface state and VLAN membership.
user@switch>
show ethernet-switching interfaces Ethernet-switching table: 0 entries, 0 learned
user@switch> show ethernet-switching interfaces
Interface State VLAN members Blocking
ge-0/0/0.0 down default unblocked
ge-0/0/1.0 down employee-vlan unblocked
ge-0/0/5.0 down employee-vlan unblocked
ge-0/0/3.0 down employee-vlan unblocked
ge-0/0/8.0 down employee-vlan unblocked
ge-0/0/10.0 down default unblocked
ge-0/0/11.0 down employee-vlan unblocked
ge-0/0/23.0 down default unblocked
ge-0/0/2.0 up voice-vlan unblocked
data-vlan unblockedThe field VLAN members shows that the ge-0/0/2.0 interface supports both the data-vlan VLAN and voice-vlan VLAN. The State field shows that the interface is up.