|Summary:||ASTERISK-07151: [copyright violation] broken audio when spying any channel|
|Reporter:||Roberto Lopes (rflopes3)||Labels:|
|Date Opened:||2006-06-12 14:35:58||Date Closed:||2006-08-25 11:25:28|
|Environment:||Attachments:||( 0) bugchanspy2.txt|
( 1) console.tar.gz
( 2) console.txt
|Description:||I have tested with 220.127.116.11 and the problem ramains. |
Everytime that I start spying a channel I heard only parts of audio. This is reproductible everytime here. Sounds like loosing frames!
|Comments:||By: Roberto Lopes (rflopes3) 2006-06-12 14:49:54|
The test is simple:
Do a SIP to SIP call and get another SIP extension to make a ChanSpy(). If one of the parties of the call keep talking, the voice is cutted several times, so a phrase like "I don't want to go away" sounds like "I ... want ...away", or something like this.
By: Serge Vecher (serge-v) 2006-06-12 20:07:45
and I've asked you to reopen the bug, not open a new one, didn't I?
1. What environment is this used in, what channels, aps, etc.
2. Is anything reported on the console --> if so, please include that console output here as an attachment.
By: Roberto Lopes (rflopes3) 2006-06-12 21:14:20
Well I'm sorry for that "reopen" thing.
Answering your questions:
1) I have tested with all types of channels (SIP, ZAP, Unicall, IAX2) but my interest is SIP channels. This occurs everytime here in lab and on my clients with 300 agents on it.
2) Nothing is reported on the console with verbosity level at 3. I'll try to increase this level tomorow.
By: Serge Vecher (serge-v) 2006-06-16 13:12:17
in addition to increasing verbosity, make sure your logger.conf has the following line:
console => notice,warning,error,debug
resart asterisk, do 'set debug 4' at cli do some spying and post the resulting console log as an _attachment_ here. Thanks.
By: BJ Weschke (bweschke) 2006-06-21 22:53:44
just out of curiosity, what does the load average of this system look like when you're trying to do this? 300 live agents is pretty intense for any single asterisk system and adding ChanSpy to things certainly will not help.
By: Roberto Lopes (rflopes3) 2006-06-22 08:37:00
Well, the load is not the problem since that even here on the lab where I have 3 agents on AMD64 3400+ with 4GB RAM the problem occurs.
I'll upload the results of console today later.
By: Roberto Lopes (rflopes3) 2006-06-23 08:27:48
Please consider only bugchanspy2.txt because the debug level was 0 on the previous file.
I have noted that:
On the lines bellow there was no voice on the spying channel
Jun 23 10:24:16 DEBUG channel.c: Spy 'ChanSpy' on channel 'SIP/3050-2658' read queue too long, dropping frames
Jun 23 10:24:16 DEBUG channel.c: Spy 'ChanSpy' on channel 'SIP/3050-2658' write queue too long, dropping frames
On the line bellow there is voice on the spying channel
Jun 23 10:24:16 DEBUG rtp.c: Got RTCP report of 88 bytes
As you can see on the file uploaded, the lines with "queue frames too long" happens a lot.
By: Roberto Lopes (rflopes3) 2006-06-23 08:45:04
I don't know if it's relevant but we are using ulaw codec. (G.711.U).
By: Serge Vecher (serge-v) 2006-06-28 12:55:04
hmmm, I don't like this message before ChanSpy even gets involved:
Jun 23 10:24:13 DEBUG channel.c: Avoiding initial deadlock for 'SIP/3005-aeaa'
in addition to 'set verbose 4' and 'set debug 4', please also do 'sip debug' and capture a complete log from when you start the call to when it ends. Please do this on your test system, so that unrevelevant traffic is not captured. Also, make sure this log is from the console, not from the debug file -- some information is missing when you log to debug file. Thanks.
By: Roberto Lopes (rflopes3) 2006-07-02 20:43:06
I'll do that on manday 07/03/06 for sure.
By: Roberto Lopes (rflopes3) 2006-07-04 15:04:02
As you asked for, here is the console with sip debug enabled.
By: Roberto Lopes (rflopes3) 2006-07-10 07:34:14
Some news about this case. It's really important to me and I believe to any call centre that monitor any agent.
By: Kevin P. Fleming (kpfleming) 2006-08-08 11:54:41
We do not accept bug reports against third-party modified copies of Asterisk. If you can reproduce your problem with Asterisk 1.2.10 without third-party patches that affect these areas of the system, feel free to request the bug to be reopened.
By: Roberto Lopes (rflopes3) 2006-08-08 12:22:35
As I wrote on the description of the bug, I have tried with 18.104.22.168 and the problem remains. Please, reopen the bug.
By: Kevin P. Fleming (kpfleming) 2006-08-08 13:30:12
There is no evidence of that in this bug report; the console trace you supplied is from a completely different product (it appears).