IP Phone Support

The IP phone support feature focusses on the following key points:

• Works only on the Flex UNI-enabled and Auto-sense ports.

• For Avaya phones, you can choose to configure and send call server and file server Link Layer Discovery Protocol (LLDP) Type-Length-Value (TLV) options through the lldp vendor-specific CLI command.

• To reduce configuration overhead, this feature includes the Auto-sense voice mechanism to detect IP phones from LLDP signalling. After the switch detects the phone, this mechanism manages the following tasks:

  • Provides the voice VLAN to the phone, tagging, Differentiated Services Code Point (DSCP), and priority parameters through the LLDP Media Endpoint Discovery (MED) signaling options.

  • Configures a switched UNI for phone traffic and sends it to the Service Instance Identifier (I-SID) that is associated with the voice VLAN.

  • Handles the configuration, whether “trusted” or “untrusted” on the port and priority re-markings.

  • Integrates with the Auto-sense functionality. For more information on Auto-sense, see Auto-sense.

Note

This feature does not support auto-creation of voice VLAN and MultiLink Trunking (MLT) or Split Multi-Link Trunking (SMLT).

This feature has the following connectivity models:

• Standalone IP phone, which connects to a switch port.

• IP Phone with PC behind it, where the IP Phone has a small inbuilt bridge, and a PC connects to that bridge port.

Note

Phone traffic is tagged with the voice VLAN whereas the PC traffic is untagged. However, you can configure the phone to send the traffic as untagged.

The IP phone connectivity supports the following scenarios:

• Call server and file Server LLDP TLV options—These TLVs are Avaya proprietary. Use them only with the Avaya IP phones to detect the IP addresses of a Call server and File Server.

• Phone detection through LLDP messaging—Use the Capabilities and Enabled Capabilities field in the LLDP packet to detect a phone. A “T” capability identifies a phone.

• Auto-sense voice option, without Network Access Control (NAC)—Use this functionality to specify the voice VLAN and voice I-SID in a single CLI command.

• Auto-ISID-Offset—Use this functionality if the voice VLAN is received without an I-SID from a Radius response. The Auto-ISID-Offset functionality determines an I-SID automatically to send the data traffic.

• Auto-sense voice, LLDP authentication, and Non- EAP (NEAP) (MAC authentication) connectivity—If you have enabled NEAP, it authorizes all the MAC addresses received on the port and IP phone. With the LLDP authentication option, a device, such as phone, is trusted and does not require a Remote Authentication Dial-in User (RADIUS) authentication. For this authentication, the Extensible Authentication Protocol (EAP) is notified after a phone is detected and the port is in the Auto-sense voice state. Then, the MAC address of the phone is added to EAP or NEAP host table.