I noticed a problem when reviewing the trace for this issue: http://track.sipfoundry.org/browse/XECS-2441
(the reported problem is not a proxy issue - ignore that part). The problem I see is that the AA sends a REFER and is (correctly) challenged, provides its identity, and then the transferee correctly provides that identity in an X-sipX-Authidentity header in the resulting INVITE, but the proxy challenges the INVITE anyway. There is no logging I can see to see why it's doing that (which is a problem in itself - at INFO level there should be). I'm guessing that the proxy is seeing that the From header matches a sipXecs identity and is challenging to construct a PAI header, but it shouldn't - it should just accept the X-sipX-Authidentity. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
