Versions Compared

Old Version 1

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Noprint
Panel
borderColorgreen
bgColortransparent
borderWidth2

Back to Table of Contents

Back to All

Back to All - Address Context

Back to Address Context - Zone

Back to Zone - Sip Trunk Group

Back to Sip Trunk Group - Signaling (All)

Use this object 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

...

Caption
0Figure
1Sip Trunk Group - Signaling - Authentication
 

Image Modified

The following fields are displayed:

Caption
0Table
1Sip Trunk Group - Signaling - Authentication parameters
 
ParameterDescription
Auth User PartUserpart to create Authorization Digest or Proxy-Authorization headers for trunk group authentication. These credentials are used when replying to local authentication requests.
Auth PasswordPassword to create Authorization Digest or Proxy-Authorization headers for trunk group authentication. These credentials are used when replying to local authentication requests.
Int Challenge Response

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. The options are:

  • disabled (default) – If this flag is disabled, Inc Internal Credentials is not used.
  • enabled
Inc Internal Credentials

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. The options are:

  • disabled (default)
  • enabled 

 

Note

The SBC will not use IPTG credentials if a call originates from a surrogate originated peer even if Int Challenge Response is enabled on the ingress leg.

Note

If IPTG authentication is configured for both ingress IPTG and IP Peer, the IP Peer configuration takes precedence. If you wish to use the flags configured on IPTG, the IP Peer must not be present in the configurations. Otherwise, the IP Peer flags default to 'disabled' state and take precedence over IPTG flags.


Make the required changes and click Save at the right hand bottom of the panel to save the changes made.