Summary:	ASTERISK-27562: ExtenSpy with whisper moves to wrong extension
Reporter:	Bart vd Akker (whizzi)	Labels:
Date Opened:	2018-01-08 07:00:11.000-0600	Date Closed:
Priority:	Major	Regression?
Status:	Open/New	Components:	Applications/app_chanspy
Versions:	13.17.2	Frequency of Occurrence	Constant
Related Issues:
Environment:	CentOS 6.x	Attachments:	( 0) asterisk-log.txt
Description:	Whenever the ExtenSpy command is started before the call, the whisper works to the Extension as expected. When a call is setup and starting the extenspy, the callee is being whispered to (not expected). S = Spy extension A = Phone I want to spy on and whisper to B = Other phone S starts the Extenspy on A A calls B S hears everything, can whisper to A (expected) What happens: A calls B S starts the Extenspy on A S hears everything and whispers to B (unexpected)
Comments:	By: Asterisk Team (asteriskteam) 2018-01-08 07:00:12.178-0600 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Bart vd Akker (whizzi) 2018-01-08 07:01:52.307-0600 asterisk log file By: Bart vd Akker (whizzi) 2018-01-08 07:05:04.385-0600 In the logfile:    -- Executing [s@c0bbedd9-0748-4553-b7bb-8261c47632c6:4] ExtenSpy("SIP/ldaptest_9EyFTus0Nb-0000000b", "ldaptest_lURNBTMy1t,sw") in new stack = started before spied extension started, correct behaviour.    -- Executing [s@c0bbedd9-0748-4553-b7bb-8261c47632c6:4] ExtenSpy("SIP/ldaptest_9EyFTus0Nb-0000000e", "ldaptest_lURNBTMy1t,sw") in new stack = started after spied extension who called started an external call, incorrect behaviour. By: Chris Savinovich (csavinovich) 2018-01-12 16:34:29.757-0600 We were able to replicate this issue by following this sequence: - Using 3 Digium phones.  a. Spy Phone  b. Phone A  c. Phone B 1. Spy phone initiates spying with specific parameter to whisper on station A.  From 1 through 5 it is successfully whispering on A 2. A calls  B 3. B puts A on hold 4. B calls A on a second line 5. A answers second call from B 6. B hangs up first call with A 7. Spy whispering has now been transferred to B! 8. From this point on, If spy phone doesn't hangup, all subsequent inbound calls from B and answered by A, whisper stays on B.