logo       

Patch: Call Authentication Support: msg#00342

telephony.openh323.general

Subject: Patch: Call Authentication Support


Just to let everyone know I have checked into the
SF patch area code to include EP (per Call) Authentication
into the OpenH323 Project.

Descryption:
The Endpoint can request or require all incoming calls
to supply authentication credentials. When the call is
received a callback is made to the H323Endpoint to check
the users supplied credentials (UserName) against
a preloaded list, and if found, the password (supports Pwd Hashing)
is then set to be authenticated against. If Authentication is successful
then the call progresses as per normal but if it fails
then it is rejected quitely with a reason SecurityDenial.

Calling EP's can use the MakeAuthenticatedCall() function
to make a Authenticated calls to a secure EP with
a username and password.

It supports 3 EP policies None, Request & Require with
the default being None.

Technical: EP1 includes CryptoTokens in the H225 Alerting_UUIE message
when calling EP2. EP2 then authenticates EP1 before proceeding.
It also supports Security Hand-Shaking via the EP2 including a
corresponding CallProceeding_UUIE cryptoToken.

It natively supports 2 Methods: H235Appendix1 and MD5 Authentication
but as it uses the PFactory system externally developed authenticators
can be easily added.

Simon

------------------------------------------------------------------------
Check the FAQ before asking! - http://www.openh323.org/~openh323/fom.cgi
The OpenH323 Project mailing list, using Mailman. To unsubscribe or
change your subscription options, goto
http://www.openh323.org/mailman/listinfo/openh323
Maintained by Quicknet Technologies, Inc - http://www.quicknet.net
------------------------------------------------------------------------



<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise