Avaya Video Telephony Solution Release Notes 5.2

Transcription

1 This document lists new product features, issues resolved, and current operational issues in Avaya Video Telephony Solution (AVTS) 5.2. It contains the following sections: Related Documents New Features Known Operational Issues Related Documents For more information on the installation, supported platforms, supported languages, and new features of AVTS and the Avaya Aura Communication Manager 5.2, see the Avaya Aura Communication Manager 5.2 Release Notes. The Avaya Aura Communication Manager 5.2 Release Notes. also contains a list of the video issues resolved by this release. In the current document, New Features on page 1 summarizes the minor incremental features of this release. For more information on the configuration of AVTS 5.2, the current limitations, and the troubleshooting steps, see the Avaya Video Telephony Solution Networking Guide 5.2. Tip: Tip: The Avaya Aura Communication Manager 5.2 Release Notes and the Avaya Video Telephony Solution Networking Guide 5.2 are available on support.avaya.com. New Features This section describes the new features in AVTS 5.2. It contains the following sections: Support for Siren 22 wideband audio codecs Support for Polycom LPR protocol Improvements to video bridge bandwidth administration Improvements to output of list video bridge New Instant-transfer button Cisco interoperability Issue 1 May

2 Management of Gatekeeper-Gatekeeper call rate New Polycom firmware Support for Siren 22 wideband audio codecs These codecs are administered in the same way as Siren 14, on the ip-codec-set form. Support for Polycom LPR protocol The Lost Packet Recovery (LPR) protocol allows endpoints to compensate for poor network conditions by using some of the bandwidth for error recovery. This reduces the resolution/frame-rate of the image to that expected from a lower bandwidth, but reduces the incidence of image artifacts, such as jagged lines, missing updates, and so on. LPR is automatically invoked by the endpoints as necessary, when supported at both ends of the call. No administration is required. Improvements to video bridge bandwidth administration Video bridges that do not provide far-end resource information can now be administered with specific bandwidth settings, instead of relying on the network region settings. This improvement allows more precise settings because administrators can set an exact required bandwidth instead of assuming the region settings are a maximum. It also means that administrators do not need to put the bridge in its own network region to get the right bandwidth. The available options are Region (the existing setup), Exact (a specific bandwidth is needed to connect), and Maximum (anything up to a specific bandwidth). Exact and Maximum require a specified bandwidth. Existing bridges retain their current setup until administrators make a change. Improvements to output of list video bridge The list video-bridge command now includes information on the status of each video bridge, as well as the network region and the type. The status is the same string that appears on the status video-bridge form. This allows administrators to get an instant picture of current status using a single command. 2 Document Number

3 New Features New Instant-transfer button Administrators can configure a button on a phone which implements an instant unsupervised transfer to the administered destination. This allows use of a desk phone to make and receive calls, which can then be instantly moved to a room system for video. The room system might belong to the phone user, or an executive assistant might make calls and transfer them to the executive s room system. A user can advertise one number for all calls and transfer video calls to the room system as appropriate. Cisco interoperability Avaya now supports basic H.323 video interoperability between Avaya Aura Communication Manager registered Avaya softclients and Polycom HDX and VSX video endpoints and Cisco Unified Video Advantage softclients registered to Cisco Call Manager. This support allows the establishment of point to point video calls between Cisco and Avaya video endpoints. The use of advanced video telephony features such as hold, transfer, and conference are not supported, because these features may cause the call to drop due to limitations on the Cisco Call Manager and endpoints. Management of Gatekeeper-Gatekeeper call rate In previous releases, Avaya Aura Communication Manager has used bandwidth requests (BRQs) for gatekeeper to gatekeeper (GK-GK) call rate management. This has now been discontinued, removing a source of call establishment problems when calling to Avaya Aura Communication Manager from gatekeepers such as SE-200 and CMA. Issue 1 May

