This section lists the issues that may affect the PowerMedia XMS Release 2.0.
The following limitations apply to this release:
Only the 16 bit/16 KHz record file format is supported.
The Play prompt file types supported are:
– wav: 16 bit/16 KHz and 8 bit/8 KHz
– alaw and ulaw: 8 bit/8 KHz
The file extension determines the encoding law, as in .alaw or .ulaw.
The table below lists issues that affect the PowerMedia XMS Release 2.0. The following information is provided for each issue:
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.
A unique identification number that is used to track each issue reported.
For defects that were resolved in a Service Update, the Service Update number is shown.
The product or component to which the problem relates; for example, an API.
A summary description of the issue. For non-resolved issues, a workaround is included when available.
Issue |
Defect |
SU |
Product or |
Description |
Resolved |
IPY00116714 |
5 |
MSML |
When fetching prompts from HTTP server, there is a crash on the MSML Media Server. |
Resolved |
IPY00116593 |
5 |
MSML |
When removing and adding connection to a conference on XMS, there is a crash on the MSML Media Server. |
Resolved |
IPY00116477 |
5 |
MSML |
The MSML Media Server deadlocks after announcements are expired from cache and web server is unavailable. |
Resolved |
IPY00116430 |
5 |
MSML |
MSML announcements and recordings can fail when a single HTTP server is unavailable. |
Resolved |
IPY00115554 |
5 |
MSML |
HTTP "External Document Fetch Error" is returned instead of "Put Error" when web server is unavailable. |
Resolved |
IPY00116666 |
5 |
XMS |
Under rare conditions, a media engine segmentation fault is observed. |
Known |
XMS-1220 |
5 |
HMP |
Under rare conditions, there is a crash when playing 16k 16bit prompts from HTTP server. |
Resolved |
IPY00116343 |
3 |
MSML |
Joining 2 call legs (bridge connection) sometimes result in a "Response Code = 500, Description = Create Streams has failed" error message. |
Resolved |
IPY00116253 |
3 |
MSML |
XMS sends BYE if it receives re-INVITE with a=recvonly in the SDP. |
Resolved |
IPY00116078 |
3 |
XMS |
Intermittent hang when shutting down XMS, which requires powering off to recover. |
Resolved |
IPY00116096 |
2 |
MSML |
XMS does not stop sending MSML messages when call leg has ended. In some cases, this caused XMS to send MSML messages on an incorrect call leg. |
Resolved |
IPY00116061 |
2 |
MSML |
Intermittent MSML play dialog returns 200 OK with 502 "No resource to fulfill request" resulting in no audio. |
Resolved |
IPY00115796 |
2 |
MSML |
Compatibility issue with SIP session timers, WebUI parameter added to control behavior. |
Resolved |
IPY00116095 |
2 |
XMS |
Script file installed in crontab during XMS install is in DOS file format. |
Resolved |
IPY00115438 |
1 |
Conferencing |
One way media on some long lived (over 6 days) calls in conference. |
Resolved |
IPY00115365 |
1 |
Conferencing |
Intermittent one way audio with calls placed into conference. |
Resolved |
IPY00115655 |
1 |
MSML |
The MSML Media Server will segmentation fault intermittently when unjoining and joining the same connection. |
Resolved |
IPY00115534 |
1 |
MSML |
The MSML Media Server will segmentation fault in some cases when mixing <var> and audio files. |
Resolved |
IPY00115417 |
1 |
MSML |
The MSML Media Server will not play audio fetched via HTTP with chunked encoding. |
Resolved |
IPY00115371 |
1 |
MSML |
The MSML Media Server stops processing calls after HTTP server fails and recovers. |
Resolved |
IPY00115350 |
1 |
MSML |
The MSML Media Server was not allowing DTMFs to pass thru the conference when <clamp dtmf=''false''> was sent. |
Resolved |
IPY00102771 |
1 |
MSML |
The MSML Media Server responds with "Bad Request - Invalid Dialog Id Requested" during DTMF detect under load. |
Resolved |
IPY00102592 |
1 |
MSML |
The MSML Media Server attempts to fetch HTTP announcement after 404 file not found had already returned, resulting in garbled audio being played. |
Resolved |
IPY00102516 |
1 |
MSML |
The MSML Media Server does not refresh the session when "refresher=uas" is specified. |
Resolved |
IPY00102512 |
1 |
MSML |
The MSML Media Server does not honor the OFFERED preferred codec list during SDP negotiation. |
Resolved |
IPY00102452 |
1 |
MSML |
G.726 codec errors when handling calls. |
Resolved |
IPY00102449 |
1 |
MSML |
The MSML Media Server fails to respond with a 200 OK to an INVITE with a disabled audio stream (audio m= line contains port 0). |
Resolved |
IPY00102398 |
1 |
MSML |
The maxptime in SDP was ignored and not parsed. |
Resolved |
IPY00102351 |
1 |
MSML |
The MSML Media Server does not refresh the session when "refresher=uas" is specified. |
Resolved |
IPY00102264 |
1 |
MSML |
Clearing a cancelled call results in a BYE being transmitted from the Media Server. |
Resolved |
IPY00102159 |
1 |
MSML |
The MSML Media Server unjoin failures when using wildcard "*". |
Resolved |
IPY00102370 |
1 |
WebUI |
NFS Mount Points, Maintenance, and Account Manager tabs are missing when using Internet Explorer (IE) in compatibility mode. |
Known |
IPY00092127 |
-- |
JSR 309 Connector |
OCCAS shows "session is already invalidated" in some situations during releasing. This has no negative impact. When the session timer expires, per SIP specification, the JSR 309 Connector is required to send a BYE message to the XMS. The problem is that if sipd on the XMS was killed, that's what caused the session timer to expire, then it will never be able to receive nor respond to the sip BYE message. The OCCAS tries to resend the message several times and then prints this message indicating that the session is invalidated and therefore cannot deliver the message. |
Known |
IPY00101220 |
-- | VXML |
Playing .ulaw and .alaw files fail when fetching from a Web server, but work fine when fetching local audio files of these types. This issue appears to be related to remote Web server mime-type settings. Refer to the Web server configuration to set .ulaw and .alaw file extension respectively to audio/basic and audio/x-alaw-basic. Tomcat web server configuration example: /tomcat/conf/web.xml |
Known |
IPY00101279 |
-- | VXML |
A NoMatch event is received instead of a NoInput event during hotword barge-in. |
Known |
IPY00101313 |
-- | VXML 2.0 | Conformance test cases 505 & 506: Unsupported language is not triggering an unsupported.language event. The speech recognition continues and triggers a NoInput event instead of unsupported.language. |
Known |
IPY00101343 |
-- | VXML 2.1 | The recordutterance property is being ignored leaving shadow variables like recording, recordingsize, and recordingduration left undefined. |
Known (permanent) |
IPY00102496 |
-- | MSML | Simultaneous play and record with record beep is not possible because both play and record cannot transmit to the same connection. |
Known (permanent) |
IPY00102025 |
-- | MSML | MSML returns error when using the var element with "duration" type and "yrs" subtype. |