HP-UX C SIP Stack Programmer's Guide (Novembery 2007)

202 HP-UX C SIP Stack Programmer’s Guide

Server Authentication Implementation

RvSipCallLegRespondUnauthenticatedDigest()

Responds with a 401 or 407 message. You supply this function with the

challenge parameters. The SIP Stack will use these parameters to create an

Authentication header. This header will be placed in the response message.

ALL-LEG SERVER

AUTHENTICATION

ALLBACKS

RvSipCallLegAuthCredentialsFoundEv()

This callback notifies the application that credentials were found in the request

message. The callback supplies the application with the Authorization header

that contains these credentials. At this stage the application should use the

RvSipCallLegAuthProceed() function

This callback also indicates whether the SIP Stack is capable of verifying the

credentials that were found.Whenever the SIP Stack does not support the

credentials (for example, if the algorithm is not MD5) the application may verify

the credentials by itself or instructing the SIP Stack to continue to the next

header.

RvSipCallLegAuthCompletedEv()

Notifies the application that the server authentication process was completed,

and indicates whether or not the sender was authenticated. According to the

authentication results, the application should decide whether to accept the

request or reject it using the RvSipCallLegRespondUnauthenticatedDigest() or

RvSipCallLegRespondUnauthenticated() functions.

RANSACTION SERVER

UTHENTICATION

UNCTIONS

The server authentication functions of the Transaction layer are similar to the

functions of the Call-leg layer.

RvSipTransactionAuthBegin()

Can be used in the following states:

 RVSIP_TRANSC_STATE_SERVER_GEN_REQUEST_RCVD

 RVSIP_TRANSC_STATE_SERVER_INVITE_REQUEST_

RCVD