PowerMedia XMS Release Notes
Dialogic® PowerMedia™ XMS Release 3.1
Release Notes
March 2016
05-2745-001
www.dialogic.com
Copyright and Legal Notice
Copyright © 2016 Dialogic Corporation. All Rights Reserved. You may not reproduce this document in whole or in
part without permission in writing from Dialogic Corporation at the address provided below.
All contents of this document are furnished for informational use only and are subject to change without notice and
do not represent a commitment on the part of Dialogic Corporation and its affiliates or subsidiaries ("Dialogic").
Reasonable effort is made to ensure the accuracy of the information contained in the document. However, Dialogic
does not warrant the accuracy of this information and cannot accept responsibility for errors, inaccuracies or
omissions that may be contained in this document.
INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH DIALOGIC® PRODUCTS. NO LICENSE,
EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY
THIS DOCUMENT. EXCEPT AS PROVIDED IN A SIGNED AGREEMENT BETWEEN YOU AND DIALOGIC, DIALOGIC
ASSUMES NO LIABILITY WHATSOEVER, AND DIALOGIC DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY,
RELATING TO SALE AND/OR USE OF DIALOGIC PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO
FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY INTELLECTUAL PROPERTY
RIGHT OF A THIRD PARTY.
Dialogic products are not intended for use in certain safety-affecting situations. Please see
http://www.dialogic.com/company/terms-of-use.aspx for more details.
Due to differing national regulations and approval requirements, certain Dialogic products may be suitable for use
only in specific countries, and thus may not function properly in other countries. You are responsible for ensuring
that your use of such products occurs only in the countries where such use is suitable. For information on specific
products, contact Dialogic Corporation at the address indicated below or on the web at www.dialogic.com.
It is possible that the use or implementation of any one of the concepts, applications, or ideas described in this
document, in marketing collateral produced by or on web pages maintained by Dialogic may infringe one or more
patents or other intellectual property rights owned by third parties. Dialogic does not provide any intellectual
property licenses with the sale of Dialogic products other than a license to use such product in accordance with
intellectual property owned or validly licensed by Dialogic and no such licenses are provided except pursuant to a
signed agreement with Dialogic. More detailed information about such intellectual property is available from
Dialogic's legal department at 6700 de la Cote-de-Liesse Road, Suite 100, Borough of Saint-Laurent, Montreal,
Quebec, Canada H4T 2B5. Dialogic encourages all users of its products to procure all necessary
intellectual property licenses required to implement any concepts or applications and does not condone
or encourage any intellectual property infringement and disclaims any responsibility related thereto.
These intellectual property licenses may differ from country to country and it is the responsibility of
those who develop the concepts or applications to be aware of and comply with different national
license requirements.
Dialogic, Dialogic Pro, Dialogic Blue, Veraz, Brooktrout, Diva, BorderNet, PowerMedia, PowerVille, ControlSwitch, IGate, Mobile Experience Matters, Network Fuel, Video is the New Voice, Making Innovation Thrive, Diastar,
Cantata, TruFax, SwitchKit, Eiconcard, NMS Communications, SIPcontrol, Exnet, EXS, Vision, inCloud9,
NaturalAccess and Shiva, among others as well as related logos, are either registered trademarks or trademarks of
Dialogic Corporation and its affiliates or subsidiaries. Dialogic's trademarks may be used publicly only with
permission from Dialogic. Such permission may only be granted by Dialogic's legal department at 6700 de la Cotede-Liesse Road, Suite 100, Borough of Saint-Laurent, Montreal, Quebec, Canada H4T 2B5. Any authorized use of
Dialogic's trademarks will be subject to full respect of the trademark guidelines published by Dialogic from time to
time and any use of Dialogic's trademarks requires proper acknowledgement.
The names of actual companies and products mentioned herein are the trademarks of their respective owners.
This document discusses one or more open source products, systems and/or releases. Dialogic is not responsible
for your decision to use open source in connection with Dialogic products (including without limitation those
referred to herein), nor is Dialogic responsible for any present or future effects such usage might have, including
without limitation effects on your products, your business, or your intellectual property rights.
2
Table of Contents
1.
Welcome ....................................................................................................... 5
2.
Overview ....................................................................................................... 6
PowerMedia XMS ..................................................................................................... 6
PowerMedia MRB ..................................................................................................... 7
Related Information ................................................................................................. 8
3.
Related Documentation ................................................................................. 9
4.
System Requirements ................................................................................. 12
Supported Virtual Machines .................................................................................... 13
5.
Release Features ......................................................................................... 14
PowerMedia XMS Release 3.1 .................................................................................. 14
Multiple Format Simultaneous Record .................................................................... 14
Whisper (Coach) Conferencing ............................................................................. 15
Transaction Record Conferencing .......................................................................... 15
RTP/RTCP Port Multiplexing .................................................................................. 16
VXML Outbound Calling Support ........................................................................... 16
MSML Enhancements .......................................................................................... 16
Enhanced Multimedia Container Support ................................................................ 17
PowerMedia MRB Enhancements ........................................................................... 17
PowerMedia XMS Controlled Introduction Features .................................................. 18
PowerMedia MRB Controlled Introduction Features .................................................. 20
PowerMedia XMS Release 3.0 .................................................................................. 21
PowerMedia XMS Release 2.4 .................................................................................. 21
PowerMedia XMS Release 2.3 .................................................................................. 21
PowerMedia XMS Release 2.2 .................................................................................. 21
PowerMedia XMS Release 2.1 .................................................................................. 21
PowerMedia XMS Release 2.0 .................................................................................. 21
Applicable Third Party License Information................................................................ 21
6.
Installation, Configuration, Licensing, Logging, and Upgrading .................. 22
Installation ........................................................................................................... 22
ISO Method ....................................................................................................... 22
RPM Method ....................................................................................................... 22
Configuration ........................................................................................................ 23
PowerMedia XMS Admin Console .......................................................................... 23
RESTful Management API .................................................................................... 23
Licensing .............................................................................................................. 23
Logging ................................................................................................................ 23
Upgrading ............................................................................................................ 24
7.
Release Issues ............................................................................................ 25
Limitations ........................................................................................................... 25
Considerations ...................................................................................................... 25
Issues Tables ........................................................................................................ 26
3
Revision History
This section summarizes the changes made in this and, if applicable, each previously
published version of the Release Notes for PowerMedia XMS Release 3.1, which is a
document that is planned to be periodically updated throughout the lifetime of the release.
Revision
Release Date
Notes
05-2745-001
March 2016
Initial release of this document.
Last modified: March 2016
Refer to www.dialogic.com for product updates and for information about support policies,
warranty information, and service offerings.
4
1.
Welcome
These release notes address new features and issues associated with the Dialogic®
PowerMedia™ Extended Media Server (also referred to herein as "PowerMedia XMS" or
"XMS") Release 3.1. This is a document that is planned to be periodically updated
throughout the lifetime of the release.
The release notes are organized into the following sections (click the section name to jump
to the corresponding section):

