============================================================= readme_va.txt: Dialogic(R) NaturalAccess(TM) Video Access 3.2 GA Release, February 2009 ============================================================= (C) Copyright 2005-2009 Dialogic Corporation ============================================================= ************************************************************* *******************IMPORTANT NOTICES************************* The product(s) to which this material pertains is/are part of the NMS Communications Platforms business sold by NMS Communications Corporation (NMS) to Dialogic Corporation (Dialogic) on December 8, 2008. All copyrights associated with the product(s) and materials previously held by NMS are now owned by Dialogic Corporation. Due to time constraints, the references to NMS or NMS Communications herein or elsewhere have not been changed, but all such references should be understood to be references to Dialogic and for clarity any end user license agreements associated with the product(s) and materials are between you and Dialogic. For the availability of this software package for other operating system platforms, or for updates for this software package, please check the Support and Downloads page at http://www.nmscommunications.com. *********************** FILE CONTENTS *********************** This information presented by this readme is organized as follows: 1. Video Access 3.2 Product Overview 2. Product Compatibility 3. New Features/Bug Fixes 4. Software Installation 5. Licensing the Product 6. VA Release Compatibility Issues 7. List of Files Shipped with Video Access 3.2 8. Documentation 9. CG Board Port Densities ************************************************************* --------------------------------------- 1. Video Access 3.2 Product Overview --------------------------------------- Video Access 3.2 (VA3.2) is a set of add-on software APIs that enable development of video applications within the Dialogic NaturalAccess (NA) framework. VA3.2 is an upgrade for VA3.1. VA3.2 is a replacement for VA3.0, not an upgrade. It is functionally equivalent to VA3.0, except that all fast call setup features are now license-protected. Concerning what has changed in VA3.2, see Section 3 for a description of new features and bug fixes; see Section 5 for further details of the licensing changes; Section 6 for notes on VA3.2 software compatibility with respect to earlier releases; and Section 8 for a summary of additional software changes in VA3.2 per their impact on the supporting documentation set. VA3.2 is composed of two principal components: - 3G-324M Interface - Video Messaging Server Interface As with earlier releases, VA3.2 seamlessly interoperates with the Dialogic® Software Video Transcoder product (SVT releases 2.0 and 2.1), allowing video applications to support an expanded set of services and features. VA3.2 does not modify NaturalAccess features. It does not degrade performance for non-video applications, provided that video and non-video applications are not running concurrently. ------------------------- 2. Product Compatibility ------------------------- 2.1 This product has been built and tested on the following operating systems with the listed versions of NaturalAccess: -- SUN Solaris 10 NA 2005-1 SP5 for Sparc Solaris 10 (32 bit), Update 3 gcc version 3.3 NA 8.1 for Sparc Solaris 10 (32 bit), Update 6 gcc version 3.3 -- Redhat Enterprise LINUX ES,version 4.0 NA 2005-1 SP5 for Red Hat Enterprise Linux 4, Update 4 gcc version 3.4.4 20050721 (Red Hat Linux 3.4.4-2) NA 8.1 for Red Hat Enterprise Linux 4, Update 6 gcc version 3.4.4 20050721 (Red Hat Linux 3.4.4-2) --Windows Server 2003: Standard Edition NA 2005-1 SP5 for Windows 2003 Server R2, SP1 Enterprise Edition Microsoft Visual Studio 6.0 SP 5 NA 8.1 for Windows 2003 Server R2, SP2 Enterprise Edition Microsoft Visual Studio 6.0 SP 5 2.2 Supported Dialogic CG Series boards: CG 6000 CG 6000C CG 6060 -3200 CG 6060 -4200 CG 6060C-4200 CG 6500C-3200 CG 6500C-6400 CG 6500C-9600 CG 6565 -3200 CG 6565 -6400 CG 6565C-3200 CG 6565C-6400 CG 6565C-12800 CG 6565e-3200 (NA 8.1 only) CG 6565e-6400 (NA 8.1 only) 2.3 System Requirements: System requirements depend on many factors, including the architecture and scalability of the application. Running tests with the expected configuration is necessary to determine the optimal processor speed and memory requirements. As a guideline though we recommend the following general system requirements for VA3.2: Processor: UltraSparcIIi at 1.5 GHz (or equivalent) Intel Xeon, 2.4 GHz (or equivalent) Memory: At least 1 GB 2.4 Audio Codecs Not all audio codec technology typically used by Video Access applications are included in the basic NaturalAccess releases. Specifically, NaturalAccess has special provisions for G.723.1, and G.729. Please contact Dialogic Sales for details. *** NOTE: The default configuration of Video Access uses only those codecs provided with the default NaturalAccess installation. 2.5 Video Transcoding under Video Access Demo Application (vmsamp) To interoperate with the Dialogic Software Video Transcoder (SVT) when using vmsamp, follow the installation instructions for SVT. This will add the following files to the Video Access installation: For Solaris and Linux -- For SVT 2.0 and 2.1 /opt/nms/include/trcapi.h /opt/nms/lib/libtrcapi.so /opt/nms/include/trcdefs.h /opt/nms/include/trctypes.h For Windows -- For SVT 2.0 and 2.1 C:\nms\include\trcapi.h C:\nms\include\trcdefs.h C:\nms\include\trctypes.h C:\nms\bin\trcapi.dll C:\nms\lib\trcapi.lib -- Use makefile.trc to compile and link vmsamp with the SVT. -- Use makefile.notrc to compile and link vmsamp without the SVT. Default utilities for compilation: Windows - nmake Others - gmake *** NOTE: Installation of the SVT TRC package results in the inclusion of other files in addition to those listed above. For the complete list, consult the Readme file for your SVT release. ------------------------- 3. New Features/BugFixes ------------------------- 3.1 This section briefly describes new features in Video Access 3.0 (and thus in VA3.2). Complete descriptions of the following features are available in the supporting product documentation for this release. 3.1.1 3G-324M Interface - Enhanced 3G-324M terminal compatibility - Enhanced 3G-324M signaling capability (h324ModifyOutVideoChannelParam) - Faster call setup - WNSRP support - MONA support - Optimization in H.245 message processing - H.264 video codec - Audio/Video synchronization - RTCP reports in compliance with RFC3550 - Additional API's in support of synchronization with RTCP - Video jitter buffer latency/control - Enhanced tracing/logging - IPv6 support - CG6060 support 3.1.2 Video Messaging Server - Enhanced SIP video terminal compatibility - Play/Record codecs (NMS-packetized format) - H.264 video codec - Enhanced 3GP support - Random access - Streaming Server profile w/SDP - H.264 video codec support - Audio/Video synchronization - RTCP reports in compliance with RFC3550 - Additional API's in support of synchronization with RTCP - MMFI skew correction - IPv6 support - CG6060 support 3.1.3 Additional VA utilities - h324Extract (used to extract audio and video data from a recorded TDM bearer channel data and to create raw audio and video files) 3.2 This section briefly describes new features in Video Access 3.2 that were not in Video Access 3.0 or Video Access 3.1. Complete descriptions of the following features are available in the supporting product documentation for this release. 3.2.1 3G-324M Interface - H.263 Profile 3 signaling support - CG6565e support (with NA 8.1 only) 3.2.2 Video Messaging Server - H.263 Profile 3 play/record support - CG6565e support (with NA 8.1 only) 3.3 This section describes the bug fixes since the GA release of VA3.1. VA3.2 includes all of the bug fixes from VA3.1 Rollup Patches #1, #2, and #3, plus additional bug fixes since Rollup Patch #3. These are desribed below. Note: There have also been CG-board behavioral issues related to video stream transmission and reception as well as certain video quality degradation issues that have been fixed. These fixes are included inside of the NaturalAccess product, either with patches or new releases. See Section 4 for Product Compatibility. VA3.1 Rollup patch #1 fixed the following bugs: _______________________________________________ 5212: Need additional H.324 start timeout control. 5227: Crash in CMH245Control::SendOLC (). After a successfull MONA negotiation if the application tries to call h324ModifyOutVideoChannelParam() the a crash occurs in the function CMH245Control::SendOLC(). 5228: Crash in CMH245Control::muxifNotifyOLCAccepted() After a successfull MONA negociation if the application crashes in CMH245Control::muxifNotifyOLCAccepted() after receiving close/open logical channel (h324ModifyOutVideoChannelParam() from the remote side). 5229: Crash in CMH245Control::getListOfVideoCodecs() After a successfull MONA negociation if the application crashes in CMH245Control::getListOfVideoCodecs() after receiving close/open logical channel (h324ModifyOutVideoChannelParam() from the remote side) 5230: H.245 library crash when a call is disconnected. 5231: An incoming nonstandard UII makes the app crash. 5232: An event does not pop up after a long call duration (more than 256 NSRP commands). 5242: T401 timeout is reported after H324EVN_STOPPED is received. 5244: Wrong/missing mux flag. The multiplexer created a TDM bitstream where there was occasionally a missing flag byte sequence before a video PDU. 5245: Undocumented MMFI error codes. The MMFI library sometimes returns an undocumented error code (e.g. -1). These error codes have been replaced by documented values. Informational trace messages have also been added. 5246: A WNSRP message contains the wrong mux entry in case of a large TCS. If the board sends a large TCS in WNSRP, then the message is segmented and the second segment is sent on the mux entry 0 instead of 15. 5247: The MMFI library's API mmOpenStream() sometimes crashes during a record under load test. VA3.1 Rollup patch #2 fixed the following bugs: _______________________________________________ 5248: The MMFI function mmWriteStream() sometimes returns with ByteCount = 0. 5249: H.245 error during negotiation with Softbank terminal 902T. The optional Port Number in the OLC was not being decoded properly causing the entire message to be discarded. 5251: H.245 error during negotiation with Motorola handset V1050. The error was reported during opening of a video OLC. 5255: Error in H324 negotiation in AL3 mode. When forcing AL3 mode the H324EVN_LCD is received after H324EVN_MEDIA_SETUP_DONE. 5257: No H324EVN_STOP_DONE event received during load test if there are setup failures. 5258: H.324 Middleware crash when receiving H.245 message. Problem related to optional port number in OLC message. 5259: H.324 Middleware crash in h324Stop(). Occasionally when invoking h324Stop(), a crash occurs in removeTimersRequest(). 5263: MMFI crash in mmOpenFile() & mmGetFilInfo(). mmGetFileInfo() crashing on a corrupted 3GP file. 5264: MMFI crash in mmOpenStream() when recording in MPEG4 with SendDCITo3gpLib set to 1. 5266: H.324 negotiation hangs when NaturalAccess is used with DefaultServer = localhost. 5269: Wrong MSD response during H.245 negotiation. VA3.1 Rollup patch #3 fixed the following bugs: _______________________________________________ 5278: H324 FrameCheckSum wrong for Linux. Endian issue in log message. 5307: DSP crash - The H.223 demuxltiplexer crashed when processing a PDU containing audio and control data where the size of the control data was larger than 100 bytes. 5308: DSP crash - The H.223 multiplexer crashed when it received large h245 messages. 5313: H.245 stack timeout causing state machine conflict in H.324 Middleware leading to a missing H324EVN_STOP_DONE event. 5314: H.324 functions occasionally hang after a successful negotation. Mutex not getting unlocked when PMSYNC_CHANGED happens with MONA disabled 5315: The MMFI function mmOpenStream() ignores the application initialization of the parameter rtpPayloadSize (part of the data structure DATA_FORMAT_DESC) and hard codes the parameter value to 1432. VA3.2 includes the additional bug fixes: _______________________________________ 5331: H.324 Middleware crash when calling h324Delete on Linux due to excess file descriptors. 5334: H.324 Middleware crash when h324Start fails. 5345: MMFI buffer overwrite due to a buffer underestimation for large frames segmented across many packets. 5346: H.324 Middleware crash due to race conditions and message queuing. 5352: H.324 negotiation failures due to FCS calculation errors when H.245 control PDU's are segmented. 5353: H.324 negotiation failures with MONA due to short stuffing sequence. 5370: H.324 negotiation problem receiving early video during MONA ACP call setup. 5371: Missing event due to NSRP sequence number rollover. 5372: Missing video data due to extra bytes inserted in the stream at the beginning of an H.324 session. Added a video buffer flush in H.223 demultiplexer at start of session. 5374: H.324 memory leak when using ctaccess LOCALHOST mode. ------------------------- 4. Software Installation ------------------------- 4.1 NaturalAccess VA3.2 is compatible with two different versions of NaturalAccess. NaturalAccess 8.1 is the most recent release of NaturalAccess. NaturalAccess 8.1 must be installed before installing VA3.2. Refer to the NaturalAccess installation booklet for detailed installation instructions. *** NOTE: For NaturalAccess 8.1 documentation, please review the corresponding documentation available from the Web site (www.nmscommunications.com). VA3.2 can also be used in conjunction with NaturalAccess 2005 SP5, which must be installed before installing VA3.2. After installing NaturalAccess 2005 SP5, the following NaturalAccess patches should be installed (in order) prior to installing VA3.2: 6160 6214 6215 These patches include all relevant video-related bug fixes inside NaturalAccess that are included by default in NaturalAccess 8.1. Please contact Dialogic Technical Services for these patches. 4.2 Video Access For Solaris 10 and Linux: 1. Log on as root. 2. Uninstall prior versions of Video Access before beginning this installation by invoking the following shell script: For Solaris: pkgrm vaccess For Linux: rpm -e vaccess 3. Create a directory for the file to be downloaded: mkdir download-directory 4. Access www.nmscommunications.com, and download the file for your platform to the download directory. 5. Go to the download directory: cd download-directory 6. Uncompress and untar the downloaded file: uncompress .tar.Z tar xvf .tar 7. Invoke the following shell script from the download directory of to install VA3.2: "./install" For Windows: 1. Log on as a member of the Administrators group. 2. Uninstall prior versions of Video Access before beginning this installation using the following procedure: Click Start->Settings->Control Panel. Double click Add/Remove Programs. Select vaccess. Click Remove. 3. Create a directory for the file to be downloaded. 4. Access www.nmscommunications.com, and download the file for your platform to the download directory. 5. Go to the download directory: cd download-directory 6. Double-click on the .exe file and unzip it specifying the download directory as the destination 7. From the download directory double-click on install.bat. ------------------------- 5. Licensing the Product ------------------------- To use VA3.2, a license file allowing up to a specified number of Video Access ports, must be purchased from Dialogic. Licenses can be obtained for 4, 24, 30, 48, 60, 72, 90, 96, and 120 simultaneous Video Access ports. Note: Previously-purchased VA3.1 licenses can be used with VA3.2. New licenses do not need to be ordered. Each platform must have a one or more valid license files installed. Product activation cannot be transferred from one host platform to another. This must be taken into consideration when planning standby or replacement equipment. 5.1 Determining the Product Identification Number Use the License Manager Tool to display the product ID number. To start the License Manager Tool, navigate to the License Manager installation directory and enter the command as below: For Windows: Directory: cd C:\nms\nmslm Command: nmslm_tool -c For Solaris 10 and Linux: Directory: cd /opt/nms/nmslm/bin Command: ./nmslm_tool -c The output should look like this: NMS License Manager tool. Version : 2.2 Copyright 2004 NMS Communications. All right reserved. Current product ID: 7e4e-0156-0b91-4159-3d21-f408 Available Interfaces: eri0 (Product ID: 7e4e-0156-0b91-4159-3d21-f408) 5.2 Obtaining Licenses An evaluation license for 4 ports and 30 days is included with the installation package for this release. Deployment of this license is described in section 5.3. Production licenses are obtained through a purchase order request placed through Dialogic Operations. The purchase order must specify the product name (VA3.2), the host specific product ID number (see Section 5.1), and a part number(which indicates the license type of interest as well as the number of desired Video Access ports). The part numbers for the various Video Access port densities are: VAL310004 VA 3.x, Runtime License 4 Port VAL310024 VA 3.x, Runtime License 24 Port VAL310030 VA 3.x, Runtime License 30 Port VAL310048 VA 3.x, Runtime License 48 Port VAL310060 VA 3.x, Runtime License 60 Port VAL310072 VA 3.x, Runtime License 72 Port VAL310090 VA 3.x, Runtime License 90 Port VAL310096 VA 3.x, Runtime License 96 Port VAL310120 VA 3.x, Runtime License 120 Port VA3.2 capacity upgrade licenses in increments of 24 or 30 ports can also be ordered: VAL310024U VA 3.x, Capacity Upgrade License 24 Port VAL310030U VA 3.x, Capacity Upgrade License 30 Port Video Access customers upgrading from previous Video Access release (pre-3.0) should obtain upgrade licenses, in accordance with the following part numbers: VAL311004 VA 3.x, Runtime License Upgrade 4 Port VAL311024 VA 3.x, Runtime License Upgrade 24 Port VAL311030 VA 3.x, Runtime License Upgrade 30 Port VAL311048 VA 3.x, Runtime License Upgrade 48 Port VAL311060 VA 3.x, Runtime License Upgrade 60 Port VAL311072 VA 3.x, Runtime License Upgrade 72 Port VAL311090 VA 3.x, Runtime License Upgrade 90 Port VAL311096 VA 3.x, Runtime License Upgrade 96 Port VAL311120 VA 3.x, Runtime License Upgrade 120 Port A developer license can be ordered as follows: VAD310120 VA 3.x, Developer Runtime License 120 Port In VA3.2, fast call setup (FCS) features are individually license-protected. These features are made and sold under license from Dilithium Networks, Inc. To enable these features, it is now necessary to order the appropriate additional license(s). Details of FCS licenses are as follows: Note: Previously-purchased VA3.1 FCS licenses can be used with VA3.2. New licenses do not need to be ordered. MONA Licenses VAM310004 VA 3.x, MONA FCS License 4 Port VAM310024 VA 3.x, MONA FCS License 24 Port VAM310030 VA 3.x, MONA FCS License 30 Port VAM310048 VA 3.x, MONA FCS License 48 Port VAM310060 VA 3.x, MONA FCS License 60 Port VAM310072 VA 3.x, MONA FCS License 72 Port VAM310090 VA 3.x, MONA FCS License 90 Port VAM310096 VA 3.x, MONA FCS License 96 Port VAM310120 VA 3.x, MONA FCS License 120 Port WNSRP Licenses VAW310004 VA 3.x, WNRSP License 4 Port VAW310024 VA 3.x, WNRSP License 24 Port VAW310030 VA 3.x, WNRSP License 30 Port VAW310048 VA 3.x, WNRSP License 48 Port VAW310060 VA 3.x, WNRSP License 60 Port VAW310072 VA 3.x, WNRSP License 72 Port VAW310090 VA 3.x, WNRSP License 90 Port VAW310096 VA 3.x, WNRSP License 96 Port VAW310120 VA 3.x, WNRSP License 120 Port Packed H.245 Messages Licenses VAP310004 VA 3.x, Packed H.245 Msg License 4 Port VAP310024 VA 3.x, Packed H.245 Msg License 24 Port VAP310030 VA 3.x, Packed H.245 Msg License 30 Port VAP310048 VA 3.x, Packed H.245 Msg License 48 Port VAP310060 VA 3.x, Packed H.245 Msg License 60 Port VAP310072 VA 3.x, Packed H.245 Msg License 72 Port VAP310090 VA 3.x, Packed H.245 Msg License 90 Port VAP310096 VA 3.x, Packed H.245 Msg License 96 Port VAP310120 VA 3.x, Packed H.245 Msg License 120 Port Orders for any of these VA3.2 license types should be sent to Dialogic Operations using the following email address: License_Administrator@nmss.com Dialogic Operations will then provide the license information in the form of two files: .lic file: A binary license file to deploy the licenses .xml file: A text file describing the license content The .lic file and the .xml file are named according to the number of the purchase order. After obtaining the license from Dialogic Operations, make a backup copy of the license files and copy them onto the machine where the licenses will be deployed. For example, the following email requests a regular 60 port runtime license: To: License_Administrator@nmss.com Subject: VA3.2 License Request Message Information: Product Name: Video Access 3.2 Product ID: 7e4e-0156-0b91-4159-3d21-f408 Part Number: VAL310060 The response to this request would be sent from Dialogic Operations and would include a .lic file and a .xml file providing the requested licensing, as described above. *** NOTE: - Valid licenses for VA 1.0 or VA 2.01 will not work with the VA3.2 release (See also Section 6). - As a result of additional license checking introduced into the Message Server MMFI library, the use of certain VA3.2 utilities is constrained as follows: - 3gpapp can only be used on a machine with a valid VA3.2 license. - h324Extract can only be used on a machine with a valid VA3.2 license when the utility is being used to convert raw files to a 3GP file. - Customers with VA3.0 licenses should replace these with VA3.2 licenses. 5.3 Deploying a License File Evaluation license for Solaris and Linux: Copy the license file nva-eval.lic from /opt/nms/vaccess/license Evaluation license for Windows: Copy the license file nva-eval.lic from C:nms/vaccess/license Production license: Use the received license file (.lic) Navigate to the nmslm installation directory, and use the License manager Tool to deploy the license as below: For Solaris and Linux: Directory for ".lic" file: /opt/nms/nmslm/bin nmslm installation directory: cd /opt/nms/nmslm/bin License Manager Tool: ./nmslm_tool -c .lic For Windows: Directory for ".lic" file: C:\nms\nmslm nmslm installation directory: cd C:\nms\nmslm License Manager Tool: nmslm_tool -c .lic The output should look like this: NMS License Manager tool. Version : 2.2 Copyright 2005 NMS Communications. All right reserved. Current Product Id : 7e4e-0156-0b91-4159-3d21-f408 Deploying license < license_file_name >.lic Updating Server... Update complete. If license deployment fails, check the following: Make sure either NaturalAccess 2005-1 SP5 or NaturalAccess 8.1 was successfully installed and the platform was restarted. Make sure the license is being deployed on the platform that matches the product ID supplied in the original license purchase order. Remember that the license is tied to the hardware. A hardware change could require a license update and/ or replacement. If a problem persists, contact Dialogic support. ----------------------------------- 6. VA Release Compatibility Issues ----------------------------------- 6.1 License Compatibility Licenses for VA 1.0 and VA 2.0 licenses will no longer work with VA3.2. VA3.0 and VA3.1 licenses remain compatible with VA3.2. If transitioning from VA3.0 to VA3.2, separate licenses are required to enable the fast call setup features of VA3.2. Transitioning from VA3.1 to VA3.2 does not require new fast call setup licenses. Refer to Section 5 for license information. 6.2 NaturalAccess Compatibility VA3.2 has been qualified with the following versions of NaturalAccess: NA 8.1. NA2005-1 SP5 plus patches 6160, 6214, 6215. 6.3 Compatibility with Earlier Video Access Releases VA3.2 remains backwards compatible with VA 2.01 APIs. However, it is no longer compatible with VA 1.0 APIs. When upgrading from VA 2.01 or VA 1.0 be sure to remove "isd0" from any resource pools in the board config files (to safeguard against the board crashing). 6.4 CG Board Configuration File Compatibility As stated in section 6.2, VA3.2 requires NA 8.1 or NA2005-1 SP5. Customers transitioning from an earlier NaturalAccess 2005 Service Pack (including SP4) and using a CG6060 or CG6565 board will not be able to use their earlier CG board configuration files without modification. The following new lines need to be added to the configuration file in order for the board to boot properly: DSP.C5x[0..N].CmdQSize = 0x100 DSP.C5x[0..N].DataInQStart = 0x2100 Where N = the last DSP used in the Mux DSP pool. The lines above can precede the following keywords in the existing configuration file: DSP.C5x[0..N].DataInQSize = 0x800 DSP.C5x[0..N].DspOutQStart = 0x2900 DSP.C5x[0..N].DspOutQSize = 0x900 Please refer to one of the following config files for the CG6060 and CG6565 delivered with the product for examples: o video_mail_6060.cfg o video_mail_6060_ipv6.cfg o video_mail_6565.cfg o video_mail_6565_ipv6.cfg ----------------- 7. List of Files ----------------- For Solaris and Linux: /opt/nms/bin/ vmsamp 3gpapp linemon vaccess.sgn h324Extract /opt/nms/cg/cfg/ video_mail_6000.cfg video_mail_6000_ipv6.cfg video_mail_6060.cfg video_mail_6060_ipv6.cfg video_mail_6500.cfg video_mail_6500_ipv6.cfg video_mail_6565.cfg video_mail_6565_ipv6.cfg /opt/nms/cg/cfg/ h324.cfg /opt/nms/cg/load/ mux.f54 mux.f41 /opt/nms/include/ h324def.h avoptions.h codecsdef.h mmfi.h /opt/nms/lib/ libnmsh245.so libh324api.so libmmfi.so /opt/nms/vaccess/license/ nva-eval.lic /opt/nms/vaccess/demos/vmsamp/ vmsamp makefile.trc makefile.notrc *.cpp *.h For Windows: C:\nms\bin\ vmsamp.exe 3gpapp.exe linemon.exe vaccess.sgn h324.dll h324Extract.exe C:\nms\cg\cfg\ video_mail_6000.cfg video_mail_6000_ipv6.cfg video_mail_6060.cfg video_mail_6060_ipv6.cfg video_mail_6500.cfg video_mail_6500_ipv6.cfg video_mail_6565.cfg video_mail_6565_ipv6.cfg C:\nms\vaccess\cfg\ h324.cfg C:\nms\cg\load\ mux.f54 mux.f41 C:\nms\include\ h324def.h avoptions.h codecsdef.h mmfi.h C:\nms\lib\ h324.lib mmfi.lib C:\nms\vaccess\license\ nva-eval.lic C:\nms\vaccess\demos\vmsamp vmsamp.exe makefile.trc makefile.notrc *.cpp *.h ----------------- 8. Documentation ----------------- Video Access documentation is available on the Software and Documentation downloads page on the web site (www.nmscommunications.com). You can: o Download or view Video Access manuals in HTML format. o Print manuals using the Adobe Acrobat Reader available from www.adobe.com. The HTML documentation is best viewed with: o Internet Explorer 6.0 or later o Mozilla 1.4 or later o Netscape 6.2 or later 8.1 Documentation Changes in VA3.2 For VA3.2, there are only minor documentation changes since VA3.0 and since VA3.1. Changes from VA3.0 to VA3.1: 3G-324M Interface Developer's Reference Manual: o Changing the defaults for the pack_h245 field in the Initializing the H.324M Middleware topic. o Adding a note about obtaining licenses for packed H.245 messages, WNSRP, and MONA in the Enabling fast call setup topic. o Adding a defaults column to the tables in the following topics: - msp_ENDPOINT_RTPFDX_IFRAME_NOTIFY_CTRL - msp_ENDPOINT_RTPFDX_OUT_OF_BAND_DCI - msp_ENDPOINT_RTPFDX_RTTS_CTRL o Replacing the BOOL data type with H324_BOOL in the following topics: - H324Start - h324SubmitEvent - H324_FAST_CALL_SETUP_PARAMS - H324_LCD - H324_START_PARAMS - H324_TERMP_CAPS o Other minor changes. Changes from VA3.1 to VA3.2: 3G-324M Interface Developer's Reference Manual: o Adding the following parameters for H.324M Middleware configuration: - LegacySyncFlagThreshold - StartTimeoutDuration o Added H.263 Profile 3 as a supported video format and added a section on how to negotiate H.263 Profile 3 o Added H324EVN_INTERNAL_EVENT Video Messaging Server Interface Developer's Reference Manual: o Added H.263 Profile 3 as a supported video format Video Mail Application Demonstration Manual: o Added "enableH263Profile3" parameter for 324M configuration Video Access Utilities Manual: o Added 3gpapp mtu size parameter 8.2 Errata from VA3.1 The following errate in the VA3.1 3G-324M Interface Developer's Reference Manual have since been fixed. o Concerning the max_n402_counter parameter in the section "Initializing the H.324M Middleware", please note the following discrepancy. The documentation states: "(Applies only when WNSRP is enabled.) The H.324M Middleware switches to NSRP mode when it receives max_n402_counter NSRP commands or responses." Whereas, to be consistent with the actual VA3.2 implementation, the documentation should state: "(Applies only when WNSRP is enabled.) The H.324M Middleware switches to NSRP mode when it receives max_n402_counter NSRP responses." o Concerning the field "length" described in the section "H324_User_Input_Indication" please note the following discrepancy. The documentation describes "length" as: "Length of time, in seconds, the keystrokes in the data field were pressed." The field "length" should be described as: "Length of the NULL terminated string data for alphanumeric and signal messages. Memory size of data for non-standard messages. Note: For non-standard messages, data is not NULL terminated." o Note that the following events signal the completion of the video channel parameters modification procedure, which is triggered by the h324ModifyOutVideoChannelParam function: - H324EVN_CHANNEL_CLOSE_FAILED: the (bi-directional) channel could not be closed, but is still in active state. - H324EVN_MEDIA_SETUP_FAILED: an issue occured when attempting to close or re-establish the Video Channel. The video channel is in inactive state. - H324EVN_LCD: the video channel was properly Re-established. Also, note that H324EVN_CHANNEL_CLOSED is just a state transition information event; it does not signal the completion of the channel parameters modification procedure. Other Manuals o References to "VA3.0" in all VA manuals delivered with VA3.2 should be interpreted as referring to "VA3.2". --------------------------- 9. CG Board Port Densities --------------------------- 9.1 3G-324M Interface The 3G-324M Interface can control one or more CG boards. The following table lists the port density performance numbers for the supported CG boards that use full-duplex channels. Host CPU calculations are not addressed by this table. ============================================================== Board Description /3200 /4200 /6400 /9600 /12800 Type MIPS MIPS MIPS MIPS MIPS ============================================================== CG 6565C Pass-through 120 N/A 120 N/A 120 -------------------------------------------------------------- With audio xcoder 60 N/A 120 N/A 120 ============================================================== CG 6565(e)Pass-through 120 N/A 120 N/A N/A -------------------------------------------------------------- With audio xcoder 60 N/A 120 N/A N/A ============================================================== CG 6060/C Pass-through 60 60 N/A N/A N/A -------------------------------------------------------------- With audio xcoder 60 60 N/A N/A N/A ============================================================== CG 6500C Pass-through 120 N/A 120 120 N/A -------------------------------------------------------------- With audio xcoder 48 N/A 96 120 N/A ============================================================== CG 6000/C Pass-through 48 N/A N/A N/A N/A -------------------------------------------------------------- With audio xcoder 48 N/A N/A N/A N/A ============================================================== Running the board with an audio transcoder allows AMR to G.711 conversion. Under the following conditions, the port density performance numbers shown do not apply and must be recalculated: o Codec other than G.711. o Board used simultaneously for multiple functions (for example, running the 3G-324M Interface and the Video Messaging Server Interface). 9.2 Video Message Server Interface The Video Messaging Server Interface can control one or more CG boards. The following table presents the port density performance numbers data for the supported CG boards. Host CPU calculations are not addressed by this table. ============================================================== Board Description /3200 /4200 /6400 /9600 /12800 Type MIPS MIPS MIPS MIPS MIPS ============================================================== CG 6565C Half Duplex (play or record) 120 N/A 120 N/A 120 No audio xcoding -------------------------------------------------------------- With audio xcoding * N/A * N/A * ============================================================== CG 6565(e)Half Duplex (play or record) 120 N/A 120 N/A N/A No audio xcoding -------------------------------------------------------------- With audio xcoding * N/A * N/A N/A ============================================================== CG 6060/C Half Duplex (play or record) 75 75 N/A N/A N/A No audio xcoding -------------------------------------------------------------- With audio xcoding * * N/A N/A N/A ============================================================== CG 6500C Half Duplex (play or record) 90 N/A 120 120 N/A No audio xcoding -------------------------------------------------------------- With audio xcoding * N/A * * N/A ============================================================== CG 6000/C Half Duplex (play or record) 60 N/A N/A N/A N/A No audio xcoding -------------------------------------------------------------- With audio xcoding * N/A N/A N/A N/A ============================================================== * When using audio transcoding, the port density numbers must be calculated based upon the specific audio codec type. The port densities shown in the table support video streams that have the following characteristics: o H.263 baseline level 10 o MPEG-4 simple profile level 0 o H.264 baseline level 1 These densities do not apply and must be recalculated if the video stream profile and level make the video bit rate exceed 64 kbit/s. They must also be recalculated if the board: o Is required to handle functionality in addition to play and record, such as redirecting traffic from another source as in a streaming application. o Is used simultaneously for multiple functions (for example, running the Video Messaging Server and the 3G-324M Interface on the same board). o Is running both Video Access and NaturalAccess applications concurrently. o Performs playing and recording of audio and video concurrently. In this case, the density numbers are effectively reduced by half in the pass-through (no audio transcoding) configuration. 9.3 Combined 3G-324M Interface and Video Message Server Interface The Video Messaging Server Interface can be combined with the 3G-324M Interface on the same board. The following table presents the port density performance data for the supported CG boards. Host CPU calculations are not addressed by this table. ============================================================== Board Description /3200 /4200 /6400 /9600 /12800 Type MIPS MIPS MIPS MIPS MIPS ============================================================== CG 6565C Half Duplex (play or record) 120 N/A 120 N/A 120 No audio xcoding -------------------------------------------------------------- CG 6565(e)Half Duplex (play or record) 120 N/A 120 N/A N/A No audio xcoding -------------------------------------------------------------- CG 6060/C Half Duplex (play or record) 40 40 N/A N/A N/A No audio xcoding -------------------------------------------------------------- CG 6500C Half Duplex (play or record) 90 N/A 90 90 N/A No audio xcoding -------------------------------------------------------------- CG 6000/C Half Duplex (play or record) 30 N/A N/A N/A N/A No audio xcoding -------------------------------------------------------------- When using audio transcoding, the port density numbers must be calculated based upon the specific audio codec type. The port densities shown in the table support video streams that have the following characteristics: o H.263 baseline level 10 o MPEG-4 simple profile level 0 o H.264 baseline profile level 1 These densities do not apply and must be recalculated if the video stream profile and level make the video bit rate exceed 64 Kbit/s. They must also be recalculated if the board: o Handles functionality in addition to play and record such as redirecting traffic from another source, as in a streaming application. o Is used for audio format conversion (audio transcoding or audio silence detection). o Is used to play video that is greater than baseline level 10 for H.263, simple profile level 0 for MPEG-4 (QCIF), or baseline level 1 for H.264. o Is performing playing and recording of audio and video concurrently. === End of readme_va.txt ===