Release Notes

Page 3

If a call initiated using SRTP on CS1K (on which MoH is configured) is put on hold, you might

experience some noisy audio (white noise) on the B179 phone at the receiving end when the B179 is

put off-hold.

Issue: The B179 phone cannot failover to a fallback account if the failover is configured using TLS.

Workaround: Do not configure transport failover using TLS.

When a call initiated from a B179 phone (A) to a phone (B) is transferred by B to a phone (C), phone

(A) still shows called ID of phone (B) when it should show called ID of phone (C). This issue is

present on the CS1K, IPO and CM platforms.

Issue: There is an existing issue when trying to dial a second number from the call list and aborting

the call while already waiting for an answer on a previously dialed number.

Workaround: Wait for an answer before dialing and aborting a second number.

Issue: A problem has been observed when using the B179 behind a hub and trying to dial Avaya

CS1K endpoints.

Workaround: Only use the B179 in a switched environment.

Issue: It is not possible to do firmware upgrades from the web interface when using https.

Workaround: Either use automatic provisioning for upgrades or to switch to http before doing the

upgrade.

Issue: It has been observed that the B179 will sometimes renegotiate to use another codec than the

initial one when doing a hold/unhold when connected to a CS1000 system.

Issue: As stated in the "Compatability matrix" in the release notes, TLS and SRTP are not supported

on CS1000 7.5.

Issue: When using redundancy and TLS transport failovers take longer to complete (up to 25-30

minutes).

Issue: In dialogue SIP OPTIONS messages are not supported in this release.

Configuration notes

Upgrading an Avaya B179 Conference Phone

1. Select Settings > Provisioning.

2. Click on the Browse… button and locate and select the firmware file.

3. Click the Upgrade icon.