Release Notes:

New Feature

  • MS Enabled SIP Timer - PowerMedia XMS Release 3.5 Service Update 15 includes a behavioral update to the PowerMedia XMS SIP Session Timer functionality to align with RFC 4028; enabling support for a MS Enabled SIP Timer.

Resolved Issues

  • XMS-11250 [MSML] When requesting to process play with barge and faxdetect, then faxdetect would terminate upon digit arrival.
  • XMS-11251 [Nodecontroller] The faxservice status shows "STARTING", although it failed to start because of race condition between SR140 driver load completion and faxservice start call.
  • XMS-11460 [RESTful] The xmsrest service crashes during load testing.
  • XMS-11295 [XMS] There is a discrepancy between the codec and SIP/RTP usage reporting.
  • XMS-11209 [XMS] After the occurrence of "491 Pending Request", XMS returns full SDP set for answer SDP to the client’s refresh.
  • XMS-11169 [XMS] All the media sent to private address of XMS deployed in EC2 after re-INVITE. As the result, DTMF digits do not reach to XMS.
  • XMS-10776 [XMS] After a failover, calls are stuck even though they are moved to the other XMS and session timers have expired.
  • XMS-10775 [XMS] After a failover, calls are stuck even though they are moved to another XMS and session timers have expired.
  • XMS-10582 [XMS] The layout_region parameter shows a different behavior if the region is ordered differently.

Known Issues

  • XMS-11297 [XMS] XMS ignores the session expiration setting and uses minimum of 90 seconds when the caller does not support session timers.
  • XMS-11521/XMS-11510 [XMS] When XMS issues a re-INVITE (i.e., direction changes) to a Google Chrome 74 (or later) client, video may be of much degraded quality and there may be flooding error prints in the messages file. This issue was revealed after release of Google Chrome 74.