Summary:ASTERISK-09075: chanspy in private whisper by default
Reporter:Gergely Dömsödi (doome)Labels:
Date Opened:2007-03-22 07:06:26Date Closed:2011-06-07 14:02:37
Versions:Frequency of
Environment:Attachments:( 0) console.log
( 1) extensions.conf
( 2) extensions.conf.test
( 3) sip.conf
( 4) sip.conf.test
( 5) verbosedebug.txt.tar.gz
Description:When using chanspy without arguments (so not in whisper mode) it "confuses" the channels. It transmits the audio from the spying channel to the spied channel, but it does'nt transmit any audio to the spying channel from the spied channel (nor the spied call).

It seems it is in the "private whisper" functionality by default, which cannot be turned off.


Using manager Originate to connect outbound calls to a queue, where the "inner" SIP channels are receiving them.
The spying channel is another SIP channel.
The "inner" spying extension is:

exten _35XXX,1,ChanSpy(SIP/${EXTEN:2})
Comments:By: Joshua C. Colp (jcolp) 2007-03-22 11:43:26

Please try with a newer version (1.4.2) as 1.4.0 is quite old now and things changed a lot in regards to whisper/chanspy.

By: Gergely Dömsödi (doome) 2007-03-23 06:33:47

Everything is the same with 1.4.2.

By: Joshua C. Colp (jcolp) 2007-03-23 12:01:22

Okay, then I need to see console output to see what channels are up and what channels are being spied on.

By: Gergely Dömsödi (doome) 2007-03-23 12:35:42

I attached the involved parts of my sip and extension.conf, and the console log.
The console log is about:
SIP/100,101 registering in
SIP/101 calls an external Zap number
SIP/100 ChanSpies on SIP/101 without any ChanSpy arguments

The audio between 101 and the Zap channel was perfect. When 100 chanspied, "sip one zero one" could be heard on that channel, and the beep indicating the beginning of spy was on SIP/101. Audio from channel 100 was transmitted to 101, but audio from the bridged call wasn't transmitted to the spying channel.

By: Serge Vecher (serge-v) 2007-03-23 13:49:54

Please redo the console log as per following:

1) Prepare test environment (reduce the amount of unrelated traffic on the server);
2) Make sure your logger.conf has the following line:
  console => notice,warning,error,debug
3) restart Asterisk with the following command:
  'asterisk -Tvvvvvdddddngc | tee /tmp/verbosedebug.txt'
4) Enable SIP transaction logging with the following CLI commands (1.4/trunk commands in parenthesis):
set debug 4 (core set debug 4)
set verbose 4 (core set verbose 4)
sip debug (sip set debug)
5) Reproduce the problem
6) Trim startup information and attach verbosedebug.txt to the issue.

By: Gergely Dömsödi (doome) 2007-03-23 14:40:13

I attached the requested file. I didn't trim the beginning because I couldn't know what is important :)
Had to gzip it because it was a little big...

By: Joshua C. Colp (jcolp) 2007-03-26 10:44:58

Here's what I have labbed up and what happened:

First scenario:
Polycom calls IAX2 address.
PAP2 ChanSpys (with no options besides SIP/polycom) on Polycom.
PAP2 hears conversation between Polycom and IAX2 address.

Second scenario:
Polycom has MixMonitor started.
Polycom calls IAX2 address.
PAP2 ChanSpys (with no options besides SIP/polycom) on Polycom.
PAP2 hears conversation between Polycom and IAX2 address.

Works as expected.

Can you test without the Zap channel present?

By: Gergely Dömsödi (doome) 2007-03-26 13:29:29

I have set up another test enviroment. An asterisk server, a VoIP (SIP/100) phone, and two software clients, one linphone SIP(102), and an SjPhone (SIP/103).

I called every client from every phone, and tried to spy from the third, but there was no audio on the spying channel.

Meanwhile I realized a few things:
- canreinvite = no MUST be set on the clients, becase if not, sometimes there are no audio between the channels
- when i called 101 from 102. A very crappy and noisy audio got transferred to the calling channel. When I spyed on it from 100. The noise stopped, and there was no audio on the spying channel...

I created a very minimalist extensions.conf and sip.conf for this testing environment, which I attach.
I tried it also on mISDN with no success...

Although I observed a little difference in this test environment. The beep following the "sip one zero zero" voice was not transmitted to the spying nor the spied channel.

By: Joshua C. Colp (jcolp) 2007-06-19 08:42:07

Hrm... this works fine for me yet again. What codecs end up getting negotiated? Is silence suppression on at all on the devices?

By: Joshua C. Colp (jcolp) 2007-07-08 23:08:23

It has been 3 weeks now without the needed information. If you can get it and this still happens, please reply.