[ previous ] [ next ] [ threads ]
 To :  yate@v...
 From :  "Raffaele P. Guidi" <raffaele.p.guidi@g...>
 Subject :  Disable silence suppression while recording sip calls?
 Date :  Fri, 28 Nov 2008 10:45:28 +0100
Hi,
I'm trying to record calls made through sip. Recording has to be started
only with peer approval, so the operator starts it dialing * three times.
This works well (see configuration below) except for one thing: being the
callrecorded in two separate .gsm files (caller, callee) silence suppression
takes out of synch leg-a and leg-b! This is awful! Even mixing together the
two legs if one of the peer stops talking the silence is not recorded (in
fact duration and weight of leg-a.gsm and leg-b.gsm are always different).

As the recording should have legal value this cannot work. Possible
solutions:
 1) record both legs in the same file
 2) disable silence suppression on both legs (but I suppose it is made at
the client side)
 3) forward both legs on a recorded conference call

I cannot find any documentation about solution 1 and 2, Can you give me some
directions? Do you think solution 3 could work?

Thanks a lot and regards,
   Raffaele


PS:
I'm using yate on the windows platform
PPS: Yate rocks! :D


[testrecord]
trigger=\*\*\*
message=chan.record
call=wave/record/c:/temp/leg-a.gsm
peer=wave/record/c:/temp/leg-b.gsm



Hi,

I'm trying to record calls made through sip. Recording has to be started only with peer approval, so the operator starts it dialing * three times. This works well (see configuration below) except for one thing: being the callrecorded in two separate .gsm files (caller, callee) silence suppression takes out of synch leg-a and leg-b! This is awful! Even mixing together the two legs if one of the peer stops talking the silence is not recorded (in fact duration and weight of leg-a.gsm and leg-b.gsm are always different). 

As the recording should have legal value this cannot work. Possible solutions: 
 1) record both legs in the same file 
 2) disable silence suppression on both legs (but I suppose it is made at the client side)
 3) forward both legs on a recorded conference call

I cannot find any documentation about solution 1 and 2, Can you give me some directions? Do you think solution 3 could work?

Thanks a lot and regards,
   Raffaele


PS:
I'm using yate on the windows platform
PPS: Yate rocks! :D

<snippet from pbxassist.conf>
[testrecord]
trigger=\*\*\*
message=chan.record
call=wave/record/c:/temp/leg-a.gsm
peer=wave/record/c:/temp/leg-b.gsm