On Sat, 2008-09-06 at 08:37 -0400, M. Ranganathan wrote: > > > Before yesterday, the strategy was to challenge only calls that require > > some permission (which should include ITSP calls, because they are > > probably billable). As of yesterday, calls From and locally defined > > user will be challenged and get a P-Assserted-Identity header added when > > they are authenticated. > > > Thank you for correcting me. How can I verify the authenticity of the > P-Asserted-Identity header when the INVITE arrives at sipxbridge?
See the documentation for the SipXauthIdentity class. Since I have not regenerated the docs on the web site recently (have to get around to automating that soon), that means either building them locally or just looking at the C++ comments that they come from: http://sipxecs.sipfoundry.org/ViewVC/sipXecs/main/sipXtackLib/include/net/SipXauthIdentity.h?view=markup You'll need to get the shared secret from domain-config (make sure that sipXbridge declares that dependency in its process definition if it doesn't already). It would be good if you implemented the verification of this in sipXcommons - it's sure to be needed elsewhere. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