4 New Polycom firmware Table 1 lists the versions of Polycom firmware that AVTS supports. Table 1: New Polycom Firmware Product Firmware Support RMX (or later) No. Recommend upgrade to AVAYA AVAYA003 Yes: Earlier 3.x.x versions not supported Yes. For more information, see Avaya Video Telephony Solution 5.2 Firmware Compatability Matrix, which is available on support.avaya.com. HDX (or later) Yes VSX (or later) Yes MGC (or later) Yes RSS No CMA Yes VBP 5300ST Yes PathNavigator (or later) Yes SE ER019 (or later) Yes Tip: Tip: Avaya recommends that administrators register Polycom endpoints such as the HDX and VSX directly to Avaya Aura Communication Manager rather than connected by way of CMA or similar devices. This allows Polycom endpoints to take advantage of enhanced call flows developed in a partnership between Polycom and Avaya. 4 Document Number

5 Known Operational Issues Known Operational Issues Table 2 describes the known operational issues in AVTS 5.2. It also describes the workarounds, where available. Note: Note: Table 2 refers to Avaya Aura Communication Manager as CM. Table 2: Known Operational Issues and Workarounds Key System Reproduction Scenario Workaround AVA-680 CM Under certain conditions, OLCReject denial events may be observed on CM when placing video calls between HDX and RMX even though video was established correctly. AVA-817 SE200 VSX registered to Polycom SE-200 may not be able to establish H.239 content channel when calling CM based video systems. AVA-846 HDX/VSX An IP Softphone calling Polycom VSX/HDX with H.263 codec may receive no video under certain configurations. AVA-940 1XC Adding a VSX endpoint to an MGC adhoc conference may result in 1XC callers receiving a black screen. Once the VSX leaves the call, video resume sfor the 1XC callers. Report the issue to Avaya support at None required. Register the endpoint directly to CM and enable the Avaya option, rather than Polycom SE-200. Disable high end video on the IP Video Softphone. This issue has been fixed in the future release of One-X Communicator (1XC). None available. Issue 1 May

6 Table 2: Known Operational Issues and Workarounds Key System Reproduction Scenario Workaround AVA-929 SE200/CMA SE200 and CMA do not support negotiation of H.245 tunneling. Generally VSX, HDX, and RMX in a Polycom CMA solution have had tunneling disabled. However, in a CM environment, the RMX has had H.245 tunneling enabled generally. If the RMX is moved back to Polycom CMA, the audio call setup with CM fails. AVA-952 Media Companion A 1XC or an IP Softphone(IPSP) caller in a HDX MP call will not see content sent by HDX during a People and Content session 8340 IXC 1XC in Roadwarrior mode does not support the Instant Transfer button as a new button. The new button does not appear on the station display. defsw SE200/CMA An CM video endpoint, which dials into a Meeting Exchange conference and then transfers to a video endpoint registered to a Polycom SE-200, may not establish video defsw MX If two remote video endpoints dial a Meeting Exchange video VDN and then a local video endpoint dials the same VDN, an adhoc conference will open on the Meeting Exchange bridge but the local video endpoint may not be heard in the conference. defsw CM An IP telephone transfer to a HDX across tandem CMs may result in audio only establishing for the HDX. Ensure that H.245 tunneling is disabled when registered to Polycom SE-200 or CMA. Host the content session on an VSX MP host. Overwrite an existing feature button on the 1XC button assignment rather than creating a new button assignment. Dial directly from the SE-200 video endpoint into the Meeting Exchange conference. Dial the Meeting Exchange video VDN from the local endpoint first. Dial directly from the HDX to the far endpoint. 6 Document Number

7 Known Operational Issues Table 2: Known Operational Issues and Workarounds Key System Reproduction Scenario Workaround defsw CM A local IP telephone attempting to initiate a video bridge adhoc conference involving two remote video endpoints does not open the adhoc conference. Initiate the adhoc call from the local video endpoint. AVA-890 Media Companion There is a poor video quality experience for 1XC users who dial into a Meeting Exchange conference that is configured for 30 frames per second (fps). Administer the Meeting Exchange conference to 7fps Issue 1 May

8 8 Document Number