Responsibility to consult the organizations responsible for the desktop, testing, and/or production environments These decisions areīased upon the best information available as of the most current date. The VA Decision Matrix displays the current and future VA IT position regarding different releases of a TRM entry. TRM Technology, obtained from the vendor (or from the release source). The Vendor Release table provides the known releases for the For additional information or assistance regarding Section 508, please contact the Section 508 Office at Decisions Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. This technology has not been assessed by the Section 508 Office.
Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation. Users must ensure sensitive data is properly protected in compliance with all VA regulations. Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 61 VA Directives 6004, 6513, and 6517 and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). For more information on the use of cloud services and cloud-based products within VA, including VA private clouds, please see the Enterprise Cloud Solutions Office (ECSO) Portal at: Cloud services provided by the VAEC, which are listed in the VAEC Service Catalog, and those controlled and managed by an external Cloud Service Provider (i.e.
#Cisco jabber for windows phone only software#
This includes technologies deployed as software installations on VMs within VA-controlled cloud environments (e.g. The TRM decisions in this entry only apply to technologies and versions owned, operated, managed, patched, and version-controlled by VA. Note: The implementation of mobile technology application that operates on Mobile Operating System must be reviewed and approved by the Mobile Technology and Endpoint Security Engineering Team: See Category tab/Comparable for the corresponding Mobile entry. This entry only covers the Desktop Edition of this technology.
More information on the proper use of the TRM can be found on theĬisco Jabber for Windows streamlines communications by unifying presence, instant messaging, video, voice, voice messaging, screen sharing, and conferencing capabilities securely into one client on a user`s desktop. Based on the chart here, it appears receive screen share will work: This bug is to more clearly have the limitation documented, especially in the release notes.Technologies must be operated and maintained in accordance with Federal and Department security and This is believed to be a product limitation with MRA at the time of this filing and the bug is filed to document the limitation. Video desktop sharing using BFCP is not supported if Trusted Relay Point or Media Termination Point are enabled on the software phone device.Ĭisco Bug: CSCuu22458 – Document screen sharing limitation forġ0.6(2) Description (partial) Symptom: Screen Sharing option will be grayed out in Jabber when connected over MRA. Remote screen control is not supported with When on a call select … > Share screen to Handles the BFCP packets that users transmit when using video desktop sharingĬapabilities. Applies to Cisco Jabber desktop clients, Cisco Jabber for mobile clients can only receive BFCP screen shares.this is a screen sharing limitation for Jabber over MRAįloor Control Protocol (BFCP) screen share is controlled by Cisco UnifiedĬommunications Manager.
0 kommentar(er)
