Summary:	ASTERISK-15354: No hold event is generated for a second call on a SIP channel
Reporter:	George Spiliotis (gspiliot)	Labels:
Date Opened:	2009-12-22 10:58:45.000-0600	Date Closed:	2011-06-07 14:00:35
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Core/ManagerInterface
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) HOLD.txt
Description:	The problem is easily reproducible. SIP Phone A calls SIP phone B. B answers the call. SIP Phone C calls phone B. B puts call A on hold (event generated) and answers C. Now phone B puts C on hold: NO hold event is generated (hold works ok though). B can unhold/hold C as many times without any event generated.
Comments:	By: George Spiliotis (gspiliot) 2009-12-22 10:59:51.000-0600 I have uploaded a trace of the events on our system (FreePBX): Phone 305 calls phone 304, 304 holds/unholds (which can be seen in the trace), then phone 4999 calls 304, 304 holds 305 and answers 4999, that's the last seen event in the trace file even if 305 holds and unholds repeatedly (I have ommited the final trace). By: Leif Madsen (lmadsen) 2009-12-22 11:08:46.000-0600 What version of Asterisk is this? By: George Spiliotis (gspiliot) 2009-12-22 12:20:00.000-0600 The asterisk version is 1.4.26.1 By: Jeff Peeler (jpeeler) 2010-01-27 16:46:15.000-0600 I've tried to reproduce this but am seeing all the hold/unhold events get generated. If this is still a problem, can you upload your sip.conf? By: Leif Madsen (lmadsen) 2010-01-28 10:46:42.000-0600 Setting to feedback while we await information from the reporter. By: George Spiliotis (gspiliot) 2010-02-01 04:55:22.000-0600 I have discovered (it is very hard to get hold of any updated documentation) that by adding: callevents=yes in sip.conf we finally get all hold events. We can now close this bug and I am very sorry for any inconvenience this might have caused. By: Jeff Peeler (jpeeler) 2010-02-01 11:07:37.000-0600 Closed at request of reporter, thanks for reporting back.