> Hello, > > From the investigation of XECS-2092, it was found out that the reason > Agents were not ringing was because ACD did not handle the challenge > from sipXproxy. When ACD places a call to available agent as a B2BUA, > if the original caller (From Url) is an internal user, it gets > challenged by sipXproxy. However, currently, there is no > implementation in ACD to handle the challenge when transferring the > calls to agents. With regard to the solution, as ACD does not have > credentials for all the callers, it should relay the challenge back to
> the original caller, gets its credentials and then answer the > challenge. > I don't think that will work - the nonce in the challenge is bound to the call-id and from tag value in the ACD->Agent > call; since those values are different in the Caller->ACD call, the authentication will fail. Good catch! > The ACD has an identity already, I believe - it probably needs to be bound to the call so that the challenge is answered. Yes, ACD does have an identity. I will look into to have it bound to the call. Thanks for the suggestion! Huijun _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
