[asterisk-bugs] [Asterisk 0012023]: dont`t correctly work ast_device_state In app_queue when ring entry to the queue

[noreply at bugs.digium.com]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=12023 
====================================================================== 
Reported By:                still_nsk
Assigned To:                putnopvut
====================================================================== 
Project:                    Asterisk
Issue ID:                   12023
Category:                   Applications/app_queue
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.4.18 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             02-19-2008 02:10 CST
Last Modified:              02-22-2008 10:32 CST
====================================================================== 
Summary:                    dont`t correctly work ast_device_state In app_queue
when ring entry to the queue
Description: 
When member of queue make outgoing call(state of member don`t going to
Ringing or Busy) and ring entry to the queue, ast_parse_device_state return
“AST_DEVICE_UNKNOWN”(QueueMemberStatus=0). Queue distribute ring to 
busy member of queue and blocked him.
====================================================================== 

---------------------------------------------------------------------- 
 putnopvut - 02-22-08 10:32  
---------------------------------------------------------------------- 
I reproduced the situation. The problem here is that you have type=friend
set for all your queue members in sip.conf. Change this to type=peer and
this situation won't happen. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
02-22-08 10:32  putnopvut      Status                   assigned => resolved
02-22-08 10:32  putnopvut      Resolution               open => fixed       
02-22-08 10:32  putnopvut      Note Added: 0082780                          
======================================================================