Overview: This section provides an overview of this release.

Related Documentation: This section provides information about the documentation
that supports this release.

System Requirements: This section describes the system requirements for this
release.

Release Features: This section describes the new features and functionality in this
release.

Installation, Configuration, Licensing, and Upgrading: This section describes topics
that are useful for getting started with this release, such as: Installation,
Configuration, Licensing, and Upgrading.

Release Issues: This section lists the issues that may affect this release.
5
2.
Overview
Dialogic’s PowerMedia XMS is a highly scalable, software-only media server that enables
standards-based, real-time multimedia communications solutions for IMS, MRF, Enterprise,
and WebRTC applications on premise or in the cloud. Built on 15+ years of software media
processing experience, PowerMedia XMS is trusted by world-class service providers and
large enterprises to power millions of rich media sessions.
With an extensive list of successful implementations that include MRF for VoLTE, carrier
hosted contact centers, enterprise communications, voice messaging and "mission critical"
next-generation 911 services, PowerMedia XMS has proven to be a key building block to
new and innovative applications. When deployed with the optional Dialogic® PowerMedia™
Media Resource Broker (MRB), PowerMedia XMS scales to meet growing service-provider
and business requirements.
PowerMedia XMS
PowerMedia XMS energizes application delivery by boosting performance with:

State of the art mixing of media-rich communications

Software providing a seamless transition to virtualization and cloud delivery

Telco hardened scalability

Supercharged WebRTC integration
PowerMedia XMS elevates what developers can create for their customers, from virtually
any development environment, on virtually any network, and connecting to virtually any
type of communication endpoint.
PowerMedia XMS is a powerful next-generation software-only media server or software
Media Resource Function (MRF) IMS network element that enables standards-based, realtime multimedia communications solutions for SIP and WebRTC for mobile and broadband
environments. PowerMedia XMS enables high density real-time multimedia communication
functions including inbound and outbound session/call control, audio/video play and record,
transcoding, transrating, transizing of video streams, multimedia conference mixing,
content streaming, and a wide range of advanced supporting functions for communication
sessions.
PowerMedia XMS is controlled by the business logic of applications deployed on SIP
application servers and web application servers. PowerMedia XMS offers multiple media
control protocols that can be used in a variety of network infrastructures. For example, a
SIP application server (AS) can drive PowerMedia XMS using the MSML control interface or
use the PowerMedia XMS VoiceXML (VXML) browser to execute VXML scripts and invoke
MRCP speech services, like ASR and TTS. For Web 2.0 and Cloud development, a web
application written in an appropriate language can control PowerMedia XMS using the HTTP
RESTful interface. Similarly, the JSR 309 Connector Software for PowerMedia XMS (JSR 309
Connector) can enable Java EE developers to control real-time applications from converged
application servers.
The MSML, JSR 309 Connector, VXML, RESTful, and NETANN interfaces support
multimedia—both audio and video, using a variety of codecs. All PowerMedia XMS APIs
provide support for handling RTP media, security (via DTLS/SRTP), and ICE negotiation from
WebRTC media sources.
6
PowerMedia XMS provides powerful and user-friendly OA&M functionality, and can be
managed remotely through a web-based operator console and the HTTP RESTful
Management interface.
A wide variety of SIP endpoints can be handled by PowerMedia XMS, resulting in the
delivery of rich full-duplex audio and video media streams to a variety of fixed and mobile
devices. With the additional support for WebRTC media, PowerMedia XMS provides the
power to mix diverse streams and enable connectivity between legacy networks, endpoints,
and WebRTC.
The following figure illustrates an example of a video conferencing delivery platform for a
PowerMedia XMS-based multimedia conferencing solution.
PowerMedia MRB
The Media Resource Broker (MRB) is a standardized network element, defined by RFC 6917,
that manages media resource availability and reliability, providing improved utilization and
reliability of deployed media resources in the network. As defined in MRB specifications, the
PowerMedia MRB performs critical media resource management functions, including:

Balancing requests from multiple application servers or app server clusters

Efficiently utilizing and allocating the MRF/Media Server (MS) resource pools

Providing a monitoring mechanism for media server status and capabilities

Supporting media control payloads such as MSML, RESTful, and VXML
Clustering of the PowerMedia XMS instances to support higher density and scalability
requirements is supported by the PowerMedia MRB. It is designed to handle large
transaction rates and can effectively and efficiently load balance the traffic among available
PowerMedia XMS instances (MRFs) including those instances located in different geographic
regions. The PowerMedia MRB is implemented to be a stateful load balancer and actively
monitors and tracks capacity and availability of individual XMS instances. Since the MRB is
stateful, it can also support real-time call preservation. In case of failure, the MRB can
dynamically restore established media sessions to an alternate XMS instance, ensuring
continuity of service.
7
The following figure illustrates the role of the PowerMedia MRB to manage PowerMedia XMS
resources among various geographic sites.
Related Information
See the following for additional information:

PowerMedia XMS product page at http://www.dialogic.com/products/media-serversoftware/xms.

PowerMedia XMS datasheet at
http://www.dialogic.com/~/media/products/docs/media-server-software/12888powermedia-xms-ds.pdf.

PowerMedia MRB datasheet at
http://www.dialogic.com/~/media/products/docs/media-server-software/14160powermediamrb-ds.pdf.

PowerMedia XMS Developer Portal at http://developer.dialogic.com.

PowerMedia XMS documentation at http://www.dialogic.com/manuals.

