Woof! On Fri, 13 Feb 2009 14:12:14 -0500, Scott Lawrence <[email protected]> wrote:
> An INVITE gets challenged if and only if the AOR in the From header is > one that appears as an identity in the credentials database, not just if > the domain part matches. The purpose of this challenge is to add the > P-Asserted-Identity to the call for use by other decisions later. Thanks for clearing that up. > Woof wrote: >> 3. When the device that got the REFER sends the new INVITE, it >> includes the X-sipX-Authidentity: header, yet the system still >> challenges it for authentication. Wasn't the purpose of >> X-sipX-Authidentity: to make is such that this would not occur, and >> instead the call would be allowed as if it came from the user >> described therein? > > Yes, that is the purpose - something is wrong. DEBUG logging may be > instructive, or there may be a bug. I'll investigate furhter and open a JIRA if I find something. --Woof! _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
