This section describes significant changes to the PowerMedia XMS Release 2.0 subsequent to the general availability release.
This Service Update for PowerMedia XMS Release 2.0 is now available. This updates provide fixes to known problems, and may also introduce new functionality. It is intended that new versions of the Service Update will be released periodically.
For information about installing this release, refer to the Dialogic® PowerMedia™ XMS Installation and Configuration Guide.
PowerMedia XMS supports a number of control interfaces including NETANN, RESTful, VXML, MSML, JSR 309, etc. It must be noted that prevailing standards related specifically to NETANN, RESTful, VXML have quickly evolved. Dialogic is fully committed to ensure that PowerMedia XMS complies to the latest standards and has enhanced PowerMedia XMS software to support newer additions to these control interfaces.
With Service Update 3, current PowerMedia XMS Release 2.0 customers that integrate to PowerMedia XMS via one of the aforementioned control interfaces (NETANN, RESTful, VXML) are strongly encouraged to upgrade their current deployment to PowerMedia XMS Release 2.2 or later to take advantage of the advancements in the product. For NETANN, RESTful, VXML, functionality remains in this release but goes through minimal validation. The issues reported against NETANN, RESTful, VXML interfaces will be fixed in PowerMedia XMS Release 2.2 or later. For clarity, we do not expect customers using MSML to be affected by this.
As a general policy, we encourage all our customers to consider using the latest generally available software release for their network deployment. If you have any questions or require assistance to upgrade to PowerMedia XMS Release 2.2 or later, please contact Dialogic global support.
The MSML Media Server has been updated to resolve several issues related to handling of SIP Session timers. The previous version of the media server includes the Supported and Session-Expires header fields in the 2xx response, but did not refresh the call session using re-INVITE messages when "refresher=uas" is specified.
With Service Update 1, if the caller / AS doesn’t specify the support of SIP session timers by including the Supported header field with the option tag "timer", the media server will assume responsibility of session refreshes and send a re-INVITE for sessions that are connected for longer than the default session expiry of 1 hour. See http://www.ietf.org/rfc/rfc4028.txt for additional information regarding use of Session timers in SIP.
Service Update 1 adds support for Early Media through MSML Media Server Interface. This feature when enabled modifies the MSML media server operational behavior to start media sessions (i.e., the RTP Receive port) in unison with sending a 200 OK containing an offer SDP. The media session is configured based on the preferred codec, which is specified by listed order in the SDP. The local receive port is initialized and configured to accept RTP packets. Once the media server starts receiving an RTP stream, it will detect if the streams payload type matches the configured settings. Upon satisfying a payload type mismatch criteria, the media server will transition to a new coder configuration corresponding to the RTP stream’s coder type as specified by the payload type of the incoming packets.
The Early Media feature is disabled by default. The feature is enabled through the PowerMedia XMS Admin Console under MSML Advanced Configuration page of the MSML menu by setting the Early Media Audio parameter to "yes" and clicking the Apply button.
This feature is restricted to audio profile types as defined in RFC 3551 http://www.ietf.org/rfc/rfc3551.txt. Only static payload types are supported. This feature is restricted to two coders types, G.711 and G.729.