Dialogic technical support at http://www.dialogic.com/support.
8
3.
Related Documentation
This section provides information about the documentation that supports the PowerMedia
XMS Release 3.1.
The following documents are available for the PowerMedia XMS Release 3.1 at
http://www.dialogic.com/manuals/xms/xms3.1.aspx.
Document
Description
Dialogic® PowerMedia™ XMS Release 3.1 Release
Notes
Addresses new features and issues
associated with PowerMedia XMS Release
3.1.
Dialogic® PowerMedia™ XMS Quick Start Guide
Describes how to install software, access
the PowerMedia XMS Admin Console for
configuration management, and run the
verification demo.
Dialogic® PowerMedia™ XMS Installation and
Configuration Guide
Provides instructions for installing,
configuring, administering, and
maintaining PowerMedia XMS.
Dialogic® PowerMedia™ XMS WebRTC Demo
Guide
Provides instructions for running WebRTC
demos with PowerMedia XMS.
Dialogic® PowerMedia™ XMS Basic Network Media
Services with SIP User's Guide
Provides detailed information about
configuring Basic Network Media Services
with SIP, focusing on Network
Announcement (NETANN).
Dialogic® PowerMedia™ XMS Message Session
Relay Protocol Feature Guide
Describes the Message Session Relay
Protocol (MSRP), which is a sessionoriented instant messaging protocol used
to provide peer-to-peer file transfer,
photo sharing, or chat services.
Dialogic® PowerMedia™ XMS MSML Media Server
Software User's Guide
Provides guidelines for using the Media
Sessions Markup Language (MSML)
software. The MSML media server
software enables a remote client, also
known as an Application Server (AS), to
control media resources on a media
server (MS). The connection between the
AS and MS is established using the SIP
protocol, thereafter media control
commands/responses (in the form of
MSML control syntax) are exchanged in
SIP messages, such as the INFO
message or the 200 OK response.
9
Document
Description
Dialogic® PowerMedia™ XMS RESTful API User's
Guide
Provides information for application
developers using RESTful API over http
transport to control media and call
control resources of PowerMedia XMS.
Dialogic® PowerMedia™ XMS RESTful
Management API User's Guide
Provides an alternative method of
performing PowerMedia XMS system
management tasks in an automated or
distributed manner.
Dialogic® PowerMedia™ XMS Variable Content
Announcements Feature Guide
Describes how to use variable content
announcements for multiple languages in
PowerMedia XMS.
Dialogic® PowerMedia™ XMS VoiceXML Reference
Guide
Contains an alphabetical reference of
supported VoiceXML elements and
provides information about application
properties, SSML support, session
variables, and application variables.
Dialogic® PowerMedia™ XMS WebRTC JavaScript
API User's Guide
Provides information on functionality to
support connecting to and performing
media operations on Web Real-Time
Communication (WebRTC) compliant
devices or endpoints (for example,
browsers) with PowerMedia XMS.
JSR 309 Connector Software
Dialogic® PowerMedia™ XMS JSR 309 Connector
Software Installation and Configuration Guide
Dialogic® PowerMedia™ XMS JSR 309 Connector
Software Developer's Guide
Provides the JSR 309 Connector
installation and configuration information
for the supported platforms.

Oracle Communications
Converged Application Server
(versions 5 and 7)

TeleStax Apache-Tomcat
Application Server

TeleStax JBoss Application
Server

IBM Liberty Application Server
Describes any extensions added to the
JSR 309 Connector (based on JSR 309
specification) in addition to which
methods/parameters are supported.
10
Document
Description
Media Resource Broker (MRB)
Dialogic® PowerMedia™ Media Resource Broker
(MRB) Quick Start Guide
Describes how to install software and
configure the PowerMedia MRB to initiate
a working test setup.
Dialogic® PowerMedia™ Media Resource Broker
(MRB) Installation and Configuration Guide
Provides instructions for installing and
configuring the PowerMedia MRB.
11
4.
System Requirements
This section describes the system requirements for the PowerMedia XMS Release 3.1.
The minimum and recommended system requirements are as follows:
Item
Requirement
Hardware
Intel Architecture-based server
Operating System
Note: 32-bit operating systems are not supported.
ISO Method Installation:
Community ENTerprise Operating System (CentOS) 7.x
RPM Method Installation:
CentOS 7.x and 6.x
Red Hat Enterprise Linux (RHEL) 7.x and 6.x
Oracle Enterprise Linux (OEL) 6.x
Note: Before running the RPM Method installation, the
following packages, available from the OS distributor,
must first be installed:
Processor

perl-core

openssl version 1.0.1e or higher
Minimum: Intel Xeon E5-1620 Quad-Core (3.60 GHz,
1600 MHz, 10 MB Cache), Intel QPI (0 GT/s) for low end
solutions
Recommended: Intel Xeon E5-2665 Dual Octal-Core
(2.40 GHz, 1333 MHz, 20 MB Cache), 2 Intel QPI (8 GT/s)
or better for performance systems
Ethernet
Single or Dual NIC 1000Base-TX (RJ-45)
Memory
Minimum: 8 GB RAM
Recommended: 16 GB RAM or higher
Storage
Minimum: 250 GB HDD
Recommended: 2 TB HDD for advanced logging
Note: The recommended server configuration is applicable for higher density audio
solutions of 1500 or greater sessions, video transcoding solutions, or solutions utilizing
virtualization.
12
Supported Virtual Machines
The supported virtual machines (VM) are as follows:

VMWare ESXi 5.x

Kernel Virtual Machine (KVM)

Oracle VM

XenServer VM
Note: Virtualization systems chosen for PowerMedia XMS should be configured for
enterprise or private virtual environments that permit customization of virtual machine (VM)
settings and hypervisor performance tuning. Virtual environments running PowerMedia XMS
must also restrict the number of VMs hosted on a single platform to facilitate the real-time
low-latency scheduling demands required for high quality media processing. Density
capacity in virtual environments may vary and is generally a factor of the host platform
capacity and the number of VMs running PowerMedia XMS. Generally, the aggregate density
of all VMs running PowerMedia XMS will be less than the bare metal capacity of the
platform.
Refer to Dialogic® PowerMedia™ XMS Application Note: Optimizing VMware Host Hardware
and Virtual Machine to Reduce Latency at
http://www.dialogic.com/webhelp/XMS/3.1/XMS_VMOptimizingAppNote.pdf for more
information.
Cloud Environments
Support for cloud environments is available as a controlled introduction for Proof of
Concepts (PoCs), development activities, and trials, but not for production use. For more
information, refer to the following white papers:

