SIP Authentication in Cluster [DRAFT]

[SIP Server Cluster Miscellaneous Features design doc]

Overview

SIP Server provides authentication of INVITE requests that are challenged by endpoints (gateways, SBC, and so on). In the Cluster environment, INVITE requests are passing to and from SIP Server through SIP Proxy.

Outbound Calls [From the SIPS DG]

For outbound calls, SIP Server receives the challenge from the switch. If authentication is configured on the outbound Trunk, SIP Server can respond to this challenge by sending a new INVITE that includes the required authorization parameters.

For example, if the following outbound INVITE:

INVITE
From: A(1001)
To: B(2002)

results in the challenge:

407 Proxy Authentication

SIP Server, if the outbound Trunk is configured for it, will resend the INVITE with additional parameters:

INVITE From: A(1001) To: B(2002); Proxy-Authorization: <Authorization Parameters>

If the parameters are correct, the new INVITE will be accepted by the switch.

Call Flow

?

Configuring SIP Authentication

Outbound Trunk DN, Annex tab, AuthClient section, options:

• username — a username to be used in the response to the Digest challenge.
• password — the password to be used in generating the response.