[SFtrack] Updated: (XECS-1919) Generalizing auth plug-ins authentication strategy
[
http://track.sipfoundry.org/browse/XECS-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joly updated XECS-1919:
------------------------------
Summary: Generalizing auth plug-ins authentication strategy (was: CLONE
-Call park Retrieve of an Outside caller does not work while using Consultative
Transfer)
Fix proposal can be found on mailing list at
http://article.gmane.org/gmane.comp.voip.sipx.devel/13896
> Generalizing auth plug-ins authentication strategy
> --------------------------------------------------
>
> Key: XECS-1919
> URL: http://track.sipfoundry.org/browse/XECS-1919
> Project: sipXecs
> Issue Type: Bug
> Components: sipXproxy
> Environment: sipxproxy 3.9.6-011404 2007-12-08T01:05:24
> albatros.pingtel.com
> sipxconfig 3.9.6-011404 2007-12-08T02:34:08 albatros.pingtel.com
> Reporter: Robert Joly
> Assignee: Robert Joly
> Priority: Critical
> Fix For: 4.0
>
>
> Precondition:
> 1. Users 123, 124 are registered with sipxchange and assigned Polycom phones.
> 2. Add a Call Park extension 959.
> 3. Call park retrieve code is set to *4.
> Steps to reproduce:
> 1. From an Outside phone dial 124@<domain name>
> 2. Answer the call on phone 124 and do Consultative transfer to the call park
> extension 959.
> 3. When the 124 gets the call park Music press transfer to complete the
> transfer.
> 4. Outside Phone gets the music (Outside Phone call is parked now.)
> 5. From the phone 123 dial *4959.
> Expected Result:
> Call should be established between Outside phone and extension 123.
> Actual Result:
> Unable to retrieve the call and the outside caller which was playing the
> music prompt goes into silence.
> The logs show the message "407 Proxy Authentication Required".
> Call Id: 675d3270-736959da-7c20346d@xxxxxxxxxxxx
> Observation:
> This issue was not observed while retrieving the Outside call which was
> parked to a call park extension using Blind Transfer.
> Attachments:
> Call_Park_Retrieve_Outsidecaller
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://track.sipfoundry.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