Dialogic® PowerMedia™ XMS and the Rackspace Managed Cloud at
http://www.dialogic.com/~/media/products/media-server-software/download/xmsdemos/Rackspace-XMS-Verification.pdf.

Dialogic® PowerMedia™ XMS and Amazon Web Services at
http://www.dialogic.com/~/media/products/media-server-software/download/xmsdemos/AWS-XMS-Verification.pdf.
13
5.
Release Features
This section describes the features and functionality supported in the PowerMedia XMS
Release 3.1.
For more information, refer to the documents listed in the Related Documentation section.
PowerMedia XMS Release 3.1
The key new features and functionality include:

Multiple Format Simultaneous Record

Whisper (Coach) Conferencing

Transaction Record Conference

RTP/RTCP Port multiplexing

VXML Outbound Calling Support

MSML Enhancements



Overlap SIP INFO

Conference Command Buffering
Enhanced Multimedia Container Support

MPEG4 (.mp4) Container Support

Matroska (.mkv) Container Support
PowerMedia MRB Enhancements



MRB for 1PCC REST (SIP Applications)
PowerMedia XMS Controlled Introduction Features

Video Encoder Sharing Support

NAT and RTP Profile Indications Support

Multiple NIC Media Routing Support
PowerMedia MRB Controlled Introduction Features

MRB for 3PCC REST

