[asterisk-bugs] [Asterisk 0015100]: [patch] Directed pickup : picker picks own channel instead of called party's channel

Asterisk Bug Tracker noreply at bugs.digium.com
Mon Sep 14 09:55:31 CDT 2009


The following issue has been RESOLVED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15100 
====================================================================== 
Reported By:                lmsteffan
Assigned To:                mnicholson
====================================================================== 
Project:                    Asterisk
Issue ID:                   15100
Category:                   Applications/app_directed_pickup
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     resolved
Target Version:             1.4.x Pending Blocker
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!): 194424 
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-05-13 16:09 CDT
Last Modified:              2009-09-14 09:55 CDT
====================================================================== 
Summary:                    [patch] Directed pickup : picker picks own channel
instead of called party's channel
Description: 
When trying to pickup an extension, Asterisk does not identify the correct
channel. The error messages are (picker being 53, called party 52) :

chan_sip.c: Trying to pick up 52 at default
channel.c: Can't masquerade channel 'SIP/53-0a273e48' into itself!
app_directed_pickup.c: Unable to masquerade 'SIP/53-0a273e48' into
'SIP/53-0a273e48'app_directed_pickup.c: No target channel found for 52

It appears that the function pickup_by_exten does not check that the
channel it has found is not its own. The included patch seems to correct
that behaviour.
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-14 09:55 svnbot         Status                   assigned => resolved
2009-09-14 09:55 svnbot         Resolution               open => fixed       
======================================================================




More information about the asterisk-bugs mailing list