Field Notice: FN - 72434 - Media Server Might Crash/Restart During Download of Prompts Over HTTP - Software Upgrade Recommended

Notice

THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTY OF MERCHANTABILITY. YOUR USE OF THE INFORMATION ON THE FIELD NOTICE OR MATERIALS LINKED FROM THE FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME.

Revision History

Revision	Publish Date	Comments
1.0	07-Nov-22	Initial Release

Products Affected

Affected OS Type	Affected Software Product	Affected Release	Affected Release Number	Comments
NON-IOS	Base Software	RI	RI.2022.05, RI.2022.06	Cisco BroadWorks Release Independent

Defect Information

Defect ID	Headline
CSCwd28631	Media Server may crash/restart during download of prompts over HTTP

Problem Description

Media Server might crash/restart during HTTP downloads for native Interactive Voice Response (IVR) applications.

Background

Media Server might crash/restart during HTTP downloads for native IVR applications. HTTP downloads for VoiceXML (VXML)/Call Control XML (CCXML) applications are not affected by this issue.

Problem Symptom

There is a possibility that Media Server might crash or restart while downloading prompts over HTTP for native IVR applications. If this occurs more than five times, manual intervention is required to restart Media Server. In order to restart Media Server, log in to Media Server as the bwadmin user and invoke startbw from the shell.

An example of such an interaction is shown here:

bwadmin@mediaserver$ startbw

BroadWorks control script version 2022.10

Starting BroadWorks...



Broadcast message from root@mediaserver (Tue Oct 25 13:48:11 2022):



===== BROADWORKS CONTROL --- START INITIATED ON MEDIASERVER =====

LogServer is already running!

Starting msfe...

 

The signature for this issue consists of a crash/restart of Media Server and a log that indicates transmission of a SIP 501 response to an INFO request. An example of such a log entry follows:

2022.06.25 13:53:08:751 EDT | Info       | Sip | 1771 | XsiCTIActionsSpeedDial100 | IVR | localHost5:4 | a145ab9e-ec0c-434d-b052-5b96f0114a49



udp 352 SIP Bytes IN from xxx.xxx.xxx.xxx:yyyy
SIP/2.0 501 Not Implemented
Via: SIP/2.0/UDP xxx.xxx.xxx.xxx:yyyy;branch=z9hG4bK-xxx.xxx.xxx.xxxV5060-0-234840274-1460704970-1656179573152-


From: <sip:zzzzzzzzzz@test.com>;tag=1460704970-1656179573152-


To: <sip:ivr@xxx.xxx.xxx.xxx:yyyy>;tag=353207722

Call-ID: BW135253152250622-382123579@xxx.xxx.xxx.xxx
CSeq: 234840274 INFO
Content-Length: 0

Workaround/Solution

Solution

In order to resolve this issue, we recommend that users download and install MS_Rel_2022.06_1.255 or later.

For More Information

If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:

• Open a service request on Cisco.com
• By email or telephone

Receive Email Notification For New Field Notices

My Notifications—Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.