Avaya PSN003614u User Manual
Product Support Notice © 2013 Avaya Inc. All Rights Reserved.
PSN #
PSN003614u
Original publication date: 12-Apr-12. This is Issue #05, published date: 8Feb-13.
Severity/risk level
High
Urgency
Immediately
Name of problem
Avaya Video Conferencing Solution (AVCS): Release 6.1
Products affected
Avaya Aura® Communication Manager (CM): Release 6.0.1
Avaya Video Conferencing Solution 6.1 including:
Avaya 9600 Series IP Deskphones
Avaya A175 Desktop Video Device
Avaya Aura® Conferencing 6.0
Avaya 1000 Series Video Conferencing Systems
Avaya one-X® Communicator
Polycom® HDX
Polycom® RMX
Problem description
Resolution
Notes
Remarks
AVCS is Avaya’s real-time video solution for the enterprise. Taking advantage of the capabilities of with Avaya Aura®., AVCS
supports a range of cost-effective, bandwidth-efficient video endpoints from Avaya, as well as third party video endpoints from other
manufacturers such as Polycom. AVCS allows customers to introduce system-wide high-definition video collaboration without the
cost, complexity and bandwidth demands associated with traditional, standalone high-end corporate video systems. Release 6.1 of the
Video Conferencing Solution (AVCS) significantly expands the documented interoperability enabled by the Solution.
Existing functionality of the Avaya Video Conferencing Solutions suite will be supported along with the AVCS 6.1 enhancements.
Avaya Video Conferencing Solution Release 6.1 enhancements provide the following capabilities to Avaya Aura® for video
communications:
Communication Manager scalability to administer 18000 video capable IP endpoints, 5333 concurrent video calls where the
video endpoints are SIP or H.323
Enhanced SIP-to-H.323 video resolution capability (High Definition) in Communication Manager administered as
Evolution Server
Expanded call scenario support for Avaya 1000 series SIP video conferencing endpoints
Expanded call scenario support for Avaya one-X® Communicator as a SIP video endpoint
Support for ADVD conferences via Avaya Aura® Conferencing MCU
Support for SIP registration of Polycom HDX endpoints to Session Manager
Support for the People+Content feature over SIP (BFCP) for Avaya 1000 series endpoints, the Polycom HDX endpoint, and
the Polycom RMX MCU.
Check that all firmware versions are updated to the supported versions; see the AVCS 6.1 Compatibility Matrix posted on
support.avaya.com for the most current details. The Compatibility Matrix can also be found below in this document for your
convenience.
For RMX units with MPMx boards installed, the system flag “SIP_H264_PACKETIZATION_MODE=NO” has to be added
to fully interop with Avaya Aura®.
For best recovery handling of the Avaya 1000 series video endpoints, it is recommended to change the setting for SIP
Signaling (under “Communications >> SIP”) from “Auto” to “TCP”.
The following known issues apply to video functionality supported with AVCS 6.1 – CM 6.0.1 SP #10 (20397):
Problem
Keyword
Workaround
Avaya Video Conferencing Manager only allows for endpoint discovery
up to a /24 subnet (254 endpoints max or smaller subnet).
147
AVCM will not discover the endpoints,
but instead manually enter them.
Avaya Video Conferencing Manager occasionally fails with "Internet
Explorer cannot download. Unspecified error." from a Microsoft
Internet Explorer browser.
163
Use Firefox or Chrome browser if you
experience problems with the Microsoft
Internet Explorer.
Sequential blind transfer of 10x0 endpoints may drop video.
255
If video is required after the transfers,
drop and make a direct call.
After a Session Manager outage, 1010/1020 may take up to 30 minutes
to re-register. Incoming calls are blocked while unregistered, but
outgoing calls are accepted and immediately initiate registration.
260
Set SIP Signaling on the Avaya 1000
series endpoints to TCP rather than
Auto. This setting is on the third page
under Administrator Preferences,
Communications, SIP.
If this is not done and there is an SM
outage some endpoints may have to be
manually re-registered following the
procedure below:
When you see a red "SIP" box in the
bottom right hand corner of the
1010/1020 screen, try manually
registering by making an outgoing call
or by:
1) Login to 10X0 Administrator
Preferences
2) Select “Communications”
3) Select “SIP”
4) Click “Register”
Scheduled upgrade of 10x0 via AVCM sometimes fail with "Failed" or
"The device is in a call."
278
Use the devices integrated web server
to directly upgrade the device.
1030/1040/1050 may transmit higher bandwidth than requested.
In some circumstances this can cause 5+ party conferences to fail
on the 1050.
288
Administer 1040/1050 endpoints to
send no more than 2M video.
An Avaya 1000 series video endpoint calling an extension with a
bridged appearance fails.
101124
An ADVD call that gets unattended/blind transferred into a video bridge
may lose video or get dropped.
111363
Dial directly into the video bridge.
Conference call between an audio endpoint and two video endpoints
may result in an audio-only conference, with no video between the two
video endpoints.
112357
120001
Unattended/blind transfer of One-X Communicator H.323 video call to
an ADVD may drop.
120468
Perform an attended/consulted transfer
or make a direct call.
© 2013 Avaya Inc. All Rights Reserved. Page 2
Loading...