<div dir="ltr"><div><div><div><div><div><div><div><div><div><div><div><div><div><div><div><div><div>hi!,<br><br></div>Asterisk Version:1.6.1.20<br></div>OS: CentOS release 5.3 (Final)<br></div>uname: 2.6.18-128.el5PAE #1 SMP Wed Jan 21 11:19:46 EST 2009 i686 i686 i386 GNU/Linux<br>
</div>Application: Queue<br></div><div>Specific Details: Obtain Acknowledgement from queue member before bridging the caller.<br></div><div>Language: AEL<br></div><div>Similar Example:<a href="http://www.voip-info.org/wiki/view/Asterisk+tips+Queue+Member+ackcall"> http://www.voip-info.org/wiki/view/Asterisk+tips+Queue+Member+ackcall</a>
</div><br>Scenario: <br>1. User calls in a General Number<br></div><br>2. Call is queued in Queue Application<br></div><br>3. Queue calls a Local/xxxx@members channel<br></div><br>4. At members context:<br></div>Dial The real member(called party) channel with a U(GOSUB X) routine<br>
</div>4.1 The "called party" answers, & is led to the GOSUB routine X:<br></div>Here the prompt is given to the called party to acknowledge the incoming call<br></div>[ depending on the out put, this will return appropriate GOSUB result ]<br>
</div>4.2 Based on the GOSUB result, the Dial proceeds<br></div><br>5. The Queue proceeds based on the result taken at 4.2 above.<br></div>i.e. <br>Take it as a success & build the bridge between the caller & member<br>
Whether to DIAL the next member<br><br></div>The Question: All goes well & the dial-plan works. If between step 4.1 & 4.2, the caller hangs up asterisk gives CPU spikes. <br>Symptom: ASTERISK CLI gets stuck until step 4.2 returns.<br>
</div><div><br>Console Error: app_dial.c: Could not stop autoservice on calling channel<br></div><div>[ Somehow get the feeling that this is not the real error]<br><br></div><div>What could be the reason for CPU SPIKES. How to avoid this ?<br>
</div><div><br></div><div><br></div><div>Regds.<br></div><div><div><br><br><div><div><div> <br><div><div><div><div><br></div></div></div></div></div></div></div></div></div></div>