[Freeswitch-users] Recording Duration on EC2

[Stephen Dame]

Byron,

 

We run a talk radio show based in EC2 with automated 55 minute shows,  I have the same issue and never could figure out why recordings where short…  You never lose full words,  but a trained radio person can hear the missing bits along the way.   Here are the last 20 shows, see below     I had tried both wav and mp3, and messed with settings for energy, write buffers, continuous transmit etc…   Never thought of trying it on bare metal server.    I’m running c1.medium with ubuntu10.04 with 1.06FS.   Overall works great, just need to fill the missing seconds in radio schedule when rebroadcasting.

 

Here is the length of last 20 shows, so how do you monitor steal time?

 

Length:      54:35

Length:      54:37

Length:      54:20

Length:      54:39

Length:      54:38

Length:      54:38

Length:      54:40

Length:      54:38

Length:      54:36

Length:      54:32

Length:      54:45

Length:      54:37

Length:      54:36

Length:      54:36

Length:      54:35

Length:      54:40

Length:      54:42

Length:      54:44

Length:      54:35

Length:      53:57

 

Regards,

Stephen

 

HostBBB – Online Learning Solutions  http://www.hostbbb.com <http://www.hostbbb.com/> 

207 Technology Group Inc.   1-888-229-9756  skype: Stephen_Dame

 

From: freeswitch-users-bounces at lists.freeswitch.org [mailto:freeswitch-users-bounces at lists.freeswitch.org] On Behalf Of Byron Clark
Sent: Monday, August 26, 2013 1:36 PM
To: FreeSWITCH Users
Subject: [Freeswitch-users] Recording Duration on EC2

 

I'm using FreeSWITCH on EC2 to call into a conference bridge and record the audio from the conference. It works well except for one thing: the recording contains all the audio from the call, but the duration of the file is shorter than the call. The duration is typically 3-5 seconds shorter than the call for each 5 minutes of call. On a recent test, wall clock showed a duration of 15:32.93 but the duration of the recording file was 15:19.96. The ugly part is that this only happens on EC2 instances where there is some CPU steal time (<5%) occurring. 

 

Here's my setup:

Operating System: Ubuntu 12.04

FreeSWITCH: 1.2.12

 

Command I'm using to start the call:

originate {record_waste_resources=true}sofia/external/SIPADDR &record(/tmp/record1.wav) default default

 

Any ideas on how to make the recording duration actually match up with the call duration? Or even what's really going wrong so I can work on fixing that?

 

--
Byron Clark

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20130828/904aa35c/attachment.html