On Thu, 2009-05-28 at 15:14 -0400, Scott Lawrence wrote: > On Thu, 2009-05-28 at 15:10 -0400, keccles wrote: > > On Thu, 2009-05-28 at 15:04 -0400, Dale Worley wrote: > > > On Thu, 2009-05-28 at 15:01 -0400, Andy Spitzer wrote: > > > > Well, the idea was to be able to call the caller back by using the > > > > phone's "callback" features, which is why the from-URI was supposed to > > > > be that of the actual caller, yet the display name was changed to be > > > > the queue it came from. That way you had both pieces of information, > > > > and the phones still did the right thing with respect to calling the > > > > caller back. > > > > > > Being able to call the caller back makes sense. If we do that, an odd > > > consequence is that the ACD must be able to present credentials for the > > > sipX domain, to handle the case where the caller is in the sipX domain, > > > and the ACD then sends its INVITE with a From-URI in the sipX domain, in > > > which case it will get challenged for credentials. > > > > > ok - sounds like the best bet is to put it back to the 3.10 style > > implemented by woof! and solve the credentials problem. > > What credentials problem? When you do the callback, it's the agent > calling, not the ACD, so it will use the agents credentials. > hmmm, the credentials problem was the original problem ...
It happens when the ACD sends the b2b Invite to the Agent in the first place... the FROM header of that Invite points to the originator of the call. The proxy has credentials for that originator, so the proxy challenges the ACD. Unfortunately, the ACD currently doesn't know what to do with the challenge, so it stops doing anything (including it doesn't even respond to the original call.) -ke _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
