[asterisk-bugs] [Asterisk 0006119]: [branch] Polycom SoundPoint IP ACD agent feature integration

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=6119 
====================================================================== 
Reported By:                bweschke
Assigned To:                bweschke
====================================================================== 
Project:                    Asterisk
Issue ID:                   6119
Category:                   Applications/NewFeature
Reproducibility:            N/A
Severity:                   feature
Priority:                   normal
Status:                     assigned
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!): 32847 
Disclaimer on File?:        Yes 
Request Review:              
====================================================================== 
Date Submitted:             01-03-2006 07:28 CST
Last Modified:              03-06-2008 10:02 CST
====================================================================== 
Summary:                    [branch] Polycom SoundPoint IP ACD agent feature
integration
Description: 
 This branch contains code to allow for integration with the Polycom
SoundPoint IP phones and Asterisk's agent infrastructure. You can
login/logout an agent and pause/unpause them from queue(s) via soft-buttons
on the phone. 

 Pre-requisites / assumptions / caveats:
 * Agent-IDs defined in agents.conf must NOT have an agentid that
conflicts with a SIP device ID/username. If you intermingle these, you will
more than likely get failed login attempts, but could get other really
undesirable results on your SIP channel. This happens because Asterisk
doesn't yet support multiple authentication realms in SIP and won't until
chan_sip3 is available. I will not be introducing any "workarounds" to
overcome this limitation between now and the time these features make it
into chan_sip3. To do so would compromise the security of the SIP channel
authentication in place now.
 * We are assuming that the From: header / username on the SIP device is
the extension that we're registering the Agent to be called back at. If the
username doesn't match the extension in extensions.conf that the device can
be reached at, the Agent login will work, but when it comes time to dial
that agent, the call will be going to the wrong location. 

 New sip.conf parameters that allow this to work:
 * The device must be "type=friend" in order for the device to be able to
use this functionality. This is generally a safe assumption for Polycom
phones that are directly connected to the Queue engine. 
 * agentlogin=yes in the device definition. If you do not have this, your
login attempts will always fail because the digestusername on
authentication will not match the username in the From SIP header, and
prior to this code, this was generally a no-no and a security violation
that resulted in an immediate negative SIP message. The default is "no", so
if you want this device to be able to login an agent from the phone, you
must specify this parameter and set it to "yes".
 * agentcbcontext=default in the device definition. This is the context
for which calls back to the agent will be sent. Default is "default". 
====================================================================== 

---------------------------------------------------------------------- 
 file - 03-06-08 10:02  
---------------------------------------------------------------------- 
This feature will not go into 1.4 as we do not put new features into it,
but it could be put into 1.6 at a later time. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
03-06-08 10:02  file           Note Added: 0083540                          
======================================================================