|
Products updated: Tandberg, Polycom, Codian, Cisco, Emblaze-VCON
Your technical support contact: services@direct-visual.com
Your sales engineering contact: sales.eng@direct-visual.com
Your maintenance contacts: bdt@direct-visual.com
Telephone: 08453 575757
Video Helpdesk: 08453 575759
Major Benefits of Recent Revisions
- New TANDBERG MXP Software Release (F8.1)
TANDBERG Profile Dual Screen 52" MXP System
F8.1 Software Release
SIP
The TANDBERG MXP endpoint now supports the ability to connect encrypted SIP calls to Microsoft Office Communicator (MOC) clients.
Changes and Improvements since Previous Version
Software Upgrades
* F8.1 software and higher will disconnect all current calls upon the start of a software upgrade [Ref. 50117].
Video
* Corrected the flash of the Picture in Picture (PIP) from being displayed when a call is connected [Ref # 66016].
* Corrected an error in the H.263 encoder packetization code. This could cause the encoder to split the video stream into a new packet resulting into a lager packet size and cause an unexpected restart. [Ref # 64038, 63455, 63670, 67491].
* Corrected the re-establish of H.239 after an endpoint has been put on hold while transmitting H.239 by improving the termination of the H.239 stream before the "On Hold" request is handled [Ref. # 60098, 51014].
* Corrected the aspect ratio from automatically switching to a letter box layout when an ISDN call in disconnected from a Polycom MGC and Polycom RMX MCU [Ref. # 62603].
* Corrected the possibility of an unexpected restart when between switching composite and S-Video video sources during a call [Ref. 62497].
* Corrected an H.264 encoder issue within the H.264 bitstream ID in that this could be set incorrectly resulting in the bottom half of the video to be blurry [Ref. # 62827].
* Previous to F8.1, it was possible for the MXP endpoint to transmit the PC screen for a split second after the connection or a call, prior to switching to the main camera. This issue was present only when the 'Use as Local PC Monitor' was enabled [Ref. # 60715, 51615, 61845].
* Corrected the wrong input-gate signal used for the VESA Display Power Management Signaling (DPMS) on the 550MXP DVI output which was preventing monitor from going into standby mode when the endpoint does [Ref. # 65778].
* Corrected the MultiSite video text timeout, which was not clearing the video text after a set time or after disconnect [Ref. 65452, 64846].
* Corrected the PC video input signal tolerance, that could toggle between the resolution of 1366x768 and 1280x768 which results in frozen video [Ref. 64586].
* The endpoint now sends XGA instead of 4CIF as the H.239 video format to Polycom VSX and TANDBERG classic E series endpoints when the PC input is a WXGA resolution [Ref. # 62797].
* Corrected the possibility of the wrong resolutions of 528x400 or 640x480 being transmitted from a TANDBERG E20 to MXP Set Tops endpoints. The correct transmitted resolution is 576x448 (w448p) [Ref. # 54882].
* Corrected the displaying of a stretched image on screen when a PAL configured endpoint is connected to a NTSC monitor [Ref. # 64668].
* Corrected the possibility of and unexpected restart during a call when the PC input resolution is changed form 1024x768 (XGA) to 1280x720 (720p) [Ref. # 63378].
MultiSiteTF
* Improved the 3 party layout during a MultiSite conference in that when the host of the MultiSite takes the floor the far-end sites will still be displayed on individual monitors. Previously the MultiSite host would display a 4split (CP4 layout) on the first monitor and selfview on the second monitor. [Ref. # 64302].
* Corrected the MultiSite host from switching the video from the 4split layout to selfview when H.239 is active and another call is established [Ref. # 64165].
* General improvements to lip-sync during a MultiSite conference [Ref. # 62405].
Network
* Corrected the H.320 data logic to process a disconnect requests even if there still is a data wait request, which could result in an unexpected restart [Ref. # 65128].
* Stability improvements to still images (snapshot) [Ref. # 63332]
* Corrected the sending of the H323 ID and E.164 alias in the setup massage when the endpoint is registered to Cisco Communication Manager [Ref. # 67458, 66810].
* Corrected the sending of the H.323 transfer request right after the hold conference request to now insure that the video and audio are stopped [Ref. # 62747, 62570, 60539].
* Corrected the encoded of misinterpreting the open logical channel of H.263++ as H.263 [Ref. # 66455].
* Corrected a possible issue in no video or audio when an endpoint transfers another endpoint into a Multiway conference [Ref. # 64545].
* Corrected an issue in restarting the Master / Slave determination request when an endpoint resumes from hold which is not allowed when there is an active Open Logical Channel. This would results in a failed encryption key exchange and audio noise [Ref. # 62661, 62549].
* Corrected an issue in that the endpoint would not attempted to registered to a gatekeeper with the DNS hostname when the endpoint is set for a static IP address and after the endpoint is restarted with no network connected [Ref. # 63655].
* Corrected a possibility of the registration request to a gatekeeper getting into a lockup state when the H.323 Call setup is changed to Direct and the gatekeeper is unavailable [Ref. #61667].
SIP
* Corrected the possibility of an unexpected restart with MXP during a 407 proxy authentication [Ref. # 61084].
* Corrected the possibility of an unexpected restart when TURN license quota on the VCS is reached [Ref. # 65089].
* Corrected an issue when a non capable ICE client called an ICE client that would no longer setup TURN permission [Ref. # 67194].
* Corrected an issue that would cause systems to disconnect when dialing system that are only capable of supporting TURN (Non ICE clients) [Ref. 67195].
* Connected an issue with MNS mode that caused a reflexive ICE candidate to not be removed [Ref. 67197].
* Corrected an issue that caused a system with ICE/MNS disabled to not setup TURN permissions when calling another system with ICE/MNS enabled. [Ref. 67198].
* Corrected an issue with BFCP during a system with ICE/MNS disabled to not setup TURN permissions when calling another system with ICE/MNS enabled. [Ref. 67198].
* Corrected the possibility of dual streams not functioning as expected during a MXP MultiSite SIP conference with E20 endpoints [Ref. # 61063, 65509].
* Corrected an internal server error that may occur on MXP when Microsoft Office Communicator Client sends a NOTIFY [Ref. # 63858].
* Corrected the use for the right subscription-state for a final 200 class responses after a transfer of an E20 endpoint [Ref. # 62750].
* Corrected an issue with NAT in certain scenarios of not accepting TURN allocation requests [Ref. # 60293].
* Corrected an issue where dual streams would not work as expected in a point to point call reliable [Ref. # 64839, 64842].
* Corrected the SIP Legacy mask feature "xConfiguration SIP Legacy Mask: " to also apply to the dual stream [Ref. # 60486, 58426].
* Corrected the wrong sequence numbers used for RE-INVITE and ACK [Ref. # 63930, 63931, 64566].
* Corrected the static SDP offer of 1152kbps when the endpoint received an empty INVITE [Ref. # 64031, 58342].
* Corrected the support of BFCP over UDP that was missing in header options which is required for dual stream to work in and interworking call [Ref. # 66938].
* Corrected the header parsing keys on wrong parameter definition [Ref. # 62456]
* Corrected the sending of the SERVICE message to Microsoft Office Communicator Server when the SIP mode is enabled to prevent error when there is no SIP URI configured. SERVICE message will now be sent once the SIP settings are saved [Ref. # 63721].
* Corrected an issue with call transfers with Microsoft Office Communicator Client in that the MXP will now cache the local SIP URI for call transfers as Call Indicator instead of Call Resume [Ref. # 56278, 56252].
* Corrected an issue within our best effort encryption signaling in OFFER / ANSWER SDP's with Microsoft Office Communicator Client in that no video would be displayed on the MOC side [Ref. # 62277].
* Corrected the use of the wrong index variable in the sim-cap-set that was indicating the MXP as a MCU [Ref. 63505, 69450].
* Corrected an issue with the handling of the RTCP stream when using TURN as this was not handled as a TURN stream [Ref. # 63097].
* Corrected the possibility of presence not function as expected during normal operation and after a software update on the MXP endpoints [Ref. # 65828, 65808, 66112, 68598]
* Corrected the scale of Microsoft keep-alive time value which could result in an unauthorized call attempted when place a call to Microsoft Office Communicator Client [Ref. # 65383].
* Corrected the possibility of the MXP endpoint from getting into an infinite loop of sending a BYE request when disconnected from Microsoft Office Communicator Client [Ref. # 66110].
* Corrected the missing authentication report displayed on the MXP endpoints when using TLS and SIP Verify TLS when registered to on Microsoft Office Communicator R2 [Ref. # 62229].
* Improvements to SIP by adding to all server types sdp.extension.v1 which is needed for supporting dual steams on the Alcatel PBX's [Ref. # 64829].
* Improved the SDP to accepted port number change when SIP calls are resumed form hold [Ref. # 64039, 64934, 66599].
* Improvement to SIP with implementing support for 301 redirect of register in a Microsoft OCS environment when Microsoft is selected as the Server Type [Ref. # 56186].
Domain Name Sever (DNS)
* Improvements to DNS name configured for Gatekeepers \ Video Communication Sever (VCS) to resolve to multiple IP addresses and attempted to registered with each gatekeeper \ VCS in turn, which is done until it successfully registers or denied permission to register [Ref. # 51090, 54209].
User Interface
* Corrected the displaying of the Logo during a telephone call when the logo is disabled [Ref. # 51702].
* Corrected the message window of "0 kbps Connection Successful" to the correct call rate when adding endpoints to a MultiSite call [Ref. # 53916].
* Corrected the displaying of the entire H.239 WXGA resolution in the received column of the call status [Ref. # 63540].
* Corrected the displaying for a blank Hold / Transfer banner being displayed on the bottom of the screen [Ref. # 63370].
* Corrected having the slide bar for the Horizontal Adjustment DVI displayed in the user interface under the Presentation menu on the 550XP as this does not support a PC input [Ref. # 63892]
Web Interface
* Corrected the displaying of the MXP web interface on a 4:3 monitor with the resolution of XGA (1024x768) in that some of the configuration tabs were not assessable [Ref # 63761].
* Corrected having the Horizontal Adjust DVI setting in the web interface under Presentation Configuration for the 550MXP as the 550MXP does not support a PC input [Ref. # 63893].
* Improved the web server of the endpoints to now use the system name as the authentication realm (User Name) for Microsoft Internet Explorer 7 and 8 password window [Ref. # 57411, 65038].
API \ XML
* Corrected the URL address listed in the ICU License information to http://source.icu-project.org/repos/icu/icu/trunk/license.html when "about" is entered [Ref. # 66269].
* Corrected the displaying of broadcast messages, (i.e. software upgrade status) on password protected endpoints. Broadcast message will be displayed once the password is entered [Ref. # 62173].
* Corrected the Security Level command from xConfiguration Security Level: <0..3> to xConfiguration Security Level: <0..2> as there is no security level 3 [Ref. # 63734].
* Corrected feedback and xfeedback to now update the dual video source that is selected [Ref. # 59898].
* Corrected the missing of TURN configuration in the CUIL XML document [Ref. 63843].
Usability
* Corrected the function of disabling the Picture in Picture (PIP) from being displayed on the screen with the following API command xConfiguration AutoPIP Mode: Off [Ref. # 64416].
* Corrected a possibility of an unexpected restart when the endpoint is unsuccessful in joining a Multiway conference due to an uninitialized variable in the Multiway startup. In addition the endpoint will now resume a point to point connection if there is an unsuccessful join of the Multiway host [Ref. # 65185, 63242]
* Corrected the control of the near-end camera on endpoints that are connected to a TANDBERG Video Switch (TVS) and in a call while transmitting H.239 [Ref. 62311].
Note: Selfview must be selected to move the local camera during an active H.239 connection.
* Corrected the uploading of the logo within a template from TANDBERG Management Suite (TMS) software version 12.2 and higher [Ref. # 65729].
* Corrected the ability of loading software to MXP endpoints from TANDBERG Management Suite (TMS) when security level 2 is enabled [Ref. # 62904].
* Corrected the stripping of the SIP prefix in the dialing string when SIP is disabled [Ref. # 65464, 62499].
* Corrected an oversight of having more then 2 concurrent calls from the Multiway host [Ref. # 64438, 64441].
* Corrected the function of Floor Control (basic floor control) during a H.323 Multiway call [Ref. 61827].
* Corrected the function of the ipaddress/streaming.ssi link to grant access to view the stream on an MXP endpoint when the streaming password is entered and no longer requiring the IP access password to the view the stream [Ref. # 64452].
Note: The IP Access and Streaming password must be set and Allow Remote Start must be enabled in the Steaming settings which is only available from the user interface.
* Improvements to a mix Multiway (SIP and H.323) call if the added sites have SIP disabled and the call in placed over H.323, which would prevent a successful connection. The SIP prefix from the URI will now be removed when transferring into Multiway [Ref. # 63605].
Interoperability
Polycom
* Corrected the narrow\squished letter box video from being displayed on the Polycom VSX when MXP endpoint with 4:3 or standard definition camera transmits H.263++ iSIF [Ref # 64986].
* Corrected a 1 minute period of no video once the MXP endpoint is connected to a Polycom RMX2000 MCU SIP conference [Ref. # 56524].
- New TANDBERG E20 Software Release (TE1.0.1)
TANDBERG E20
This release note describes the new features and capabilities included in the TANDBERG E20 software version TE1.0.1 released on 22nd of April 2009.
Note: This software applies to endpoints that run the TE series of software. The TANDBERG MXP endpoints do not run TC software, but rather F or L series software. Statements and functionality in this release note does not apply to the TANDBERG MXP systems. Please see the Software Release Document for F and L series software.
Changes and improvements since previous version
Misc
• Tuned timing on NAND interface to support NAND chips with date code 907 and newer
- New TANDBERG VCS Software Release (X4.2)
TANDBERG VCS
SOFTWARE RELEASE NOTES FOR TANDBERG VCS VERSION X4.2
These release notes describe the features and capabilities included in the TANDBERG Video Communication Server, software version X4.2 released on the 3rd of April 2009.
New Features
X4.2 is a maintenance only release. No new features or functionality are included within this version over the previous release, X4.1.
Changes and Improvements since the Previous Version
Interoperability
Avaya
An issue that would prevent the transmission and receipt of video between an endpoint registered to the TANDBERG VCS to an endpoint registered to the Avaya Communications Manager over an H.323 trunk has been resolved [Ref. # 57531].
Cisco
An issue that would prevent proper operability of an H.323 neighbor zone to a Cisco IOS Gatekeeper running versions 2.3 or 2.4 has been resolved [Ref # 62177].
Microsoft
An issue that would prevent video from appearing on a Microsoft Office Communicator (MOC) client registered to Microsoft Office Communications Server (OCS) 2007 when connected to an H.323 endpoint registered to the TANDBERG VCS has been resolved [Ref # 63543].
X4.1 resolves an issue that will prevent the VCS from sending proper presence information to OCS when Interworking is configured to "On" instead of "Off" or "Registered Only" [Ref # 62679].
LifeSize
The VCS will now properly interpret and respond to an H.225 setup message from a LifeSize endpoint when starting an embedded MCU call [Ref # 62005].
Movi
Previously, if a Movi registration was proxied from the VCS-Expressway into the VCS-Control, a call that was made from that Movi client to an H.323 endpoint registered on the VCS-Expressway would not be interworked properly if the VCS-Expressway interworking mode was set to "Registered Only." This issue has been resolved in X4.2 as the VCS-Expressway will now consider all registrations that it proxies as locally registered endpoints [Ref # 60812].
H.323
Improved the reason provided within H.225 releaseComplete messages sent from the VCS to the remote endpoint [Ref # 61034].
The VCS will now provide proper information logged within Facility messages sent to H.323 endpoints [Ref # 61053].
SIP
An issue has been fixed in the VCS that would prevent dual streams (Binary Floor Control Protocol, BFCP) from being established during a SIP traversal call. This issue also prevented any H.323 devices within a FindMe consisting of both H.323 and SIP endpoints from being alerted as to an incoming call [Ref # 60687].
Note: This functionality must be explicitly enabled via the CLI of the VCS using the commands below.
xConfiguration SIP Require UDP BFCP Mode: On
xConfiguration SIP Require Duo Video Mode: On
An issue that prevents the VCS from properly handling null characters within SIP payloads have been resolved [Ref # 63088].
The VCS will now properly send INFO messages to SIP endpoints to request a picture fast update when it receives an error code to previously sent INFO messages [Ref # 58582].
An issue that could cause a VCS to restart unexpectedly when processing m lines in the form of "m=message 7654 TCP/MSRP" has been resolved [ref # 61758].
When connecting a Multiway, Interworked call, the VCS will now append the isFocus parameter to the Refer-To portion of the SIP message rather than the Contact portion of the message, as it did previously [Ref # 61942].
Interworking
Resolved an issue that will cause the VCS to improperly convert the H.264 capabilities from a SIP-only client to an H.323-only client [Ref # 56954].
The VCS will now properly tear down an interworked call when no video and audio capabilities match between the H.323 and SIP sides of the connection [Ref # 60674].
Resolved an issue where the eventlog of the VCS would incorrectly log net address failures when it receives an LRQ and resolves the address in that LRQ to a SIP address [Ref # 60742].
Clustering
An issue has been resolved that would prevent settings from being properly replicated to peer VCS's within a cluster if a new peer was added to the cluster and not immediately reachable [Ref # 61087].
In X4.1 and previous versions, a VCS that is removed from a cluster would not properly release the cluster configuration, preventing new changes to the settings of the VCS from being properly changed within the configuration. This issue has now been resolved [Ref # 61164].
A reporting issue that would cause a VCS in a cluster to incorrectly report cluster status to TMS has been resolved in X4.2 [Ref # 61470].
The cluster replication script on the VCS has now been fixed to no longer state that TMS is required to setup a cluster [Ref # 62347].
Logging has been improved to properly capture the errors occurred when clustering has been setup [Ref # 54595].
Multiway
The VCS will now properly set the isFocus parameter of a setup message when invoking Multiway and sending the setup message to an MCU [Ref # 61658].
The VCS will no longer send a BYE message prior to receiving a NOTIFY message from the SIP end of a Multiway call that is interworked from an H.323 endpoint. Previously, the BYE message would be sent too early to the SIP side, causing the call to disconnect [Ref # 62043].
System
The VCS will now report more information in the eventlog when the license limit is reached on the system. This information will include the call identifier and other call-specific information to improve the ability of the administrator to understand why a call failed if the license limit is reached [Ref # 57517].
Resolved an issue with the LDAP stack in the VCS that would allow it to consume all available resources on the VCS and cause an unexpected restart [Ref # 62044].
An issue that could cause an automatic restart when running a CPL script to modify IP address "1.1.1.1" has been resolved [Ref # 60961].
The VCS will now properly log all calls that are processed with the same call serial number [Ref # 61058].
- New TANDBERG MXP Software Release
TANDBERG MXP (F.8)
These release notes describe the new features and capabilities included in the TANDBERG MXP Endpoints software version F8.0 released on 15 April 2009.
Note: This software applies to all MXP endpoints that run the F series of software. The TANDBERG 150MXP does not run F software, but runs L series software. Statements and functionality in this document do not apply to the TANDBERG 150MXP system. Please see the Software Release Document for L series software.
Camera Software Upgrade
F8.0 software will automatically upgrade the Precision HD camera to software version S01692-3.0Final [ID:30037] when connected to the TANDBERG High Speed Serial Interface (THSI - Data Port 2). This software upgrade will occur 30 seconds after the codec restarts the second time after the endpoint software upgrade. The Precision HD camera is still functional during the upgrade process, but will restart automatically once the software is loaded resulting in no video for 15 seconds.
New Features
Video
Aspect Ratio (Local Display)
F8.0 supports the adjustment of the aspect ratio for the TV and DVI-I outputs to Auto, Clip, Letterbox, and Fill, allowing the end-user to customize the aspect ratio of the monitor to the preferred configuration. The Aspect Ratio setting are located in the user interface under Control Panel > General > Screen Settings > Aspect Ratio.
WXGA Input Support
F8.0 now supports PC resolutions of up to WXGA (1280x768, 1280x800, 1366x768 and 1360x768) for both local view and transmit to the far end during an active video call, either as the main stream or the dual stream. Depending on the far end capabilities, these resolutions can now be transmitted at the following native resolutions: XGA (1024x768), 1280x768, 1280x800, 4CIF, w720p or w576p.
H.239 WXGA
F8.0 software supports transmit and receive of WXGA PC resolutions of 1280x768 and 1280x800 over the H.239 dual channel if supported by the far-end.
WXGA Output
F8.0 supports the selection of WXGA (1280x768) output from the user interface. This is located under Control Panel > General > Screen Settings > Video Out > VGA Out Quality.
Keep Duo Open
F8.0 software support the ability to keep the dual channel open even when there is no presentation video source connected to the endpoint.
Command: xConfiguration KeepDuoOpen:
PrecisionHD Camera
Precision HD camera software ID 30037 is a maintenance update to improve the tuning of zoom control and pixel correction. There are no new features included within this release.
Note: It may be possible that the Precision HD camera is not detected after the camera has been upgraded. Power cycle the camera or system to re-establish communication to the camera.
MultiSite
Wide CP Layout
As an enhancement to the Continuous Presence layouts already supported by the MXP endpoints, F8.0 now includes support for wide CP layouts, transmitted in w576p (1024x576) in both the 4-split and 5+1-split video layout to the far-end systems. If the wide CP layout is not preferred, then this can be disabled with the commands below, in which case the host will transmit all CP layouts using 4CIF.
xConfiguration Conference VideoFormatCP: 16:9 (Wide CP, Transmits w576 > 1024x576)
xConfiguration Conference VideoFormatCP: 4:3 (Normal CP, Transmits 4CIF > 704x576)
3 Party Layout
F8.0 now supports a 3 party layout on the multisite host that utilizes the dual monitor setting of the system to display the two far-end sites on individual monitors. This feature is supported when the multisite picture mode is set to Auto Split or 4 split. When a dual stream is started during the conference, the screen will return to a standard 4-split in order to display the dual stream on the second monitor. Upon termination of the dual stream, the layout will return to the 3 party layout. This can be enabled or disabled from the user interface from the following location > Control Panel > General > Screen Settings.
Audio
Assisted Listening Device (ALD)
F8.0 software has been enhanced to improve the experience for any end users that require additional listening assistance.
Hearing Impaired Mode reduces the delay on audio output 3 from 100 ms to 23 ms, allowing a listening device to be installed in conjunction with this output and still maintain a high level of lip synchronization. This mode is controlled through the use of an API command:
xConfiguration Audio HearingImpaired Mode: [On/Off]
Noise reduction can also be controlled on the endpoint through the use of an API command. When turned on, noise reduction will be added to the output used for hearing impaired devices installed on output 3.
xConfiguration Audio HearingImpaired NoiseReduction: [On/Off]
An equalizer can also be enabled on the system, adding more amplification to the higher frequencies typically found in voices. On by default, this behavior is also controlled through an API command:
xConfiguration Audio HearingImpaired EQ: [On/Off]
Network
H.323
Alternate Gatekeeper
F8.0 software now displays the alternate gatekeepers from the data port with the following API command.
Command: xStatus h323gatekeeper
H.323 Transfer
F8.0 software supports the ability of transferring a H.323 call from one endpoint to another. During a point-to-point call, select the connect button on the remote control and enter the number of the system you wish to transfer the far-end system to and select the Transfer icon. The call will then be transfered to this system causing your local system to be disconnected.
Multiway
F8.0 software supports the released version of the Multiway feature that will extend point to point calls to conferences on MCU's hosted on the network over H.323 and SIP. The new participant will be consulted before he is added to the conference. The setting for the Multiway feature is available from the following location in the user interface > Control Panel > General > Multipoint Call Options.
SIP
Interactive Connectivity Establishment (ICE)
F8.0 software supports SIP interactive connectivity establishment (ICE) for SIP traversal. ICE is a client protocol that governs NAT traversal for SIP endpoints through a combination use of Simple Traversal of UDP through NAT (STUN) and Traversal Using Relay NAT (TURN, also known as STUN Relay) by allowing the endpoint to determine the best possible path to the far end system.
Traversal Using Relay NAT (TURN)
F8.0 software supports SIP traversal using relay NAT (TURN) for SIP traversal, allowing endpoints behind a NAT to traverse the firewall through a relay server, such as a TANDBERG VCS.
MNS (Media Network Services)
F8.0 software supports Media Network Services mode for SIP traversal functionality that prioritizes the use of TURN, so that all media traffic is relayed, unless sent to an endpoint on the local network.
Microphone Mute Indication
F8.0 software supports the microphone mute indication banner that the far-end systems microphone is muted over SIP.
New SIP RFC's
RFC4508 Conveying Feature Tags with the Session Initiation Protocol(SIP) REFER Method
draft-ietf-mmusic-ice-19: Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols
draft-ietf-behave-turn-13: Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)
RFC 5389: Session Traversal Utilities for NAT (STUN)
draft-ietf-behave-stun-test-vectors-04: Test vectors for STUN
draft-ietf-sip-ice-option-tag-02: Indicating Support for Interactive Connectivity Establishment (ICE) in the Session Initiation Protocol (SIP)
User Interface
Last Number dialled
F8.0 software supports the ability of calling the last number dialed by pressing the connect button twice on the remote control.
Horizontal Adjust DVI
F8.0 software supports the horizontal adjustment of the PC input form the user interface under the following location > Control Panel > Presentation > Horizontal Adjust DVI.
Number Key Mode
In F8.0 software a "Use as Default" check box was added to the Number Key Mode window that appears on the screen when a number key is pressed during a call. This allows the user the set this quickly to the preferred default setting.
SIP Settings
The SIP settings menu has a new look with the addition of sub-menus for SIP Server Settings, Authentication, and SIP NAT Traversal.
DTMF Keypad
In F8.0 software the DTMF keypad that is displayed on the screen will be moved to the opposite corner of the Icon Placement settings.
Call Manager Settings
F8.0 software supports an extension number along with the IP address for the Cisco call manager. When the endpoint is configured to communicate to the Call Manager, both the extension and IP address would be registered.
Note: The Call Manager Extension and H.323 E.164 Alias utilize the same field which results in any changes to one will affect the other.
Secure File Transfer
The MXP now supports the ability to transfer files securely from a client to the MXP over the Secure Copy Protocol (SCP) to retrieve the security log from the endpoint [Ref # 60369].
API \ XML
For more details, please reference to the F8 Codec References Manual, document D13887 Rev.09
Usability
Reverse Camera Steering
F8.0 software now supports the ability of reverse the local camera control, allowing the camera to more naturally mimic the directional arrows of the remote. This behavior can be controlled from the data port with the following API command.
xConfiguration CameraReverseControl: (Default is off)
Do Not Disturb
All calls that are received (and thereby rejected) when the endpoint is in Do Not Disturb mode, will now be logged under "Missed Calls" within the call log.
Russian - Phone Book Search
F8.0 software supports the ability of searching the phone book in Russian language.
- New TANDBERG MXP Software Release
TANDBERG MXP
These release notes describe the new features and capabilities included in the TANDBERG MXP Endpoints software version F7.3.3 released on 9 March 2009.
Note: This software applies to all MXP endpoints that run the F series of software. The TANDBERG 150MXP does not run F software, but runs L series software. Statements and functionality in this document do not apply to the TANDBERG 150MXP system. Please see the Software Release Document for L series software.
New Features
F7.3.3 is a maintenance release only. There are no new features included in this release.
Note: The F7.3.2 software included two new features, Secure File Transfer and Assisted Listening Device, and was released at the same time as our new TANDBERG Profile 6000 MXP system. Please see the Software Release Document for details.
Changes and Improvements since Previous Version
Display
Improvements were made in the MXP endpoint to improve the menu display and configuration of an MXP installed in the new 52" Profile.
- New TANDBERG C90 (T3) Software Release
TANDBERG C90 (T3)
This release note describes the new features and capabilities included in the TANDBERG C90 software version TC1.0.4 released on 7th of April 2009. The release includes minor fixes required for the TANDBERG T3 telepresence system. There is no need to upgrade none TANDBERG T3 systems to TC1.0.4.
Note: This software applies to endpoints that run the TC series of software. The TANDBERG MXP endpoints do not run TC software, but rather F or L series software. Statements and functionality in this release note does not apply to the TANDBERG MXP systems. Please see the Software Release Document for F and L series software.
Changes and Improvements since Previous Version
Video
• Added more robustness to the video decoder. Packets arriving out of order and outside of the jitter buffer, will be dropped.
• Fixed an issue which could cause the Presentation channel to establish with too low bandwidth causing blurry images.
Network
• Disabled path MTU for media. If MTU is too large for the network causing fragmentation, the network will now be instructed to notify the endpoint, which will reduce the MTU size to avoid fragmentation.
• Implemented jitter buffer based upon audio and video jitter. Previously only audio was used to build up the jitter buffer. This will provide better video when video packets arrive out of order within the jitter buffer, as the unit will be able to re-order the packets before they are fed to the decoder.
• Implemented support for IEEE 802.1X. 802.1X
New xCommands:
• xConfiguration Network 1 IEEE8021X Mode: Off
• xConfiguration Network 1 IEEE8021X AnonymousIdentity: ""
• xConfiguration Network 1 IEEE8021X Identity: ""
• xConfiguration Network 1 IEEE8021X Password: "***"
• xConfiguration Network 1 IEEE8021X Eap Md5: On
• xConfiguration Network 1 IEEE8021X Eap Ttls: On
• xConfiguration Network 1 IEEE8021X Eap Peap: On
Audio
• Implemented support for telephone add on connected to the T3 center codec using line input x and line output 4.
- New TANDBERG C60 Software Release
TANDBERG C60
This release note describes the new features and capabilities included in the TANDBERG C90 and C60 software version TC1.1.2 released on 3rd of April 2009.
Note: This software applies to endpoints that run the TC series of software. The TANDBERG MXP endpoints do not run TC software, but rather F or L series software. Statements and functionality in this release note does not apply to the TANDBERG MXP systems. Please see the Software Release Document for F and L series software. The TANDBERG T3 systems must run the software version specified in the TANDBERG TCU release notes.
Changes and Improvements since Previous Version
Video
• Corrected an issue causing the composite output to only output near end video. The composite output can now be set to act as either first or second monitor [Ref. #60108]. This output still has some limitations listed in the Known Limitations section below.
Audio
• Corrected an issue where occasionally when dialling into a Codian MCU under heavy load, the system would select wrong audio codec and cause a buzzing noise [Ref. #67267].
• Corrected an issue which could cause the dial tone to be heard a few seconds after connect [Ref. #63302]
• Implemented support for call type telephone using H.323. To place a telephone call, select "Audio call" as call rate.
Network
• Improved DHCP handling. The DHCP client will now ARP the address given by the DHCP server, if any other clients reports that this address is taken, the DHCP client will send a DHCP DECLINE message [Ref. #63046].
- New TANDBERG Codian Software Releases
TANDBERG Codian MCU & MSE
The TANDBERG Codian MCU 4200 Series, MCU 4500 Series, MSE 8420 Media Blade, and MSE 8510 Media2 blade version 2.4(1.18) is a maintenance only release and is available in four versions:
*Release 2.4(1.18) for the TANDBERG Codian MCU 4200 Series
*Release 2.4(1.18) for the TANDBERG Codian MCU 4500 Series
*Release 2.4(1.18) for the TANDBERG Codian MSE 8420 Series
*Release 2.4(1.18) for the TANDBERG Codian MSE 8510 Series
Resolved in version 2.4(1.18), 6 January 2009
*In previous releases, on low-bandwidth calls, high-resolution content data may lead to corruption and/or blank screens at the start of the call, along with the display of the packet loss icon. This is fixed in Release 2.4 (1.18)
*In previous releases, using DTMF could cause the MCU to become unresponsive when in a SIP call to a 8510 Media2 blade. This is fixed in Release 2.4 (1.18)
*In previous releases, use of HTTPS could cause the MCU to become unresponsive. This is fixed in Release 2.4 (1.18)
*In previous releases, the custom auto attendant banner failed to show on the PIN entry screen if you dialed directly to the conference using the E.164 number. This is fixed in Release 2.4 (1.18)
In previous releases, there were issues with multicast streaming when the conference name was in Unicode. This is fixed in Release 2.4 (1.18)
- New TANDBERG Codian Software Releases
ISDN Gateway
TANDBERG Codian ISDN Gateway software
The TANDBERG Codian ISDN GW 3241 & 3200 and the TANDBERG Codian MSE 8321 & 8310 blade software version 1.4(1.9) is a maintenance only release, addressing the following changes and improvements:
*Calling through an Avistar gateway to the ISDN GW fails.
*Calls via Tandberg TCS through the ISDN GW using H.264 could cause the ISDN GW to crash.
*ISDN GW supports a maximum of 10 management user accounts. The new maximum is 200.
Note that version 1.4(1.5)N to 1.4(1.8)N and version 1.4(1.5)P to 1.4(1.8)P has not been published.
- New TANDBERG Software Releases
Codian MCU & MSE
TANDBERG Codian MCU and MSE – Release 2.4(1.10)
The TANDBERG Codian MCU 4200 Series, MCU 4500 Series, MSE 8420 Media Blade, and MSE 8510 Media2 blade version 2.4(1.10) is a maintenance only release and is available in four versions:
*Release 2.4(1.10) for the TANDBERG Codian MCU 4200 Series
*Release 2.4(1.10) for the TANDBERG Codian MCU 4500 Series
*Release 2.4(1.10) for the TANDBERG Codian MSE 8420 Series
*Release 2.4(1.10) for the TANDBERG Codian MSE 8510 Series
The software addresses the following changes and improvements:
Resolved issues on the MSE 8510 Media2 blade in version 2.4(1.10)
The following limitations on the MSE 8510 Media2 blade have been corrected:
*Real-time clock not being updated
*In previous releases, the real time clock would not always correctly update when you rebooted the MSE 8510. This is fixed in Release 2.4(1.10).
SIP support
*SIP is now fully supported on the MSE 8510 Media2 blade.
Uploading SSL certificates
*The uploading of your own SSL certificate is now fully supported on the MSE 8510 Media2 blade.
Resolved in version 2.4(1.10)
*In previous releases, custom codec selection for some SIP endpoints did not always work properly. This is fixed in Release 2.4(1.10).
*In a previous release, the MCU wrongly required multicast streaming users to log in. This is fixed in Release 2.4(1.10).
*In software version 2.4 (1.1), the MSE 8510 Media2 blade could be made to hang in response to certain serial backplane communications from the supervisor blade. This resulted in a loss of network and serial port connectivity. This is fixed in Release 2.4(1.10).
*In previous releases, the MCU sometimes crashed in response to certain HTTPS web page requests. This is fixed in Release 2.4(1.10).
*In previous releases, the generation of the JPEG participant thumbnail image for display in Codian Director's participant properties tab could cause the MCU to reboot. This is fixed in Release 2.4(1.10).
*In software version 2.4 (1.1), diagnostic information was not stored by the MSE 8510 Media2 blade. This is fixed in Release 2.4(1.10).
*In previous releases, the use of HTTPS would cause excessive CPU usage and slow web interface response. This is fixed in Release 2.4(1.10).
*In previous releases, on connections to FieldView cameras, the MCU would stop transmitting video a short time after connection. This is fixed in Release 2.4(1.10).
*In previous releases, calls through Cisco IP/IP gateways disconnect if the MCU advertises H.239 capabilities to them. This is fixed in Release 2.4(1.10).
*In previous releases, when the MCU was configured to send feedback messages to API hosts, the MCU’s event log included misleading 'Unexpected response' error messages. This is fixed in Release 2.4(1.10).
In the previous release, newly-created private conferences appeared in the menus of connected auto attendants. This is fixed in Release 2.4(1.10).
- New Polycom Software Feature Release
SIP 3.1
New Features
The following notification is for the SIP 3.1 feature release - now available from Polycom.
This release is applicable to all SoundPoint IP and SoundStation IP family products except SoundPoint IP 300 and 500 models.
The key new features in this release are:
Telephony Enhancements
*Enhanced Feature Keys
*Configurable Telephony Soft Keys
*Server driven message display to user
*Enhanced ‘Dialog Package’ BLF
*Electronic Hookswitch compatibility with Plantronics Headsets
*Introduction of Polish and Slovenian as supported languages
Application Developer API Enhancements (Beta in SIP 3.1)
*Programmable Soft Keys
*Telephony Control and Status API
*Push Capability
*XHTML browser link in a SIP message
Administrator Enhancements
*User activated restart for faster configuration changes
*De-register on a reboot
- New TANDBERG Software Releases
Gatekeeper & Border Controller
TANDBERG Gatekeeper and TANDBERG Border Controller software now available!
N6.1 is a maintenance only release. No new features or functionality are included within this version over the previous release, N6.0.
Changes and Improvements since Previous Version
Security
*The timer that records the Border Controller’s “Up Time” will now continue to increment beyond 49.7 days without wrapping.
*The TANDBERG Border Controller will now ensure all call identifiers ids are unique which will eliminate intermittent call setup failures.
*The TANDBERG Border Controller has been updated to prevent exposure to web based cross-site scripting vulnerabilities.
Multiway (Beta)
During the setup of a Multiway (beta) call through the TANDBERG Border Controller, the setup messages will now include the requested bandwidth of the original call, even if the call has been down sped.
RAS Messaging
*The TANDBERG Border Controller will now accept an LCF from a configured alternate if it is running a version of software prior to Q6.1.
*If the TANDBERG Border Controller received a RRQ message which had been malformed, the box would unexpectedly restart; this issue was been resolved.
*If the TANDBERG Border Controller received an unexpected facility message while in a specific call scenario this would cause the Border Controller to become unstable and subsequently restart, this issue was been resolved.
Registration Control
The TANDBERG Border Controller will no longer allow an additive registration to be accepted without first checking if there is a matching entity in the Allow and/or Deny List Policy.
When using the web interface of the TANDBERG Border Controller, an administrator can now enter a registration restriction pattern with a maximum of 60 characters.
Call Control
An issue has been resolved where the TANDBERG Border Controller became unstable and subsequently restart if the ‘xcommand checkbandwidth’ command was issued on the Traversal Subzone while it is was being used.
An issue has been resolved with the CPL Policy on the TANDBRERG Border Controller that will enforce the authenticated user field to be included when the policy is evoked.
IP
An issue has been resolved with SSH while the TANDBERG Border Controller is running in IPv6 mode.
- New TANDBERG Software Releases
F7 MXP Platform
There have been the following improvements/changes made to TANDBERG MXP systems, available through a software update.
Video
*Low-delay 720p: Improved lip synchronization with HD w720p video format
*Optimal resolutions: Improvements to w576p (1024x576) video resolution. Improvements to the transition of w288p (512x288) to HD w720p (1280x720). Improvements to display the correct aspect ratio for w448p video format.
*Animated layouts now included
*Addition of RateControl for remote users
Network
*Secure management for remote users
*Optimal resolutions
*Multiway
*Site naming
Microsoft OCS 2007
*Presence
*Audio & video
For more in depth release notes please CLICK HERE
- New Microsoft Software Releases
for TANDBERG Compliance
The following security updates were released by Microsoft in February 2008 and apply directly to the TANDBERG Server Appliance. For more information on the security updates themselves, please reference www.microsoft.com and search for the corresponding KB number.
KB 946026: Vulnerability in WebDAV Mini-Redirector Could Allow Remote Code Execution (946026)
KB 947890: Vulnerability in OLE Automation Could Allow Remote Code Execution (947890)
KB 944533: Cumulative Security Update for Internet Explorer (944533)
KB 942831: Vulnerability in Internet Information Services Could Allow Elevation of Privilege (942831)
KB 942830: Vulnerability in Internet Information Services Could Allow Remote Code Execution (942830)
For details, please visit TANDBERG for instructions on how to install Microsoft Windows Service Pack 2 on the TANDBERG Server Appliance.
- New TANDBERG VCS Software Releases
x2.0 for TANDBERG VCS
With today’s release of version X2, the TANDBERG VCS will offer even greater SIP and H.323 inter-working capabilities, making it easier than ever for organizations to migrate their video communications devices to SIP while continuing to future proof their existing H.323 infrastructure.
The following features have been introduced in version X2.0 of the VCS software:
Dual Network Interfaces
*Allows the VCS Expressway to connect to two separate networks in a DMZ deployment.
Easier to manage, quicker to deploy
*Increased usability of the administration web interface.
Extended parity between H323 & SIP
*Encryption supported for H323 – SIP gateway calls.
*Dual video support for H323 – SIP gateway calls.
- New Polycom HDX Software Release
2.0.2
New Features
*New USB Software Upgrade
*New Software Options
*New White Balance Settings for the Polycom EagleEye HD Camera
*Adjustable VGA Input Settings
*Live Music Mode
*Video Scaling Adjustments
*Additional Camera Support
*New API Commands
API: The listen sleep command now works properly.
Camera: If you attached a DVI source to a Polycom HDX8000 HD system, the system sometimes subsequently failed to detect VGA sources. The issue has been corrected.
Encryption: If remote participants dialled in over ISDN to an encrypted multipoint conference hosted on a Polycom HDX system that required downspeeding, some endpoints may have failed to negotiate encryption. This issue has been resolved.
Interoperability (VCON): Problems with placing or receiving H.323 calls between VCON HD3000 and Polycom HDX4000 systems have been corrected.
User Interface/Web Interface: Although the user interface allowed you to set the audio input type to line input or microphone, Polycom HDX8000 HD systems support only line input. The interface now displays the correct options.
- New TANDBERG MXP Software Releases
F6.3 for TANDBERG Videoconferencing Codecs
New Features
Microsoft OCS 2007 integration
F6.3 software supports the integration of Microsoft OCS (Office Communicator Server) 2007, which supports registration, authentication and calls between other endpoints registered to the OCS SIP server.
*Availability: Available on all F-series MXP systems
*Restrictions: DuoVideo, call transfer and presence is not currently supported.
*SRTP is not supported for OCS calls.
*AES (128bit) encryption is not currently support with OCS 2007.
Note: AES (128bit) encryption over SIP is only supported with Transport of TLS
Improvements
Video
*Corrected the missing H.263++ capability during a SIP call when H.264 is enabled [Ref. #
49450].
-
What’s New in the Polycom 8.7 Release?
Monitor Configuration Changes
In Version 8.7, when Monitor 1 is configured as a VGA monitor:
*Monitor 2 can either be disabled or connected to S-Video or composite video
*The VCR monitor input is always enabled and can be connected to S-Video or composite video
These monitor configuration changes only apply to the VSX 7000s, VSX 7000e, and VSX 8000, which support a second monitor and have a VGA port.
SIP and H.323 Switching
With version 8.7, the V Series and VSX systems can switch between H.323 and SIP without restarting.
Switching between H.323 and SIP without restarting only applies to the 128 MB systems (V700, VSX 3000A, VSX 5000, VSX 6000A, VSX 7000s, VSX 7000e, and VSX 8000). All other systems must restart when switching between H.323 and SIP.
If you are unsure of the memory size of your system, refer to the System Information page (System > System Information). The memory size of the system, noted as (64) or (128), now appears after the Model name.
Quality of Service Configuration Enhancements
Version 8.7 includes the following enhancements in Quality of Service (QoS):
*Option to select Auto for the Maximum Transmission Unit Size setting
*Dynamic bandwidth allocation within the call rate when packet loss exceeds 5%; for example, the system could drop the bandwidth for a video call with no motion and then increase the bandwidth up to the call rate only when there is motion.
Video Overlay
You can apply a video overlay that borders the screen at the near site and that provides information for the user. To customize the video overlay, you can choose the color of the border and can enter text to display. For example, you could apply a yellow video overlay with the text, “Medium Security,” to indicate a system that you have designated as somewhat secure.
Whether the VSX system is or is not in a call, the video overlay and customized text both appear on the monitor displaying the near-site video, and the customized text alone appears on the screens in the user interface of the near-site system. The far site cannot see the video overlay and customized text on your system.
Because the video overlay is displayed on top of the monitor image, portions of video or content might be obscured.
Gatekeeper Enhancements
Version 8.7 includes the following gatekeeper enhancements.
Viewing the Current Gatekeeper
The Current Gatekeeper IP Address field displays the IP address of the primary or alternate gatekeeper that is currently active.
Polling and Restoring the Primary Gatekeeper
When Use Gatekeeper is set to Specify or Specify with PIN and the Gatekeeper IP Address is entered (System > Admin Settings > Network > IP > H.323 Settings), V Series and VSX systems can poll the primary gatekeeper’s IP address and re-register to the primary gatekeeper after temporary registration to an alternate gatekeeper.
The V Series or VSX system downloads a list of available alternate gatekeepers from the primary gatekeeper. If the primary gatekeeper becomes unavailable, the system automatically switches to an alternate gatekeeper. Once the primary gatekeeper comes back online, the system re-registers with the primary gatekeeper and displays the primary gatekeeper as the current gatekeeper. This change results in a more controlled environment for the V Series and VSX systems.
Supported gatekeepers include the Polycom PathNavigator™, RADVISION®, and Cisco gatekeepers.
SNMP Enhancements for Remote Management
Version 8.7 supports simple network management protocol (SNMP) version 2c (v2c) for standards-based remote management of the video conferencing system.
IBM Integration for SIP Interoperability
Version 8.7 includes support for SIP sites using Lotus® Sametime® or Lotus Notes® in audio and video calls with V Series and VSX systems. These audio and video calls support instant meetings, scheduled meetings, and Click2Call using the RAS200I Polycom Conferencing Application Server (PCAS).
For more information, refer to the Lotus Sametime or Lotus Notes Integrated Video Conferencing Deployment Guide or User Guide.
Video Freeze
Version 8.7 supports the Freeze Picture command defined in the International Telecommunication Union (ITU) H.320, H.323, H.261, H.263, and H.264 protocols.
Some third-party MCUs may send the Freeze Picture command to sites while switching presenters. The VSX system accepts this command and freezes the people image for up to six seconds. The VSX system also freezes the local picture for up to 30 seconds when ISDN framing is lost.
Video freeze is supported on people video only and on H.323 and H.320 calls only.
Finnish Language
Version 8.7 includes translation of the user interface and user documentation into the Finnish language.
Updated System Name
The memory size of the system, noted as (64) or (128), now appears after the Model name on the System Information page (System > System Information).
New API Commands
The following API commands are new in version 8.7.
overlayname
Sets or gets the video overlay name set on the site.
*Syntax
*overlayname get
*overlayname set “name”
overlaytheme
Sets or gets the video overlay theme set on the site.
*Syntax
*overlaytheme get
*overlaytheme set <0|1|2|3|4|5>
showgatekeeper
Returns the gatekeeper addresses in the API feedback.
*Syntax
*showgatekeeper active
*showgatekeeper primary
*showgatekeeper alternates
*showgatekeeper all
Feedback Examples
*showgatekeeper active returns
*current gatekeeper ip address: 192.168.1.201
*showgatekeeper primary returns
*primary gatekeeper ipaddress: 192.168.1.202
*showgatekeeper alternates returns
*showgatekeeper alternates begin
*showgatekeeper alternates ipaddress 192.168.1.203
*showgatekeeper alternates ipaddress1 192.168.1.204
*showgatekeeper alternates ipaddress2 192.168.1.205
*showgatekeeper alternates end
*showgatekeeper all returns
*showgatekeeper all begin
*showgatekeeper current ipaddress 192.168.1.201
*showgatekeeper primary ipaddress 192.168.1.202
*showgatekeeper alternates ipaddress 192.168.1.203
*showgatekeeper alternates ipaddress1 192.168.1.204
*showgatekeeper alternates ipaddress2 192.168.1.205
*showgatekeeper all end
API Command Changes
The following API commands have been changed in version 8.7.
callpreference
This command has new parameters.
: Sets or gets the supported call types.
gatekeeperip
This command now sets or gets the IP address of the primary gatekeeper.
*VSX 3000A customers may experience flicker and unusual behaviour on their displays when upgrading to version 8.7. This is normal behaviour and it is critical that the system NOT be turned off during this process. The complete upgrade should take 2-3 minutes, and after the upgrade is complete, the system will restart automatically.
- Polycom 1.0.2 Software for the HDX Product Range
What’s New in the 1.0.2 Release?
Version 1.0.2 includes all of the features of previous versions, as well as the following additions:
*Support for Internet Explorer version 7
*Improved remote control IR performance
*New configuration settings for Eagle Eye cameras
Support for Internet Explorer Version 7
With version 1.0.2, you can use Microsoft Internet Explorer 6.x or 7 to access the Polycom HDX system’s web interface.
Improved Remote Control Performance
Operation of the Polycom HDX system’s remote control has been improved in certain high-energy florescent lighting environments. With version 1.0.2, the remote control transmits button signals more reliably and camera panning is smoother.
New Configuration Settings for Polycom Eagle Eye Cameras
With version 1.0.2, you can use the system’s web interface to configure or restore the following Eagle Eye camera settings:
*White Balance
*Brightness
*Black Level
*Colour Saturation
To adjust the Eagle Eye camera’s white balance;
1, On a computer, open a web browser.
2, In the browser address line, enter the system’s IP address to go to the Polycom HDX web interface.
3, Go to Admin Settings > Cameras.
4, If Model is not set to Polycom Eagle Eye for the appropriate camera(s), click the Detect Camera button.
5, Select a value for White Balance.
6, Click Update.
To adjust Eagle Eye camera’s brightness, black level, or colour saturation:
1, On a computer, open a web browser.
2, In the browser address line, enter the system’s IP address to go to Polycom HDX web interface.
3, Go to Admin Settings > Cameras.
4, If Model is not set to Polycom Eagle Eye for the appropriate camera(s), click the Detect Camera button.
5, Click Advanced.
6, Select values for brightness, black level, and colour saturation.
7, Click Update.
To restore the Eagle Eye camera’s default settings:
1, On a computer, open a web browser.
2, In the browser address line, enter the system’s IP address to go to the Polycom HDX web interface.
3, Go to Admin Settings > Cameras.
4, Click Restore. White Balance, Brightness, Black Level, and Colour Saturation are returned to their default values.
- New TANDBERG MXP Software Releases
F6.0 for TANDBERG Videoconferencing Codecs
Camera Software Upgrade
F6.0 software will automatically upgrade a Precision HD camera to software version 3.0Final [ID:30020] when connected to the TANDBERG High Speed Serial Interface (THSI – Data Port 2). This software upgrade will occur 30 seconds after the codec restarts the second time after the endpoint software upgrade. The Precision HD camera is still functional during the upgrade process, but will restart automatically once the software is loaded resulting in no video for 15 seconds.
Firmware Upgrade
When upgrading from a previous version to F6.0, the system will install additional firmware that will add approximately 10-15 seconds to the first boot after upgrade. It is very important that power not be interrupted during this procedure. Because the installation is done very early in the boot process, no display will be shown on the screen. This should not be mistaken as a system failure – continue to let the system boot up as normal.
New Features
TANDBERG Precision HD Camera
With software release F6, the TANDBERG MXP endpoints now support the ability to send and receive HD resolution (w720p) at up to 30 frames per second (fps) with the TANDBERG Precision HD Camera.
Installation Wizard
Helps with the installation and setup of a new video system.
SIP Improvements
A number of usability enhancements as well as new security features.
Multiway Beta
The ability to connect multiple sites during a video call without the use of a built in MCU, or
beyond the limits of an internal MCU (Gatekeeper and MPS required).
System Profiles
To increase the portability and flexibility of the system, the MXP endpoints now support up to 20 system profiles. Profiles are convenient for situations where an endpoint may be shared by several users.
D3.10 for the TANDBERG MCU products
Improvements:
*The MCU will now respond to an SNMP broadcast query
*Resolved issue where the MCU could unexpectedly restart when receiving ISDN bit errors
*When the MCU receives a call from an endpoint using a routed mode gatekeeper it will now
report the E.164 alias of the system as opposed to the IP address of the gatekeeper
*Resolved issue where incoming ISDN calls may fail to fully connect
*Resolved issue where excessive packet may have caused unexpected restarts
TMS11.7 for TANDBERG Management Suite
*Bridging Methods Report -
A new type of report has been added to TMS’s reporting capability which illustrates the methods people use to connect calls.
*Active Directory Group support
*New Auditing Log for changes to TMS
*Reporting Templates
*Bridging Phonebook imports and export to file
*TANDBERG Movi Support
*TANDBERG Entrypoint Support
*TANDBERG Experia Support
*TANDBERG Content Server Clustering Support
* Radvision/Cisco MCU Support Update
*Enhanced SNMP Scanning to increase speed of detecting offline systems
*Enhanced Ad-hoc Meeting Resolution – Resolution for MultiSite calls
|
|
Print
this page
Email this page
