Release Notes

Page 6
Ticket ID
Summary
AVAYAB100-286
Phone doesn't reboot when Save button is pressed on Provisioning web page
Known Defects
Ticket ID
Summary
Workaround
AVAYAB100-209
B179 hangs for several minutes when
trying to access the external phone if the
LDAP URL is invalid
Please insure that the LDAP URL is properly
configured and confirm this by checking that
when the External Phone Book is accessed
from the, it displays in a timely fashion
AVAYAB100-213
The B179 will crash if it receives a SIP
request containing a REPLACES header
and “Enable SIP Replaces” is not
enabled
For any B179 that will be registered to IP
Office, set “Enable SIP Replaces” to TRUE.
AVAYAB100-246
If an 1100 or 1200 Series Deskphone
running SIP 4.4.18 (4.4 SP2) connected
to CS1000 with MSBT is enabled tried
to place a call to B179, the call fails.
In a system with B179s as well as 1100s or
1200s, disable MSBT.
AVAYAB100-369
B179 ignores VLAN setting advertised
via LLDP
The B179 waits a maximum of 31 seconds for
a message from an LLDP server. If your
network configuration can not guarantee that
the B179 will receive a message from the
LLDP server meant to change the VLAN ID
within 31 seconds, you should configure the
VLAN ID using the L2QVLAN parameter in
DHCP option SSON, in the configuration file
or using the Web interface.
Known Limitations
DHCP SSON: Contrary to the note in the web interface, allowable choices for SSON include only
options 43, 60, 61, 62 and 128 through 254
DHCP SSON: The B179 will use values of only four parameters from DHCP option specified by SSON:
 HTTPSRVR, TLSSRVR, HTTPDIR and L2QVLAN.
The B179 will ignore any other parameters that might be included in the option.
UCaaS or ACME SBC: When connected to UCaaS or through an ACME SBC, the B179 will register
simultaneously to the first and second proxy only if no failover/failback sequence has occurred since the
B179 rebooted. Once the B179 fails over to the secondary proxy and fails back to the first, it will only
support alternate registration to the secondary proxy. The only known impact is that any failover or
failback after the first will require a few seconds longer.
Upgrading an Avaya B179 Conference Phone
Log in to the web interface as administrator.
1. Select Settings > Provisioning.
2. Click on the Browse… button and locate and select the firmware file.
3. Click the Upgrade icon.