[Asterisk-Dev] Problems with call recording (and NEWJB?)

[Steve Kann]

Tamas,

    Do calls which are not being monitored work well with the New JB?  I 
can see two possibilities here:

a) There's a problem with the NEWJB handling something about your 
environment;  generally, you'd see this on the calls going IAX->*->PRI 
you mention.  See the new README.jitterbuffer, or my previous e-mails to 
the list for debugging steps here.  Do iax2 show netstats to see what 
the jitterbuffer is doing..

b) There's some strange interaction between res_monitor, (or more 
specifically, the monitoring stuff in channel.c, and ast_writestream and 
friends), and the new JB.   Perhaps it is barfing when it sees 
interpolation frames (voice frames with datalen==0), or something, but 
if you're recording to slinear, the PLC should actually make more normal 
voice frames in this case..



Tamas J wrote:

>Update:
>I recompiled the CVS-HEAD with turned off NEWJB (in chan_iax2.c
>commented #define NEWJB) and surprisingly the problem went away. I have
>normal call recording now :)
>Unfortunately I don't have possibility to try other channels (e.g. SIP),
>so I cannot be sure that the chan_iax2 is itself broken or something
>else around new jitterbuffer.
>
>Regards,
>	Tamas
>
>ps: probably I should prepare a bug ticket now...
>
>Tamas Jalsovszky wrote:
>  
>
>>Update:
>>
>>I did more compilation and found:
>>version CVS-D2005.03.17.00.00.00 still works, while version
>>CVS-D2005.03.18.00.00.00 doesn't.
>>
>>I tryed to call from IAX->*->PRI where the codec was alaw (also tryed
>>speex with the same result). I also tryed to turn off plc (genericplc =>
>>false) but still got the same.
>>
>>I also did a PRI->*->PRI with call recording and it looks the issue is
>>not present in this case.
>>
>>Also did PRI->*->IAX2. This time I got the problem again, however now
>>the 'out' leg was wrong (I'm getting big files time to time with
>>different sizes).
>>
>>Regards,
>>	Tamas
>>
>>Tamas Jalsovszky wrote:
>>
>>    
>>
>>>Hello!
>>>
>>>I use call recording (Monitor application) and right upgraded to CVS
>>>HEAD of Asterisk. For my surprise, the recording went really bad. This
>>>means, that my 'in' call leg's file size started about 430MB.
>>>Interesting is, that the 'out' recording is normal.
>>>I'm recording into sln format and the wrong file consists of 0x00 data
>>>at the beginning (I guess, the 1st unneeded megabytes).
>>>
>>>Version CVS-D2005.03.10.17.10.00 looks to be OK (the previouse version I
>>>used).
>>>
>>>I use:
>>>exten => s,8,Monitor(sln,${RECORDDIR}/${subdir}/${CALLFILENAME},mb)
>>>The filename is good, that shouldn't be the problem.
>>>
>>>Can anybody help?
>>>
>>>Thanks in advance,
>>>	Tamas
>>>      
>>>
>
>_______________________________________________
>Asterisk-Dev mailing list
>Asterisk-Dev at lists.digium.com
>http://lists.digium.com/mailman/listinfo/asterisk-dev
>To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-dev
>
>  
>