Call Recording - Is it broken?

[MisterEd]

Was just testing call recording (sounds like a neat feature). Made a 10 second call, got the WAV file in email but nothing will play it. I looked at it and it in Outlook and it says it's only 151 bytes, when I save it, it is a ZERO byte file.

I then made a second call. Same problem. Is call recording broken?

I have attached the 2 WAV files if anyone wants to look at them.

[MisterEd]

Interesting .... from vPanel the files play fine and from GMAIL WEBMAIL they are fine. It must be Outlook that is killing them.

[MisterEd]

When I have the file emailed to my GMAIL account it comes through as a zero byte .WAV attachment that won't play. When I send it to my VERIZON or COMCAST email accounts it comes through as old fashioned MIME text data embedded in the message like this:


From: vpanel@voipo.com [mailto:vpanel@voipo.com]
Sent: Saturday, December 12, 2009 3:00 PM
To: ed
Subject: VOIPo Call Recording

Reply-To: do-not-reply@voipo.com

Content-Type: multipart/mixed; boundary="PHP-mixed-a9b7cd66318e562786bc89bb58802089"

Message-Id: <20091212200002.30AD12DCC23F@db03.voipwelcome.com>
Date: Sat, 12 Dec 2009 20:00:02 +0000 (UTC)


--PHP-mixed-a9b7cd66318e562786bc89bb58802089

Content-Type: multipart/alternative; boundary="PHP-alt-a9b7cd66318e562786bc89bb58802089"

--PHP-alt-a9b7cd66318e562786bc89bb58802089

Content-Type: text/html; charset="iso-8859-1"

Content-Transfer-Encoding: 7bit

<p>You have received a new VOIPo recording, file is attached as wav format.</p>

--PHP-alt-a9b7cd66318e562786bc89bb58802089--

--PHP-mixed-a9b7cd66318e562786bc89bb58802089

Content-Type: audio/wav; name="8003310500_20091212-194751.wav"

Content-Transfer-Encoding: base64

Content-Description: Sound attachment

Content-Disposition: attachment; filename="8003310500_20091212-194751.wav"

UklGRqRUCABXQVZFZm10IBAAAAABAAEAQB8AAIA+AAACABAAZG F0YYBUCAAIAAAAAAAIAAgACAAQ

AAgACAAQABAACAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQAB AAEAAQABAAEAAQABAAEAAQABAA

EAAQABAAEAAIABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEA AQABAAEAAQABAAEAAQABAAEAAQ

ABAAEAAQABAAEAAQABAAEAAQABAAEAAQABAAEAAQAAgAEAAQAB AAEAAQABAAEAAQABAAEAAQABAA

[usa2k]

Just tried it and it worked perfectly.

Only complaint I have is I have never had DTMF work when call recording is used. DTMF works on the same number when dialed without call recording. I put a ticket in, but that was never corrected yet. I do not think its been forgotten, just other priorities at VOIPo for now. I've only made test calls, and never had an actual need for it. (JJL-797313)

[statustray]

Just tried it and it worked perfectly.

Only complaint I have is I have never had DTMF work when call recording is used. DTMF works on the same number when dialed without call recording. I put a ticket in, but that was never corrected yet. I do not think its been forgotten, just other priorities at VOIPo for now. I've only made test calls, and never had an actual need for it.

I used it about 4 times today, and each time it worked perfectly for me. I even had it email me too to my gmail account. The conversation recorded lasted about 10 mins or so, and the wave file was about 9 megabytes.

Played perfectly in gmail email, and also when I downloaded to my computer it played perfectly too.

I don't know if it was me though or what on another issue, at times the conversation became a little garbled- as if I were talking on a cell phone. Not sure what was up with that.

I did see in vpanel that they said call quality could be negatively impacted as the call was not being routed through the traditional voice servers. Perhaps that could have been it??

Other than that, it was fine ;-)

[MisterEd]

Strange ... I can listen to regular voicemail anywhere with no problem (Outlook included) but the "call recording" emails in Outlook won't work (I tried 6 different emails including Comcast.net, verizon.net and 4 from gmail). They are fine thorugh webmail and are even fine on my iPhone email. Something Outlook doesn't like about the way they are sent out.

[usa2k]

I use Google Apps GMail with my own URL.

[fredco]

The two inbound and one outbound call recordings I made about 30 minutes ago (to demo the feature to a friend who I am trying to refer to VOIPo) all arrived as plain text emails with a text attachment instead of a .wav file. Same situation as mentioned previously in this thread. A couple weeks ago when I did a test recording it worked fine and I received a .wav attachment.

I am receiving voicemail emails in HTML format with attached wave files. No problems there.

Using Outlook 2003 as my email program and NIS 2009 as the AV scanner.

[tritch]

Something Outlook doesn't like about the way they are sent out.

MisterEd, I tested this about a month ago and can confirm the same problem in Outlook. I download all of my email through Gmail's POP3 server to Outlook 2003. The issues you described are identical to mine. If I access the email through Gmail's web interface or retrieve the file through vPanel, the wav file seems to be fine. I've never had an issue with any attachment in Outlook before, so something is a bit strange about this email that Outlook doesn't like.......

[MisterEd]

MisterEd, I tested this about a month ago and can confirm the same problem in Outlook. I download all of my email through Gmail's POP3 server to Outlook 2003. The issues you described are identical to mine. If I access the email through Gmail's web interface or retrieve the file through vPanel, the wav file seems to be fine. I've never had an issue with any attachment in Outlook before, so something is a bit strange about this email that Outlook doesn't like.......

Even stranger is that my IPHONE was getting them fine but this morning my IPHONE also received one as MIME text then when I resent it it was fine. I have also turned off Anti-Virus but since it happens on my iPhone as well I can't blame that, I have also tried through 3 different ISP's as well.

In Outlook 2007 they are always unplayable 151 byte files and when saved they are ZERO bytes. They play fine in vPanel and via webmail.

I just send myself a few small WAV files from 1 ISP to another and it downloaded and played fine in Outlook.

The problem has to be the way these emails are being sent from the source.