[Home]

Summary:ASTERISK-06600: Unnecessary Unlink and Link Events generated and send when digit pressed on phone
Reporter:Gerhard Venter (gventer)Labels:
Date Opened:2006-03-22 15:37:10.000-0600Date Closed:2006-04-11 15:27:55
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Core/ManagerInterface
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:With any active call (with 2 channels involved, SIP or ZAP) whenever you press a digit on the phone Asterisk will send a Unlink followed by a Linked event. This following example generates 4 Unlink and 4 Linked events when you park a call (ASTERISK-694). So if you do a transfer like in our case #0XXXX, it generates 10 of them.

Now I am not sure if this is by design or why it happens but it seems to me that it is unnecessary. I think we can cut out a lot of overhead by streamlining that.

Correct me if I am wrong please.
Comments:By: Gerhard Venter (gventer) 2006-03-31 11:03:40.000-0600

What does the "Issue Monitored: srt" means in the issue history? I don't see any notes logged so I was wondering.
By: Denis Smirnov (mithraen) 2006-03-31 11:15:21.000-0600

It means that user 'srt' would get copy of all messages there by email.
By: Gerhard Venter (gventer) 2006-03-31 11:19:46.000-0600

OK thank you. :)
By: Kevin P. Fleming (kpfleming) 2006-04-11 15:27:54

This is because the call is being bridged (which generates the Link/Unlink events) and the bridge is broken each time DTMF is received so that Asterisk can determine whether a feature key sequence is being typed or not. Changing this behavior will require modifying the bridging code to not break the bridge until it is known that a feature sequence has been completely entered, which will require significant modifications. That work is already slated to be done, but may not be done in time for the 1.4 release.