Release notes: http://www.dialogic.com/webhelp/XMS/3.2/XMS_ReleaseNotes.pdf

Software download link: http://www.dialogic.com/en/products/downloads/xms/xms.aspx

Updates in PowerMedia XMS Release 3.2 Service Update 1 (Build 15331) include:

Controlled Introduction Features

Controlled introduction (CI). These are features that are under development or have a limited scope before being made generally available. These features are available for customers that are looking to perform Proof of Concept (PoC) with the listed functionality.

  • Added Primary Video Source for SFU -- provides an API (primary_video_source) that allows setting the video to be sent to each party in a Selective Forwarding Unit (SFU) conference. This feature is available at the user level and conference level, and possible selections include "loudest speaker" (default) and all conference parties. This API is available in add_party and update_party.
  • Added Dynamic Frame Size Adaptation -- enhances the dynamic frame size adaptation that dynamically changes the encoding frame size based on the estimated bandwidth. This feature has been delivered in XMS 3.2 as a controlled introduction, and has been further developed in XMS 3.2 SU1 to provide good video quality of experience even at low bitrates in the varying network environment. This feature is available only for VP8 and VP9 to maintain interoperability with legacy multimedia devices
  • Added Maintain Video Aspect Ratio in Join and Play -- supports a transcoding mode that maintains the video aspect ratio in video calls and playing multimedia files. When the level (in MPEG-4, H.264, and H.263) and/or max-fs of the remote client support frame size of incoming video, XMS doesn't do resizing. If not, XMS performs resizing to meet the maximum frame size specified by level and/or max-fs but maintaining the aspect ratio so that the video frame is not distorted. When the SDP includes sprop for H.264, XMS uses the frame size specified in the sprop.

Resolved Issues

  • IPY00118358 [HMP] There is audio issue when static HMP buffers are used.
  • IPY00118280 [MRB] When using MRB in RTP proxy mode, the video may freeze.
  • IPY00118449 [MRCp] When using MRCP, barge-in does not stop playing a file even when it is enabled.
  • IPY00118468 [MSML] When a caller enters digits while playing a file, the MSML service crashes.
  • IPY00118391 [Phrase Server] When playing a variable prompt using 24-hour time format, the parser incorrectly inserts a "hundred " after every hour.
  • IPY00118477 [RESTful] When the hangup_ack_mode parameter is set to "manual ", RESTful interface still acknowledges call hangup automatically and deletes its associated call resources.
  • IPY00118383 [RESTful] RESTful goes into failed state with no requests getting processed.
  • IPY00118374 [RESTful] There is no response returned for RESTful conference requests.
  • IPY00118369 [RESTful] There is no response returned for RESTful call requests.
  • IPY00118427 [Video] There are pixelation effects due to resolution changes.
  • IPY00118432 [WebGUI] The WebRTC demo fails to run if there is already a previously opened WebGUI page in the same browser.
  • IPY00118410 [WebGUI] WebGUI does not restrict the character set in username and password.
  • IPY00118505 [XMS] XMS is not relaying video flows with Google Chrome (Version 56).
  • IPY00118408 [XMS] The Call-Info from SIP header is not delivered to RESTful application.
  • IPY00118399 [XMS] RESTful is not responding due to insufficient Basic Audio licenses.
  • IPY00118311 [XMS] There is no video on outbound call when H.264 codec is selected.

Known Issues

  • XMS-6066 [HMP] Video quality may occasionally degrade over time on ingress side of HMP. For mobile clients, the video quality may be degraded from the beginning of the call into theSFU conference.
  • XMS-5875 [HMP] When recording to MP4, MKV or WebM, the messages file may indicate failures writing certain frames to files. For example: ssp_x86Linux_boot: MMRSC(161):VRCRD Cannot write one frame to a+v file
  • XMS-5626 [HMP/SFU] Many improvements have been made in both the video receiver and sender sides of XMS to reduce video freezes in low bandwidth environments. Further
  • improvements are planned specifically around bandwidth estimation and adapting the video frame size based on bandwidth conditions. Until these changes are fully complete, video freezes are still likely when the available bandwidth is below 500 kbps for 720p video.
  • XMS-6036 [Nodecontroller] Nodecontroller may crash when continuously queried via HTTP REST for license and service status.
  • XMS-6076 [SFU] Occasional long waits when connecting 4G clients to SFU before seeing any video.
  • XMS-6075 [SFU] Frequent video source changes may cause audio and video to become out of sync for some parties in the SFU conference; the video is delayed in relation to the audio.
  • XMS-6061 [SFU] Initial ramp-up time and recovery speed of bandwidth estimation can be improved when the network becomes good. The same root cause may also result in degraded video quality out of the SFU conference to Google Chrome.
  • XMS-6050 [SFU] Switching between VAS and primary video source very quickly will result in a failure to switch.
  • XMS-6049 [SFU] Playing OPUS/VP8 WebM file to SFU conference has no effect. Known XMS-6039 1 SFUCI Video freeze is observed (typically 5-10 s) when switching from
  • primary video source to VAS with dtmf_clamping=yes.
  • XMS-6028 [SFU] Video may disappear for about 1 s when changing audio RTP direction.
  • XMS-6026 [SFU] When updating a call in a conference with a re-INVITE to change the direction XMS is streaming from audio=sendrecv and video=sendrecv to audio=sendonly and video sendrecv, video disappears in Google Chrome Canary.
  • IPY00117920 [XMS] XMS is recognizing CED tone in VXML while playing a file even when no tones are being sent. Workaround: If a false positive occurs, comment out the CED tone definition in system-tones.conf under /etc/xms/tones.d. (permanent)