You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Current »
Use this parameter to support local authentication autonomously on a per-IP trunk group basis in situations where an IP-PBX does not perform a registration and the service provider does not require/want registrations (refer to IP Trunk Group Authentication for additional feature functionality).
Command Syntax
% set addressContext <name> zone <name> sipTrunkGroup <name> signaling authentication
authPassword <authentication password for trunkgroup>
authUserPart <userPart used for authentication>
intChallengeResponse <disabled | enabled>
incInternalCredentials <disabled | enabled>
Command Parameters
Authentication Parameters
Parameter | Length/ Range | Description |
---|
authPassword | 6-32 characters | <password> – Password to create Authorization Digest or Proxy-Authorization headers for trunk group authentication. These credentials are used when replying to local authentication requests. |
authUserPart | 1-127 characters | <userpart> – Userpart to create Authorization Digest or Proxy-Authorization headers for trunk group authentication. These credentials are used when replying to local authentication requests. |
intChallengeResponse | N/A | Enable this flag on the ingress IP Trunk Group (IPTG), respective to the request, to allow the SBC to reply locally to egress IPTG authentication challenges. If this flag is disabled, the SBC will not reply to authentication challenges locally even if credentials are configured on the egress IPTG. If this flag is disabled, incInternalCredentials is not used. disabled (default)enabled
NOTE: The Unable to show "metadata-from": No such page "_space_variables" will not use IPTG credentials if a call originates from a surrogate originated peer even if intChallengeResponse is enabled on the ingress leg.
|
incInternalCredentials | N/A | Enable this flag on the ingress IP Trunk Group, respective to the request, to allow egress IPTG authentication to be internally created using the authorization information in mid-dialogue without being challenged. disabled (default)enabled
|