Notice

Nortel Page 7 of 20
access process, might impact current customer network configurations, especially if
something special was done to compensate for the former operation of the phone.
1) Voice VLAN enabled with the Automatic VLAN Discovery feature – initial DHCP request is
forwarded based on the Data VLAN policy (i.e. untagged if Data VLAN is disabled or tagged
with the Data VLAN ID if Data VLAN is enabled). Subsequent DHCP requests and the
resolution of a Voice VLAN will be as per existing automatic operation.
The potential impact of this change to an installed customer network is:
 If they have a Data VLAN configured
on the phone, and
 they have the auto configure VLAN feature enabled, and
 they DO NOT have their DHCP server on the Data VLAN
then the phone running these new firmware images will not register to the call server.
Customers should check that the DHCP server is on the Data VLAN if they've configured a
Data VLAN on their phones.
2) Stripping of egress Data VLAN tag is configurable – VLAN tag stripping can be enabled
or disabled in addition to enabling VLAN support on the phone’s PC port. If VLAN is enabled
on the phone’s PC port (ingress direction), the default will be to strip the tag on the egress
direction. However, this can be manually overridden to disable stripping even if VLAN
tagging (ingress direction) is enabled on the phone’s PC port. Likewise if VLAN is disabled
on the phone’s PC port, the default will be to NOT to strip the tag on the egress direction.
But this again can be overridden to enable stripping even if VLAN is disabled on the phone’s
PC port (ingress direction).
If stripping is disabled, the packet is sent to the phone’s PC port unmodified. If stripping is
enabled, the 802.1q header is removed (assuming one exists) from the packet before
forwarding it out the phone’s PC port