MRB RTP Proxy
Multiple Format Simultaneous Record
PowerMedia XMS Release 3.1 supports simultaneous recording of the same media source to
multiple container formats. The XMS MSML and RESTful APIs have been updated with the
capability to attach multiple recorders to the same IP connection or conference output and
specify different file formats for each recording. While the recording occurs on the same
media, each recording can be controlled separately and independently. This feature is useful
for applications looking to simultaneously store real-time media in two file formats, such as
a multimedia file (.3gp) and an audio file (.wav) for the same video caller. As an example of
this scenario, an application may choose to send the audio recording to a third party
process to get a transcript of the video recording.
14
Note: The XMS system is limited to n records where n is the number of XMS ports. Using
multiple records on the same media stream will deduct from the total number of available
system recorders.
Note: Simultaneous recording must be done to separate files or the recordings will be
corrupted.
Whisper (Coach) Conferencing
PowerMedia XMS 3.1 supports whisper (coach) conferencing. This feature enables an
application controlled method to connect a party’s media to multiple conferences
simultaneously. Through full-duplex and half-duplex media connections, an application can
enable a secondary whisper (or coach) conference that one caller (agent) hears while
talking in the main conference to another caller (client). This feature enables use cases such
as supervisor coaching/whispering and sidebar consultative conferences with multiple
supervisors that parallel a main conference. This feature is supported for audio or video
conferences with MSML and RESTful API.
Note: Multiple connections are permitted in a sendonly direction.
Note: This feature is not supported by the PowerMedia MRB as of this release.
For examples in the MSML API, refer to the Dialogic® PowerMedia™ XMS MSML Media
Server Software User's Guide.
Transaction Record Conferencing
PowerMedia XMS 3.1 supports creation of a transaction record conference to record the
audio or video transaction of a joined call or transcoding session. The transaction record
conference can be created in parallel to the audio or video joined call, allowing an
application to record the transaction without interfering with the peer-to-peer interaction.
This feature is enabled by providing the ability for an application to connect a caller’s media
to the other party and conference simultaneously to support this use case. This feature is
supported for audio and video use cases with MSML and RESTful API.
For audio callers, an application can join audio callers in a peer-to-peer connection while
simultaneously connecting the media from both parties into an audio conference. The audio
conference output can be recorded to provide a mixed audio transaction recording of the
audio conversation.
For video callers, an application can join video callers in a peer-to peer connection while
simultaneously connecting the media from both parties into a multimedia conference. The
video callers will experience a peer-to-peer video call in which each party sees the other’s
video and hears the other’s audio. In parallel, the multimedia conference mixes both parties
with supported video layouts and allows the application to record the multimedia conference
output into a single file. The single recorded file can contain a side-by-side or tiled view of
both video callers and provides a recording of the video conversation.
Note: Recording the output of a video conference requires an extra video license to provide
the video transcoding into the multimedia file.
Note: This feature is not supported by the PowerMedia MRB as of this release.
For the MSML API, refer to the Dialogic® PowerMedia™ XMS MSML Media Server Software
User's Guide for more information.
For the RESTful API, refer to the Dialogic® PowerMedia™ XMS RESTful API User's Guide for
more information.
15
RTP/RTCP Port Multiplexing
PowerMedia XMS Release 3.1 supports RTP/RTCP port multiplexing on SIP or WebRTC calls,
as defined by "RFC 5761: Multiplexing RTP Data and Control Packets on a Single Port." This
feature provides the capability within XMS to use SDP to negotiate a single multiplexed port
for both RTP and RTCP data for the same RTP media stream. RTP/RTCP port multiplexing
helps with Network Address Port Translation (NAPT) and NAT Traversal by reducing the
number of NAT bindings that must be open at a firewall during ICE negotiation and RTP
session establishment. The feature is mainly used in SDP negotiations with WebRTC
browsers to limit the number of ports used for NAT Traversal and ICE connectivity checks.
VXML Outbound Calling Support
PowerMedia XMS 3.1 supports VXML outbound calling. This feature allows VXML API users to
make outbound SIP calls from XMS to support applications such as outbound dialing and
outbound call notification using VXML script execution. The feature provides a Dialogic
<callplacer> API method for initiating a single SIP outbound call or multiple SIP outbound
calls from within a VXML script context. The <callplacer> method dials an outbound call
using the call parameters and Destination URI specified for the method. Once the
destination has answered the call and it is connected, the outbound call proceeds with its
own VXML dialog for the connected call session.
Refer to the Dialogic® PowerMedia™ XMS VoiceXML Reference Guide for more information.
MSML Enhancements
The following feature is specific to the MSML API and provides optimizations to an MSML
script handling under specific conditions.
Overlap SIP INFO
PowerMedia XMS Release 3.1 provides support for overlapping SIP INFO messages carrying
MSML script payloads. This feature enhancement allows an application to send SIP INFO
messages carrying an MSML (RFC 5707) payload to the XMS for processing without waiting
for the 200 OK to be returned. This allows an application to submit multiple MSML dialogs
within subsequent SIP INFO messages before XMS acknowledges receipt of the SIP INFO. It
can be used by MSML applications to reduce latency between subsequent SIP INFO
commands. PowerMedia XMS will buffer SIP INFO commands from the application and
execute them in sequential order. This feature is only valid with MSML API, and MSML
application developers should consider the tradeoffs between SIP latency and script
buffering execution in their application designs.
Conference Command Buffering
PowerMedia XMS Release 3.1 supports conference command buffering. This feature can
optimize command handling at XMS conferences. In this release, the product supports
buffering of overloaded commands targeted to the same conference ID. PowerMedia XMS
will buffer all simultaneous requests to the same conference device, such as multiple join
request and conference play that might occur at the same time, which alleviates the
application responsibility for command queuing. This feature provides some performance
benefits at the start of a conference where multiple parties might be joining and playing
prompts in quick succession.
16
Enhanced Multimedia Container Support
PowerMedia XMS 3.1 supports additional multimedia containers: MPEG4 (MP4) and Matroska
(MKV). Both new multimedia container formats can be used for direct play and record of
audio and/or video media within XMS.
Note: Independent playback of .mkv and .mp4 files by 3rd party clients is dependent on the
client capabilities. PowerMedia XMS .mp4 and .mkv files are supported by VLC media player
(https://www.videolan.org/vlc/).
MPEG4 (.mp4) Container Support
PowerMedia XMS has been updated to support MPEG4 (.mp4) record and playback. The MP4
(MPEG-4 part 14 file format) container is one of the most popular Internet file formats and
used in many mobile devices and Internet applications to stream multimedia data. Some of
the highlighted functionality provided in this release for the MP4 container includes the
following:

Play and record directly to and from .mp4

Support for audio only, video only, and multimedia (A/V) files

Supported video codecs: H.264, MPEG4, and H.263

Supported audio codecs: AMR-NB and AMR-WB
Note: AAC codec is not supported in MP4 container.

DVR modes: skip forward, skip back, pause, and resume
Matroska (.mkv) Container Support
PowerMedia XMS has been updated to support MKV record and playback. The MKV container
(Matroska container format) is an Open Standard and Open Source container format that
can support a wide range of video, audio, and track data. The MKV container is popular
because of its support as a container for WebRTC codecs, such as the VP8 video codec and
the OPUS audio codec. Additionally, Google based its WebM (VP8/OPUS) container on the
MKV format. Some of the highlighted functionality provided in this release for the MKV
container includes:

Play and record directly to and from .mkv

Support for audio only, video only, and multimedia (A/V) files

Supported video codecs: VP8 and H.264

Supported audio codecs: OPUS, AMR-NB, and AMR-WB

DVR modes: skip forward, skip back, pause, and resume
PowerMedia MRB Enhancements
The following section details new release features in the PowerMedia Media Resource Broker
(MRB) version 1.5 supported by XMS 3.1.
MRB for 1PCC REST (SIP Applications)
The PowerMedia MRB has been updated to provide media load balancing, failover, and high
availability features for 1PCC RESTful SIP applications. 1PCC RESTful SIP applications are
RESTful applications that terminate SIP calls on the MRB. SIP calls can be routed directly to
the MRB or can be steered to the MRB via an application server acting as a Back-to-Back
User Agent (B2BUA). The PowerMedia MRB will provide a single RESTful API entry point to
a cluster of XMS media server instances.
17
Other updates to the PowerMedia MRB include:

Support for the latest versions of Java 8 and JAIN SIP stack

Conference cascade improvements to handle larger conference sizes

Media server failover detection improvements
PowerMedia XMS Controlled Introduction Features
In addition to general availability of new features and functionality, PowerMedia XMS
Release 3.1 also introduces new functionality in a controlled introduction. The controlled
introduction features are those 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. Customers interested in
these features should contact their Dialogic Sales Representative or Technical Support
Service Engineer for further information on usage.
The following features are offered in the PowerMedia XMS Release 3.1 controlled
introduction:

Video Encoder Sharing Support

NAT and RTP Profile Indications Support

Multiple NIC Media Routing
Video Encoder Sharing Support
PowerMedia XMS Release 3.1 supports video encoder sharing. Video encoder sharing
includes Dialogic patented video technology that provides enhanced performance for video
conferencing and video mixing applications. Video encoder sharing works by reducing the
CPU cycles required to perform the most CPU intensive video function: video encoding. In
video conferencing applications, such as for WebRTC video conferencing between browsers,
the video conference output can be encoded once and shared among various multiple users.
The video encoder sharing technology provides the capability to encode once for a number
of video conference participants and perform, via Dialogic patent-pending technology,
dynamic bitrate adaptation to each endpoint independently. This feature increases the
number of supported sessions while treating the network conditions to each party uniquely,
promoting better video quality at each endpoint. This feature, combined with the centralized
video mixing, also provides reduced bandwidth over point-to-point video sharing between
WebRTC browsers.
Refer to the Dialogic® PowerMedia™ XMS Installation and Configuration Guide for more
information.
18
NAT and RTP Profile Indications Support
PowerMedia XMS 3.1 supports various combinations of SIP header indications to specify NAT
and RTP profiles on SIP calls. This feature supports ICE (Lite), SDES, DTLS, AVPF/SAVPF,
and combinations in a SIP INVITE when using Dialogic proprietary Supported header tags.
The tags apply to MSML, VXML, and NETANN to set up the given call with the provided
feature support in the XMS offer SDP. In RESTful API calls, the tags are provided to the
customer application through the SIP header. The RESTful application can extract the SIP
header indications to control the call session response. Refer to the following table for a list
of the Dialogic proprietary Supported header tags.
Tag
Description
dlgc-encryption-sdes
Enables sdes-srtp
dlgc-encryption-dtls
Enables dtls-srtp
dlgc-ice
Enables ICE (Lite)
dlgc-rtcp-feedback-audio
Enables AVPF/SAVPF for audio (not
currently supported)
dlgc-rtcp-feedback-video
Enables AVPF/SAVPF for video
dlgc-rtcp-feedback-audiovideo
Enables AVPF/SAVPF for audio and video
(only video is currently supported)
dlgc-rtcp-feedback-none
Overrides configuration and disables RTCP
feedback on audio and video (only video is
currently supported) if configured to be
enabled by default
Multiple NIC Media Routing
PowerMedia XMS Release 3.1 provides user-defined media routing rules to support multiple
NIC interfaces for RTP media traffic routing. This feature provides a method for XMS users
to indicate a particular network interface that should be used when establishing SIP and
WebRTC calls or media connections. A useful application of this feature is to separate media
traffic between two interfaces, such as with a media gateway application supporting local
and public network interfaces.
Multiple network interface support is enabled through media routing rules defined by a
media routing profile. The media routing profiles allow a customer to define a media route
profile for any call session request sent to XMS. XMS will attempt to match each call to a
media route profile and use the network interface that best matches the specified indication
in the XMS offer. Using this method, a user can define routing rules that can be supported
by any XMS remote API (MSML, RESTful, VXML, NETANN, or JSR309) to route media
through the appropriate network interface to the desired network.
The multiple NIC media routing feature is available on all call sessions and is configured
through the Protocol > RTP page in the WebGUI.
Refer to the Dialogic® PowerMedia™ XMS Installation and Configuration Guide for more
information.
19
PowerMedia MRB Controlled Introduction Features
In addition to general availability of new features and functionality, PowerMedia MRB also
introduces new functionality in a controlled introduction. The controlled introduction features
are those 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. Customers interested in these features should
contact their Dialogic Sales Representative or Technical Support Service Engineer for further
information on usage.
The following features are offered in the PowerMedia Media Resource Broker (MRB) version
1.5 supported by XMS 3.1:

MRB for 3PCC REST

MRB RTP Proxy
MRB for 3PCC REST
The PowerMedia MRB has been updated to provide media load balancing, failover, and high
availability features for 3PCC RESTful applications. 3PCC RESTful applications are those that
support call signaling for WebRTC or SIP at the application server and use the PowerMedia
XMS only for media establishment and media operations. The PowerMedia MRB provides
media resource brokering of RESTful API media calls and conferences by handling the
RESTful API calls (over HTTP transport) and providing an RTP proxy location for media
routing and failover.
MRB RTP Proxy
The PowerMedia MRB supports a new RTP proxy mode. The MRB RTP proxy provides a
single landing point for RTP media sessions that are monitored by the MRB. The RTP proxy
routes media to the appropriate PowerMedia XMS instances that are managed by the
PowerMedia MRB. The MRB RTP proxy monitors the RTP traffic and will indicate RTP
information about the sessions to the MRB. This RTP monitoring allows the MRB to detect
lost RTP sessions and re-route media to a new destination in order to support media server
failover of media operations.
20
PowerMedia XMS Release 3.0
For notable features and functionality included in PowerMedia XMS Release 3.0, refer to the
Dialogic® PowerMedia™ XMS Release 3.0 Release Notes at:
http://www.dialogic.com/webhelp/XMS/3.0/XMS_ReleaseNotes.pdf
PowerMedia XMS Release 2.4
For notable features and functionality included in PowerMedia XMS Release 2.4, refer to the
Dialogic® PowerMedia™ XMS Release 2.4 Release Notes at:
http://www.dialogic.com/webhelp/XMS/2.4/XMS_ReleaseNotes.pdf
PowerMedia XMS Release 2.3
For notable features and functionality included in PowerMedia XMS Release 2.3, refer to the
Dialogic® PowerMedia™ XMS Release 2.3 Release Notes at:
http://www.dialogic.com/webhelp/XMS/2.3/XMS_ReleaseNotes.pdf
PowerMedia XMS Release 2.2
For notable features and functionality included in PowerMedia XMS Release 2.2, refer to the
Dialogic® PowerMedia™ XMS Release 2.2 Release Notes at:
http://www.dialogic.com/webhelp/XMS/2.2/XMS_ReleaseNotes.pdf
PowerMedia XMS Release 2.1
For notable features and functionality included in PowerMedia XMS Release 2.1, refer to the
Dialogic® PowerMedia™ XMS Release 2.1 Release Notes at:
http://www.dialogic.com/webhelp/XMS/2.1/XMS_ReleaseNotes.pdf
PowerMedia XMS Release 2.0
For notable features and functionality included in PowerMedia XMS Release 2.0, refer to the
Dialogic® PowerMedia™ XMS Release 2.0 Release Notes at:
http://www.dialogic.com/webhelp/XMS/2.0/XMS_ReleaseNotes.pdf
Applicable Third Party License Information
FFmpeg
This software uses libraries from the FFmpeg project licensed under the LGPLv2.1, and
source code for these libraries can be downloaded from the distributable image for
PowerMedia XMS.
21
6.
Installation, Configuration, Licensing, Logging,
and Upgrading
This section describes topics that are useful for getting started with the PowerMedia XMS
Release 3.1, such as: Installation, Configuration, Licensing, and Upgrading.
For more details describing how to install software, access the PowerMedia XMS Admin
Console for configuration management, and run the verification demo, refer to the
Dialogic® PowerMedia™ XMS Quick Start Guide.
For more details providing instructions for installing, configuring, administering,
maintaining, and upgrading PowerMedia XMS, refer to the Dialogic® PowerMedia™ XMS
Installation and Configuration Guide.
For more details on running a WebRTC demo with PowerMedia XMS, refer to the Dialogic®
PowerMedia™ XMS WebRTC Demo Guide. Because WebRTC demos require an HTTPS
connection, the guide provides the necessary procedures to set up and establish the secure
connection for each compatible web browser prior to running a WebRTC demo.
For more details providing instructions for installing and configuring the JSR 309 Connector,
refer to the Dialogic® PowerMedia™ XMS JSR 309 Connector Software Installation and
Configuration Guide.
For more details providing instructions for installing and configuring Dialogic® PowerMedia™
MRB, refer to the Dialogic® PowerMedia™ Media Resource Broker (MRB) Quick Start Guide
and the Dialogic® PowerMedia™ Media Resource Broker (MRB) Installation and
Configuration Guide.
Note: For limitations or issues related to installing or upgrading PowerMedia XMS, refer to
the Release Issues section beforehand for more information.
Installation
There are two installation methods available:

ISO Method

RPM Method (used for a CentOS or RHEL installation)
ISO Method
The ISO installation method is a complete system installation that includes the CentOS, OS
optimizations, and PowerMedia XMS software. The ISO can be installed from a DVD drive to
a physical or virtual machine.
For more information, refer to the Dialogic® PowerMedia™ XMS Quick Start Guide and
Dialogic® PowerMedia™ XMS Installation and Configuration Guide.
RPM Method
The stand-alone RPM installation method is used for installation on top of a pre-existing
CentOS or RHEL installation. The RPM installation will install the PowerMedia XMS software
and prerequisite packages required to run PowerMedia XMS. The RPM installation will also
make OS adjustments for real-time audio and video processing required for optimal
performance.
For more information, refer to the Dialogic® PowerMedia™ XMS Quick Start Guide and
Dialogic® PowerMedia™ XMS Installation and Configuration Guide.
22
Configuration
There are two configuration methods available:

PowerMedia XMS Admin Console

RESTful Management API
PowerMedia XMS Admin Console
The PowerMedia XMS Admin Console ("Console") is a secure web-based GUI used to
manage PowerMedia XMS. The Console can be reached using a web browser and the
PowerMedia XMS IP address.
For more information, refer to the Dialogic® PowerMedia™ XMS Quick Start Guide and
Dialogic® PowerMedia™ XMS Installation and Configuration Guide.
RESTful Management API
The RESTful Management API is an alternate way of configuring and performing system
management tasks for PowerMedia XMS. The RESTful Management API is a remote API
carried over HTTP transport that allows the option to incorporate configuration elements into
an application or web interface in a more automated or distributed manner.
For more information, refer to the Dialogic® PowerMedia™ XMS RESTful Management API
User's Guide.
Licensing
PowerMedia XMS comes with a 4-port verification license to get started. The name of the
license file is verification.lic.
PowerMedia XMS evaluation software can be requested by filling out a form through the
Dialogic website at http://www.dialogic.com/products/media-server-software/xms/xmsdownload.aspx.
PowerMedia XMS production licenses or trial licenses for larger session installations can be
obtained through your authorized Dialogic distributor or by contacting Dialogic Inside Sales
(insidesales@dialogic.com).
The following licensing capabilities are supported in this release:

Hardware-Independent Licensing: The license is locked to a 33-byte License
Node ID retrieved from the XMS system WebGUI or RESTful Management API.

Additive Licensing: To increase licensed resources or scale system capability, you
can augment an existing license with multiple licenses. The licenses must be
production (non-trial or non-verification) licenses.
Logging
In PowerMedia XMS 3.1, the default logging level is set to DEBUG. The DEBUG setting
provides the most intensive logging levels. For production-level traffic or high density
testing, it is recommended to set the logging level to ERROR because the ERROR setting
provides the lightest logging levels. To set the logging level, go to the System >
Diagnostics page in the PowerMedia XMS Admin Console.
When running XMS Diagnostics logging at increased logging levels (e.g., DEBUG), there is
additional CPU and hard drive access loading. The loading is dependent on the channel
density of the system and also the level of logging that has been enabled. If system
23
performance issues are encountered, users may need to reduce the channel load or reduce
some of the debugging prints.
Upgrading
As part of the PowerMedia XMS Admin Console, the Upgrade page of the System menu
provides the option to upgrade the system by uploading a system upgrade package.
Perform the following steps to upgrade the system:
1. Select the System menu.
2. Click the Upgrade tab.
3. Click Browse from the Upload System Upgrade Package section to access a
system upgrade package file (.tgz) that has been downloaded.
4. Once you select the system upgrade package file, click Upload. After the upload
completes, the system upgrade package file will be listed in the System Upgrade
Package section.
5. Locate the appropriate system upgrade package file and click Upgrade.
Note: If upgrading from 3.0 Service Update 1 or 2.4 Service Update 7, you must use the
command line upgrade process. There is a known defect in the 3.0 SU 1 and 2.4 SU 7
WebUI upgrade process. If you have already attempted to upgrade using the WebUI, you
can remove and reinstall XMS using the command line installation. Refer to "RPM
Installation and Script Options" in the Dialogic® PowerMedia™ XMS Installation and
Configuration Guide for information on how to upgrade your system using the command line
upgrade script.
Note: If there is already a system upgrade package file listed in the System Upgrade
Package section, you can click Upgrade on the appropriate system upgrade package file.
Note: XMS configuration settings are preserved when upgrading the XMS system. Direct
user modifications to XMS files may be overwritten with upgraded versions.
24
7.
Release Issues
This section lists the issues that may affect the PowerMedia XMS Release 3.1 and
PowerMedia MRB.
PowerMedia XMS Release 3.1 includes all of the applicable resolved issues from the
following releases:

PowerMedia XMS Release 3.0 Service Update 2 (Release Notes)

PowerMedia XMS Release 2.4 Service Update 8 (Release Notes)

PowerMedia XMS Release 2.3 Service Update 5 (Release Notes)

PowerMedia XMS Release 2.2 Service Update 10 (Release Notes)

PowerMedia XMS Release 2.1 Service Update 2 (Release Notes)
Limitations
PowerMedia XMS Release 3.1 has the following limitations:

The RPM installation method can automatically install prerequisite operating system
packages. If installing PowerMedia XMS on an existing system, it is recommended to
have the yum package manager configured to use the online repository or a
repository consisting of a locally mounted DVD or ISO of the operating system
version being installed on.

When upgrading a previous PowerMedia XMS installation and using the RESTful
programming interface, verify the route entries in the Routes page of the
PowerMedia XMS Admin Console after the upgrade completes.

When using the web upgrade method for PowerMedia XMS, ensure your system has
net-snmp (x86_64), net-snmp-libs (x86_64), and net-snmp-libs (i686) installed
before the upgrade, or have yum enabled with the standard repository that matches
your OS (the prerequisite packages will be installed automatically).
Note: When using the command line upgrade method for PowerMedia XMS,
appropriate messages will be displayed instructing the user to install those packages
if yum is not configured.
Considerations
GNU Bourne Again Shell (Bash) Vulnerability
A vulnerability "Shellshock" has been reported in the GNU Bourne Again Shell (Bash), the
common command-line shell used in most Linux/UNIX operating systems (OS). The flaw
could allow an attacker to remotely execute shell commands by attaching malicious code in
environment variables used by the OS. Patches have been released to fix this vulnerability
for affected OS versions. Note that the current solution does not completely resolve the
vulnerability. We recommend that the user install existing patches and pay attention for
updated patches.
PowerMedia XMS makes use of the bash shell in several components. For ISO installations,
we recommend that the user log into the PowerMedia XMS command line and update the
bash package with the following command line:
# yum update bash
25
For PowerMedia XMS RPM installations, the user should check the version of bash package
installed and apply any patches if required. Additional information about Shellshock can be
found at http://www.us-cert.gov/ncas/alerts/TA14-268A.
Issues Tables
The following tables list issues that affect the PowerMedia XMS and/or PowerMedia MRB.
The following information is provided for each issue.
Issue Type
This classifies the type of release issue based on its effect on users and its disposition:

Known – A minor issue. This category includes interoperability issues and
compatibility issues. Known issues are still open but may or may not be fixed in the
future.

Known (permanent) – A known issue or limitation that is not intended to be fixed in
the future.

Resolved – An issue that was resolved (usually either fixed or documented) in this
release.
Defect No.
A unique identification number that is used to track each issue reported.
Product or Component
The product or component to which the issue relates; for example, an API.
Description
A summary description of the issue. For non-resolved issues, a workaround is included when
available.
Issues Sorted by Type, PowerMedia XMS Release 3.1
Issue
Type
Defect
No.
Product or
Component
Description
Known
XMS-3430
HMP
When receiving G.723 with a 30 ms
frame size and recording to AMR-WB
or Opus, recordings are not played
back properly.
Known
XMS-3685
XMS
Any WebRTC or SIP calls that remain
active when the XMS services are
restarted or stopped (either by a
normal stop or stopped after the
graceful shutdown timer has expired)
will be displayed as active in the CDR
results even though those calls have
been terminated.
26
Issue
Type
Defect
No.
Product or
Component
Description
Known
N/A
CDR
When upgrading to XMS 3.1, CDR
configuration settings are not
preserved and must be reentered.
Known
N/A
WebUI
If upgrading from 3.0 Service Update
1 or 2.4 Service Update 7, you must
use the command line upgrade
process. There is a known defect in
the 3.0 SU 1 and 2.4 SU 7 WebUI
upgrade process. If you have already
attempted to upgrade using the
WebUI, you can remove and reinstall
XMS using the command line
installation. Refer to "RPM Installation
and Script Options" in the Dialogic®
PowerMedia™ XMS Installation and
Configuration Guide for information
on how to upgrade your system using
the command line upgrade script.
Known
(permanent)
XMS-2863
HTTP
When using both HTTPS and lighttpd
under high stress, PowerMedia XMS
performance is negatively impacted.
The factors that cause this are as
follows:

Lighttpd can cause
performance issues when
handling HTTPS transactions.

XMS uses libcurl, which has
code that blocks during HTTPS
transactions.
The performance penalty of using
both HTTPS and lighttpd grows under
the constant load. This causes the
XMS to perform negatively in various
ways. For example, delays in fetching
prompts and lost media transactions
have been observed.
During Dialogic testing, these issues
were not observed when using
Apache, so consider using alternative
HTTP servers for high volume
deployments.
27
Issue
Type
Defect
No.
Product or
Component
Description
Known
(permanent)
XMS-3028
Install (ISO)
In some cases, text and image
overlays for conferencing captions
are not visible in video conferences
after installing PowerMedia XMS on
CentOS 7. To resolve the issue, open
a terminal session on the PowerMedia
XMS system, update the following
packages, and restart the system:

yum update glib2

yum update gdk-pixbuf2
Known
(permanent)
XMS-2830
Install (ISO)
Newer servers require OS install boot
media to be UEFI bootable.
Known
(permanent)
IPY00102868
MSML
Simultaneous play and record with
record beep is not possible because
both play and record cannot transmit
to the same connection.
Known
(permanent)
IPY00102674
MSML
When playing audio and video, both
files must reside on either local
(file://) or server (http://).
Known
(permanent)
IPY00102025
MSML
MSML returns error when using the
<var> element with "duration" type
and "yrs" subtype.
Known
(permanent)
XMS-2579
MSML
MSML legacy does not accept session
IDs and session versions longer than
9223372036854775807, which
causes re-INVITEs to be ignored.
Known
(permanent)
XMS-2999
Dialogic®
Brooktrout®
SR140
Software
When using driver modules that are
not supplied by Red Hat, the
following message is found after
rebooting XMS: kernel: boston:
module verification failed: signature
and/or required key missing - tainting
kernel. However, the message is not
an indication of an issue.
Known
(permanent)
XMS-2885
WebGUI
Changing user settings (user
passwords, polling times in options
menu) can make user credentials
temporarily invalid. Refreshing the
page in the browser resolves the
issue.
28
Issue
Type
Defect
No.
Product or
Component
Description
Known
(permanent)
XMS-3232
XMS
The API supports both 8 kHz and 16
kHz for the sampling rate of Opus
recordings, but XMS internally uses
the sampling rate of 16 kHz for
generating Opus audio streams.
Issues Sorted by Type, PowerMedia MRB
Issue
Type
Defect
No.
Product or
Component
Description
Known
MRB-178
MRB
If failover occurs while performing an
unjoin, the MRB will fail to respond to
the unjoin.
Known
MRB-134
MRB
PowerMedia MRB does not transmit
MSML send events to the correct
media server.
Known
MRB-129
MRB
When the conference is moved to the
new MS such that all licensed ports
are taken over, the Signaling
Sessions are reduced to 0. This
results in OPTIONS pings to the MS
getting returned with a "486 Busy
Here", which the MRB adaptor
interprets to mean the MS has failed.
Known
MRB-97
MRB
There are active dialogs on the
conference (such as record or play
announcement into the conference)
when the MRB decides to perform a
failover. In this case, the active
dialogs are not recreated on the
conference after it has been failed
over to the different XMS.
MRB
PowerMedia MRB does not support
the management of multiple MSML
conference instances in a single SIP
control channel.
Known
29
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising