Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Message clipping after codec swap

Unity 4.03sr1 integrated with CM3.3.4 and Exchange 2003.

We recently changed our recording codec from G711ulaw to GSM 6.10 to save email space and to allow playback on handheld devices.

Since the codec swap, users are reporting random clipped voicemail messages. They either get a blank 0 second wav file, or the message is clipped to only the last few seconds of what the caller actually recorded. The caller isn't getting cut off, so they think the message has recorded correctly.

The callers are mostly from other CM sites using intercluster trunks (no gateway involved), but we have had reports of callers in the same site too.

We're seeing this in the event log on the box also:

Event Type: Warning

Event Source: CiscoUnity_ConvSubscriber

Event Category: Warning

Event ID: 457

Date: 10/11/2005

Time: 11:17:49 AM

User: N/A

Computer: UNITYCMH1

Description:

The description for Event ID ( 457 ) in Source ( CiscoUnity_ConvSubscriber ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: Zero length Stream found, 412, H:\views\ESB1_view\un_Conv1\AvConvSubscriber\AvConvSubMsgPlaySvr\AvSValidMsgStreams.cpp,

We don't want to swap the codec back, but we're going to have to if we can't get this figured out.

2 REPLIES
Cisco Employee

Re: Message clipping after codec swap

You may be running into a known defect CSCef93868.

4.0(3)ES100 is available to address this issue, you should contact TAC in order to obtain this fix.

New Member

Re: Message clipping after codec swap

I hadn't had a chance to post a followup yet today. We contacted TAC this morning and they came to the same conclusion. Fix is going in tonight.

220
Views
0
Helpful
2
Replies
CreatePlease login to create content